Skip to main content

Purchasing Cart and Multi-Branch Purchasing (Warenlogistik: Warenkorb, Bestellabfragen, Filialenfunktionen)

1. Purpose and scope​

This chapter covers two connected parts of the IXOS goods-logistics module (Warenlogistik):

  1. The purchasing cart (Warenkorb). This is the staging area where order lines for one supplier are collected, checked, optimised and then sent. It covers how carts are created (by hand, by the system, or from an automatic order proposal), what a cart line carries, how lines are moved between carts, suppliers, sub-orders and the scheduled-order note, the rule-driven "order queries" (Bestellabfragen) that must be answered before ordering, quantity optimisation, the order proposal and its saved hit lists, the choice of transmission channel, cut-off times, minimum order values, and cart printouts.
  2. Multi-branch purchasing and goods exchange (Filialenfunktionen). In a network of branch and partner pharmacies, this covers joint carts and orders whose quantities are split across pharmacies, joint order proposals, three delivery/invoicing set-ups (central, decentral with central invoice, and split), joint goods receipt and redistribution, inter-branch transfers started by either side, visibility of other branches' stock, internal net-price billing, and remote printing.

Out of scope, and covered by other chapters: the notepad and order notes before the cart (Merkzettel: defect note, scheduled-order note), the sent-orders stage and the processing of supplier responses, goods receipt as such, returns, supplier master data and conditions, offer-list management, the order-quantity optimisation and cart-determination models themselves, and assortment control. These appear here only as dependencies.

Who uses it: pharmacy purchasing staff every day; the branch manager or head office for joint purchasing; staff in receiving branches for transfers and goods receipt.

2. Key concepts and terms​

German termEnglishMeaning
WarenkorbcartCollection of order lines for one supplier. It is either fetched by the supplier (passive) or sent actively. Once sent it becomes an order (Bestellung).
Warenkorbpositioncart lineOne article line in a cart: quantity, free goods, price, supplier, hint code, origin and customer links.
Merkzettel / Warenkorb / Bestellungen / Lieferungen / Retouren / Archivnotepad / cart / orders / deliveries / returns / archiveTabs of goods logistics in process order. A cart's status can be changed to notepad, order, booking or archive.
LieferantsupplierAny party you buy from: wholesaler, manufacturer, branch pharmacy.
GroßhändlerwholesalerSupplier not flagged as a vendor.
Anbietervendor / manufacturerEntry in the national list of pharmaceutical manufacturers and distributors (kept up to date by the data service). It becomes a supplier only once it has the "supplier" contact role. A direct supplier (Direktlieferant) is a supplier that is also a vendor.
Filial- und Partnerapotheke (F&P)branch / partner pharmacyMember of a pharmacy network (Apothekenverbund).
Auftragsart (A.-Art)order typeNormal (blank), SO special order (Sonder-Auftrag), ST batch order (Stapel-Auftrag), VR stock-up purchase (Vorratskauf), ZT timed order (Zeit-Auftrag).
Unterauftragsub-orderPart of one order that the supplier packs and invoices separately under its own order number (for example cold chain, narcotics, pickups, robot).
Bestellabfrageorder queryA system-generated checkpoint on a cart line that needs a decision before ordering (cheaper offer, cold item, narcotic, recall and so on).
Eigene Bestellabfragecustom order queryA user-defined query. It takes priority over the automatic ones.
Artikelhinweis / Bestellhinweis (A.-H.)line hint codeCode sent to the supplier with a line: DS (may re-order from the manufacturer), NL (back-order allowed), VB (may source from its partner branches).
Nara (Naturalrabatt)free goodsFree extra units granted on a line or offer.
EK / Brutto-EK / Netto-EKpurchase price / gross / netLine price. It is shown as "gross" once manual discounts exist; the net price is after manual discounts.
ABDA-EK / Apo-EKofficial list purchase pricePharmacy purchase price from the national drug database.
Anbieterpreisvendor priceSupplier-specific price, used as an alternative price basis.
prog. eff. EKprojected effective purchase pricePrice after applying the supplier's condition agreements and offer lists.
Angebot / Angebotslisteoffer / offer listSupplier promotion: offer quantity, offer price, free goods. A list can be flagged as preferred.
Verhandlungssache-Angebotnegotiable offerSpecial terms with no percentage (0 %), so no offer price can be computed.
Konditionsvereinbarungcondition agreementSupplier contract terms: discounts, minimum order value, minimum pack count, monthly turnover target, agreed average Rx pack price.
Lieferantenoptimierung / Warenkorbermittlungsupplier optimisation / cart determinationAutomatic choice of the best cart or supplier for an item according to cart-determination models (Warenkorbermittlungsmodell).
Mengenoptimierung / Bestellmengenoptimierungquantity optimisationComputing order quantities from demand statistics, stock, open orders and the days of stock to cover.
Mengenvorgabefixed quantity presetFixed quantity pre-filled for each newly entered item.
Dispozeitdisposition time / days of coverNumber of days the stock should last. It can be static or shrink toward month end.
Bewertungszeitraumevaluation periodPeriod of sales history used for optimisation (current year plus the two before).
Bestellvorschlag / Trefferlisteorder proposal / hit listGenerated list of articles and quantities per vendor or supplier. It can be saved and reopened.
Abruf / Bestellschluss / Tagfetch time / order cut-off / dayWhen the supplier collects the cart, the supplier's cut-off for the next delivery, and whether the fetch is today or tomorrow.
Spätauftraglate orderCart flag for a late (evening or overnight) order run; cart-determination models can keep items such as narcotics out of it.
sendebereitready-to-sendCart queued for automatic transmission at its order time.
Terminnotiz / Terminbestellung / Bestellturnusscheduled-order note / scheduled order / order rhythmLines parked for a future order date or a recurring rhythm.
Defektnotizdefect noteNote of items the supplier could not deliver.
Abholung / Nachlieferung / Abholscheinpickup / back-order for customer / pickup slipCustomer-linked demand that creates cart lines.
POS / POR / Negativartikelstorage statusesPOS = stock-managed article (positive stock keeping). POR = article not tracked by quantity (shown as "A" in order logs). Negativartikel = not stocked. Exact definitions are in the article-master chapter.
Dauersortiment / Dauerbesorgerpermanent assortment / permanent procure-on-demandArticle flags that exclude items from slow-mover or new-stock queries.
Ladenhüter / Auslaufartikel / Verfallartikel / Bevorzugt abzugeben / Überbestandslow mover / discontinued / near-expiry / preferred-to-dispense / overstockStorage flags that can be exchanged across the network.
AV-Artikel (Außer Vertrieb) / zurückgezogen / Rückrufoff market / withdrawn / recalledDistribution statuses of an article.
Gemeinsamer Warenkorb / Gemeinsame Bestellungjoint cart / joint orderMulti-branch cart or order with per-pharmacy quantity shares.
Bestellende Apotheke / Apotheke mit Bestellanteilordering pharmacy / pharmacy with a shareRoles in a joint purchase.
AMOaverage monthly salesPer pharmacy, last year. Shown for information only.
BMOweighted monthly sales per optimisation modelAverage monthly sales including no-sales and cancellations, weighted by the month weights of the ordering pharmacy's model. It drives the distribution between pharmacies.
Vorratstage / Reichweite / Gesamtreichweitedays of stock / coverage / total coverageStock duration metrics.
Lagerausgleichstock balancingRedistributing existing stock between branches (separate topic).
Umlagerung / Umlagerungsauftragtransfer / transfer orderMoving goods between network pharmacies. It is booked as an order at the receiver and as an invoicing job (Faktura) at the supplier.
Fakturainvoicing moduleCustomer jobs, delivery notes and invoices. Used for the supplying side of transfers.
Sofortrechnung / Sammelrechnungimmediate invoice / collective invoiceInternal billing documents between network pharmacies.
Verrechnung aus internem Warenaustauschinternal goods-exchange billingOption that bills internal exchange at net, without VAT, in a separate invoice-number range.
Wertbuchung / Bestandsbuchungvalue booking / stock bookingBooking the invoice values of a goods receipt versus booking only the quantities.
Chargendokumentationbatch documentationRecording batch numbers for drugs passed between pharmacies.
MSV3wholesaler ordering protocolGerman standard web-service protocol for ordering and availability checks.
DFÜremote data transferCart is fetched electronically.
DIREKTpluspurchasing cooperationA buying cooperation with its own joint-order variants (icons only in the help).

3. Data model​

