Skip to main content

Administration: purchasing rules, storage locations, classifications and invoicing terms (Systempflege: Warenlogistik-Verwaltung, Lagerorte, Artikelklassifikation, Kontaktklassifikationen, Fakturierungsbedingungen)

1. Purpose and scope​

This chapter covers six administration modules that sit under IXOS "system maintenance" (Systempflege). None of them runs a daily transaction itself. Each one defines rules, master structures or templates that the transactional modules (ordering, POS, invoicing, reports) then apply.

  1. Goods-logistics administration (Warenlogistik-Verwaltung). This is the purchasing rule engine. It has four parts:

    • Order-quantity optimisation models (Bestellmengenoptimierung) decide how much to order.
    • Basket-determination models (Warenkorbermittlung) decide which supplier basket and send time an item goes to. These are the supplier-routing rules. They also cover late-order (evening) batching.
    • Own order queries (Eigene Bestellabfragen) are user-defined checks that move or block items while a basket is processed.
    • Settings for notifications about supplier responses, transmission errors and new offer lists, plus back-order cancellation-date tracking.
  2. Storage locations (Lagerorte). A tree of physical locations with location types (main or overstock). Sales points can be mapped to locations. The module also runs overstock management (Übervorratsverwaltung): refill lists that tell staff which reserve stock to move to the sales shelves.

  3. Item classification (Artikelklassifikation). User-defined flags, enumerations and hierarchies that group items for reports, bulk processing and selections in other modules.

  4. Contact classification (Kontaktklassifikationen). User-defined tags on contacts, scoped to a contact role and used to select customers for campaigns.

  5. Invoicing terms (Fakturierungsbedingungen). This module holds three kinds of template:

    • payment-terms models for invoices (due date, value days, tiered cash discount, direct-debit discount and SEPA pre-notification);
    • dunning-terms models (up to 3 dunning levels with fee, new due date and text);
    • billing models (Fakturamodelle), which bundle the payment method, invoicing cycle, payment and dunning terms, bank account, an expense flat fee, automatic print and e-mail options, and the print form per document type.

    The module also merges duplicate billing models after branches exchange contacts.

Several features in these modules are built for multi-pharmacy groups (Verbund: branch and partner pharmacies). Examples are group-wide exchange of classifications and models, origin markers, and duplicate merging.

Out of scope here (they belong to other chapters):

  • how baskets are actually sent, received and booked;
  • article details pages (stock data, order optimisation, assigning locations to an item);
  • contact details (Faktura page, supplier delivery parameters);
  • the Reports query builder;
  • Notes (tasks);
  • the invoice run itself;
  • print forms;
  • the picking robot (KS-System) POS settings.

2. Key concepts and terms​

German termEnglishMeaning
Warenlogistik-VerwaltungGoods-logistics administrationAdmin module that holds the purchasing rule models and the order-notification settings.
Bestellmengenoptimierung / OptimierungsmodellOrder-quantity optimisation / optimisation modelPrioritised rule that computes demand, minimum stock and order quantity for a set of items.
WarenkorbBasketPending order for one supplier and one send time. Items are collected here before transmission.
Warenkorbermittlung / ErmittlungsmodellBasket determination / determination modelPrioritised rule that decides which supplier basket an item is placed into.
Eigene BestellabfrageOwn order queryUser-defined rule that is triggered for matching items in a basket. It can do nothing, block the order, or move the item to a supplier's next basket.
BestellabfrageOrder queryA system prompt or check raised while a basket is being processed (for example "multiple order").
Nachlieferung / Nachlieferartikel / NachliefermengeBack-order / back-order item / back-order quantityQuantity owed to a customer because it was sold or promised but was not in stock. It is ordered for that customer.
LagerartikelStock itemItem ordered to replenish the pharmacy's own stock.
POS / PORStock-keeping statusesItem stock-keeping statuses. POS pharmacies trigger optimisation automatically when stock falls below minimum. POR allows capping the order quantity relative to the last order. The precise semantics are defined in the article-master chapter.
Dispozeit / BevorratungsdauerDays of cover / stocking periodNumber of days the ordered quantity must cover.
BedarfsbewertungDemand evaluationWeighting table for past 30-day sales intervals.
Gewichteter Absatz pro MonatWeighted monthly salesΣ (sales in interval i × weight i).
Bruttobedarf / BedarfsmengeGross demand / demand quantity(Weighted monthly sales / 30) × days of cover.
Bestellauslösung / MindestbestandstabelleOrder trigger / minimum-stock tableTable that maps gross demand to minimum stock.
Variabler / Fester MindestbestandVariable / fixed minimum stockThe computed minimum and the per-item manual minimum. The trigger uses the larger of the two.
Maximaler BestandMaximum stockPer-item cap on the target stock level.
SaisonfaktorSeasonal factorRatio of sales after vs. before the same date in the previous two years. It scales the demand.
Dynamische DispozeitDynamic days of coverDays of cover that shrink towards a cut-off day of the month.
Absatzabhängige DispozeitSales-dependent days of coverTable that maps weighted monthly sales to days of cover.
NeinverkaufNo-sale (lost sale)A recorded request that could not be fulfilled. It counts as demand.
BasismodellBase modelVendor-supplied fallback model. It cannot be deleted and its data are fixed.
HauptlieferantMain supplierThe pharmacy's primary wholesaler.
Direktlieferant / DirektbestellungDirect supplier / direct orderManufacturer supplying directly, and an order placed with that manufacturer.
ZwischenbestellungInterim orderOne-off order at a wholesaler to bridge a direct-supplier item.
SpätauftragLate orderThe last regular order transmission of the day to a supplier. It is delivered overnight or early morning.
TagesbedarfDaily demandExpected sales per day.
AngebotslisteOffer listA supplier's contractually binding list of offered items and conditions.
Effektiver EKEffective purchase priceNet purchase price after conditions. It is used to compare suppliers.
Apo-EK / ABDA-EKPharmacy purchase price (list)List purchase price from the drug database. It is a common item-selection criterion.
AbgabebestimmungDispensing regulationRx-only, pharmacy-only, OTC and so on. Used as a selection criterion.
AnbieterProvider/manufacturerManufacturer or marketer of the item.
Kühlartikel / Betäubungsmittel (BtM)Refrigerated item / narcoticSpecial handling classes that can be excluded from or routed by rules.
RückmeldungSupplier responseSupplier's reply to an order (availability, shortfalls).
ÜbertragungsfehlerTransmission errorFailure while sending an order.
Voraussichtliches StornodatumExpected cancellation dateDate when a supplier is expected to cancel an open back-order line.
DS / NLDispo / back-delivery item notesOrder-line notes that allow the supplier to deliver later as dispo (DS) or as back-delivery (NL).
LagerortStorage locationNode in the location tree (shelf, drawer system, fridge, robot and so on).
HauptlagerortMain locationLocation from which an item is normally sold. Several per item are allowed, all with equal rank.
ÜbervorratslagerortOverstock locationReserve location from which main locations are refilled.
ÜbervorratsartikelOverstock itemStock item that has at least one main location and at least one overstock location.
VerkaufsortSales pointWorkstation (POS till or secondary workstation) mapped to the locations it sells from.
KapazitätCapacityNumber of packs that fit at a main location.
Vermutlicher BestandPresumed stockCapacity − dispensings from that location.
ÜV-BestandOverstock stockEstimated packs still in overstock.
AuffülllisteRefill listWork list of packs to move from overstock to main locations.
GesamtlisteTotal listVendor-predefined refill list that covers all overstock items.
Nicht zuordenbare Abgaben (NzA)Non-assignable dispensingsSales that cannot be attributed to a specific main location.
Kommissioniersystem / KommissionierautomatPicking system / robotAutomated dispensing robot.
AuslagernOutput/retrieveRobot ejects packs to an output chute (Schacht).
ArtikelklassifikationItem classificationA user-defined classification scheme.
ArtikelklasseItem classA value or level of a classification to which items are assigned.
ArtikelkennzeichenItem flagYes/no property. It is both a classification and a class.
ArtikelaufzählungItem enumerationFlat list of mutually exclusive values of one property.
Artikelhierarchie / HierarchiestufeItem hierarchy / levelTree of classes, for example product groups.
ArtikeltrefferlisteItem hit listSearch result list in article management.
Kontaktklassifikation / KlassifikationsartContact classification / kindTag on contacts. Its kind is the contact role it applies to.
Verbund / Filial- und PartnerapothekenPharmacy group / branch and partner pharmaciesMulti-site group whose data can be exchanged.
Austausch / HerkunftExchange / originGroup-wide sharing flag, and the abbreviation of the originating pharmacy.
Dublette / mischenDuplicate / mergeRecords that are near-identical across branches, and consolidating them into one.
FakturierungsbedingungenInvoicing termsAdmin module for payment terms, dunning terms and billing models.
ZahlungsbedingungsmodellPayment-terms modelDue date, value days, cash discounts and debit discount.
Mahnungsbedingungsmodell / MahnstufeDunning-terms model / dunning levelUp to 3 levels, each with title, fee, due days and text.
FakturamodellBilling modelTemplate of billing settings assigned to customers, homes, home units, or implicitly to all walk-ins.
LaufkundeWalk-in customerAnonymous or non-registered customer.
Heim / Heimeinheit / HeimbewohnerNursing home / home unit / residentInstitutional customers with their own structure.
ZahlungszielPayment due periodDays until payment is due.
ValutatageValue daysDays added before the due period starts counting.
Skonto / SkontofristCash discount / discount periodPercentage discount for early payment within N days.
LastschriftabzugDirect-debit discountPercentage deducted when paying by direct debit.
Pre-NotificationSEPA pre-notificationAdvance notice of the debit date to the payer.
Rechnungslegung / TurnusInvoicing mode / cycleAutomatic with a cycle, or manual.
SofortrechnungImmediate invoiceAn invoice is created per sale.
Aufwands-PauschaleExpense flat feeFixed handling charge added as an invoice line.
Lieferschein / NachlieferscheinDelivery note / back-delivery noteThe second lists back-delivered and still-outstanding lines.
Sammelschein LS/RECollective slip for delivery notes / invoicesSummary document.
Quittung / EinzelaufstellungReceipt / itemised statementUsed mainly for home and care-service residents.
Lohnblistern / externe VerblisterungContract blisteringGoods delivered separately by a blister centre.
Notes / AufgabeNotes / taskIXOS task and reminder module, with recurring task series.
InfocenterInfocenterIXOS message centre.
MMRManagement ReportLicensed business-analytics report of the vendor.
MSV3MSV3German standard protocol for ordering from wholesalers.