3.1 Cart (Warenkorb)​

  • supplier_id (exactly one). This can be a wholesaler, a direct supplier (vendor with supplier role) or a branch pharmacy (in which case the cart is a transfer request).
  • origin: manual (created by the user) or automatic (created by the system from sales, the defect note, the scheduled note, assortment control, order proposals or cart determination).
  • created_date: set only for manual carts.
  • fetch_time (Abruf) and fetch_day (today / tomorrow): set only for automatic carts tied to a supplier's order times.
  • order_cutoff (Bestellschluss): the time reported by the supplier up to which delivery at the next delivery date is guaranteed.
  • late_order flag (Spätauftrag).
  • order_type: NORMAL | SO | ST | VR | ZT.
  • price_basis: ABDA list price | vendor price.
  • send_state: none | ready-to-send | being fetched | being transmitted | transmission error.
  • has_open_order_queries; avg_rx_pack_price_exceeded (the supplier contract defines an agreed average price per Rx pack).
  • is_joint and, for joint carts, executing_pharmacy plus participating_pharmacies.
  • locked_by_user: set while a user edits lines, processes queries, or the cart is being sent actively or passively.
  • msv3_not_possible: shown for a direct supplier that cannot take MSV3 orders.
  • Derived values: position_count; value = sum of line purchase values including discounts.
  • info_text at cart level; order-level discounts.
  • Sub-order tabs: All plus one tab per active sub-order. There is also an "Order queries" pseudo-tab.
  • Status transitions: cart → (set ready-to-send ⇄ remove ready-to-send) → order (on successful transmission, or immediately for "mark as ordered", e-mail or fax). There is also a manual status change to notepad, order, booking or archive. On a transmission error the cart stays and must be acknowledged before further editing.

3.2 Cart line (Warenkorbposition)​

  • article_id (national article code PZN), or a free-text article that is not in the article master.
  • qty; free_goods_qty (Nara); purchase_price (editable); gross/net price after manual discounts; manual line discounts.
  • supplier_id: defaults to the cart's supplier and can be set per line. A different supplier moves the line to that supplier's cart.
  • order_type (editable per line); hint_code (none / DS / NL / VB); info_text.
  • sub_order (assigned automatically by priority, changeable by hand).
  • Origin and customer-link markers, in display priority:
    1. back-order or scheduled order without a direct customer;
    2. customer order (one or more customers; links to customer records);
    3. from the defect note;
    4. from the defect note for customers;
    5. from the scheduled note;
    6. from the scheduled note for customers;
    7. back-order for courier delivery without a customer;
    8. back-order by post without a customer.
  • partial_quantities: one line can aggregate several components, each with customer, pickup number (Abholnr.) and quantity, plus a replenishment quantity for stock already handed out. The links to pickup slips are kept.
  • listed_by_assortment_control flag (displayed in blue).
  • evaluation_period: an optional stored period, set by optimisation, re-optimisation or by ordering from an analysis list.
  • order_query_flags: which queries apply; whether each has been processed.
  • Display-only values joined from other modules: dispensing restrictions (Rx, narcotic, blood product, haemophilia product, non-Rx blood product, T-prescription, substitution exclusions, hospital module, pharmacy-only, monitoring required), dosage form, pack size, standard pack size, import or auxiliary-tariff status, article-info and sales-info icons, storage status, stock, reserved quantity, deliverability from online inquiry, storage location.

3.3 Sub-order (Unterauftrag)​

  • Per supplier, the set of activated sub-order types (supplier contact settings). For MSV3 suppliers the agreed number of "free order identifiers" limits this.
  • Types in assignment priority: narcotics > blood products > cold-chain (maximum storage temperature 8 °C) > pickups (customer pickups and back-orders by courier, post, invoicing or online orders) > picking robot > main alphabet > visible choice (behind counter) > free choice (self-service) > remaining (normal).
  • Each sub-order is transmitted under its own order number and delivered and invoiced separately.
  • A user-supplied own order identifier replaces all sub-order IDs of the cart with one custom sub-order.

3.4 Order query instance (Bestellabfrage)​

  • type: offers or cheaper suppliers, discontinued, off-market or withdrawn, narcotic, direct purchase, fixed supplier, branch sourcing, import search, cold item, slow mover, new stock listing, multiple order, returned article, recalled article, or custom.
  • Linked cart line; state open or processed.
  • Re-opened when the line quantity changes (offers query, if so configured) or when "recalculate queries" is run.

3.5 Saved order-proposal hit list (Trefferliste)​

  • joint flag; created_at; supplier; last_edited_at; last_editor.
  • stale flag: more than 48 h after creation. It is suppressed if a custom evaluation period excluding the current month was used.
  • Lines: article, Apo-EK, vendor/supplier, total stock (across evaluated pharmacies), proposal quantity, final quantity, selection flag. For joint lists also a per-pharmacy share and a participation flag.
  • Lifecycle: saved → edited (any number of times) → converted to a cart or order (the list is then deleted automatically) or deleted by the user.

3.6 Joint cart / joint order extensions​

  • Header: dispo_days (minimum cover for all participating pharmacies), executing_pharmacy, and the delivery mode (central / decentral with central invoice / split).
  • Per line and pharmacy (BranchShare):
    • participates, storage_status, AMO, BMO;
    • available_stock (excludes reserved quantities such as open pickups);
    • days_of_stock (∞ if BMO = 0), proposal_qty, qty, coverage, overstock_flag.
    • Back-order quantities can be carried in (shown under "Customer orders" at goods receipt).
  • Line totals: total available stock, total quantity, total coverage.
  • Mirror copies at each branch: read-only, containing only that branch's lines and quantities, shown grey with the executing pharmacy's code.
  • At joint goods receipt, per pharmacy: original split (Aufteilung Best.), proposal based on the delivered quantity (Vorschlag Lief.), and the final quantity. Final quantities must add up exactly to the delivered quantity.

3.7 Per-pharmacy order-optimisation master data (shown in branch statistics)​

  • Fixed order quantity: always order this amount or an integer multiple. It must not exceed the maximum order quantity.
  • Maximum order quantity: cap on optimised quantities.
  • Maximum stock: never fill above this level.
  • Variable minimum stock: computed by the model.
  • Fixed minimum stock.
  • An order is triggered when stock falls below max(fixed, variable) minimum stock.

3.8 Transfer (Umlagerung)​

  • Receiving pharmacy: an order whose supplier is the supplying pharmacy.
  • Supplying pharmacy: an invoicing job whose customer is the receiving pharmacy.
  • Delivery notes carry batch data. Every change made after delivery-note creation is synchronised to the receiver as a response with a reason code: quantity correction / new entry / deletion / cancellation.
  • Billing documents: an immediate invoice per branch share (decentral delivery) or a collective invoice at an agreed time.

3.9 Network pharmacy contact​

  • Three independent contact roles per member pharmacy: tenant (Mandant, under "Branches & Partners"), supplier, and customer (company).
  • Customer role: invoicing permitted; invoice with net prices; a discount model (usually based on the purchase price) with "prefer the discount model's price" set; a batch-documentation setting.
  • Branch/partner master data: "internal goods-exchange billing" (net, no VAT, separate invoice-number range).
  • Preferred-branch ranking, used for stock display order.
  • Supplier role settings: activated sub-orders; auto ready-to-send; joint purchase "deliver to each pharmacy, invoice to own pharmacy"; contract data with free order identifiers; condition agreement with minimum order value, minimum pack count and monthly turnover target.

4. Features​

Part A: The purchasing cart​

4.1 Cart overview [GENERIC]​

  • Purpose: one list of all open carts, both user-made and system-made, one row per supplier cart.
  • Row content: send-state icon; order-query icon (an open query, the agreed average Rx pack price exceeded, or both); supplier name; late-order, joint-cart, locked-by-other-user and no-MSV3 flags; fetch time; supplier cut-off; fetch day (today/tomorrow); creation date (manual carts only); order type; number of lines; total value including discounts. Columns are configurable.
  • Filters: left navigation by supplier class: wholesalers only, vendors/direct suppliers only, branch and partner pharmacies only, or all. The default start view shows wholesaler carts only. The config "filter cart overview" can change it, for example to "all orders".
  • Joint carts of other branches: carts created by another network pharmacy for a joint purchase (not yet ordered) appear grey and read-only.
  • Overview actions: new cart; new joint cart (network members only); delete cart; edit; info text per cart; add articles; free-text article; discount info (what each supplier would grant for this cart); print; supplier change (merge this cart into another cart); change order status (notepad / order / booking / archive); order; change order type; quantity optimisation; print settings; open supplier contact; open invoicing; reopen a saved hit list; show turnovers.
  • Delete guard: deleting a whole cart that contains items below minimum stock shows a warning naming those items, and the user can cancel.