3. Data model​

3.1 Purchasing rule entities​

OrderQuantityOptimisationModel (Bestellmengenoptimierungsmodell)

  • id, name, status (active / inactive; shown on separate tabs), priority (list position; a higher position wins). Created/changed timestamps and users.
  • isBaseModel. The base model is always lowest priority, cannot be moved or deleted, its data are fixed, and only its dynamic days of cover can be set.
  • itemSelection: reference to a Reports item query, which is dynamic. The predefined query "All items" carries a marker icon.
  • demandEvaluation: ordered list of 30-day intervals, each with a weight %. It can be loaded from predefined weighting tables.
  • orderTriggerTable: ≥2 rows of (grossDemand decimal(·,1), minimumStock). The demand values must be distinct. It can be loaded from predefined use-case tables, which are specified for 30 days of cover.
  • linearSmoothing: boolean. When on, the minimum stock is interpolated between rows.
  • daysOfCover (int). This is disabled when a sales-dependent table is used.
  • dynamicDaysOfCover: {enabled, minimumDays, cutoffDayOfMonth}.
  • salesDependentDaysOfCover: ≥2 rows of (weightedMonthlySales, daysOfCover).
  • seasonalFactor: {enabled, maxFactorPct ≥100 or empty, minFactorPct ≤100 or empty}.
  • porMaxSurchargeOnLastOrderPct.
  • groupUse (Verbundweite Nutzung): exchanged flag, and the list of pharmacies using it.
  • Limit: 99 models.

BasketDeterminationModel (Warenkorbermittlungsmodell)

  • id, name (auto-generated from the selection criteria), description, priority 1–8 (unique; the base model is fixed at 9), status active/inactive, isStandard, isBaseModel. Limit: 8 own models.

  • itemSelection: either a Reports item query (standard criteria: list purchase price, storage location, dispensing regulation, provider; more criteria need a licence) or an offer list (one linked supplier offer list). The standard model's item selection cannot be edited.

  • itemRestriction: {allItems, refrigerated, narcotics, otherItems} booleans.

  • backOrderRules[] (ordered; evaluated top-down). Each rule has:

    • customerSelection (Reports customer query or explicit customer list; default all customers including walk-ins);
    • ruleType ∈ {nextCall, nextDelivery, mainSupplierNextCall, mainSupplierNextDelivery, optimalSupplier, cheapestSupplier, specificSupplier, provider};
    • supplier (when specific);
    • onlineAvailabilityCheck, applyLateOrderSettings and respectFixedItemSupplier (booleans);
    • basketGrouping ∈ {oneBasketForSelection, onePerCustomer}.
    • The base rule "All items" cannot be deleted.
  • stockItemRule: ruleType, supplier, onlineAvailabilityCheck. Late-order settings and the fixed item supplier always apply.

  • alsoForDirectOnlyItems: boolean.

  • lateOrder. Either mode orderInLateOrder with these criteria:

    • whileStockAboveDailyDemand {considerFixedMinStock};
    • onEarlierOrderNeeded {alsoMoveExistingLateOrderPositions | onlyCoverDailyDemand};
    • lastSaleMoreThanDays N;
    • alwaysAfterTime HH:MM.

    Or mode neverLateOrder, or mode treatAllOrdersEqually.

OwnOrderQuery (Eigene Bestellabfrage)

  • priority (rank order), name, description, active flag (default active), itemSelection (Reports item query).
  • action ∈ {none (stay in determined basket; default), doNotOrder, nextBasketOfSupplier}, plus supplier (required for the third action).
  • Created date, last edit, editor. Limit: 10.

GoodsLogisticsSettings (one per pharmacy)

  • responseNotification: {none | createTask, priority (high/normal/low), assignee, deputy, acousticSignal if high}.
  • transmissionErrorNotification: {infocenterMessage | createTask, priority, assignee, deputy}.
  • offerListNotification: {createTask (default) | none, priority (default normal), assignee (default "Apotheke" = everyone, or individual users), deputy}.
  • stockStatusNegativeTask: {notification, priority, assignee, deputy, schedule (when and how often)}.
  • cancellationPeriods[]: per supplier, {supplier, period value + unit (days/weeks/months), extension period, item-note flags DS/NL}.
  • cancellationHintLeadDays (int).
  • cancellationDateTask: {notification, priority, assignee, deputy, schedule}.

Related entities owned by other modules but referenced here:

  • Supplier: order times, main order time, delivery times, late-order flag per send time, "allow interim order at wholesaler", conditions, offer lists.
  • Item: fixed supplier, fixed minimum stock, maximum stock, stock status.
  • Basket: supplier, send time.
  • Back-order line.

3.2 Storage entities​

StorageLocation (Lagerort)

  • id, parentId (tree of any depth), name, icon, type ∈ {main, overstock}.
  • isVendorPredefined. Name and icon are then fixed, deletion is not allowed, but the type can be changed.
  • salesPoints[]: workstations that sell from this location.
  • Vendor-predefined top-level locations: Lager, Hauptalphabet, Kommissioniersystem, "Kommissioniersystem und weitere Lagerorte", Kühlraum, Kühlschrank, BtM-Schrank, Freiwahl, Sichtwahl, Rezeptur.

ItemLocationAssignment (maintained in article management; used here)

  • itemId, locationId, role (main | overstock; prefilled from the location type).
  • capacity (packs; main only).
  • presumedStock (computed; can be corrected manually).
  • refillFromDispensedPacks (per-item, per-location threshold).
  • Dispensing counters per location: new / printed / sum / total.

RefillList (Auffüllliste)

  • id, name, isTotalList (vendor-predefined).
  • itemSelection: report query (dynamic) or single items (static). Only overstock items are considered; the default is all overstock items.
  • mainLocationFilter[]. Selecting a parent location does not include its children.
  • thresholdPacks + thresholdBasis ∈ {none (use item-level threshold), acrossAllLocations, atEachLocation, atLeastOneLocation}. The two fields must be set together.
  • assignee, deputy, notesTask (recurring series; default every working day 09:00–15:00), note (printed on the list), refillPeriod (derived from the task series, else "refill on demand").
  • status ∈ {new, printed, newWithPrintExisting}.
  • View filter: refillable only / all. Saved default print options.

RefillListLine (per item)

  • dispensedTotal (all main locations including non-assignable, over new and printed lists), overstockStock (estimated), toRefillTotal.
  • Per location: capacity, toRefill, refilled (system-proposed, user-overridable), reason ∈ {completelyRefilled, notCompletelyRefilled} (required when refilled < toRefill).
  • nonAssignableDispensings.

3.3 Classification entities​

ItemClassification (Artikelklassifikation)

  • id, kind ∈ {flag, enumeration, hierarchy}, name, description.
  • exchangeInGroup (yes/no; for hierarchies it is set on the top level), origin (pharmacy abbreviation, or "PT" for vendor).
  • protectedByRight (optional user right needed to edit).
  • Vendor-fixed classifications: "MMR-Ausschluss-PZN" and "ESL-Etikett". They cannot be deleted or exchanged.
  • Sort order is user-movable.

ItemClass (Artikelklasse)

  • id, classificationId, parentClassId (hierarchy only), name, description, sortOrder, assignedItemCount, lastAssignmentChange.
  • A flag has exactly one implicit class (itself).
  • An enumeration must have at least one value (class).

ItemClassAssignment: itemId, classId. For an enumeration an item normally takes one value (the help describes it as "one of several values").

ContactClassification (Kontaktklassifikation)

  • id, name, description.
  • kind = one contact role (customer, supplier, field representative and so on). It cannot be changed after creation.
  • exchangeInGroup. The default is no. Once set to yes and saved it is irreversible. It is not allowed for the built-in "Außendienst" and "Lieferant" classifications.
  • origin, contactCount, created/changed by and at.

ContactClassificationAssignment: contactId, classificationId.

HitListClassificationColumns: 5 slots, each {classificationId, columnHeader ≤10 chars}.

3.4 Invoicing-terms entities​

InvoicePaymentTermsModel (Zahlungsbedingungsmodell – Rechnung)

  • id, name, isStandard (exactly one), infoText, isVendorBase (read-only).
  • Bank-transfer fields: valueDays, dueDays, alternativeText (replaces the due/discount text on the invoice), discountTiers[≤3] {days, percent}.
  • Direct-debit fields: debitDiscountPct, debitAfterDays (pre-notification), additionalTextAbove, debitInfoFormat (short | long; the default is long), printSufficientFundsSentence (default on), anonymiseCustomerIban (default on).
  • discountAppliesTo: item categories and prescription types.
  • Validation: dueDays or debitDiscount must be given, and the longest discount period must be ≤ dueDays.

DunningTermsModel (Mahnungsbedingungsmodell)

  • id, name, isStandard, infoText, isVendorBase.
  • levels[1..3], each {printTitle, fee (EUR), dueDays, text}. Title, fee and due days are mandatory before the next level can be added.

BillingModel (Fakturamodell)

  • id, name, description, isStandardForCustomers, isStandardForWalkIns, linkCount (homes + home units + customers; walk-ins are not counted).
  • Payment info:
    • paymentMethod ∈ {transfer, directDebit};
    • invoicingMode ∈ {automatic(cycle ∈ immediate, daily, weekly, semi-monthly, monthly, quarterly), manual, none};
    • paymentTermsModelId, dunningTermsModelId, alternativePharmacyBankAccountId;
    • expenseFee {label, grossAmount}.
  • Print options: numberOfDeliveryNotes, numberOfBackDeliveryNotes, numberOfInvoices, labelPrintingWithDeliveryNote, autoPrintDeliveryNotes ∈ {off, always, alwaysExceptSeparatelyDeliveredOnly}, printZeroDeliveryNotesOnInvoice, printZeroReceipts, createZeroInvoices, printOrSendZeroInvoices, autoPrintOrSendInvoices, autoCreateInvoicePdf, autoPrintOrSendDunning.
  • Forms (each with an optional second setting): deliveryNote (+ include outstanding back-orders, show prices/totals), invoice (+ line sort order), dunning, collectiveSlipDN (+ sort), collectiveSlipInvoice, labels (label / customer / home / clinic), receipt and itemised statement (+ sort).
  • Group exchange is possible except for the standard model.
  • Assigned to: customer, nursing home, home unit, resident (inherits from the home), and implicitly to walk-ins.

4. Features​

4.1 Goods-logistics administration (Warenlogistik-Verwaltung): module shell [GENERIC]​

  • Purpose: one admin place for the purchasing rules. It holds the quantity optimisation models, the basket determination models, the own order queries and the notification/back-order settings.
  • Where: system maintenance menu. It opens on the quantity-optimisation page.
  • Access:
    • Without permission, the whole module opens read-only (view mode).
    • Editing each rule area needs its own permission (section 8).
    • The Settings page is not limited to any permission profile.
    • The pharmacy's workstation/user protection concept also applies.

4.2 Order-quantity optimisation models (Bestellmengenoptimierung) [GENERIC]​

  • Purpose: compute how many packs to order per item from its sales history, days of cover, minimum-stock tables, seasonality and caps.
  • Trigger:
    • The model is chosen per item while an order is being built.
    • In POS-mode pharmacies, optimisation runs automatically in the background as soon as an item falls below minimum stock.
    • Configuration parameters named "Optimierung" can enable optimisation in further goods-management processes.
    • Manual processes that pass their own days of cover (re-optimisation, order proposals, evaluations) can also trigger orders.
  • Model choice: models are ranked by priority, and the first active model whose item selection contains the item is used. The base model catches everything else.
  • Active/inactive:
    • Models live on an Active tab and an Inactive tab.
    • A newly activated model is inserted directly above the base model. The user then moves it with the priority buttons; a higher position means higher priority. The base model cannot be moved.
  • Inputs per model: see 3.1. The standard selection criteria are the pharmacy list purchase price, the dispensing regulation, the storage location and the provider. More criteria need a licence. Selection is made through a Reports query, for example a predefined query "list purchase price > €100".
  • Create:
    • Click New in the current tab. The model is created in that tab.
    • Basic settings tab:
      • name;
      • group options;
      • item selection;
      • demand-evaluation table: intervals × weight %, typed in or loaded from predefined weighting tables with descriptions;
      • order-trigger table: gross demand → minimum stock, at least 2 pairs with distinct demand values, typed in or loaded from use-case tables;
      • linear-smoothing checkbox;
      • days of cover. Loading a table presets 30 days, because table values are defined for 30 days of cover. If the days are changed, a refresh button rescales the demand values to the new days of cover.
    • Advanced settings tab:
      • dynamic days of cover to month end;
      • sales-dependent days of cover table (≥2 pairs). Using it locks the basic days-of-cover field, because rescaling the demand table would be ambiguous.
      • seasonal factor with max/min caps;
      • POR maximum surcharge % over the last ordered quantity.
    • Save (stays open) or Apply (saves and closes).
  • Change: changes take effect immediately on save. The help advises checking the effect.
  • Copy: opens the copy in edit mode. A copy of a group-exchanged model keeps the "group-wide use" setting but loses its link to the original.
  • Delete: only inactive models can be deleted, after confirmation.
  • Group exchange (Verbund):
    • Area "group-wide use".
    • Exchanged models first appear on the Inactive tab in each participating pharmacy.
    • Any participant may edit them.
    • Icons show "exchanged and used in at least one pharmacy" (the tooltip lists which pharmacies) or "exchanged but inactive everywhere".
    • Deletion is allowed only if the model is used nowhere.
  • Base model:
    • Vendor-preconfigured and optimises all items.
    • Its values cannot be changed, except that dynamic days of cover may be enabled.
    • Copy it to start your own models.
  • Limits: up to 99 models.
  • Transparency:
    • Each optimisation step is logged in article management's "stock and order control" (Bestands- und Bestellkontrolle).
    • The seasonal factor can be displayed from item details within a basket (stock control).
  • Algorithm: section 6.1.

4.3 Special cases in quantity optimisation [GENERIC]​

  • Days of cover shortened by a pending direct order:
    • If a direct order with a manufacturer has an announced delivery date inside the computed days of cover, the days of cover are cut so the order only bridges until that delivery.
    • If the announced date has already passed, the system orders for 1 day only, because the delivery is expected any day.
  • Interim wholesaler order for direct-supplier items (Zwischenbestellung):
    • Items normally ordered only from a direct supplier can be ordered once from a wholesaler to cover today's need. Eligible items are POS items and items in a specific wholesaler's "WaWiExtra" programme.
    • All of these conditions must hold:
      • stock < (variable or fixed) minimum stock;
      • no wholesaler order already exists for the item;
      • at least one wholesaler has delivery or order times stored.
    • Target: the wholesaler with the next delivery. If no delivery times are stored anywhere, the wholesaler with the next order time.
    • Quantities already in the direct supplier's basket are not touched.
    • Because the item now sits in two baskets, the system's "multiple order" query appears. The default option "leave item in current basket" must be kept for the wholesaler order to go out.
    • This is enabled per direct supplier with "allow interim order at wholesaler" (default off).
  • Variable minimum stock when the days of cover differ from the model:
    • When the governing days of cover differ from the model's demand-dependent days of cover, the given days are used only for the demand quantity.
    • The variable minimum stock is always computed from the model's demand-dependent days of cover.
    • The governing days can differ because of: an order proposal with its own days (default 90), a shortening due to a direct order, or dynamic month-end days of cover.
    • This prevents over-ordering when the days are long and under-ordering when they are short.

4.4 Basket-determination models (Warenkorbermittlung): supplier routing [GENERIC]​

  • Purpose: decide automatically which supplier basket (and therefore which supplier and which send time) a back-order item or stock item goes into. The rules can depend on:
    • item group: list price, Rx status, location, provider, an offer list;
    • special classes: refrigerated or narcotic;
    • the customer the back-order is for: walk-in vs. nursing-home resident vs. physician;
    • time and urgency, using late-order batching.
  • Trigger:
    • The model is evaluated per item during ordering.
    • In POS-mode pharmacies it runs automatically in the background when an item falls below minimum stock.
    • It applies to both POS and POR items.
  • Model choice:
    • Priorities run 1–8, and each value can be used once. A lower-priority model is used only if no higher one applies to the item.
    • One model can be flagged Standard. It covers every item and customer not caught by a higher-priority model. Its item selection cannot be edited, only its settings and late-order options.
    • The vendor's unchangeable base model at priority 9 guarantees that a basket is always found.
  • Typical uses named in the help:
    • Expensive items always go to the main supplier, to secure the required minimum turnover.
    • Certain items always use a given supplier's offer list for the effective purchase price.
    • Rx items go to the main supplier, because offers save little on them and this secures turnover.
    • Refrigerated items and narcotics go to one supplier. Reasons: cooling and narcotics fees, and not having to store a fixed supplier on every narcotic.
    • Residents of nursing homes get separate baskets.
    • Stock items are batched into the evening late order.
  • Wizard (3 pages):
    1. Basic data:
      • description (the name is auto-built from the selection criteria);
      • priority;
      • Standard flag;
      • item selection: a Reports query, or an offer list. With an offer list, its items are always ordered from the supplier who granted it; set that supplier on page 2 as "specific supplier". This works around effective-price comparisons ignoring negotiated offer-list items that have no stored price.
      • item restriction checkboxes: all / refrigerated / narcotics / other.
    2. Settings:
      • Back-orders table:
        • Rows are evaluated top-down for items in the model's selection.
        • Each row holds: customer selection, supplier rule, supplier (if specific), Online, Late, Fixed supplier, and basket grouping (one basket for the whole selection, or one per customer).
        • The base row "all customers / all items" cannot be deleted but can be edited.
        • Rows can be inserted, deleted and reordered.
      • Stock items row: rule, supplier and Online. Late-order and fixed-supplier settings always apply here.
      • Checkbox "also for direct-only items": apply these rules even to items normally available only from the direct supplier, for example when wholesalers hold depot contracts. Otherwise those items go only into the direct supplier's baskets.
    3. Late order: see 4.5. Then Finish.
  • Supplier rule options:
    • next call: the supplier's next order time;
    • next delivery: the supplier's next delivery time;
    • next call of the main supplier;
    • next delivery of the main supplier;
    • optimal supplier: best under the conditions explicitly selected for supplier optimisation;
    • cheapest supplier: absolutely cheapest under all stored conditions, even those not selected for optimisation;
    • specific supplier;
    • provider (Anbieter). This one is listed but not explained.
  • Column semantics:
    • Online: also run an online availability inquiry when ordering, and prefer a supplier that can deliver.
    • Late: apply the late-order page to back-orders as well. Without it, the late-order rules affect stock items only.
    • Fixed supplier: a fixed supplier stored on the item overrides the row's rule.
  • Change: takes effect immediately on save.
  • Delete: with confirmation. The base model cannot be deleted.
  • Limit: 8 models.