4.2 Creating a cart and choosing its supplier [GENERIC]​

  • Trigger: "New" (single pharmacy) or "New joint cart" (network).
  • Supplier picker: name search (standard or phonetic), extended search, tabs Supplier / Vendor. In a network a button shows the exchanged contacts of all other network pharmacies; it is visible only if the pharmacy has restricted visibility of exchanged contacts.
  • Vendor promotion: picking a vendor that does not yet have the supplier role asks whether to add the role. On yes, the role is added and the cart is created.
  • New contact: a new contact can be created on the spot (a name is the minimum) and contact details can be opened.
  • Completion:
    • OK creates an empty cart and opens line entry.
    • "With evaluation" starts the automatic order proposal (4.12).
    • "Without evaluation" (joint carts) creates an empty joint cart.
  • Later: at any time the user can check the order thresholds (minimum order value and minimum pack count from the supplier's condition agreement), add or delete lines, send, or delete the cart.
  • Automatic creation: the system also creates carts itself, for example when cart determination moves an item to a supplier that has no cart yet, or when a direct-purchase query moves an item to a vendor.

4.3 Entering lines [GENERIC]​

  • Entry points: "Add article" from the overview or from an open cart. It is not available when no cart exists. Opening an empty cart lands on the first entry row.
  • Per row: article by PZN or name (all article-search syntax applies); quantity; optional purchase price; optional free goods; supplier (defaults to the cart's supplier).
  • Quantity prefix: typing 15/ASS presets quantity 15 and searches for "ASS".
  • Free-text line (Freitext erfassen): orders an article that is not in the article master.
  • Mode switches before typing an article (sticky until changed; only in add mode, not in edit mode):
    • Quantity optimisation: the suggested quantity comes from the optimisation model.
    • Fixed quantity: every new line is pre-filled with the given number.
    • Cart determination: after entry the item is moved automatically to the cheapest or optimal cart according to the cart-determination models. If that supplier has no cart, one is created.
  • Supplier optimisation: when enabled, the optimal supplier is preselected on entry.
  • Discard: pressing Esc before leaving the row asks whether to save; No discards the entry.
  • POS-0 list: after a confirmation prompt, adds every POS article whose stock is ≤ 0 and that is not currently on order. The user then removes unwanted lines and adjusts quantities.
  • Order queries during entry: if "show order queries on entry" is on, applicable queries open immediately while lines are entered.

4.4 Line editing, deletion and the detail area [GENERIC]​

  • Editable fields: quantity, free goods, purchase price, supplier, order type, hint code, info text, manual discount(s) for this line or all lines. The article's storage status can also be changed directly from the cart, and the stock of all network members can be shown.
  • Deleting a line: asks for confirmation. If the line is a customer pickup, a further warning names the customer link and allows cancelling.
  • Detail area for the selected line:
    • Sales statistics: sales and no-sales (unmet demand) for the current and two previous calendar years.
      • POS articles: sales minus reversals or cancellations.
      • POR articles: purchases minus returns.
      • If the system parameter "demand statistics and optimisation with sales data" is on, the figures come from transaction history and no-sales.
    • Article info: stock, open back-order quantity, prices, last delivery.
    • Assortment-control status: article in changeover with planned actions (new storage status, preferred-to-dispense value); delisted on a date; listed on a date; stocked as an alternative to a back-order; temporarily listed as a substitute for an unavailable article X.
    • Price table: see 4.5.
  • Live update from sales: if a sale is later changed at the order interface, the linked cart line (and also scheduled-note and defect-note lines) adjusts itself. A cancellation or reduced quantity lowers the line or deletes it; an increased quantity raises it.

4.5 Price table, offers and supplier switching [GENERIC]​

  • Rows: one per offer or condition. Each row shows:
    • type icon (wholesaler / vendor / branch pharmacy);
    • supplier name, which can also be the name of a branch that has the article available;
    • price origin (condition agreement or offer);
    • offer quantity (the amount for which the advertised price applies);
    • free goods;
    • negotiable-offer flag;
    • preferred-list flag (when an article is on several lists, the preferred list's settings are used for pricing even if another list is cheaper), plus a variant for a preferred list with priceless offers;
    • projected effective EK;
    • saving in currency and in % against the pharmacy list price.
  • Sorting:
    • In "offer EK" mode: negotiable offers first, then offer price ascending, then quantity ascending, then list priority from offer-list management.
    • In "projected effective EK" mode: price ascending, then quantity ascending, then main supplier first, then supplier name alphabetically.
  • Taking an offer: double-clicking an offer row raises the quantity to the offer quantity if needed, applies the offer price and moves the line to that supplier's or branch's cart or order. The offers query then opens only if an even cheaper offer exists.
  • Cheaper effective price: double-clicking a cheaper projected-effective-EK row switches supplier. The system first works out whether the row is a tiered discount, a negotiable offer or a condition price.
  • Price basis per cart: the official list purchase price or the vendor price. Changing it re-prices all lines and keeps the entered discounts, which are applied to the new basis.
  • Discount info: shows the discounts each supplier grants for the article (line level) or for the cart (overview level).

4.6 Line hint codes (Artikelhinweis) [GENERIC]​

  • What: a code attached to a line and sent with the order. The supplier acts on it.
    • DS: the supplier may order from the manufacturer if it is out of stock.
    • NL: a later back-delivery is acceptable.
    • VB: the supplier may source the item from its network branches.
  • Availability: which codes are offered depends on goods-logistics settings. The direct-purchase query uses DS as its default (4.10.4).

4.7 Sub-orders [GENERIC]​

  • Purpose: the supplier packs each class of goods in its own tote with its own invoice number, so the pharmacy can process cold, narcotic, pickup or robot goods separately.
  • Prerequisites:
    • Activate the wanted sub-order types per supplier.
    • Maintain storage locations on articles (needed for the robot, main alphabet, visible-choice and free-choice types).
    • For MSV3 suppliers, agree at least as many free order identifiers as sub-orders are configured.
  • Assignment: automatic, by the priority in 3.3. Examples:
    • A customer back-order always goes to "pickups", even if its location is visible choice.
    • An item located in both free choice and the robot goes to "robot".
    • With overstock management, an item with shelf locations plus overstock in the robot goes to "robot". It is stored there and later sent to the shelves via refill lists.
  • Viewing: the cart, order and delivery screens offer tabs: All, plus one tab per sub-order.
  • Change sub-order: moves selected lines (option "apply to all selected") to another activated sub-order of the same supplier, in view or edit mode of a cart or order. Typical use: avoid an extra tote and an extra booking for a single item.
  • On ordering: each sub-order is sent under its own order number and is processed by the wholesaler as an independent order.

4.8 Moving lines between carts, suppliers and notes [GENERIC]​

  • Supplier change on a line: moves the line to another order, another cart, the optimal supplier, the cheapest supplier, or into the defect note.
  • Merge carts: in the overview, supplier change merges a whole cart into another cart.
  • Moving to a branch: taking a branch offer from the price table, or choosing branch sourcing in the order query, moves the line (or part of it) into a cart addressed to that branch. Ordering that cart creates a transfer.
  • Scheduled order (Terminbestellung): moves one line out of the cart into the scheduled-order note. Typical reasons: waiting for a better price, deferring an expensive item to next month, or a customer who wants to collect on a given date.
    • If the line aggregates several partial quantities (customer back-orders plus a stock replenishment quantity), a dialog lists each part with customer, pickup number and quantity, all ticked. Unticked parts stay in the cart. Example: keep the customer back-orders for today and defer only the stock top-up.
    • Then the user enters an order date or a rhythm. The default is the first day of the next month.
    • Each part becomes an individual scheduled line with its own date and keeps its customer and delivery-type markers. Pickup-slip links are preserved.
    • Pickup-linked scheduled lines update automatically when the sale changes.
  • Local to joint: see 4.20.

4.9 Locking and concurrency [GENERIC]​

  • Exclusive lock: a cart is locked for other users while one user adds or edits lines, processes order queries, or while the cart is being sent actively or fetched passively. Other users see a lock icon.
  • Online order: starting an online order locks the cart.
  • After sending: a successful send refreshes the cart overview on all workstations.
  • Saved hit lists: if another user converts, deletes or edits a saved hit list while you have it open, you get a message.

4.10 Order queries (Bestellabfragen) [GENERIC] unless tagged otherwise​

  • Purpose: filter out the cart lines that need a decision before ordering.
  • Order-queries tab: visible only while queries are open. It shows one checkbox per query type present (untick to hide that type) and the affected lines.
  • Processing: "Edit" opens the first query. Confirming moves to the next, in a fixed internal order, until all are done; Esc interrupts. When all are processed the tab disappears, and it returns when a new line meets a condition.
  • Recalculate queries: re-evaluates all queries. Useful when lines have sat for days.
  • Configuration: "show order queries on entry" makes them pop up during line entry. Each query type has its own enable parameter.
  • Custom queries: user-defined queries, aimed especially at ordering from branch or partner pharmacies, take precedence over automatic ones when both match.
  • Common dialog content: header with article identity, dispensing restrictions, import status, info icons (current info under 6 months old / own info / other info such as herbal-tea, product or vendor info), quantity, free goods, price, storage status, stock and quantity reserved in open sales. Common actions: delete the line (with confirmation), open article details, change supplier, Next/Finish.
#QueryTriggerOptions (default bold)Notes
4.10.1Offers / cheaper suppliersSupplier offers exist for the article. Titled "cheaper suppliers" when the projected effective EK is shown.Keep in cart; pick an offer by hand; cheapest offer; cheapest supplier; optimal supplier; choose another cart; edit quantity and free goods. The "optimised quantity" field shows the optimisation's suggestion.See the selection rules below.
4.10.2Discontinued article (Auslaufartikel)Article carries the discontinued flagOrder; order and clear the discontinued flag; do not orderDefault ON
4.10.3Off-market / withdrawn (AV)Distribution status is off market or withdrawnOrder successor (if one is offered); order successor and transfer statistics; order AV article (default if no successor); do not orderSee successor handling below. Default ON
4.10.4Direct purchase (Direktbezug)Article obtainable only from its vendor, but entered in a wholesaler cartKeep with hint code DS (the wholesaler re-orders from the vendor); keep as normal; move to a cart of the vendorIf the vendor has no supplier role it gains one and a cart is created. Default ON
4.10.5Fixed supplierArticle pinned to a fixed supplier other than the cart's. The pin comes from article details or from a cart-optimisation model rule, for example "Rx stock items → supplier X".Move to the fixed supplier's cart; order here; order here and delete the pin (only for pins set in article details, not model pins)Not raised for customer back-orders or for lines from recurring scheduled orders
4.10.6Narcotics [DE-SPECIFIC]Narcotic in the cartKeep in this cart; move to a chosen cart; "applies to all narcotics of this cart"Narcotics must be handed over in person, so order them only on deliveries during opening hours. A cart-determination model can also bar them from late orders. Default ON
4.10.7Cold-chain itemsItem with maximum storage temperature 8 °CKeep; move to a chosen cart; "applies to all cold items of this cart"Must be refrigerated on arrival, so order on daytime deliveries. Alternatively route cold items to morning deliveries through cart determination and supplier order times, and switch this query off. Default ON
4.10.8Branch / partner sourcingItem entered in a wholesaler cart while another network pharmacy has it flagged slow mover, discontinued, near-expiry, preferred-to-dispense or overstockTransfer the full quantity from the selected pharmacy; transfer a different quantity (1 to the available stock; the rest stays); keep in current cartSee the branch table below. Default OFF
4.10.9General import search [DE-SPECIFIC]Cheaper parallel-import packs existOrder the original; pick an import (the original is removed and the import added)See the import list below
4.10.10Slow mover (Ladenhüter)See the conditions belowOrder; no, mark discontinued (line removed); no, take off stock (set status non-stocked; only if stock is 0)Shows sales statistics as a decision aid. Default ON
4.10.11New stock listing (Lagerneuaufnahme)Non-stocked article, not a permanent procure-on-demand item, with ≥ N sales in the last M months (sales to branches excluded)Yes: change storage status, order an extra (editable) stock quantity and set a storage location; no, keep status (order only the sold quantity)Parameters: enable, period in months, minimum number of sales
4.10.12Multiple order (Mehrfachbestellung)Article already in another cart or in an undelivered orderMove to a chosen listed cart; keep in this cart; do not order additionallyMoving into already-sent orders is impossible. Table: type (cart/order), joint and direct icons, supplier, send state, order type, fetch time and day (or stated delivery date for direct orders), quantity, free goods. Default ON
4.10.13Returned articleArticle is also in an open normal return orderOrder; no, take it from returnsSee the returns rules below
4.10.14Recalled article (Rückruf)Manufacturer recall flagOrder; do not order; no, take off stock (status non-stocked, line removed)Default ON

Selection rules for the offers query (4.10.1):

  • Cheapest offer: the best offer from the displayed offer lists for the entered quantity.
  • Cheapest supplier: lowest effective price, considering only suppliers that have offer lists and conditions stored. Those conditions do not need to be flagged for supplier optimisation.
  • Optimal supplier: the same, but only conditions and lists explicitly selected for supplier optimisation. The offer list counts as part of the condition. If the booking price is the basis of the effective price, the offer normally booked against is included.
  • In all three automatic modes the entered quantity is kept. An offer qualifies only if its minimum quantity is ≤ the entered quantity (with quantity 4, an "from 5" offer is skipped and a "from 2" offer qualifies). If nothing qualifies, the line is unchanged.
  • A special offer recorded with 0 % special-offer percentage is valued at the list price.
  • Picking an offer by hand takes over the offer's quantity (possibly raised), free goods and price. These stay editable.
  • On confirm the line moves to the winning supplier's cart, or stays put if the winning supplier is the same one, for example the original supplier's volume offer.
  • The query reopens if the line quantity later changes (move, sale, analysis, manual edit) and "show query on entry" is on.

Successor handling for off-market articles (4.10.3):

  • Transferring statistics opens a confirmation where the successor's storage status can be changed, for example taken into stock.
  • If the line came from a recurring scheduled order, the system asks whether to replace the article by its successor in the scheduled note as well, so future runs order the successor.

Branch table for branch sourcing (4.10.8):

  • Columns per pharmacy: pharmacy, available stock, flag (overstock with count / discontinued / near-expiry / preferred-to-dispense), price, expiry date.
  • A larger quantity than ordered can be taken, for example to absorb another branch's slow movers of an article you sell regularly.
  • The resulting transfer line goes into a cart addressed to the selected pharmacy.
  • Requires that storage flags are exchanged in the network. Further parameters choose which flags are evaluated.

Import list for import search (4.10.9):

  • The original article is on top, the cheaper imports below. The list shows distribution status, Red-Hand and information letters (flagged during their validity or for up to 6 months), training material, predecessor and successor, self-created marker, dispensing restrictions, vendor, effective price (with an "own price" marker), fixed-amount / aut-idem / negative-list markers, stock or no-sale marker, order status (open order, sent, not deliverable, open return, returned, scheduled, in back-order job, in disposition job), back-order quantity from pickups, a network-stock icon, deliverability with a tooltip naming deliverable vendors, and storage location.
  • An online availability inquiry is started automatically.
  • Thresholds: only when the saving is at least x EUR and/or x %.

Slow-mover conditions (4.10.10):

  • The article is flagged slow mover and is not in the permanent assortment, and one of these holds:
    • its storage status was changed before the "slow mover after X days without sale" window and it already carries the flag;
    • it is being re-ordered because of a sale in the last 5 days and carried the flag before that sale, because the previous sale was at least X days earlier;
    • it was last sold more than 5 days ago and before X days.
  • Sales to branches are not counted.

Returns rules for returned articles (4.10.13):

  • Buy-back orders are ignored (not yet booked out).
  • Returns with reason "expired", "short delivery" or "credit follows" are ignored.
  • The user enters a take-out quantity per open return (several returns can be used). The total may exceed the ordered quantity but not a return's quantity, otherwise a warning appears.
  • Stock booked out when the return was created is booked back in.

4.11 Order-quantity optimisation on a cart [GENERIC]​

  • Trigger: "Optimisation" in the cart overview for the selected cart or order. Typical uses: quantity optimisation was off during entry, the cart has existed for a long time, or you want to re-check quantities and supplier before sending.
  • Parameters for one run:
    • Optimisation on or off.
    • Dispo days override. It replaces the model's dispo time for this order only, does not shorten the dispo time of direct orders, and causes the article's fixed and variable minimum stocks to be ignored.
    • Evaluation period override (dates within the current year and the two previous years), or "use the evaluation periods stored on the lines".
    • Deduct stock on hand (default on).
    • Deduct quantities already in carts (default on).
    • Deduct quantities in open orders (default on).
    • Cart determination: optimise the supplier as well.
  • Re-run behaviour: quantities already marked "to order" by a sale-triggered optimisation are counted against the dispo time. If the result is "nothing needed", the line and its linked pickups are deleted from the cart without a prompt.

4.12 Automatic order proposal and hit lists [GENERIC]​

  • Trigger: choose a supplier for a new cart or order, then "With evaluation".
  • Article selection:
    • Vendor: a manufacturer for a direct order.
    • Supplier (offers only): only that supplier's offers; option "only cheapest offers" keeps offers that are the cheapest across all vendors.
    • Include free-choice, visible-choice and prescription-only articles (each a checkbox, default on).
  • Quantity rules:
    • Dispo days and evaluation-period overrides as in 4.11.
    • Deduct stock, cart lines and order lines.
    • Minimum order quantity: only articles whose computed demand is at least this value.
    • Quantity smoothing: round the computed total up to a multiple of N (for example 5 or 10). The original percentage split of demand is kept when distributing.
    • Consider overstock: reduce the order by the overstock.
  • Processing: "edit hit list first" shows the list; otherwise lines go straight into the cart or order and the user can add more.
  • POS pharmacies: proposals come from statistics and stock.
  • POR or mixed stock keeping: all POR and non-stocked articles of the vendor are listed with stock 0 and proposal and quantity 1. Manual review is expected.
  • Hit list content:
    • Selection boxes (all ticked initially).
    • Columns: restrictions, name, dosage form, pack size, standard pack size (N1/N2/N3, "nb" not covered by the pack-size regulation, "nt" larger than the largest reference size), PZN, list price, vendor/supplier, total stock, proposal, editable quantity.
    • Footer for selected lines: delivery value, article count, pack count.
    • Detail area: statistics, article info and price table.
  • Hit-list actions: edit quantity (the value and offer table recalculate); save the list; article details; print (all or marked lines, with or without statistics); select all; create cart (when started from a new cart) or create order (when started from a new order) from the marked lines.
  • Saved hit lists: reopened from the cart or orders overview. Each shows creation date, supplier, last edit and editor, a joint flag and a staleness icon (more than 48 h). They are deleted automatically once converted.

4.13 Online availability inquiry and online order from the cart [GENERIC] (MSV3 is DE-specific)​

  • Inquiry: asks the cart's supplier for the entered quantities only. Deliverability icons appear per line.
  • Online order: orders at once. If the cart's supplier cannot deliver, lines reported deliverable elsewhere can be moved into a cart of a deliverable wholesaler. When several can deliver, the preferred wholesaler is used.
  • Locking: an online order locks the cart.

4.14 Ordering: release, timing and transmission [GENERIC]​

  • Automatic release: if the supplier's send parameters say carts are set ready-to-send automatically, no manual step is needed. The supplier's cart is sent actively at the order cut-off time.
  • Manual release: select the cart and choose Order.
    1. Threshold check: if the minimum order value or minimum pack count from the condition agreement is not reached, an information message appears. It is a warning, not a hard block.
    2. Choose the transmission type:
      • Set ready-to-send: queue the cart for its order time. If already queued, the same option reads "remove ready-to-send". It can be revoked until sent.
      • Send actively: MSV3 now.
      • Send with own order identifier: MSV3. All lines go into one sub-order with a user-defined ID instead of the standard sub-orders. Uses: an "emergency duty" box to dip into overnight and return the rest; or "procure-on-demand items to stock" captured separately from daily business. The number of IDs per order type is limited by the contract's free order identifiers; beyond that, items arrive in the normal order.
      • E-mail: opens a new message with the order attached. Requires the pharmacy's SMTP account settings, which are verified by sending an automatic test mail to the sender address when saved.
      • Fax: through a web-fax service. The fax number comes from the supplier contact, is editable, and must be formally valid before OK is enabled. An optional note is printed under the order number. A preview is shown, then the fax is sent. Delivery status is checked in the provider's fax journal. On failure, reset the order status in the Orders tab and resend. A special fax form exists for health-food-shop articles.
      • Mark as ordered only: no transmission; the cart simply moves to Orders. Use for orders placed by phone or with a sales rep.
    3. Direct suppliers: enter the expected delivery date. Later quantity optimisation of following carts covers demand up to this date. For MSV3 direct suppliers with maintained delivery parameters, the computed delivery time is shown.
    4. Transmission: the cart becomes an order. The expected delivery date is the next day, or per the lead time in the supplier contact.
  • After the cut-off: a manual MSV3 order placed after the supplier's cut-off shows an information message that delivery on the next run is not guaranteed. The user decides what to do.
  • Errors: a transmission-error icon appears when credentials are missing or wrong, or when no send-status response arrives within 30 minutes. The user must acknowledge the response before the cart can be edited again.
  • Supplier responses: unavailable items (defects) are processed in the responses screen. Alternatively, config "auto-rebook shortages" moves them automatically to another cart or to the defect note.
  • Defect-note automation: when automatic checking and ordering of defects is configured, items that are deliverable but excluded from immediate online ordering (too expensive, blood product, narcotic) are placed in the cart of a deliverable supplier and marked with an icon.

4.15 Supplier turnover versus target [GENERIC]​

  • Data source: a monthly turnover target set in the supplier's condition agreement.
  • Display: per supplier: target met or missed icon, name, target, approximate current turnover (calculated per the condition-agreement settings), difference in EUR and in %.
  • Auto-display: can pop up daily on a chosen workstation (config "show supplier turnovers daily").
  • Permission: see section 8. Without the right "see turnovers" only the differences are shown.

Part B: Multi-branch purchasing (Filialenfunktionen)​

4.16 Network constellations [GENERIC]​

  1. Central delivery, central invoice: the ordering pharmacy receives goods and invoice, then transfers each branch's share.
  2. Decentral delivery, central invoice: the supplier ships each share to its pharmacy. Each pharmacy books its own goods receipt. The ordering pharmacy receives the invoice and value-books it. Branches are charged through internal billing without a physical transfer.
  3. Decentral delivery, decentral invoice (splitting): the joint order is split into local orders. Each pharmacy is delivered and invoiced directly.
  • Prerequisites: each member pharmacy exists as tenant, supplier and customer contact; the customer role has invoicing permitted and net-price invoices; order data exchange between systems is configured.

4.17 Joint cart and joint order [GENERIC]​

  • Creation: "New joint cart" (cart overview) or "New joint order" (orders overview; for example when goods were already ordered by other means). Choose the supplier, then "without evaluation" or "with evaluation" (joint proposal, 4.18).
  • Joint cart header: a dispo-days field, meaning the minimum days all participating pharmacies should be covered.
  • Entry mode chosen before entering items:
    • Quantity optimisation: the system computes a quantity per pharmacy from current stock and sales frequency. The optimisation model of the executing pharmacy always applies. Example: A 0, B 11, total 11.
    • Fixed quantity: the given number is the total, distributed so the goods sell through fastest, considering each pharmacy's stock and sales frequency. Example: 20 split as 5 and 15.
  • Per-line detail per pharmacy: participation checkbox, storage status, AMO, BMO, available stock, days of stock, proposal, quantity, coverage and an overstock notice ("after the dispo time this pharmacy would still have stock left; reduce the order and use stock balancing"). Line totals: total stock, total quantity (with a refresh button to redistribute), total coverage. Price table.
  • Quantity editing:
    • Changing one pharmacy's quantity changes the total and leaves the other shares unchanged. Example: 0 raised to 20 takes the total from 30 to 50.
    • Only participating (ticked) pharmacies are editable.
    • Unticking a pharmacy sets its quantity to 0, locks it and reduces the total; the other shares stay.
    • Ticking a previously excluded pharmacy and entering a quantity raises the total. Ticking it without a quantity and pressing refresh redistributes the total across all participants by need.
    • Changing the total and pressing refresh recomputes the distribution.
  • Branch view: on the next synchronisation each participating branch sees a mirror cart or order. It is grey, labelled with the executing pharmacy's code after the supplier name, read-only, and contains only that branch's lines and quantities. After ordering it moves to the branch's Orders tab. After the branch books its goods receipt it moves to the Archive.
  • Shortages: if a supplier response reports a shortage on a joint line, the distribution across pharmacies is adjusted automatically. The order entry window shows the expected quantity under "open" and "total quantity".
  • Edit restrictions: with decentral delivery only the ordering pharmacy may edit, and only until any pharmacy starts goods receipt.
  • Icons: ordering pharmacy, pharmacy with a share, joint purchase, and variants for a purchasing cooperation (DIREKTplus) including a decentral-delivery variant where the branch sees only its own share.

4.18 Joint automatic order proposal [GENERIC]​

  • Same as 4.12, plus:
    • Deductions of stock, cart lines and order lines run across all evaluated pharmacies.
    • The minimum order quantity applies to demand summed over all pharmacies.
    • Quantity smoothing basis is selectable: the total order, or each local share. If no value is given, each pharmacy's stored optimisation factors apply.
    • "Consider overstock" reduces the total by the sum of the pharmacies' overstocks.
    • Pharmacy selection: list of network members (with codes) to include or exclude. This can be revised per article in the hit list.
    • For POR pharmacies the stock and overstock options are disabled, and stock = 0 and quantity = 1. POS pharmacies in the same network still get real stock and optimisation.
  • Distribution: follows each pharmacy's computed demand for the dispo time.
  • Hit-list actions: edit shares; discard changes (restore the system proposal for the selected article); open branch details (4.19); article details; save; select all; print (4.25); create a joint cart or order, or a local cart or order. The local option lets one pharmacy act as central warehouse: it buys for everyone's demand and transfers later when needed.
  • Info area per pharmacy: approximate delivery value, article count, pack count.

4.19 Branch article statistics [GENERIC]​

  • Access: from the joint cart ("branch details") or the joint hit list ("F&P details"). An article navigator browses the last hit list.
  • View 1: per pharmacy participation, status, AMO, BMO, available stock, days of stock, proposal, quantity, coverage and overstock, plus monthly purchase and sales statistics. The default window is the last 12 months; buttons step ±1 month or ±1 year within a maximum of 3 years (two previous years plus the current year to date).
  • View 2: per pharmacy optimisation master data: fixed order quantity, maximum order quantity, maximum stock, variable minimum stock, fixed minimum stock, stock, proposal, share, plus the same statistics.
  • Saving: share and participation changes are taken into the hit list on OK. Columns are configurable in both views.

4.20 Move a local cart into a joint cart [GENERIC]​

  • What: a branch can move a whole local cart (from the overview) or selected lines (option "apply to all selected") into an existing joint cart. If there is none, a message appears.
  • Rules:
    • Quantities add up when the article is already in the joint cart.
    • Other pharmacies' shares are untouched; the moved quantity (including back-orders) is added to the own pharmacy's share.
    • Back-orders travel along, so a joint line can carry customer back-orders. These are shown under a "Customer orders" tab at joint goods receipt.
    • Shares stay manually editable afterwards.

4.21 Decentral delivery with central invoice [GENERIC]​

  • Configuration:
    • Per direct supplier: supplier contact, Settings, Joint purchase, "deliver to each pharmacy, invoice to own pharmacy".
    • Per single order: toggle "central/decentral delivery" from the cart or orders overview. Allowed only while no pharmacy has started goods receipt.
  • Flow:
    1. Joint cart and order as usual.
    2. Each pharmacy receives its share directly and does goods receipt, stock booking and difference processing. It does not need to wait for the invoice.
    3. Once any branch starts goods receipt, the order is frozen (icon). Another icon tells the ordering pharmacy that a branch is still waiting for goods after a partial delivery.
  • Returns from differences:
    • The ordering pharmacy handles all returns and credit notes centrally, because the credit goes to it.
    • The branch can only ship the return and print a return slip; it cannot edit (icon).
    • Returned items are not billed internally, so the branch needs no credit monitoring. These returns are hidden at the branch and passed to the ordering pharmacy (icon).
  • Central value booking:
    • Enter direct-supplier conditions: an order discount at booking time (when several deliveries are booked together, only on the whole invoice, not while composing the positions) and article discounts.
    • Then "joint value booking": all (partial) stock-booked deliveries of the same joint order are preselected.
  • Internal billing: an immediate invoice is generated automatically for each branch share. No transfer is created. In the invoicing module the job shows as delivered and fully invoiced, flagged "branch order with external delivery". The invoice notes that delivery is separate.
  • Credits: handled by the ordering pharmacy as value credit, goods credit or destruction, per the supplier agreement.

4.22 Splitting a joint order [GENERIC]​

  • When: some or all pharmacies should be delivered directly and book their own receipt.
  • Irreversible.
  • Steps:
    1. Create the joint cart.
    2. Print the order log for the pharmacies that will be split off, to hand to the supplier's rep.
    3. Order.
    4. The joint order appears in all receiving pharmacies (black for the orderer, grey read-only for the others).
    5. In the ordering pharmacy choose "Split order". The dialog has two lists, "joint" and "local", always pre-filled with the current order's participants even if a different default was saved.
    6. Move pharmacies to "local". Optionally "save as default" for future splits.
    7. Confirm the irreversibility warning.
    8. Print the order log "entire order with distribution view" for the remaining joint delivery; split-off pharmacies show quantity 0.
  • Rule: if only one pharmacy is left under "joint", the joint order is dissolved and every pharmacy gets a local order.
  • After the split: local orders lose the joint flag; joint orders keep it (grey where another pharmacy is delivered).

4.23 Joint goods receipt and redistribution [GENERIC]​

  • Ordering pharmacy:
    • Goods receipt on the joint order, the same as a standard receipt but without back-order or scheduled info.
    • Per article: total stock (including branches), delivered quantity, and per pharmacy status, AMO, available stock, days of stock, original split, a proposal recomputed from the delivered quantity, and the final quantity.
    • The distributed total must equal the delivered quantity; a warning appears otherwise.
    • Capture by scan or PZN, by electronic import (for example from the picking robot; branch items already stored are retrieved again), or by taking quantities from the order (branch items are not retrieved because they were never stored).
  • Booking the receipt:
    • Creates one invoicing job per receiving pharmacy.
    • Delivery notes are generated and printed automatically.
  • Redistribution:
    1. Pick goods by delivery note and send goods and notes.
    2. The receiving branch books goods receipt against an automatically created transfer order. Expiry date and price are pre-filled from the ordering pharmacy's invoicing job, and the branch's customer discount model applies.
    3. Changes to the distribution during the orderer's receipt show as differences at the branch.
    4. Branch differences follow transfer rules: no return to the supplying pharmacy or to the supplier.
    5. The branch stock-books, or value-books when the orderer's invoice is available. Value-booked receipts in the archive show the ordering pharmacy as supplier.
    6. Changes to the orderer's invoicing job do not change the branch's order.
  • Billing: at an agreed time the ordering pharmacy invoices each branch through the invoicing module.

4.24 Inter-branch transfers [GENERIC]​

  • What: a transfer (Umlagerung) is the technical basis of nearly all goods movement between network pharmacies.
  • Three triggers:
    1. The receiving pharmacy orders from the branch.
    2. The supplying pharmacy pushes.
    3. Automatically, from a joint-order share when the joint receipt is booked.
  • Eligible articles: only drug-database articles and self-created articles with storage status POS.
  • Receiver-initiated (A needs, B has):
    1. A creates a cart with supplier = B and enters the items. The line price is B's own purchase price; if B has none, the price is 0.
    2. A orders. This sends the transfer, which can be triggered only once: later edits to A's order do not re-send, and the status cannot be manually turned back from order to cart. Allow about 5 minutes for transmission.
    3. B receives an invoicing job automatically and an Infocenter notice on all workstations (with a count if there are several; optional sound). The invoicing overview must be refreshed by hand.
    4. B creates delivery notes. With a robot, the items are retrieved first. B then documents the batches; delivery notes print with batch data and the goods are staged. Prices updated after B's goods receipt flow onto the delivery note and into both systems.
    5. Sync rule: after the delivery notes exist, every change B makes to the job (new line, price, quantity, deletion, info text, cancellation) is pushed to A's order as a supplier-style response with a derived reason: quantity correction / new entry / deletion / cancellation. This stops once A has booked goods receipt; later changes are ignored. A shortage reported by B can be processed by A like a wholesaler response only once; repeated shortage reports are display-only.
    6. B ships and A books goods receipt.
  • Supplier-initiated (B pushes to A):
    1. B creates an invoicing job with customer = A. The price comes from A's customer discount model. Each branch initially has a discount model named "Umlagerung" (transfer), which can be changed.
    2. B creates delivery notes (robot retrieval and batch documentation as above).
    3. An order appears automatically at A, and later quantity changes by B reach A as responses.
    4. A books goods receipt.
  • Remote control: either flow can be run entirely from one pharmacy via remote access to the other's system.
  • Returns to a branch: not possible as a real return; do a transfer back.
  • Serialisation [DE-SPECIFIC]: transfers do not verify or deactivate securPharm pack identifiers. Only batch and expiry are asked, if configured in the branch customer contact's batch-documentation setting.

4.25 Seeing other branches' stock [GENERIC]​

  • Article search: a "Branches & Partners" view adds one stock column per pharmacy, headed by its short code, with the preferred branch placed next to the own pharmacy. Other views show a status icon when a branch has stock.
  • Article details: "stock info branches & partners" shows stock info for all members.
  • Cart: "Branches" shows member stock from inside the cart.
  • Price tables: list branch pharmacies that have the article (with price) as possible sources.
  • Sales statistics: article sales details have separate tabs for transfers to branches and for transfers to partners (for example within a buying group). Transfers are excluded from the pharmacy's own sales statistics and do not count in monthly statistics. Slow-mover and new-listing checks also ignore sales to branches.
  • Option "internal goods-exchange billing" (branch/partner master data): internal invoices are net, without VAT, in a separate invoice-number range, so ordinary gross invoices stay gap-free. It also switches on net-price invoices.
  • Customer discount model: the branch's model is usually purchase price (+ VAT). "Prefer the discount model's price" must be on; otherwise a sale without a sales price could come out at 0.
  • Billing forms: immediate invoices (decentral delivery), invoices per joint receipt, or a collective invoice for transfers at an agreed time.
  • Accounting export: internal movements appear separately in the accounting export (DATEV).
  • Batch documentation [DE-SPECIFIC]: legally required when drugs pass between pharmacies (German pharmacy operating regulation, ApBetrO §17(6c)). The supplying pharmacy records it and passes it to the receiver.

4.27 Remote printing [GENERIC]​

  • What: when working remotely on a branch's system, a single branch workstation can be set to use the own pharmacy's network printer as its preferred printer. This is a workstation-scoped setting; answer "no" to applying it to all workstations.
  • Fallback: the preferred printer is used whenever it supports the paper format; otherwise another printer is chosen automatically.

4.28 Mixed-product networks [vendor-specific]​

  • Scope: with members on the vendor's other product line (XT), only stock data is exchanged (POS stock, negative stock, expiry dates; expiry is not yet displayed). Changing an item from non-stocked to POS triggers a stock reconciliation.
  • Not supported: transfers, joint purchase, stock balancing and contact exchange.
  • Billing: internal billing still works. A cart to an XT branch creates no transfer order but invoices correctly.
  • Gaps: purchase price and AMO are blank in stock info; no offer list is shown for an XT branch; self-created articles are not exchanged.
  • General idea: a degraded interoperability mode for heterogeneous systems.

5. Workflows​

5.1 Daily wholesaler order (automatic carts)​

  1. Sales, the defect note, scheduled-note due dates and assortment control drop demand lines into each supplier's cart. Cart determination and supplier optimisation pick the cart.
  2. Lines are assigned to sub-orders by priority. Customer-linked lines carry their origin markers.
  3. Before the cut-off, a user opens the cart, works through the order-queries tab (offers, cold, narcotic, multiple order and so on), optionally re-runs quantity optimisation and/or "recalculate queries", and adjusts lines.
  4. If the supplier is set to automatic ready-to-send, the cart is sent at the order cut-off. Otherwise the user chooses Order, then a transmission type.
  5. The cart becomes an order. Supplier responses arrive; defects are processed or rebooked automatically. Goods receipt follows in the Orders tab.

5.2 Manual cart, for example a direct (manufacturer) order​

  1. New, then choose a vendor (it gets the supplier role if it has none), then OK; or choose "With evaluation" for a vendor-based proposal.
  2. Enter lines (quantity optimisation or fixed quantity), check offers in the price table, check the order thresholds.
  3. Order, choose the transmission type (MSV3 / e-mail / fax / mark as ordered), enter the expected delivery date. Quantity optimisation then covers demand up to that date.

5.3 Deferring a line​

  1. Select the line and choose "scheduled order".
  2. If the line has several parts, untick the parts that should stay (for example customer back-orders).
  3. Enter a date (default: 1st of next month) or a recurring rhythm. The lines move to the scheduled-order note, keeping their customer links, and return to a cart when due.

5.4 Branch sourcing instead of buying​

  1. An item is entered in a wholesaler cart, and another member has it flagged slow mover, overstock and so on. The branch-sourcing query appears (if enabled).
  2. Choose full or partial transfer from the selected pharmacy. A transfer line is created in a cart addressed to that pharmacy; the rest stays.
  3. Ordering that cart triggers a receiver-initiated transfer (5.7).

5.5 Joint purchase with central delivery​

  1. Executing pharmacy: New joint cart, choose a supplier, then "with evaluation" (choose the pharmacies, dispo time, smoothing and so on) or "without evaluation" plus the quantity mode.
  2. Review the per-pharmacy shares (AMO/BMO, stock, coverage, overstock), branch statistics and fixed or maximum quantities; edit shares, include or exclude pharmacies, refresh the distribution. Branches may add their local carts or lines.
  3. Print the order log or proposal (overall with distribution, or per branch). Order. Mirror orders appear at the branches.
  4. Goods arrive at the executing pharmacy. Run joint goods receipt and adjust the distribution to the delivered quantities (the sum must equal the delivery).
  5. Book the receipt. This creates invoicing jobs per branch and prints delivery notes.
  6. Pick and ship per delivery note. Each branch receives against its automatic transfer order and books it. Internal invoices follow at the agreed time.

5.6 Joint purchase with decentral delivery​

  • Central invoice: configure the supplier or order for decentral delivery. Order. Each branch receives and books its own share. The orderer value-books the supplier invoice with joint value booking, which generates an immediate invoice per branch. Returns are handled centrally.
  • Split invoicing: after ordering, split the joint order (irreversible). Split-off pharmacies receive local orders and are delivered and invoiced directly. Print order logs before and after the split for the supplier's rep.

5.7 Inter-branch transfer​

  • Pull: A creates a cart for supplier B and orders it (once). B gets an invoicing job and a notice, creates delivery notes with batch documentation and ships. Changes are synced to A as responses until A books receipt. A books goods receipt. B bills periodically with a collective invoice.
  • Push: B creates an invoicing job for customer A and creates delivery notes. An order is auto-created at A. B ships. A books goods receipt.

6. Business rules and calculations​

  • One supplier per cart. A line whose supplier differs from the cart's is moved to that supplier's cart, which is created if needed.
  • Sub-order assignment: the first matching type wins, in this order: narcotics, blood products, cold-chain (≤ 8 °C), pickups, robot, main alphabet, visible choice, free choice, normal. A custom order identifier collapses all of them into one.
  • Offer qualification: an offer applies only if its minimum quantity is ≤ the entered quantity. The automatic cheapest/optimal choices never raise the quantity; a manual pick may raise it to the offer quantity. A 0 % special offer is valued at the list price.
  • Cheapest vs optimal supplier: cheapest considers all suppliers with stored conditions and offer lists. Optimal considers only those explicitly enabled for supplier optimisation and treats offer lists as part of conditions.
  • Projected effective price = list price after the supplier's condition agreements and offer lists. Saving = list price − effective price (currency and %).
  • Preferred offer list: when an article is on several lists, the preferred list determines the price even if another list is cheaper.
  • Order-quantity optimisation overrides: a manual dispo time disables the article's minimum stocks for that run and does not shorten direct-order dispo time. Evaluation periods are limited to the current year and the two previous years. Deductions of stock, cart quantities and open-order quantities are each switchable. A re-run that yields zero deletes the line and its linked pickups silently.
  • Proposal filters: minimum order quantity (demand ≥ value, summed across pharmacies for joint proposals). Smoothing: ceil(total / N) × N, or per local share; the distribution follows the original demand percentages. Overstock is subtracted when chosen.
  • POR handling in proposals: stock 0, proposal 1, quantity 1. POR items are excluded from joint proposal printouts.
  • Joint distribution drivers: BMO (sales including no-sales and cancellations, weighted by the executing pharmacy's month weights, using sales from all members) and available stock (excluding reservations). Higher BMO means a larger share; higher stock means a smaller share. Days of stock = ∞ when BMO = 0. Total coverage is based on the sum of AMO, not on the dispo time.
  • Share editing: editing one share changes the total and keeps the others. Excluding a pharmacy zeroes its share. Refresh redistributes the total by need.
  • Joint receipt distribution: the sum of shares must equal the delivered quantity.
  • Min/max article parameters: an order is triggered when stock < max(fixed min, variable min). The fixed order quantity (or a multiple) is used and must be ≤ the maximum order quantity. Optimised quantities are capped at the maximum order quantity. Fill-up never exceeds the maximum stock.
  • Threshold warnings: minimum order value and minimum pack count are warned about at ordering time (not blocked). Ordering after the cut-off is warned about (delivery not guaranteed).
  • Transmission error: no status within 30 minutes, or bad credentials, sets the error state. Acknowledgement is required.
  • Transfers:
    • Only drug-database articles and self-created POS articles.
    • The price at the receiver = the supplier's own purchase price, or 0.
    • Triggered once.
    • The supplier's later edits are synced with reason codes until the receiver's goods receipt.
    • A shortage response can be processed only once.
    • No returns: reverse with a transfer.
    • Batch documentation is mandatory.
    • No serialisation verification or deactivation.
  • Slow mover: "not sold in X days" (configurable), with the 5-day rules in 4.10.10. Permanent-assortment items are exempt; sales to branches are ignored.
  • New stock listing: a non-stocked, non-procure-on-demand article with ≥ N sales in M months.
  • Returned article: returns with reasons expired, short delivery or credit follows are excluded; buy-back orders are excluded. The take-out quantity per return is ≤ that return's quantity.
  • Fixed-supplier query: suppressed for back-orders and for recurring scheduled lines. A pin that comes from a model cannot be deleted from the query.
  • Hit lists: stale after 48 h (unless the evaluation period excludes the current month); deleted on conversion.
  • Order log stock column: POR shows "A", POS shows the quantity, non-stocked or no status shows 0. Sorted alphabetically.
  • Fax reprint date: a cart printout uses the current date and time; an order printout uses the original order date and time.
  • Internal billing: net, no VAT, separate number range, net-price invoices implied.

7. Configuration and settings​

ParameterScopeEffectDefault
Filter cart overviewSystem parameter, GeneralInitial filter of the cart overview (wholesalers / all orders and so on)Wholesalers only
Show order queries on entrySystem parameter, "order articles" pageQueries pop up while entering lines; re-show the offers query after quantity changesnot stated
Auto-rebook shortagesSystem parameter, "order articles" pageSupplier-reported defects are moved automatically to another cart or the defect note instead of manual response processingnot stated
Order query for offer articlesSystem parameter, Order queriesEnables 4.10.1not stated
Show projected effective EKConfigurationShows the effective price and renames the offers query to "cheaper suppliers"not stated
Order query for discontinued articlesSystem parameter, Order queries4.10.2ON
Order query for AV articlesSystem parameter, Order queries4.10.3ON
Order query for direct purchaseSystem parameter, Order queries4.10.4ON
Order query for fixed-supplier articlesSystem parameter, Order queries4.10.5not stated
Order query for narcoticsSystem parameter, Order queries4.10.6ON
Order query for cold itemsSystem parameter, Order queries4.10.7ON
Order query for multiple ordersSystem parameter, Order queries4.10.12ON
Order query for recalled articlesSystem parameter, Order queries4.10.14ON
Query on possible branch sourcing (+ which storage flags of other branches to evaluate)System parameter, Order queries 24.10.8OFF
Order query for slow moversSystem parameter, Order queries 24.10.10ON
Slow mover if not sold in the last X daysArticle-management system parameterSlow-mover thresholdnot stated
Order query for new stock listings; period in months; minimum number of salesSystem parameter, Order queries 24.10.11not stated
Order query on import search; import search from x EUR saving; from x % savingSystem parameter, Alternative searches4.10.9not stated
Demand statistics and optimisation with sales dataGoods logistics > Optimisation > POR storage status / stock keepingStatistics based on history and no-salesnot stated
Show supplier turnovers dailyWorkstation (notices)Auto-popup of turnover versus targetoff (implied)
Supplier: activated sub-ordersSupplier contact, SettingsWhich sub-orders exist for that suppliernone
Supplier: automatic ready-to-sendSupplier contact, send parametersCarts sent automatically at the cut-offnot stated
Supplier: free order identifiersSupplier contact, contract dataMaximum number of sub-orders / own IDs per order type (MSV3)per contract
Supplier: minimum order value, minimum pack count, monthly turnover target, agreed average Rx pack priceCondition agreement, GeneralThreshold warnings, turnover display, cart flagnone
Supplier: joint purchase "deliver to each pharmacy, invoice to own pharmacy"Supplier contact, SettingsDecentral delivery with central invoice for all joint orders with that supplieroff
Per order: central / decentral deliveryCart or orders overview actionOverrides the delivery mode of one joint order (before any goods receipt)from the supplier setting
Split defaultSplit dialog "save as default"Pre-selects the local/joint split for the next joint ordernone
Line hint codes availableGoods-logistics settingsWhich hint codes can be chosennot stated
SMTP account (sender, authentication, server)System maintenance, e-mail sendingEnables e-mail ordering; a test mail is sent on savenone
Fax serviceInterface configurationEnables fax ordering via a web-fax providernone
Network member: internal goods-exchange billingBranch/partner contact, master data, further dataNet, no VAT, separate invoice-number rangeset up by vendor
Network member customer role: invoicing permitted, invoice with net prices, discount model + "prefer model price", batch documentation for medicinesCustomer contactPricing and documentation of transfersset up by vendor (discount model "Umlagerung")
Preferred branches rankingContacts > Branches & Partners > classificationOrder of branch stock columnsnone
Visibility of exchanged contactsNetwork contact settingsWhether other members' contacts show in supplier searchnot stated
Preferred printerWorkstation, printer settingsRemote printing to the own pharmacylocal printer
Cart-determination models / quantity-optimisation modelSeparate modulesSupplier routing (for example narcotics never in late orders), dispo time, month weights—

8. Roles and permissions​

  • See turnovers (Umsätze sehen), rights group Contacts-Supplier: needed to see absolute supplier turnover and the target. It is pre-granted to the roles Manager (Leiter) and Turnover officer (Umsatzbeauftragter). Users without it see only the differences in EUR and %.
  • Joint purchases: only the executing (ordering) pharmacy can edit a joint cart or order; branches see read-only mirrors. With decentral delivery, editing stops once any goods receipt has begun.
  • Returns from decentral joint deliveries: branches may only ship them; the ordering pharmacy edits and credits.
  • Transfers: only the supplying pharmacy edits the invoicing job; the receiver's order cannot be moved back to cart status.
  • Locking: a cart is exclusive to one user while edited, queried or sent.
  • No other permission names appear in these pages.

9. Integrations, hardware and external services​

  • MSV3 [DE-SPECIFIC] (general idea: a standard wholesaler ordering and availability web service): active sending, ready-to-send fetch, own order identifiers, sub-order numbers, availability inquiry, cut-off and delivery-time reporting, responses, error status after 30 min.
  • Remote data transfer fetch (DFÜ): the supplier collects ready-to-send carts at the fetch time.
  • E-mail (SMTP) ordering with an automatic configuration test. Web-fax providers for fax orders, with a fax journal kept at the provider.
  • Online service providers for availability of imports and alternatives.
  • Picking robot (Kommissionierautomat): robot sub-order; retrieval of transferred goods; electronic goods-receipt import.
  • Document management: order logs and fax forms can be stored as PDF.
  • Network data exchange between member pharmacies' systems: orders and transfers (about 5 minutes latency), stock and storage flags, contacts, synchronisation of joint carts and orders.
  • Remote access to branch systems, with remote printing to the own pharmacy's printer.
  • Accounting export (DATEV) [DE-SPECIFIC] (general idea: export to an accountant's ledger): internal movements listed separately.
  • securPharm [DE-SPECIFIC] (general idea: anti-counterfeit pack serialisation): not applied to internal transfers.
  • National drug database (ABDA) [DE-SPECIFIC] (general idea: a national product master with list prices, statuses and storage temperatures): list price, distribution status, storage temperature, vendor list.

10. Printouts, reports and exports​

  • Order log (Bestellprotokoll) for a cart or order: alphabetical; stock column shows "A" (POR), the quantity (POS) or 0 (non-stocked). Preview, printer settings, PDF to document management.
    • Joint version: entire order, optionally with a distribution view (orders only, not carts), or one printout per branch share (all branches ticked by default).
    • Used to brief the supplier's rep before and after splitting, and to distribute goods after receipt.
  • Fax order form: includes addresses and an optional note to the supplier under the order number. It can be printed or sent through the fax service. The form can be customised by vendor support; with a custom form the note position must be configured by support. A special form exists for health-food-shop articles. A reprint for a cart shows the current date and time; for an order, the order date and time.
  • Labels from the cart, order or receipt print menu. When an order is split into sub-orders, labels are printed for all sub-orders automatically.
  • Order-proposal printout: all lines or only marked lines, with or without statistics. Joint version: entire order (optionally with distribution) or per-branch shares; POR excluded.
  • Delivery notes for joint-purchase redistribution and transfers, including batch documentation.
  • Internal invoices: immediate invoice per branch share (decentral delivery); invoices per joint receipt; collective invoice for transfers. Net, separate number range.
  • Turnover versus target screen per supplier.

11. Dependencies on other modules​

  • Notepad: defect note and scheduled-order note, including order rhythm and the defect-note automation settings (other chapter).
  • Orders stage, processing of supplier responses, goods receipt, value booking, order discounts and article discounts, returns and credits (other chapter).
  • Order-quantity optimisation model, cart-determination and supplier-optimisation models, supplier conditions, offer-list management (other chapter).
  • Article master: storage statuses, storage locations, fixed supplier, min/max quantities, discontinued and slow-mover flags, successor and statistics transfer, batch documentation.
  • Assortment control (listing and delisting, defect automation).
  • Contacts: supplier, vendor, customer, branch/partner roles, discount models, preferred branches, phonetic and extended search.
  • Invoicing (Faktura): jobs, delivery notes, invoices.
  • Online inquiry and ordering; alternative and import search.
  • Sales and POS: pickups, back-orders and reservations drive cart lines and live quantity updates.
  • System settings, printer settings, e-mail and fax configuration, Infocenter notifications and sound signals.
  • Stock balancing between branches (Lagerausgleich) and cross-branch sales (separate topics).

12. Portability notes​

Generic, worth adopting for Shefa (pharmacies and drug warehouses):

  • A per-supplier cart as a staging object, with clear states (cart → queued → sent order) and exclusive editing locks.
  • Line origin tracking (stock replenishment vs customer back-order vs deferred) and automatic adjustment when the originating sale changes.
  • Rule-driven pre-order checks ("order queries") with per-rule toggles, a fixed processing order, re-validation before sending, and user-defined rules. Good rules to start with: cheaper offer elsewhere, duplicate on order, item in an open return, recalled or withdrawn with successor, discontinued, slow mover, new-stock candidate, cold chain or controlled substance to be delivered in opening hours, fixed supplier, available in another branch.
  • Offer and condition engine: projected effective price, offer quantity thresholds, preferred lists, "cheapest" vs "optimal" supplier.
  • Sub-orders by handling class (cold, controlled, customer orders, storage zone) so the supplier packs and invoices separately.
  • Quantity optimisation with days of cover, evaluation window, deductions and min/max parameters; saved and stale-marked proposal lists.
  • Multi-branch: joint purchase with demand-weighted distribution, central-warehouse mode, three delivery/invoicing set-ups, inter-branch transfers with a sync protocol and reason codes, branch stock visibility, internal billing at cost in a separate invoice series.
  • Supplier cut-off times, minimum order value warnings, turnover targets, and several channels (API, e-mail, fax, "mark as ordered" for phone or rep orders).

Germany-specific, with the underlying idea:

  • MSV3: a standard wholesaler API. Syria has no equivalent, so Shefa can define its own warehouse-ordering API between pharmacies and drug warehouses (both sides are on the platform), with order IDs per sub-order and an availability inquiry.
  • ABDA list price / PZN: a national product master with list prices. Use the Syrian drug registry or the platform's own catalogue with the official price list.
  • Narcotics query: controlled substances need in-person handover and documented chains. Generalise to "items with handover constraints only on staffed deliveries".
  • Import search: suggest cheaper equivalent packs (generics or parallel imports) at order time when the saving exceeds a threshold.
  • securPharm exemption, ApBetrO batch documentation: traceability rules for internal transfers. Keep batch and expiry on every inter-branch movement.
  • DATEV export, net internal invoices without VAT: a separate internal billing series, kept apart from taxable sales, exportable to accounting.
  • Red-Hand letters, aut-idem, fixed amounts: regulatory article flags. Show local regulatory notices instead.
  • DIREKTplus, XT interoperability: vendor-specific.

13. Open questions​

  • Order rhythms and delivery tours: these pages show fetch time, fetch day, cut-off and the late-order flag, but not how supplier order times or tours are defined, nor how automatic carts are opened and closed per tour. The supplier delivery and send parameters are documented elsewhere.
  • Distribution algorithm: the exact formula for distributing a joint quantity (BMO, stock, dispo time, "other factors") and for the per-pharmacy proposal is not given. The same applies to the precise effect of "refresh" after unticking a pharmacy: the text says refresh before saving gives no redistribution, which looks inconsistent with the include case.
  • Sub-order priority list: the text lists "remaining (normal)" with "e.g. main alphabet" although main alphabet is its own sub-order. It is unclear which wins.
  • Order type codes: the business meaning of SO, ST, VR and ZT (and how the supplier treats them) is not explained.
  • Minimum order value: confirmed only as a warning; whether ordering can proceed regardless is implied but not stated explicitly.
  • POR vs POS: exact semantics belong to the article-master chapter. Here POR stock is treated as 0 / "A".
  • Several defaults are not stated (offers query, fixed-supplier query, new-listing parameters, import thresholds, show-on-entry).
  • "Recalculate queries": it is not stated whether it also re-opens queries already answered with "keep".
  • Supplier change by projected price: the behaviour after detecting a tiered, negotiable or condition row is not described.
  • Custom order queries: their definition (Eigene Bestellabfragen) is in another topic; only their priority is known here.
  • DIREKTplus variants: purchasing-cooperation icons are shown without workflow detail.

14. Source pages​