4.5 Late-order batching (Spätauftrag) [GENERIC]​

  • Purpose:
    • Move non-urgent replenishment into the last regular transmission of the day. Which send time counts as the late order is flagged per supplier in the delivery parameters.
    • Goods then arrive overnight or early morning instead of during peak hours or the thinly staffed afternoon.
  • Options (one of three modes):
    1. Order in late order when any enabled criterion holds:
      • While stock > daily demand. The item waits in the late order while the remaining stock covers today's demand.
        • If a later sale breaks that, the system automatically moves the whole quantity out of the late-order position into the next order of the same supplier (per the stock-item basket rule).
        • Items with very low daily demand (<1 pack/day) are still ordered as soon as possible. To keep them in the late order, raise the "last sale > N days" setting.
        • Consider fixed minimum stock: if stock falls below the item's fixed minimum, order earlier (and move it out of the late order) even if daily demand is covered.
        • When an earlier order is needed: either also move any existing late-order positions forward, or only order enough to cover the daily demand.
      • Last sale more than N days ago. The item goes into the late order even if stock no longer covers the daily demand, and it is never moved out automatically. The reasoning: an item that sells only every 10 days is unlikely to be asked for again today.
      • Always after HH:MM. From that time on, stock items always go into the late order, with no later move. The reasoning: at 14:00 a 17:30 delivery is little better than next morning.
    2. Never order in late order (for the model's items and, if Late is ticked, back-orders).
    3. Treat all orders equally: the late order is not special, and any item can go into any basket.
  • Recommendation in the help: exclude narcotics and refrigerated items from the late order, because most suppliers do not deliver them overnight.

4.6 Customer selection for back-order routing [GENERIC]​

  • Purpose: route back-orders differently per customer group.
    • Time-critical walk-in customers can go to the next basket.
    • Non-critical nursing-home residents or physicians can go to the optimal supplier via the late order, or to a specific or pseudo supplier.
  • Modes:
    • Report query: predefined and own customer queries. For example, "all active home residents" with the variable Home set to one home, saved under a new name. New queries are possible, for example for physicians.
    • Single customers: chosen via contact search.
  • Worked pattern "pseudo-supplier per nursing home":
    1. Create a model with item selection "All items" and a back-order row whose customer selection is that home's residents and whose rule is "specific supplier".
    2. Create a new supplier contact "Heimlieferant" with a delivery time (for example 19:00) on every weekday. A basket is then created daily at that time. Tick "also for direct-only items".
    3. As prescriptions and orders for the residents are entered, that basket fills.
    4. Staff move its lines to the real supplier with supplier change (Lieferantenwechsel) and send that basket with their own order identifier, for example "Heim". With MSV3, use the option to send with an own order identifier.
    5. The wholesaler packs the delivery in a separate tote labelled with that identifier, which simplifies handing the goods over to the home.

4.7 Own order queries (Eigene Bestellabfragen) [GENERIC]​

  • Purpose:
    • User-defined rules shown or applied when an item in a basket matches a report query.
    • They supplement the system's automatic order queries. The intended use is especially orders to branch or partner pharmacies.
    • An own query takes precedence over an automatic system query when both match.
  • Fields: priority (rank buttons), name, description, active flag (new = active), item selection (Reports query; standard criteria list purchase price, location, dispensing regulation, provider; more with licence), default action, supplier.
  • Actions:
    • none: the item stays in the determined basket. This is the default.
    • do not order: the item is not ordered. If stock exists, the item is flagged as a discontinued item (Auslaufartikel). If there is no stock, the item is removed from stock-keeping.
    • next basket of supplier X: the item is moved to that supplier's next open basket, and a basket is created if none exists. The supplier is mandatory.
  • Detail view: report query, action, created date, last edit, editor.
  • Limit: 10.

4.8 Order notifications and back-order management settings [GENERIC]​

  • Supplier responses needing action:
    • Default: no notification. Option: create a Notes task with priority high, normal or low. High allows an acoustic signal. Set an assignee and a deputy.
    • In "today's tasks" the icons distinguish: unprocessed responses, transmission error, item not deliverable.
    • "Execute" jumps to the goods-logistics response window. "Close response" there acknowledges it.
    • The task must then be set done in Notes. This has no effect on goods logistics.
  • Transmission errors:
    • Choose between an Infocenter message and a Notes task (same options).
    • After a passive send fails, the task is generated automatically. Its subject and text depend on the error type.
  • New offer lists:
    • Notify about new contractually binding supplier offer lists. Default: create a task with priority normal, assignee "Apotheke" (all users) or chosen employees, and a deputy.
    • The task shows the list and the linked supplier(s). Priority and condition agreements are maintained in "manage offer lists" and in the supplier contact.
    • If the new list cannot be linked automatically, a task is still created so it can be linked by hand.
  • Back-order management:
    • Stock-status change task: when an item with open back-order lines changes stock status to "negative", create a Notes task. Settings: priority, assignee, deputy, and when and how often.
    • Expected cancellation date:
      • Per supplier, define a cancellation period (number + days/weeks/months) and an extension period, and tick the item notes DS and/or NL the rule applies to. Mandatory fields are validated on save.
      • The system calculates an expected cancellation date for open back-order lines. The exact formula is not given.
    • Hint lead time: show an icon in back-order management N days before the expected cancellation date.
    • Cancellation-date task: a Notes task with priority, assignee, deputy and schedule.
    • All three cancellation features apply only to suppliers configured in the table.

4.9 Storage location tree (Lagerortverwaltung) [GENERIC]​

  • Purpose:
    • Model every physical location as a tree, so item hit lists show where each item sits.
    • Typed locations and sales-point mapping also drive overstock management.
  • Predefined locations: see 3.2. Vendor locations cannot be renamed, re-iconed or deleted, but their type (main/overstock) can be changed.
  • Create:
    • "New main store" creates a top-level location: name, type (main or overstock) and icon (a default is offered and can be changed).
    • "New" under a selected node creates a sub-location with name, type and icon.
    • Each own location can have its own icon. Hit lists show the icon of the specific sub-location.
  • Item assignment:
    • Done in the item data or by bulk report-result processing (other chapters).
    • A location's type prefills the role (main/overstock) when it is assigned to an item.
    • An item's overstock location is defined by assigning a location with role overstock.
  • Sales-point mapping:
    • Activate the workstations that sell from a location.
    • It is needed only when an item has several main locations and per-location refill quantities are wanted. The picking system is an exception.
    • The mapping must be unambiguous. Overlapping sales points across one item's main locations make per-location refill impossible, and those sales become "non-assignable dispensings".
  • Edit: rename and re-icon own locations. Drag and drop to restructure, including promoting a sub-location to top level. Item assignments are preserved.
  • Sorting rule after reload:
    • Own top-level locations first, alphabetically, then the vendor top-level locations.
    • From level 2 down, own and vendor locations are mixed alphabetically.
    • A newly created or moved node shows where it was placed until the tree is reloaded.
  • Delete own location: cascades to all sub-locations and all item assignments, after a warning.

4.10 Overstock management and refill lists (Übervorratsverwaltung / Auffülllisten) [GENERIC]​

  • Purpose:
    • Items with high (often seasonal) turnover, or items bought in bulk, are kept partly in reserve (overstock locations) and partly on sales shelves (main locations).
    • The system counts dispensings per main location and produces refill lists telling staff how many packs to bring from reserve to each shelf.
    • Optional per-location capacities let it estimate presumed shelf stock and the remaining reserve.
  • Activation:
    • The workstation-scope article-management parameter Application area (Anwendungsbereich) sets which sales count: none (default, so the feature is off), front counter (Offizin), back office, or both.
    • Back office can be excluded because some pharmacies pick invoice/delivery orders straight from overstock, so counting them would be wrong.
    • Activate only after main and overstock locations are assigned to all relevant items.
  • List types:
    • total list: vendor-predefined, all overstock items. Suited to one-pass refilling, or to the remainder after targeted lists.
    • location-related: main-location filter, for example the self-selection area. It can also be used to refill a picking robot.
    • item-related: item selection, for example sun-care items, so promotion items stay stocked on shelves.
    • An item appears only if it is an overstock item and passes the list's threshold.
  • Create/copy:
    • New or Copy (copies all settings).
    • name;
    • item selection:
      • report query: dynamic, membership changes as the data change. Queries can be created or edited in Reports, and saving under a new name creates a new query.
      • single items: static, kept even if the query results later change. Items come from item search or are taken from a report.
    • main-location filter: each location must be ticked explicitly, because a parent does not include its children;
    • threshold "refill from N dispensed packs" + basis:
      • none: use the per-item, per-location threshold from article management. If none is set there, the item appears from the 1st pack.
      • across all locations: total dispensed ≥ N.
      • at each location: every assigned location has ≥ N.
      • at least one location: some location has ≥ N.
      • List thresholds override item thresholds. A higher threshold is useful when time is short.
    • assignee, deputy, note (printed on the list);
    • recurring Notes task (default series every working day 09:00–15:00, changeable via series type);
    • Save.
  • List view:
    • Filter "only refillable items" (items that have overstock stock) vs. "all items". Search by name or PZN.
    • Per item: dosage form, unit, standard pack size, PZN, provider, dispensed total, overstock stock, to-refill total.
    • Per location: capacity, to refill, refilled, reason. Locations not in this list are shown greyed.
    • Only the items shown are printed.
  • Statuses and life-cycle:
    • new: accumulates dispensings continuously.
    • Print: freezes the list as printed, and a sibling list "new, printout exists" starts accumulating later sales. That sibling also shows whether the printout is stale.
    • Complete item(s): on a printed list, multi-select. The proposed "refilled" values and any non-assignable dispensings count as done, and the items leave the list. Anything dispensed but not refilled goes to the new list.
    • Edit item: one item, also possible on a new list. Override "refilled" per location before completing. If refilled < to refill, a reason is mandatory:
      • completely refilled: the shelf is full. The outstanding quantity is removed from all new and printed lists, and the excess dispensings are re-booked as non-assignable in the new total list.
      • not completely refilled: the missing quantity is carried into the new list for that location.
      • A warning icon marks a missing reason, or refilled > to refill. Amounts beyond the location's dispensings plus non-assignable dispensings are ignored.
    • Complete list (F10): all items count as refilled, taking into account the estimated overstock and the resulting "refilled" values. Unrefillable remainders and sales since printing move to the new list.
    • List complete (Ctrl+F10): set done regardless of overstock and dispensed quantities. Use it to reset counters, for example before introducing capacities or before reorganising the store.
    • Which statuses allow done/complete is configurable (section 7). On a "new" list, complete respects the overstock stock and list complete ignores it. Completing one of a printed/new pair leaves the other untouched.
    • Discard printed list (Alt+F10): the printed list's dispensed quantities are moved into its "new, printout exists" sibling, the printed list is deleted, and the sibling reverts to "new". Use it when the printout could not be worked.
    • Delete list: after confirmation. It also deletes the list's Notes task.
  • Manual refill outside lists:
    • From article management (item stock-data page, hit-list context menu, or the assign-locations window).
    • It covers all of the item's dispensings across all lists.
    • It is available only if at least one pack has been dispensed from a main location.
    • Partial refills can be documented.
  • Insufficient overstock: only what the reserve holds is put on the list. The system assigns those packs to a main location, and the rest carries over after print and done.
  • Sale reversal of an overstock item:
    • The item stays on the refill list and the dispensing counters are not reduced. The system cannot know whether the returned pack goes back on the shelf or is destroyed.
    • Staff correct the presumed stock by hand if it was shelved.
  • Store reorganisation:
    • Example: new location with capacity 10 that currently holds 5. Set capacity 10, then "correct stock" from 10 to 5, and the item appears with 5 to refill.
    • Finish or "complete" existing lists before reorganising.
  • Capacity roll-out procedure:
    1. Refill all shelves.
    2. "List complete" to reset the counters.
    3. Enter capacity per item and location.
    4. Correct the presumed stock where a shelf is not full, so the gap appears on the next list.
  • Notes reminder:
    • The recurring task appears in "today's tasks". "Execute" opens the storage module with the list selected: the printed one if it exists, else the new one.
    • After processing, Esc asks whether to set the task done. Yes marks it done. No reactivates the task so it reminds again.
    • The help states the task must be set done in Notes in order to open the list.
  • Picking robot as overstock location:
    • Case 1, output at time of sale: POS workstation parameter "output on scan" ON. A pack taken from the shelf is replaced from the robot immediately, so the item never appears on refill lists.
    • Case 2, output when working the list: "output on scan" OFF. Output is triggered from the refill list (all items, or a single item via context menu) or directly at the robot.
    • Case 3, robot used only for overstock, always output from the list, even with empty shelves:
      • At POS workstations: "picking robot" OFF and "output on scan" OFF.
      • At the refill workstation: "picking robot" ON and "output on scan" OFF.
    • Parameter overstock output location: 0 = the default output chute (taken from the general output-location parameter), otherwise a chute number such as 5.
    • These parameters apply only when the robot is used as overstock. A robot used as a main location is covered elsewhere.
  • Without printing: with the robot as overstock and the list output fully, the list can be set done without printing (saves paper), provided the configuration allows completing new lists.

4.11 Refill-list and label printing [GENERIC]​

  • Trigger: print from the refill-list overview (always the whole list) or from an open list. From an open list, marked entries only is possible when some but not all entries are marked.
  • Refill list print:
    • By item: per item, the total to refill and, beneath it, each main location with capacity, to refill and a pre-filled "refilled" value for handwritten correction. If to refill > overstock, the first column shows "(overstock/to-refill)".
    • By location: per location, the items and quantities.
    • Both orderings can be printed in one run.
    • Non-assignable dispensings (NzA) appear separately. A location with only non-assignable demand shows a blank quantity, and staff write in what they actually refilled.
  • Labels:
    • Type: price label, location label, unit-price label, or own activated print forms of these types.
    • Count: refill quantity (optional maximum), total stock (optional maximum), or a fixed number.
  • Default print options: "Save as default" stores the options for next time. They can still be changed temporarily.
  • Process advice:
    • Note deviations on paper, then use edit item for those.
    • Complete the remaining refilled items in one action.
    • If interrupted, discard the rest and print a fresh list later.
    • Do not stretch refilling over hours, especially with several staff or lists, because printed lists go stale.
    • Lists printed by location make partial documentation harder: edit each item, using the PZN search.

4.12 Item classification (Artikelklassifikation) [GENERIC]​

  • Purpose: group items by any viewpoint so they can be:
    • queried in Reports;
    • picked as an "item group" in other modules for joint processing;
    • shown as hit-list columns.
  • Kinds:
    • Flag: a simple property such as discontinued or offer goods. The flag itself is the class.
    • Enumeration: a list of equal-ranking values of one property. The item gets one of them.
    • Hierarchy: a tree such as product groups. Create sub-levels under the selected level, to any depth.
    • All three kinds can be evaluated in Reports.
  • Overview:
    • Tree with search (auto-expands to the hit) and move up/down.
    • The kind icon is shown on the top level only.
    • Origin suffix: "(ABC)" for another group pharmacy, "(PT)" for vendor.
    • Markers: protected (view mode), exchanged in group, vendor non-exchangeable.
    • Item count, and date of the last assignment change.
  • Create:
    • New → choose kind → name, description.
    • Enumeration: "new value" rows. Hierarchy: "new sub-level".
    • Exchange flag.
    • Assigning items and "remove all" are available only when editing, not while creating.
    • When a flag is created from an item's stock-data page, a checkbox assigns it to that item immediately.
  • Assign items:
    • From the overview or the edit window.
    • Insert via item search.
    • From report: run a Reports query and append the result, with duplicates removed.
    • From file: CSV/TXT with PZNs, either a single column or a column headed "PZN". The file must not be open. Success or error is reported. If the class already has items, choose replace or add (duplicates removed).
    • Remove one or remove all. Open item details.
    • Assignment is also possible from article management.
  • Delete:
    • Deleting a classification cascades to all sub-classes and all item assignments, after a warning.
    • Deleting a value or level asks for confirmation. Empty unnamed classes without assignments are deleted silently. Once the last value or level is gone, only "delete classification" or "add value" remain.
    • An enumeration cannot be saved without at least one value.
  • Protection:
    • A user with the right "Contacts > Staff: edit user account and assign rights" can lock a classification behind a chosen right.
    • Users without that right see it in view mode: delete and edit are disabled, and "assign items" becomes "show items".
    • A tooltip names the protecting right. Setting the right back to "none" unlocks it, which needs the same admin right.
  • Group exchange:
    • Possible if centrally enabled. Only whole classifications are exchanged, including their classes and item assignments; single classes or assignments cannot be exchanged.
    • The origin pharmacy shows no origin marker. The others show the origin abbreviation.
    • All participants may edit and delete. Self-created classifications can be deleted anywhere after extra confirmations.
    • Only the origin pharmacy can revoke the exchange, after which the classification disappears from the others.
  • Vendor-fixed classifications:
    • MMR-Ausschluss-PZN: items to exclude from the vendor's Management Report analytics.
    • ESL-Etikett: items with electronic shelf labels.
    • Neither can be deleted or exchanged. To replicate them in a group, export via Reports and import in each pharmacy.
    • The MMR exclusion always also contains:
      • items flagged "INTERN-DROGEN";
      • crude drugs;
      • chemicals;
      • product-group keys BF01/BF02;
      • services;
      • sales to partner/branch pharmacies.
  • Hit-list columns: up to 5 classifications can be configured as extra columns in the item hit list, each with a header of ≤10 characters. They are activated in article management's free list views.

4.13 Contact classification (Kontaktklassifikationen) [GENERIC]​

  • Purpose: tag contacts with interests or traits (for example "Diabetes", "Alternative medicine") to select customers for campaigns and actions.
  • Fields: name, kind (the contact role it can be assigned to; any single role; fixed after creation), description, exchange (group; default no; irreversible once saved as yes; not possible for the built-in "Außendienst"/"Lieferant"), origin.
  • Search: the search term is progressively shortened until at least one match is found.
  • Delete:
    • Shows a warning and removes the classification from all contacts.
    • An additional warning appears if it is exchanged, because it is then deleted in the other group pharmacies too.
    • No warning appears if it is unexchanged and unused.
    • It takes effect on Save.
  • Assign contacts:
    • The "assigned contacts" window: search, add via contact search, remove one, remove all (confirmed), open contact details.
    • Import: CSV/TXT of customer numbers, either a single column or a column headed "Kundennummer". The file must be closed. Choose replace or add.
    • Assignment is also possible from the Contacts module.
  • Merge duplicates:
    • Only classifications of the same kind can be merged.
    • The merge grid shows each attribute against the source pharmacies' values. The own abbreviation repeats if all sources are local.
    • Status per row: equal, optional-empty, optional-differs, mandatory-differs.
    • The selection is prefilled when the values are equal or only one exists. Otherwise pick one value, enter a new value, or clear.
    • Merge creates one new classification.
  • Display settings: for example, show created/changed by and at.

4.14 Invoice payment-terms models [GENERIC, SEPA parts DE/EU]​

  • Purpose: define how invoiced sales must be paid. One model is Standard and applies to every customer without an explicitly assigned model, which is set in the contact's billing details.
  • Fields and rules:
    • Bank transfer:
      • value days extend the due period;
      • due period in days;
      • up to 3 cash-discount tiers (days, %), where the longest tier ≤ due days. Example: 10 days 4 %, 20 days 2.25 %, 30 days 1.5 %;
      • alternative text that replaces the printed due/discount wording.
    • Direct debit:
      • debit discount %;
      • "debited in N days", printed as the SEPA pre-notification. The vendor standard model uses 14. Systems migrated with an existing model get 7 auto-filled, described as the minimum;
      • text above the payment info;
      • debit info in short form (amount, due date, creditor ID, mandate reference) or long text (the default);
      • toggle for the "please ensure sufficient funds" sentence (default on);
      • anonymise customer IBAN (default on; digits shown as X).
    • Validation: a due period or a debit discount must be given.
    • Scope of discounts:
      • Choose the item categories and prescription types that the cash discount and debit discount apply to.
      • Defaults: self-selection/visible-selection items with restricted discounting, plus private and "green" prescriptions.
      • Always included (cannot be unticked): self-selection/visible-selection without restrictions, and normal sales.
      • The same settings govern the debit discount. The discount amount appears in the details and on printed invoices.
  • Vendor base model: read-only. Copy it to change it.
  • Create, copy, delete:
    • Copying proposes the name "Kopie von <name>".
    • Multi-select delete with confirmation.
    • Search by name. The Standard model is listed first.

4.15 Dunning-terms models [GENERIC]​

  • Fields: name, Standard flag, info text.
  • Per level (1–3): print title (for example "2nd reminder"), fee in EUR, new due period in days, free text. All of these are printed on the dunning letter.
  • Rules:
    • The mandatory fields of the current level must be filled before a level can be appended.
    • Only levels 2 and 3 can be deleted, highest first.
    • The vendor base model is read-only but can be copied.
  • Assignment: like payment terms. The standard applies unless the customer has an assigned model.

4.16 Billing models (Fakturamodelle) [GENERIC]​

  • Purpose:
    • A reusable bundle of billing settings for a customer, a nursing home, a home unit, or all walk-ins.
    • Changing the model changes all linked customers at once, for example a new invoice form for a whole customer group.
  • Defaults and inheritance:
    • The model flagged standard for customers is assigned to every new customer, and to a walk-in when converted to a customer.
    • The model flagged standard for walk-ins (for example with immediate invoice) applies implicitly to all walk-ins and is not counted in the link totals.
    • Residents created in a home's structure, or assigned to a home, receive the home's billing template.
    • The standard model cannot be deleted. Deleting any other model removes it from its contacts, after a warning.
    • The vendor base model can be edited and copied, unlike the payment-terms base model.
  • Payment info:
    • payment method: transfer or direct debit;
    • invoicing:
      • automatic with a cycle (immediate, daily, weekly, semi-monthly, monthly, quarterly), which the invoice run filters on;
      • manual: excluded from automatic runs, so the contact must be invoiced explicitly;
      • none: no preset;
    • payment-terms model and dunning-terms model;
    • alternative pharmacy bank account, chosen from the company-master bank accounts. Resolution order:
      1. direct debit to the company account;
      2. alternative pharmacy account;
      3. the company master's standard account;
    • expense flat fee: a label (required for the line to print) and a gross amount (empty means a 0.00 line).
      • It is printed as an invoice line that has no underlying order or delivery-note line. It therefore does not appear in Reports and is not transferred to the Management Report.
      • It can be removed from a specific invoice in the invoice totals.
  • Print options (automatic print/delivery):
    • number of delivery notes (first = original, the rest = copies);
    • number of back-delivery notes;
    • number of invoices (first printed or e-mailed as the original, the rest printed as copies);
    • label printing with the delivery note:
      • After the order is closed and the delivery note created, the system asks for a count, then prints dosage, customer, home and clinic labels.
      • No reprint happens after later changes or after a pickup slip is resolved.
      • The printer and format come from the print-form default.
    • automatic delivery-note printing:
      • always: even for externally blister-packed deliveries, which get a "delivered separately" note;
      • always except separately-delivered-only: notes for contract-blistered goods are created but not printed, and a note prints only if pharmacy goods are included;
    • print zero-value delivery notes on the invoice;
    • print zero-value receipts (home and care customers);
    • create zero-value invoices;
    • print/send zero-value invoices. If off, the invoice gets status Intern;
    • automatically print/e-mail invoices. A preview is offered by default before printing and always before e-mailing;
    • automatically create the invoice as PDF, independent of printing:
      • path <drive>/IXOS_Dokumente/<year>/<month>/;
      • the file name contains the invoice number and date;
      • copies get the suffix "-Kopie";
    • automatically print/e-mail dunning letters.
  • Forms (per document; empty = standard form):
    • delivery note (+ whether to print all outstanding back-orders and whether to show prices and totals);
    • invoice (+ line sort order);
    • dunning letter;
    • collective slip for delivery notes (+ sort);
    • collective slip for invoices;
    • labels (customer, home, clinic);
    • receipt and itemised statement (only in home, care-service or clinic structures; + sort).
  • Overview:
    • Name, description, link count, standard-for-customers checkbox, standard-for-walk-ins checkbox.
    • Configurable columns per pharmacy, workstation or user, for example last change date and editor.
  • Group use: models of branch and partner pharmacies can be used when contact exchange and cross-branch invoicing are centrally enabled. The standard model is excluded from exchange and must be agreed once.

4.17 Billing-model duplicate merge [GENERIC multi-site]​

  • Purpose:
    • After contacts are exchanged across branches, near-identical billing models exist under different names.
    • Merging them gives a uniform customer-facing appearance and one billing process across the chain.
    • Duplicates remain fully usable until they are merged.
  • Process:
    1. "Edit duplicates" lists all models with a checkbox, name, description and link count. Mark 2–3 of them.
    2. The merge grid shows attribute rows against each model's value (columns labelled with the pharmacy abbreviation) and a selection column.
      • Status per row: equal or chosen, optional-empty, optional-differs (not auto-resolvable, or prefill cleared), mandatory-differs (not auto-resolvable).
      • The selection is prefilled when all values are equal or only one exists.
      • Otherwise pick a model's value, enter a new value, or clear the choice.
    3. Work through the pages with Next and Back, then Merge.
  • Result:
    • A new model is created, the old models' customers are re-pointed to it, and the old models are deleted.
    • The merge cannot be undone.
  • Precondition: no other workstation may be editing contacts at the time (changes, duplicate processing or deletion). Otherwise the merge is blocked.

5. Workflows​

5.1 Automatic replenishment of one item (combined purchasing rules)​

  1. A sale, or another stock movement, lowers the stock of a POS-mode item. A sale without stock creates a back-order quantity for the customer.

  2. Basket determination.

    • The system walks the basket-determination models by priority (1→8, then the base model at 9).
    • It takes the first model whose item selection and item restriction include the item.
  3. Back-order lines:

    • Rows are evaluated top-down. The first row whose customer selection contains the customer wins.
    • A fixed supplier stored on the item wins over the row's rule if "Fixed supplier" is ticked.
    • The supplier rule (next call, next delivery, main supplier, optimal, cheapest, specific) picks the supplier and send time.
    • "Online" adds an availability inquiry and prefers a supplier that can deliver.
    • "Late" applies the late-order criteria.
    • Basket grouping decides between one basket per customer and one basket for the whole selection.
  4. Stock items: the stock-item rule picks the supplier. The late-order criteria then decide between the late-order basket and the next basket.

  5. Direct-only items go to the direct supplier's basket unless "also for direct-only items" is ticked. An interim wholesaler order is the exception (4.3).

  6. Quantity optimisation.

    • The highest-priority active optimisation model whose selection contains the item computes the minimum stock and the order quantity (6.1).
    • The quantity is added to the basket line, so the back-order quantity plus the optimisation top-up is ordered.
  7. Own order queries. When the basket is processed, matching own order queries act on the item:

    • none: leave it;
    • do not order: the item becomes discontinued, or is removed from stock-keeping;
    • move to supplier X's next basket.

    They take precedence over system queries.

  8. Late-order re-booking. If a later sale makes the stock fall below the daily demand, the whole quantity of a late-order position is moved to the next order of the same supplier. Depending on the settings, only the daily demand may be ordered instead. Items placed there by the "last sale" or "after time" criteria are not moved.

  9. Notifications.

    • After transmission, supplier responses needing action and transmission errors create Notes tasks or Infocenter messages, according to the settings.
    • Open back-order lines with suppliers that have a configured cancellation period get an expected cancellation date, an advance icon, and optionally a task.

5.2 Set up a purchasing rule set (admin)​

  1. Review the base optimisation model and copy it.
  2. Create specialised optimisation models, for example for high-value items, using a report query on the list purchase price.
  3. Set weights, the trigger table, days of cover (static 14–18 days recommended, or dynamic), and seasonal caps (300 % and 33 % recommended).
  4. Order them by priority and activate them.
  5. Create basket models in priority order. Examples:
    • priority 1: refrigerated items and narcotics → a specific supplier, never in the late order;
    • priority 2: items on supplier X's offer list → X;
    • priority 3: Rx items → main supplier;
    • then the standard model for everything else.
  6. Add back-order rows per customer group, such as home residents or physicians.
  7. Configure the late-order criteria.
  8. Define own order queries, for example items not to be ordered, or items to route to a partner pharmacy's basket.
  9. Configure the notification settings and the per-supplier cancellation periods.

5.3 Nursing-home pseudo-supplier routing​

Follow the steps in 4.6:

  1. Create the model, with customer selection set to that home's residents.
  2. Route those lines to a pseudo-supplier with a daily 19:00 basket.
  3. Each day, move the basket's lines to the real supplier.
  4. Send with the order identifier "Heim".
  5. Receive the separate tote and transfer the goods to the home.

5.4 Set up overstock management​

  1. Create the overstock locations (type = overstock), for example "Keller" or the robot.
  2. Map sales points to main locations, unambiguously, where items have several main locations.
  3. In article management, assign main and overstock locations to each relevant item. Optionally add per-location capacities and refill thresholds.
  4. Check the robot parameters if a robot is used as overstock.
  5. Set "Application area" to front counter, back office or both, on each workstation where sales should count.
  6. Optionally create location-related or item-related refill lists in addition to the total list. Set the assignee, deputy, note and recurring Notes task.

5.5 Daily refill cycle​

  1. The Notes reminder appears. Execute it to open the storage module with the list selected.
  2. Print the list by item and/or by location, and print labels if needed. The list is now frozen as "printed", and a "new, printout exists" list starts collecting later sales.
  3. Staff fetch packs from overstock, refill the shelves, and note deviations on the paper.
  4. In the system:
    • For deviating items, use "edit item": enter the refilled quantity and the reason.
    • Complete the remaining items, or "complete list".
    • Remainders flow into the new list.
  5. If interrupted, discard the printed list (its quantities fold into the new list) and print again later.
  6. Return to Notes and set the task done. Answering No keeps the reminder active.

5.6 Introduce capacities​

  1. Refill everything.
  2. "List complete" to reset the counters.
  3. Enter the capacities. The presumed stock is set to the capacity.
  4. Correct the presumed stock where a shelf is not full. The gap appears on the next list.

5.7 Classify items in bulk​

  1. Create the classification: flag, enumeration with values, or hierarchy with levels.
  2. Open "assign items" on the class.
  3. Choose one source:
    • add from item search;
    • append the result of a report;
    • import a PZN CSV and choose replace or add.
  4. OK.
  5. Optionally protect it with a user right, exchange it in the group, and show it as a hit-list column.
  6. Use it in Reports or in other modules' item-group selections.

5.8 Customer campaign selection​

  1. Create a contact classification for the role "customer", for example "Diabetes".
  2. Assign contacts manually, from the Contacts module, or by importing a CSV of customer numbers.
  3. Select by classification in Reports or in the campaign modules (other chapters).

5.9 Set up invoicing terms for a customer group​

  1. Create an invoice payment-terms model, for example 30 days net, 10 days 2 % discount, 3 value days, discount on OTC and private prescriptions only.
  2. Create a dunning model with 3 levels: fee and new due days per level.
  3. Create a billing model with these settings:
    • payment method;
    • cycle (for example monthly);
    • the two terms models;
    • the alternative bank account;
    • the expense fee;
    • print and PDF options;
    • the forms.
  4. Assign the billing model to customers, homes or home units in the contact details. Alternatively flag it as standard for new customers or for walk-ins.
  5. The monthly invoice run selects all customers whose cycle is "monthly". Manual customers are skipped.
  6. Overdue invoices escalate through the dunning levels.

5.10 Harmonise after a branch merge​

  1. Ensure no workstation is editing contacts.
  2. Merge the billing-model duplicates two or three at a time, choosing each attribute.
  3. Merge the duplicate contact classifications, kind by kind.
  4. The new records replace the old ones chain-wide, and customer links are re-pointed.

6. Business rules and calculations​

6.1 Order-quantity optimisation​

  • Sales count per 30-day interval = sales + no-sales (lost sales) − cancellations.
  • Weighted monthly sales (WMS) = Σᵢ (sales count in interval i × weightᵢ). Interval 1 is the current 30 days, interval 2 the 30 days before that, and so on.
  • Days of cover (D):
    • the model's static value;
    • or the sales-dependent table lookup by WMS (for example WMS up to 999.9 → 15 days);
    • or dynamic: it shrinks daily so that the cover does not pass the cut-off day of the month, but never below the minimum. It resets on the 1st.
    • It is shortened by a pending direct delivery. If the direct delivery is overdue, D = 1 day.
  • Gross demand (GD) = (WMS / 30) × D. In the example it is rounded down to whole packs (1.4 → 1); the rounding rule is not stated in general.
  • Seasonal factor (optional):
    • For each of the previous 2 years, at the same calendar date:
      • after = w₁ × sales(date…+30) + w₂ × sales(+30…+60);
      • before = w₁ × sales(−30…date) + w₂ × sales(−60…−30);
      • factor = after / before.
      • A year is skipped if either sum < 1.
    • Average the yearly factors.
    • Clamp to [min %, max %] if set. The max must be ≥ 100 % and the min ≤ 100 %; empty means no clamp.
    • Multiply the demand by the factor.
    • Example: weights 70/30, order date 10 Oct. Year 2024 = (0.7·2 + 0.3·2)/(0.7·4 + 0.3·3) = 0.54. Year 2023 = (0.7·2 + 0.3·0)/(0.7·2 + 0.3·1) = 0.82. Mean = 0.68, so a demand of 10 packs becomes 7.
    • The minimum stock is always replenished. The seasonal factor cannot push the stock beyond the maximum stock.
  • Minimum stock from the trigger table:
    • Look up the row bracket containing GD.
    • If smoothing is on, interpolate linearly between rows. If it is off, take the next-higher row's value.
    • Example: GD 0…2 → minimum stock 1.
  • Variable minimum stock = the table value, computed with the model's own demand-dependent D even when the order uses a different D.
  • Effective minimum = max(fixed minimum stock on the item, variable minimum stock).
  • Order trigger: an automatic order happens only when stock < effective minimum. Manual processes with an explicit D can also order.
  • Order quantity:
    • Default: qty = minimum stock − current stock + back-order qty − already ordered qty.
    • Nothing is ordered if current stock − back-order qty + already ordered ≥ minimum stock.
    • If a maximum stock is set and GD > maximum stock: qty = maximum stock − current stock + back-order qty − already ordered.
    • The result is added to the existing basket line. Example: basket 3 (the back-order) + 1 = 4.
  • POR cap: the order quantity must not exceed the last ordered quantity × (1 + surcharge %).
  • Variable minimum-stock independence: for order proposals with D = 90, D is used only for the demand quantity, and the minimum stock uses the model's D (for example 15).

6.2 Basket determination precedence​

  • Models: priority 1 (highest) to 8, then the base model 9. Standard = the fallback below all specific models. Each priority value is unique.
  • Within a model:
    • back-order rows run top-down;
    • customer selection membership decides the row;
    • the item's fixed supplier overrides the row's rule when that row's option is ticked, and always for stock items.
  • Late-order settings apply to stock items always, and to back-orders only when "Late" is ticked.
  • Direct-only items stay with the direct supplier unless the model opts in.
  • Interim wholesaler order (4.3): wholesaler with the next delivery, else the next order time. Only if no wholesaler order exists and stock < minimum. Direct-basket quantities are unchanged.

6.3 Own order queries​

  • They are evaluated by rank. Their priority is above the system's automatic order queries.
  • "Do not order": stock > 0 → flag as discontinued item; stock = 0 → remove from stock-keeping.
  • "Next basket of supplier": move the item, creating a basket if needed.

6.4 Overstock calculations​

  • Presumed shelf stock = capacity − Σ dispensings from that location. It is set equal to the capacity when a capacity is first entered, recalculated when the capacity changes, and can be corrected manually, which updates the lists.
  • Overstock stock = current total stock − (Σ capacities − dispensed total). Dispensed total counts all main locations, including non-assignable dispensings, across new and printed lists. Example: 7 − (5 + 5 − 4) = 1.
  • Refillable now = min(to refill, overstock stock). The remainder carries over to the next list.
  • Attribution of a sale:
    • Single main location: that location.
    • Several main locations: the location whose mapped sales point made the sale.
    • Ambiguous or unmapped sales points, or dispensings beyond capacity: non-assignable.
    • Causes of non-assignable dispensings: more packs on the shelf than the capacity, undocumented refills, or packs taken from another location, the overstock or goods-in and sold at a sales point mapped elsewhere.
  • Threshold to appear on a list: see 4.10. Default 1 pack.
  • Reason rule: refilled < to refill requires a reason.
    • "completely refilled" clears the outstanding quantity everywhere and books the surplus dispensings as non-assignable.
    • "not completely refilled" carries the gap forward.
  • Counting scope: set by "Application area" (front counter / back office / both / none).
  • Reversals do not decrement the counters.

6.5 Classification rules​

  • An enumeration needs ≥ 1 value to be saved. Deletes cascade.
  • Empty unnamed classes are deleted without a prompt.
  • Exchange happens at classification level only. Only the origin can revoke it.
  • Vendor classifications cannot be deleted or exchanged.
  • A protected classification is editable only with the chosen right.
  • A contact classification's kind is fixed after creation. Its exchange flag is irreversible, and it cannot be set for Außendienst/Lieferant.
  • Merging is allowed only within the same kind.
  • Import files: PZN or Kundennummer as a single column or as a header-named column, and the file must be closed. Add mode removes duplicates.

6.6 Invoicing rules​

  • Due date:
    • due date = delivery/receipt date + value days + due days.
    • Example: delivered on the 12th with 3 value days → the period starts on the 15th, so with 30 due days the payment is due 30 days after the 15th.
    • Discount tiers count from the same start (inferred).
  • Constraints:
    • longest discount period ≤ due days;
    • due days or a debit discount is required;
    • up to 3 discount tiers;
    • up to 3 dunning levels;
    • dunning level N + 1 needs the mandatory fields of level N;
    • only levels 2 and 3 can be deleted, from the top.
  • Discount base: only lines in the selected item categories and prescription types count. Unrestricted OTC and normal sales are always included.
  • SEPA:
    • The payer must be pre-notified at least 14 days before the debit unless otherwise agreed. Vendor default: 14.
    • Migrated models get 7, described as the minimum.
    • The customer IBAN is masked by default.
  • Standard resolution:
    • Payment and dunning terms: the customer's assigned model, else the Standard model.
    • Billing model:
      • an explicit assignment;
      • else, for a home resident, the home's template;
      • else the standard-for-customers model at creation time.
      • Walk-ins use the standard-for-walk-ins model implicitly.
  • Bank account precedence: direct debit to the company account → alternative pharmacy account → standard bank account.
  • Zero-value handling:
    • Separate switches control: creating zero invoices, printing/sending zero invoices, printing zero receipts, and printing zero delivery notes on the invoice.
    • A zero invoice that is created but not printed or sent gets status Intern.
  • Copies:
    • The first document is the original and the rest are copies.
    • For invoices, the original may be e-mailed and the copies are printed.
    • The PDF of a copy carries the suffix "-Kopie".
  • Expense fee:
    • A gross amount with a label.
    • The line is not analysable in Reports or the Management Report.
    • It can be removed per invoice.
  • Merging billing models is irreversible and re-points all links.

7. Configuration and settings​

ParameterScopeEffectDefault
Optimisation model: days of coverper modelDays the order must coverTables assume 30. The vendor recommends 14–18 static. The base model example uses 15.
Dynamic days of cover {min days, cut-off day}per model (also on the base model)Shrinks the days of cover towards the cut-off day of the monthoff
Sales-dependent days of cover tableper modelWMS → days of cover; locks the static field—
Demand evaluation weightsper modelWeight per 30-day intervalfrom the selected table, for example 70/30
Order-trigger table + linear smoothingper modelGross demand → minimum stock≥2 rows required
Seasonal factor {on, max %, min %}per modelSeasonal scaling with clampsoff; recommended max 300 %, min 33 %
POR max surcharge % on last orderper modelCaps the order quantity for POR—
Group-wide useper modelExchange in the pharmacy group—
"Optimierung" configuration parameterssystemRun optimisation in further processesnot specified
Basket model priority 1–8 / Standardper modelPrecedencebase model = 9
Back-order rows {customers, rule, supplier, Online, Late, Fixed supplier, basket per customer/selection}per modelRouting of back-ordersbase row "all customers"
Stock-item rule {rule, supplier, Online}per modelRouting of stock items—
Also for direct-only itemsper modelApply rules to direct-supplier itemsoff (inferred)
Late-order mode and criteriaper modelLate-order batchingnot specified
Allow interim order at wholesalerper direct-supplier contactEnables the interim orderoff
Own order query actionper querynone / do not order / next basketnone
Response notificationpharmacyTask with priority, assignee and deputynone
Transmission-error notificationpharmacyInfocenter message or tasknot specified
Offer-list notificationpharmacyTask for new offer liststask, priority normal, assignee "Apotheke"
Task on stock status → negative (items with back-orders)pharmacyNotes tasknot specified
Cancellation period per supplier {period, unit, extension, DS/NL}per supplierExpected cancellation date of back-order lines—
Hint N days before cancellationpharmacyIcon in back-order management—
Cancellation-date taskpharmacyNotes task—
Location type (main/overstock)per locationPrefills the item role—
Sales points per locationper locationPer-location dispensing attributionnone
Application area (Anwendungsbereich)article-management system settings, workstationWhich sales count for overstock: none / front counter / back office / bothnone (feature off)
Refill list completion ("Auffüllliste erledigen")config parameter (scope not stated)Which list statuses may be completed: printed only / printed and new / all including "new, printout exists"printed only
Output on scan (Auslagern beim Scannen)POS settings, workstation, KS-System pageRobot replaces the pack at the time of sale—
Picking robot (Kommissionierautomat)POS settings, workstationRobot present at this workstation—
Overstock output locationPOS settings, workstationChute for overstock output; 0 = default chute0
Refill list Notes seriesper listReminder scheduleevery working day 09:00–15:00
Refill print options defaultper list (save as default)Prefilled print options—
Hit-list classification columns 1–5 {classification, header ≤10 chars}settings in item classificationExtra hit-list columnsempty
Classification protection rightper classificationEditing limited to holders of that rightnone
Exchange flag (classification)per classificationGroup sharingitem: per choice; contact: No
Billing model standard for customers / walk-insper modelDefault assignmentvendor base model (assumed)
Billing model fields (see 3.4)per modelInvoicing behaviourprefilled with standard entries when new
Payment-terms model Standardone per typeDefault termsvendor "Standard PT" (debit 14 days)
Table configuration (billing-model list, contact-classification list)pharmacy / workstation / userVisible columns—

8. Roles and permissions​

  • Goods logistics: edit order-quantity optimisation (Warenlogistik: Bestellmengenoptimierung bearbeiten). Included in the roles Leiter (manager) and Konfigurationsverantwortlicher (configuration officer). It is also available as a standalone role.
  • Goods logistics: edit basket determination (Warenlogistik: Warenkorbermittlung bearbeiten). Same roles; also standalone.
  • Start and edit own order query (Eigene Bestellabfrage starten und bearbeiten). Same roles; also standalone.
  • The goods-logistics admin module opens read-only without these permissions. Its Settings page needs no specific profile.
  • Workstation protection (Arbeitsplatzschutz) can additionally restrict the modules per workstation or user.
  • Contacts > Staff: edit user account and assign rights is needed to protect or unprotect item classifications. Protected classifications are editable only by holders of the selected right; everyone else gets view mode.
  • No permissions are stated for: storage locations, refill lists, contact classifications, or invoicing terms (open question).

9. Integrations, hardware and external services​

  • Supplier order transmission:

    • Order times, main order time, delivery times and the late-order flag come from supplier contacts.
    • Online availability inquiry is used by the "Online" option.
    • Supplier responses and transmission errors feed the notifications.
    • MSV3 (German wholesaler order protocol) supports sending with your own order identifier, so the wholesaler packs a separate tote. [DE-SPECIFIC; the idea: pass a customer-defined order reference so the supplier packs separately.]
  • Supplier offer lists:

    • Contractually binding lists linked to suppliers. A notification is raised for new lists.
    • They can be used as the item selection in basket routing.
  • Picking robot (Kommissioniersystem):

    • It can be a main or an overstock location.
    • Outputs go to numbered chutes.
    • Output can be triggered by scanning at the POS or from the refill list.
  • Notes (task module):

    • Recurring refill reminders, and order and back-order notifications. Each has priority, assignee, deputy, and an acoustic signal for high priority.
    • "Execute" deep-links into the relevant module.
  • Infocenter: an alternative channel for transmission errors.

  • Reports:

    • Item and customer queries define the scope of:
      • optimisation models;
      • basket models;
      • own order queries;
      • refill lists;
      • classification assignment.
    • Classifications are evaluable in Reports. The vendor Management Report (MMR) exclusion list is a classification.
  • Electronic shelf labels: the vendor classification "ESL-Etikett" marks the items concerned.

  • E-mail delivery of invoices and dunning letters. PDF archive of invoices on a file share.

  • Company master bank accounts are used for billing.

  • Pharmacy group (Verbund): exchange of:

    • classifications;
    • optimisation models;
    • billing models (with contact exchange and cross-branch invoicing);
    • contact classifications.

    This must be enabled centrally by the vendor.

  • Blister centres (external or contract blistering) affect delivery-note printing.

10. Printouts, reports and exports​

  • Refill list:
    • Sorted by item: total, per-location capacity, to refill, a pre-filled "refilled" column, and (overstock/to-refill) where there is a shortage.
    • Sorted by location: the items per location, with non-assignable dispensings marked NzA.
    • The note from the list is printed on it.
    • Whole list or marked entries.
  • Labels from refill lists:
    • Types: price, location, unit-price, or custom forms of these types.
    • Quantity: refill quantity, total stock (with an optional maximum), or a fixed number.
  • Billing documents controlled by the billing model:
    • delivery note (with outstanding back-orders and prices or totals optional);
    • back-delivery note;
    • invoice (line sort order);
    • dunning letter (title, fee, due date and text per level);
    • collective slips for delivery notes and for invoices;
    • customer, home, clinic and dosage labels;
    • receipts and itemised statements;
    • invoice PDF archive.
  • Invoice payment section:
    • due date and discount tiers, or an alternative text;
    • for direct debit: the pre-notification debit date, creditor ID, mandate reference, the masked IBAN, the optional "ensure sufficient funds" sentence and extra text above;
    • the discount amount.
  • Imports:
    • PZN list into an item class;
    • customer-number list into a contact classification.
  • Export: classifications can be replicated across a group through the Reports export plus the classification import. This is the workaround for vendor classifications.

11. Dependencies on other modules​

  • Article management (article master): stock status POS/POR, fixed and maximum stock, the fixed supplier, location assignment with capacity and threshold, manual refill, "stock and order control" log, item classification on the stock-data page, hit-list views 5–7.
  • Supplier contacts: order and delivery times, late-order flag, direct-supplier settings ("allow interim order at wholesaler"), offer lists, conditions.
  • Customer contacts: assigned payment, dunning and billing models (Faktura page); home structure; contact classification assignment; contact duplicate merge.
  • Goods logistics (ordering): baskets, supplier change, order queries, back-order management, responses, MSV3 sending.
  • Offer-list management (Angebotslisten verwalten).
  • Reports: query builder for items and customers.
  • Notes: tasks and series. Infocenter.
  • Invoicing (Faktura): invoice runs by cycle, invoice totals (removing the expense fee), dunning runs, blister orders.
  • Print forms module: default label and document forms.
  • Company master: bank accounts; the MMR/BI portal.
  • POS system settings: KS-System (robot) parameters.
  • User and right management (staff contacts), and workstation protection.

12. Portability notes​

Generic (re-implement as is):

  • Prioritised rule models with query-based item scope, used for both quantity and supplier routing, with a non-deletable fallback model.
  • Demand forecasting from weighted 30-day intervals including lost sales, days of cover, a minimum-stock lookup table with interpolation, the fixed vs. variable minimum, a maximum-stock cap, and the order formula.
  • A seasonal factor from the previous two years, with clamps.
  • Dynamic days of cover to fit month-end billing by suppliers.
  • Late-order batching, to shift goods receipts off peak hours, with automatic re-booking when stock gets critical.
  • Customer-segment routing of back-orders, for example institutional customers to a consolidated basket or a pseudo-supplier.
  • Pending inbound direct deliveries shorten the days of cover. Interim orders at a wholesaler bridge the gap.
  • Own order queries: simple user rules (block, move to a supplier) applied during basket review.
  • Notification routing (task with assignee and deputy, priority) for supplier responses, transmission errors, new offer lists, and expected cancellation of back-orders.
  • Location tree with types, sales-point mapping, capacities, presumed shelf stock, reserve-stock estimation, refill work lists with a print-freeze and a continuation list, reason codes for partial refills, and robot integration.
  • Classifications: flags, enumerations, hierarchies, with bulk assignment from queries or CSV, right-based protection, and use as hit-list columns.
  • Contact tags scoped to roles, for marketing selections.
  • Payment terms with value days and tiered cash discounts; dunning levels with fee, due period and text; billing templates that bundle cycle, terms, documents, forms, zero-value rules, PDF archiving and an expense fee. Defaults for registered vs. walk-in customers, with inheritance from institutions.
  • Multi-site harmonisation: exchange flags with origin markers, and a merge UI for duplicates (an attribute-by-attribute chooser with status per row; merging creates a new record and re-points links).

Germany-specific, with the idea underneath:

  • ABDA list purchase price and dispensing regulation as selection criteria. The idea: use the national drug-database price and the legal dispensing category as rule criteria.
  • MSV3 order identifier. The idea: a supplier-side packing reference per order.
  • GEHE "WaWiExtra" items. The idea: wholesaler-specific assortment programmes that change which supplier is eligible.
  • Narcotics (BtM) cabinet and narcotics fees. The idea: controlled-substance storage and supplier surcharges that drive routing.
  • Prescription types (private, "green") as the discount base. The idea: cash discounts allowed only on non-reimbursed or self-pay lines, not on lines regulated by the payer.
  • SEPA direct-debit pre-notification (14 days, creditor ID, mandate reference, masked IBAN). The idea: regulatory advance notice and data masking for bank debits. In Syria this would map to whatever local payment mechanisms apply.
  • Discount-contract changes (Rabattverträge) as a cause of sales outliers. The idea: clamp forecast factors against payer-driven demand shifts.
  • The MMR exclusion contents (crude drugs, chemicals, product-group keys BF01/BF02). The idea: exclude non-commercial or intra-group lines from margin analytics.

13. Open questions​

  • The semantics of the stock statuses POS vs. POR are not explained in these pages, beyond POS triggering automatic optimisation and POR offering a cap on the last order quantity.
  • The rule option "Anbieter" (provider) in basket determination is listed but not explained. It probably means ordering directly from the manufacturer.
  • The exact definitions of "next call" and "next delivery" when several suppliers qualify, and how "optimal" and "cheapest" supplier are calculated (conditions, effective purchase price), are covered elsewhere.
  • How the basket "Online" check chooses when several suppliers are able to deliver.
  • The rounding rule for gross demand and order quantities. The example truncates 1.4 to 1. Whether the bracket bounds of the trigger table are inclusive is also not stated.
  • How the weights of more than two intervals feed the seasonal formula. Only a 2-interval example is given.
  • How the expected cancellation date is computed from the period and the extension period, and what exactly DS/NL restrict.
  • What "when and how often" scheduling options exist for the back-order tasks.
  • Whether optimisation and basket models are evaluated in a fixed order relative to each other (quantity first or basket first).
  • Whether own order queries run automatically or only when a user reviews the basket.
  • The scope (workstation or pharmacy) and location of the "Auffüllliste erledigen" parameter is not stated.
  • The help states the Notes task must be set done in order to open the refill list. This contradicts the "Execute opens the list" flow. The intended dependency is unclear.
  • How dispensings from back-office invoice orders interact with refill lists when the application area is "both".
  • Permissions for storage locations, refill lists, contact classifications and invoicing terms are not stated.
  • Whether the start date for the due period is the invoice date or the delivery date. The help says "delivered on the 12th".
  • Whether cash-discount periods also start after the value days.
  • What exactly happens to existing customers when the Standard payment or billing model is switched. Presumably customers without an explicit assignment follow the new standard.
  • Whether an enumeration strictly enforces a single value per item.
  • How many hierarchy levels are allowed.
  • What the "move" buttons in the classification tree change (display order only?).
  • The file encoding and delimiter expected for CSV imports.

14. Source pages​

All 55 pages of the manifest were read.