Skip to main content

Delivery service, sales overview, customer apps and portals, web-shop connection (Liefermanagement / Botendienst, Verkauf, App & Web „Meine Apotheke“, Connect-Produkte, Webshop)

1. Purpose and scope​

This chapter covers everything in IXOS that moves goods or orders between the pharmacy and people outside the shop counter:

  • Delivery management (Liefermanagement, also called Botendienst / courier service). Planning courier tours (one-time and recurring), automatic assignment of sales to tours, packing of deliveries with scan checks, a counter-scan of shipping containers for care-home and clinic supply (Pro edition), handing the tour to the courier on paper or via a mobile web app (digital delivery list), settling money and delivery status after the tour, archiving and statistics, and shared tours across a branch network.
  • Sales menu overview (Verkauf). A one-page map of the sales modules (POS, invoicing, open items, prescription management, cost estimates, delivery management, sales management, prescription requests, blister management).
  • Customer app and web portal ("Meine Apotheke" App & Web). A pharmacy-branded patient app and portal: registration, ordering (search, pack scan, prescription photo, e-prescription), offers, bonus display, assortments, messages, digital receipts, intake plans, pickup stations, courier option, online payment (PayPal), and use across a pharmacy network. Also how the pharmacy processes these orders in IXOS.
  • B2B "Connect" portals. Arzt.connect (doctor's practice orders practice supplies), Klinik.connect (hospital wards order supplies), Rezept.connect (care homes send prescriptions in advance by scanner), Heim.connect (care homes order medicines/supplies).
  • Other satellite products. Media.connect (in-store TV / customer display content), IXOS.team (staff mobile app: learning, chat, clinic packing, inventory counting), IXOS.view (reporting portal), Artikelscan.mobil (handheld goods-receipt scanner).
  • Web-shop connection. Third-party pharmacy web shops connected through a standard interface (ADAS) or a vendor-specific interface (Mauve): pickup pre-orders, pre-orders with prescription image, mail-order (shipping) orders, coupons, reporting, goods-logistics links, tub control at goods receipt.

A common design pattern runs through the app, portal, connect and web-shop features: every incoming online order becomes a task in the order list (Bestell-Liste) of the Notes module, pops up at all workstations, and is "executed" by staff into a POS sale (reservation, customer not present) or an invoicing order. From there the normal back-order, pickup and courier processes take over.

2. Key concepts and terms​

German termEnglishMeaning
Liefermanagement / BotendienstDelivery management / courier serviceModule for planning, packing, delivering and settling courier tours.
Liefermanagement Basis / ProBasic / Pro editionBasic: licence "IXOS U5 Botendienst (IXOS.Liefermanagement Basis)". Pro: for high volumes and home/clinic supply, billed by beds supplied per month; licence sizes S, M, L mentioned for counter-scan.
Tour (einmalig / ständig)Tour (one-time / standing)A courier run at a given date/time. Standing tours are templates that generate dated instances.
TourstationTour stationA stop on a tour (level 2): a single recipient or a group (home, home unit, clinic, clinic ward).
Gruppe / GruppenstationGroup / group stationSeveral recipients delivered together (e.g. all residents of a home or a home unit).
StartapothekeStart pharmacyThe pharmacy that created a shared branch tour; route starts there.
FilialtourBranch tourA tour shared by several pharmacies of a branch/partner network.
Planen/Packen, Liefern/Abrechnen, ArchivPlan/Pack, Deliver/Settle, ArchiveThe three tabs of the module.
Botenaufgabe (ständige)Courier task (standing)A non-sale errand on a tour (e.g. collect something); standing = recurring.
TourvorbereitungszeitTour preparation timeLead time before a tour's departure within which new sales are pushed to a later tour. Separate values for stock goods and ordered goods.
Lagerware / BestellwareStock goods / ordered goodsItems in stock vs. items that must first be ordered from a wholesaler.
Gesamtlieferung / TeillieferungTotal delivery / partial deliveryWhether a sale with stock and ordered goods is delivered in one go or split.
Automatischer TourvorschlagAutomatic tour proposalPreselection of a tour in the sale's delivery dialog.
Bevorzugte TourPreferred tourStanding tour stored on the customer or home master data.
Packen im BackofficePacking in back officeParameter deciding where/when courier printouts are produced and whether packing is a separate back-office step.
TourpacklisteTour pack listCustomer-independent list of all unpacked stock items needed for a tour.
Gegenscan / VerpackungseinheitCounter-scan / packaging unitScanning container labels (crates, tubs, bags) in addition to items to prove each item went into the right group's container (Pro).
Auslagern (Kommissionierer)Retrieve (from picking robot)Trigger dispensing of items from an automated picking robot at packing time.
ErsatzartikelSubstitute itemItem delivered by the supplier instead of the ordered one.
Lieferliste (digital / Ausdruck)Delivery list (digital / printed)The courier's run sheet; digital version is a mobile web app.
TourprotokollTour logData the courier recorded on the device: payment type, signature, start/end, comments.
BotenbonCourier receiptReceipt-printer slip stapled to the bag; shows address, tour, amount due, barcode.
BotenetikettCourier (bag) labelLabel-printer label with address, tour/time, prescription-due flag, amount due.
PacklistePack listPer-sale list of items to pack (PZN, supplier, totals).
ZusatzbonSupplementary receiptCustomer-facing receipt listing items handed over now and items to be delivered.
Botenempfangsbestätigung / EmpfangsbestätigungCourier receipt confirmationSigned acknowledgement for narcotics (BtM) and prescription-only deliveries.
Abholschein / AbholungPickup slip / pickupPOS transaction whose goods are collected later (or delivered).
Lieferschein / SammellieferscheinDelivery note / collective delivery noteInvoicing documents for on-account customers.
Faktura / FakturaauftragInvoicing / invoicing orderModule and order type for on-account sales (homes, clinics).
RezeptschuldPrescription debtGoods dispensed before the prescription was handed in.
Offene Posten / NachlieferungenOpen items / back-ordersModule listing unfinished transactions; tab for pending back-order deliveries.
VerkaufsverwaltungSales managementArchive/editor for stored sales.
Kunde nicht anwesend (Reservierung)Customer not present (reservation)Sale mode where items are reserved/flagged as later-delivery and nothing is handed over now.
Abrechnungsstatus / LieferstatusSettlement status / delivery statusPer-item outcome of a tour (delivered, not delivered, amount received, credit, etc.).
Kredit / TotalrabattCredit / total discountTwo ways to handle a shortfall at settlement: book as customer debt, or waive.
Notes / Bestell-Liste / Heutige AufgabenNotes / order list / today's tasksTask module; online orders arrive here; pop-up of today's tasks at all workstations.
AusführenExecuteTurn an order task into a POS/prescription transaction.
Rezeptdaten prüfenCheck prescription dataDialog to verify/complete data recognised from a prescription image.
Meine Apotheke (App & Web)"My Pharmacy" app and web portalPharmacy-branded customer app and portal.
Zugangsdaten / KennwortbriefAccess data / password letterCustomer credentials page and printed letter with login QR and password.
EinwilligungserklärungConsent declarationSigned customer consent required before activating app access.
InfocodeInfo codeQR code on the POS receipt that leads to the app.
Sortiment / RubrikAssortment / categoryThemed product group on the app order page (max six).
KundenbonusCustomer bonusAccount-based loyalty credit shown in the app.
Mein PostfachMy mailboxIn-app/portal inbox for orders and documents.
AbholstationPickup stationLocker/terminal from which a customer collects a prepaid order with a code.
ApothekenverbundPharmacy networkBranch group in which App & Web can be shared.
Arzt.connect / Klinik.connect / Rezept.connect / Heim.connectDoctor / clinic / prescription / home connectB2B web portals for practices, hospitals and care homes.
SprechstundenbedarfPractice suppliesItems a doctor's practice orders for use in the practice, billed on a special prescription.
VorablieferungAdvance deliveryGoods delivered before the prescription is received.
VorgangskarussellTransaction carouselPOS control listing pending orders to pull into a sale.
Click & Collect / E-CommercePickup pre-order / mail-orderWeb-shop licence levels.
Abholungsvorbestellung (mit Rezeptbild)Pickup pre-order (with prescription image)Web-shop order for in-store pickup, optionally with a photographed prescription.
VersandhandelsbestellungMail-order (shipping) orderWeb-shop order shipped to the customer; invoiced in the shop.
Externe Vorgangsnummer / Externe Auftragsnr.External transaction / order numberWeb-shop's own order number stored on the IXOS document.
Externer AuftragspartnerExternal order partnerCompany-master entry representing a connected web shop.
Automatische BestandsbuchungAutomatic stock bookingDeduct stock on arrival of a mail-order.
NL auflösenResolve back-orderConvert pending back-order into a delivery.
Wannensteuerung / WannenabfrageTub control / tub queryShop-side assignment of mail-order goods to numbered tubs; IXOS asks for the tub at goods receipt.
BeleglistenabfrageDocument list queryPeriodic count of pending orders in the shop back office.
Rabatt nach TotalDiscount after totalDiscount applied on the whole sale; used for web-shop coupons.
Verkaufskanal / externes VerkaufssystemSales channel / external sales systemReport fields identifying web-shop sales and which shop.

3. Data model​

3.1 Tour​

  • Kind: one-time (einmalig) or standing (ständig). A standing tour is a template; IXOS generates dated instances from it.
  • Fields: name; start date (for standing: start of series); start time (= delivery time); recurrence "every N <period>" with weekday checkboxes for weekly series; display count (Touranzeige): how many future instances are always visible in the tour list and in the sale's delivery dialog (default 3 for weekly, 1 for monthly); courier (an employee, or "none"); branch-tour flag plus participating branches; counter-scan flag (Gegenscan Verpackungseinheit) plus the average number of packs per container; route mode (car, bicycle, pedestrian); dwell time per customer (Aufenthaltsdauer); delivery-list mode (digital and/or printed, with or without overview map); tour password (generated); courier e-mail; ApoTune hand-off flag; customer assignment (none / report query / map area) plus "only for assigned customers" flag; preparation time for stock goods, with "keep proposing until the tour is closed"; preparation time for ordered goods; delivery behaviour (total or partial delivery); optional info text for the courier.
  • Each tour has a unique internal identifier, which is used when it is sent to ApoTune, so re-sending does not create duplicates.
  • States (as the help names them): unplanned (unbeplant: no stations); planned with stations; pack state per tour (nicht gepackt / vollständig gepackt); closed and handed over (it moves to Deliver/Settle, "in Lieferung"); stopped/completed by the courier; settled (abgerechnet, moved to Archive). A standing-tour instance with no deliveries whose time has passed expires (verfällt). Manually archived legacy deliveries form a pseudo-tour "Manuell archiviert" with a time stamp.
  • Template rule: editing an instance leaves the template unchanged. Editing the template does not change instances already displayed; the change applies from the next generated instance.

3.2 Tour station and grouping (three levels)​

  • Level 1: the tour.
  • Level 2: stations the courier drives to and that are packed together: single stations (private recipients), or group stations (a home, a clinic, or a home/clinic unit that has separate delivery). Only level-2 stations are used in route planning. Each branch's stations form their own group stations; they are never merged across branches.
  • Level 3: recipients delivered through a group station (residents, patients), sub-units with separate delivery, and for clinics the clinic orders (Klinikaufträge).
  • Whether delivery goes to the home/clinic as a whole or to a unit depends on the "separate delivery" (Separate Belieferung) checkbox in the home/clinic structure (contact > structure > delivery/agreements).
  • Station attributes: order number after optimisation; geo address point; desired delivery time; courier note text; branch code (when from another branch); pack status; visit status (open / completed / customer not met); settlement status per branch ("Abrechnung offen" while unsettled).

3.3 Delivery item (the thing being delivered)​

  • Document types: pickup (Abholung, from a POS sale), delivery note, collective delivery note, order (invoicing order without, or without all, delivery notes), courier task, cross-branch sale (a sale made in another network pharmacy and delivered from there). The archive also shows credit (Kredit) and note (Notiz) entries.
  • Pack status: not packed, packed, partly packed (in stock or reserved but not packed; not in stock and not packed), fully packed, substitute delivered. Station/group level: fully packed / packable / not packable.
  • Robot retrieval status: handed to the robot and queued; retrieval running; not yet triggered; aborted (not possible); retrieved but less than requested; retrieved in full.
  • Order status of item lines: open order, sent order, expiring item, slow mover.
  • Dispensing flags: prescription-only; prescription-only with a general substitution exclusion; part of a sale whose prescription is missing; narcotic; verification-required (securPharm) or partly verified; storage location; storage conditions (refrigerated, cold chain, light-sensitive, moisture-sensitive, position-sensitive, maximum and minimum storage temperature); e-prescription info note.
  • Delivery status (after tour): delivered (geliefert), could not be delivered, or reassigned to another tour.
  • Settlement data: received amount, payment type (cash or online payment), shortfall and its handling (credit to a customer, or total discount), "settle later", "correct later via sales management", courier comments.
  • Partial delivery chain: one sale can produce several partial deliveries. Each later partial delivery is a successor entry of the original.

3.4 Courier task​

  • One-off: text, optional address (free text or a contact), map lookup, assigned to a tour.
  • Standing: a series with recurrence. It is either unplanned or attached to one or more standing tours, with weekdays excluded. It can be linked to a customer or a walk-in customer. Per-day instances can be edited without changing the template.
  • Branch pickup tasks (Filial-Abholaufgabe) are generated automatically for stations from other branches and carry an editable note.

3.5 Packaging unit (counter-scan, Pro)​

  • Running packaging (label) number per tour; linked group (home/unit/clinic ward); linked tour; contained items; narcotics flag (separate "BTM" label when narcotics are packed separately).
  • Label QR content: tour data, recipient address data, label number.
  • Own labels are recognised by a configurable code prefix.
  • A packaging can be linked, released (unlinked) or merged.

3.6 Tour log​

For a tour or a station: payment type, signature image, tour start and end times, courier comments, and the "customer not met" outcome.

3.7 Customer/contact data used here​

  • Preferred tour; phone numbers with remarks (shown to the courier when "call customer" is enabled); delivery address; geo point.
  • App access ("Meine Apotheke"): active flag, password, login QR code, consent declaration on file. Registration state shown at the POS in five states: no access/no credentials; credentials issued but registration not finished; registered; has access; orders via the app.
  • Auto-created contacts from online registration carry an info text saying so.
  • Payer (Kostenträger), needed for manual prescription orders.
  • Bonus account; invoicing permission (Faktura-Erlaubnis), set automatically for mail-order customers.
  • For homes and clinics: structure (home > house > ward), the "separate delivery" flag, and assignment of residents to a doctor contact (used by Arzt.connect).

3.8 Online order (Notes task)​

  • Source type: app order, gematik-app order, web-portal order, home order (Rezept.connect / Heim.connect), doctor's practice order (Arzt.connect), web-shop order, call-back request.
  • Fields: customer (name, mobile number), prescription details/images (several per order), order lines (PZNs, scanned packs), delivery type (pickup, courier, pickup station, shipping), customer message/info text, assigned employee/deputy, priority, due date/time, internal info (not sent to the customer), external transaction number (web shop), online-payment flag.
  • Status: task open / done (Erledigt). Detail status "Erledigt" (all goods in stock and sold) or "Bestellt" (back-order pending until the full quantity arrives). Rezept.connect also tracks per-prescription-image processed/deliverable checkmarks. Message read/unread status.
  • The link between the POS transaction and the online order is removed automatically if all order lines and the customer are removed from the transaction.

3.9 Web-shop data on sales​

  • Sales channel (Webshop), external sales system code (which shop), external document number, external customer number, customer info text, coupon IDs, "web-shop order with cart" marker, operator "System", completion type "Online".
  • Mail-order invoicing orders: status "In Bestellung" / "Teilw. auf Lager" / "Auf Lager" / "geliefert", plus the "Vollfakturiert" (fully invoiced) flag; an internal delivery note numbered "I/xx".

3.10 Connect access (doctor, clinic, home)​

Active flag per product; password (stored encrypted); generated user name; URL; for Rezept.connect also an installation key. Klinik.connect additionally has pharmacy-side user groups with rights levels; every user belongs to a group.

3.11 Other entities​

  • Assortment: themed item group shown on the app order page; at most six are displayed.
  • Pickup station: name configured in system settings; type is integrated (code issued by IXOS) or stand-alone (code issued by the station).
  • Digital document: receipt PDF and analyses in the customer mailbox, automatically deleted after two years.
  • Bonus credit: for example, credit 1 = 500 points = a 10.00 EUR voucher, stored as a co-payment with a negative amount.

4. Features​

A. Delivery management (Liefermanagement)​

4.1 Module overview and editions [GENERIC]​

  • Purpose: organise the pharmacy's own courier service end to end in one window: plan tours with map support, assign deliveries automatically, pack, hand over to the courier digitally (smartphone/tablet) or on paper, settle, archive.
  • Scope: delivers POS sales (pickups marked for delivery), invoicing orders, and POS transactions closed as invoicing orders, to private recipients and to care homes/clinics. Reached from the Sales menu and the desktop.
  • Tabs: Plan/Pack (Planen/Packen), Deliver/Settle (Liefern/Abrechnen), Archive (Archiv). A filter marker on a tab shows that the view is restricted.
  • Editions: Basic, and Pro for large volumes and home/clinic supply.
  • Pro-only functions:
    • preferred delivery type stored on the home/home unit or clinic/ward structure;
    • splitting packable and back-order items into two tour stations, each assignable to its best-fit tour (system setting under Packen);
    • pack lists per group;
    • filtering items to pack by group/packaging, or "pack group";
    • retrieving whole groups from the picking robot;
    • moving groups between tours;
    • counter-scan of packaging.
  • Pro billing: by number of beds supplied per month (see 6.10).

4.2 Create and edit tours [GENERIC]​

  • Trigger: Plan/Pack > "Standing tours" list (new/edit), or "Create one-time tour". A new one-time tour appears selected and is initially unplanned.
  • Inputs: all tour fields in 3.1.
  • Digital delivery list: delivered by e-mail when a courier e-mail is set, otherwise by QR code at handover or a QR printout later.
    • Route mode: car, bicycle or pedestrian.
    • Dwell time per customer.
    • Tour password: generated automatically and can be regenerated. It is entered once per new device, per tour.
    • Courier e-mail: the courier receives the link after the tour is finalised.
  • Printed delivery list: with the option to also print an overview map of all stations.
  • ApoTune: checkbox enabling hand-off to the external route optimiser.
  • Counter-scan: available only with a Liefermanagement licence S, M or L. The average number of packs per container lets IXOS compute how many container labels to generate at the start; each label carries a QR code.
  • Customer assignment for the automatic proposal:
    • none (default): the tour is unrestricted, but customers whose preferred tour is this one are still considered;
    • report selection: pick a saved report query or create one (for example by place of residence) and save it with a name;
    • area selection: a map polygon. IXOS proposes the pharmacy's delivery area; the user can drag the corner points or move the whole shape.
    • Option "use this tour only for the assigned customers": the tour is then proposed only to those customers and is unavailable to others.
  • Rules: see 6.1 (preparation times) and 6.2 (instances and expiry).

4.3 Automatic tour proposal [GENERIC]​

  • Where: in the sale, when payment/delivery terms are set: the POS dialog "Abholung/Lieferung" or the invoicing dialog "Lieferkonditionen", in the list "plan for tour" (Für Tour einplanen). It needs existing tours; otherwise assignment is manual in the module.
  • Output: a tour preselected in the field. The list offers every tour visible in the tours overview. Tours whose preparation time has passed are shown greyed/italic but stay selectable. If nothing matches and the "propose next tour" parameter is off, nothing is preselected.
  • Priority rules: see 6.1.

4.4 Assign a transaction to a tour, or remove it [GENERIC]​

  • Drag a delivery from the deliveries overview onto a tour, or use "assign to tour" (in the pack window: "assign to another tour"). A list of tours appears; confirm.
  • Remove by dragging back to the deliveries overview, or with "remove from tour".
  • A new tour can be created directly in the assignment dialog.
  • Branch tours show a marker whose tooltip lists the start pharmacy, the own pharmacy and the participating pharmacies.
  • Removing a station from a planned tour returns it to the deliveries overview. If it was the only station, the tour becomes unplanned. Removing a group station removes all its single stations.

4.5 Courier tasks [GENERIC]​

  • One-off: select a tour > new courier task. Enter the task text and an optional delivery address (typed, or picked from contacts). A map lookup shows whether the address was found. Saved onto the tour.
  • Standing: created as a series.
    • Either "unplanned task" with its own recurrence, or "add to standing tour(s)", with weekdays to exclude.
    • Note text = the errand. Optional address or customer search.
    • Optionally linked to a customer or walk-in customer.
    • Standing-tour instances receive the standing tasks when they are generated. Instances that are already displayed do not pick up tasks created later. Workaround: delete those instances; they are re-created automatically before their delivery time, now including the task.
    • The template is edited from the list. A single day's task (text and address) can be edited without touching the template.

4.6 Map display and address points [GENERIC]​

  • Google Maps is used at tour creation, planning, Deliver/Settle and in the digital delivery list.
  • Map markers: several stations at one address (for example a home); desired delivery time; station done; customer absent; approximate position of the courier vehicle; pharmacy.
  • Route display: not yet optimised or station newly inserted; optimised route (shown in a distinct colour); route driven with completed stations.
  • Address not recognised: in the sale's pickup/delivery dialog, open the map, search, click the point and confirm. IXOS computes the distance to the pharmacy and uses the point in the tour.
  • Wrong coordinates can be corrected during tour assignment or in master data ("reset address point").
  • Map icons in the overviews open the whole tour map (tour selected) or a single address point (station selected).

4.7 Plan/Pack tab [GENERIC]​

  • Shows: a deliveries overview (unassigned deliveries) and a tours overview, with the status icons from 3.3 and an item-detail area.
  • Scanning the barcode on a pack list or pickup slip finds the delivery in any overview.
  • Tour optimisation: computes the station order for the shortest route.
    • Protected by the permission "Liefermanagement: Tour optimieren", which is needed both to optimise and to release a tour.
    • In a branch network the route starts at the start pharmacy, visits pickup stations at other branches first in ascending distance, then the delivery stations.
    • The station order can be changed by arrows or drag and drop, or reset to the default sort.
  • Close tour (when fully packed and the courier is due):
    • With a courier e-mail: the tour moves to Deliver/Settle and the courier gets an e-mail link.
    • Without one: a QR code is shown, to scan with the device or print for handover.
    • If the tour's delivery time has not yet been reached at handover, IXOS creates a new unplanned tour for that time, so an extra run can be slotted in.
  • Automatic packing (no pack check):
    • (a) "auto pack" on tours in state "not packed": all stock and back-order items are marked packed (dispensed quantity raised to sold quantity). The tour shows "fully packed" in Plan/Pack and can still take more deliveries.
    • (b) "close tour" on an unpacked tour asks: manual or automatic packing.
    • The result follows the sale's delivery behaviour. Total delivery: all items must be complete. Partial delivery: only stock items are packed; back-order items move to a later tour according to the ordered-goods preparation time and stay in Plan/Pack.
    • Missing delivery notes are generated and printed without preview, and the delivery list is printed.
    • Substitutes and robot retrieval are not supported; responsibility lies with the user.
  • On pack or close-with-auto-pack, the courier receipt (Botenbon) of POS pickups is "resolved" automatically.
  • Unpack: packed stations can be unpacked. Unpacking an invoicing order cancels the delivery notes already created (often unnecessary; editing the station is usually enough). Unpacked POS pickups are booked back into stock.
  • Edit an item: jump to sales management, change and complete the sale. The changed item is re-flagged for delivery (unless the flag is removed) and returns to the deliveries overview or its original tour.
  • Change delivery terms of a station:
    • remove the delivery flag if the customer or home collects;
    • change the delivery address;
    • unpacked pickups: edit the pickup/delivery dialog (for example switch to pickup, or change the address);
    • packed pickups: unpack first, then edit;
    • orders and delivery notes: edit the delivery conditions, where "do not deliver" removes the courier flag.
    • A change to a grouped station affects the whole group.
  • Edit group: delivery time, notification channel and delivery-note settings, applied to all contained stations.
  • Item info (shopping-cart icon): shows which purchase order brings the item.
  • Delete tour (with confirmation): items return to the deliveries overview.
  • Archive old delivery notes (first use of the module): see 4.18.

4.8 Pack delivery (Lieferung packen) [GENERIC] (securPharm part [DE-SPECIFIC])​

  • Purpose: assemble the bags per tour station once goods are in stock. Optionally verify each pack by scanning (pack check). For verification-required packs, scanning the securPharm code verifies the pack and, on success, decommissions it. General idea: serialised-pack verification at dispensing.
  • Trigger: double-click a tour, or "pack delivery", for a single station or the whole tour. Missing delivery notes and courier labels are generated and printed at this point. Packing can happen before or after a tour exists.
  • Three working modes set by the parameter "Packen im Backoffice":
    1. No (pre-sorted, not back office): all courier printouts (pack slip, narcotic/Rx receipt confirmation, supplementary receipt, customer labels, courier receipt, bag label) print at the sale. Stock items are laid out pre-sorted; ordered goods are assigned after goods receipt.
    2. Yes (pre-sorted, back office): at the sale only the pack slip, supplementary receipt and customer labels print. At pack completion the narcotic/Rx receipt confirmations (parameter "Empfangsbestätigung drucken"), the courier receipt and the bag label print, according to their print-count parameters.
    3. Yes incl. printing (recommended; no pre-sorting): ordered goods go into a "tour crate" after goods receipt.
      • Print the tour pack list for stock items (all stock items outside the robot), collect them, open the pack window.
      • Scan the securPharm code; IXOS decides which station needs the item.
      • A customer/home pack label prints per pack, to stick on it.
      • When a station is complete it closes automatically, and its narcotic/Rx confirmation, supplementary receipt, courier receipt and bag label print as configured.
      • Recommendation: switch off print preview for these documents.
  • Capturing items:
    • Scan the securPharm data-matrix code; otherwise the product-number (PZN) barcode. Scans are assigned to stations automatically and increase the quantity.
    • Or select a station and raise the dispensed quantity (Abgabemenge) manually; partial quantities are allowed.
    • Or "item complete" / "station complete", which sets dispensed quantity = delivery quantity. Caution: this also covers items that are not in stock or not yet booked in.
  • Station closes automatically (shown with a lock) when fully packed, or via "station complete" or "close station". Fully packed stations are hidden after the next action; "show all" brings them back.
  • If a verification-required item was not captured by its securPharm code, or not verified, a "capture pack information" dialog opens.
  • Pack window details:
    • Stations grouped: private recipients under "without home assignment"; residents under their home or home unit; clinic units with separate delivery as their own groups.
    • Counters: stations packed / packable / not packable.
    • Paperless dispensing check: for a prescription line, the prescription image is shown beside the related items and info, and the selection follows the scans. Users can move between several images of one station. E-prescription persistent notes are shown. The detail pane can be hidden; its splitter size is stored per workstation.
    • Enlarged prescription image: store a persistent note on the prescription, or print a copy.
  • Filter (in the pack window): by packaging label number, group, customer, item, item type, pack status, storage location. "Packable items only" restricts to items/stations not fully packed. Both filters apply together. An active filter is highlighted.
  • Select a station by scanning the pack list or courier-receipt barcode. This needs the courier-receipt print form option "print barcode and courier-receipt number". The scanned station is shown even if the "packable only" filter would hide it. If it belongs to another tour, a message appears.
  • Robot retrieval: see 4.9.
  • Substitute item: if the supplier delivered a substitute for an ordered item, the item is flagged; confirm in the "substitute delivered" dialog. After choosing the special code (Sonderkennzeichen), IXOS may ask whether to reprint the prescription. Then pack the substitute in the delivered quantity.
  • Partial delivery at packing: capture only the quantity to deliver now. This also works for fully available items, to hold stock back for another customer. Closing the station asks whether to record a partial delivery. No: back to packing. Yes: the remainder stays on the current tour or moves to the next possible tour, according to the ordered-goods preparation time. It can be packed and delivered even if the first partial delivery is not yet settled.
  • Interrupt: leaving the pack window buffers all entries, scans, pack states and securPharm data. Resume only on the same day and the same PC. Fully packed stations are unaffected.
  • Unpack station inside the pack window: the station stays on the tour. For invoicing orders the delivery notes are cancelled.
  • Switch to sales management from the pack window.
  • Tour pack list: printable from the tour or the pack window (see 10).

4.9 Robot retrieval at packing [GENERIC]​

  • Applies when "Packen im Backoffice" is active and the sale was started as a reservation "customer not present": items are not dispensed from the robot at the sale.
  • At packing: retrieve item, station, group or whole tour.
  • A tour containing only clinic groups sends one retrieval job per group, each with its own tub assignment, executed one after another.
  • Batch and expiry of verification-required items are stored and the securPharm booking is made.
  • An item, station or group packs itself automatically when the retrieved quantity equals the quantity to deliver.
  • Caution: if the parameter "use WWKS2 pack information for securPharm" is active and not the whole tour was retrieved, the user must not leave the pack window or continue while "retrieval in progress" is shown (until it turns green, yellow or red). Otherwise the station may not close, or labels may not print.

4.10 Counter-scan of groups/packaging (Gegenscan) — Pro [GENERIC]​

  • Purpose: for home/clinic deliveries, check that each item lands in the correct container (crate, tub, bag) of the correct group.
    • IXOS estimates how many containers each group needs and prints container labels.
    • During packing, either each container is linked to a group, or the container–group link is checked at item scan.
    • Own labels can be used instead of IXOS labels.
    • For invoicing stations packed this way, container numbers are passed to invoicing: they appear in the detail area and on the delivery note.
  • Enabled per tour with the checkbox "Gegenscan Verpackungseinheit".
  • System setting "Gegenscanmodus", four modes (IXOS labels or own labels × counter-scan after or before the item scan):
    1. IXOS labels, after the item scan;
    2. IXOS labels, before the item scan;
    3. own labels, after;
    4. own labels, before.
  • Related settings:
    • code prefix for own labels;
    • "pack narcotics separately" (BtM separat packen): separate narcotics container label; IXOS labels only (modes 1 and 2);
    • "allow bypassing the counter-scan": shows a bypass button;
    • success and error sounds.
  • Mode 1 (after, IXOS labels):
    • Select the tour, then pack delivery or pack group. IXOS offers to print container labels (or print them manually from Plan/Pack or the pack window). Stick them on.
    • Scan the first item; a counter-scan dialog opens. For quantity > 1, scan the further packs.
    • Reprinting a label and bypassing (if allowed) are possible.
    • Scan the group's container QR. If the group in the QR matches the item: the securPharm decommissioning is booked, batch and expiry are transmitted, the dialog closes with the success sound, and the container number appears on the item line.
    • If the container is linked to another tour or group: the dialog stays open with the error sound.
  • Mode 2 (before, IXOS labels):
    • The pack header first warns in red that no container is active and that items will not be assigned. Items scanned before activating a container get no assignment.
    • Scan a container label for the group to activate it (error if it belongs to another tour).
    • The header shows the active container number and group, the other inactive containers of that group, and required vs. assigned container counts (required according to the tour configuration).
    • Item scans are then linked to the active container, with securPharm booked.
    • When a container is full, scan another. Extra labels can be printed from the header.
    • The active container can be deactivated and another reactivated.
    • Unused scanned containers can be released in the overview.
  • Mode 3 (after, own labels): prefix required.
    • Scan the item, then scan any own label. If the label is not yet linked, it becomes linked to the item's group. If it is already linked to another group: error.
    • An address label for the container can be printed.
  • Mode 4 (before, own labels): as mode 2 with own labels.
    • For clinic packing with the IXOS.team app, use linear Code-39 or DataMatrix codes without spaces.
    • Containers can be deactivated (for example when an item is too large).
    • Large items packed without a container get an item label ("labels for selected items").
  • Container overview (from the counter-scan dialog, the pack window and all tabs):
    • lists scanned containers and their contents (final check);
    • merges items of one group spread over several partly filled containers into one, freeing the others;
    • unlinks containers;
    • prints a copy of a label, or a label for an additional container for the group.

4.11 Liefermanagement Pro consumption view [GENERIC]​

"Current consumption" is available in all tabs. It counts the individual stations inside groups delivered to a home or clinic on completed tours. Each resident counts once per month, however many deliveries they get. A warning appears shortly before the volume of the booked package is reached.

4.12 Deliver/Settle tab [GENERIC]​

  • Shows only packed tours handed over and not yet settled (Plan/Pack also shows unpacked ones). Three levels: tour, stations (single and group), residents within groups.
  • With the digital list: visited and open stations with delivery details and comments. Completed parts and parts still to deliver are distinguished by colour.
  • Icons: document type; branch-tour marker with the start pharmacy; greyed stations of other branches with their branch code; map; station order number; notes (courier note present; courier note plus a note the courier sent back via the web app; courier comment); delivery-list type and info (digital, printed, station completed, customer not met).
  • Functions:
    • expand/collapse; hide/show the deliveries, tours or item-detail panes;
    • filter by delivery period, customer name, or pickup-slip/delivery-note number, plus the general filter (4.20);
    • reorder stations;
    • delete a tour (items return to Plan/Pack's deliveries overview);
    • while the tour is not yet out: add items, change assignment, remove items (removing the only item deletes the tour);
    • jump to sales management with the transaction selected; item details;
    • reprint the delivery list (tour selected > print) or the documents of one delivery;
    • tour log (3.6) for the tour or a station.
  • Invoicing changes while in delivery:
    • change of doctor, status change without a co-payment change, or change of payer ID (IK): no new delivery note; the delivery stays in Deliver/Settle;
    • price change (for example a discount) with the same items and quantities: a new delivery note is created, and the delivery also stays.
  • Editing orders already handed out:
    • Orders: if already with the courier, the user must check. Continue only if the goods are still in the pharmacy, otherwise cancel to avoid inconsistencies. A warning appears when such an order is opened from invoicing, but not when opened from delivery management.
    • POS pickups already packed cannot be edited at all.
  • ApoTune resend: if transfer to the external optimiser failed, a marker appears beside the delivery time; select the tour and "send to ApoTune".

4.13 Settle tour (Tour abrechnen) [GENERIC]​

  • Purpose: close all items of a tour in one step after the courier transmitted data (digital list) or returned with signed papers and cash.
  • Where: should be done at a workstation licensed as a POS workstation, so the money enters the daily Z-report and cash book. At secondary workstations the user must remember to create a Z-report. For high volumes a back-office POS is recommended.
  • Steps:
    • Select the tour and settle. For each item check the delivery status and the received amount.
    • If everything was delivered and the courier has exactly the money due, confirm the preset given amount (= total).
    • If the courier brings a different sum, enter the given sum and pay out change.
    • If the courier could not collect everything, change the received amount at the item (4.14).
    • Delivery status: keep "delivered", mark "could not be delivered", or assign the item to another tour.
    • Undelivered goods go to another tour or back to the deliveries overview for re-planning.
  • Prescription debt: missing prescriptions handed in late can be printed from here. This calls the prescription-debt module, settles there, prints the prescriptions, and returns.
  • Only visited level-2 stations are settled. Residents (level 3) are settled indirectly through their group.
  • Credit with or without a customer: unpaid deliveries appear with their amounts in the "settlement information" column. Credit-closed transactions appear in the customer's open items. Open undelivered items of a partial delivery can then be delivered later.
  • Cash recycler (CashGuard): money is fed in through the device. The due amount is shown per customer, with the received amount preset; the total received is the amount to feed in. Feeding less than the due sum triggers a warning.
  • Branch tours: see 4.19.
  • Partial-delivery restriction: see 6.4.

4.14 Change received amount (Erhaltenen Betrag ändern) [GENERIC]​

  • Options:
    • Full amount received.
    • Correct the sale later via sales management: for a faulty sale (for example a wrong co-payment status). The received amount is set to 0 because the actual amount due is unknown. Note the receipt number and finish the settlement. Then find the sale in the archive or sales management, edit it (for example set the prescription status to "co-payment required"), complete it and reprint the prescription.
    • Settle later: the delivery stays in Deliver/Settle; this excludes single deliveries from the overall settlement.
    • No amount received.
    • Partially received: not available for groups.
  • Fields:
    • received amount (prefilled per option; editable for partial);
    • payment type (cash or online payment);
    • shortfall and its handling: credit (shows in the customer's open items; a credit slip print is optional, default off) or total discount (waive the rest);
    • "credit to customer": prefilled for regular customers; another customer can be chosen.
  • Group restrictions: no partial payments, no total discounts, no change of credit recipient; credit is assigned to the resident automatically.
  • Shortcut: typing a partial amount directly in the column opens the dialog with "partial" preselected; typing 0 preselects "no amount".

4.15 Digital delivery list (courier web app) [GENERIC]​

  • Delivery to the courier: a web app on any internet-capable iOS/Android device.
    • The courier receives the tour by e-mail link, or by scanning a QR code from the IXOS screen. The link must open in the system default browser.
    • If the QR is scanned from the Deliver/Settle tab, the password is transmitted too. Otherwise the courier enters the tour password once per new device, per tour.
    • Android asks on first open whether to use the browser or the courier app, and can install it as a home-screen app. iOS: open the link and enter the password.
  • Connectivity: internet is needed only to start the tour. All later steps work offline (online is recommended).
  • Tour start screen: map with stations, pharmacy name, courier name, number of stations, computed total duration and distance, date, start time, computed end time, optional info text.
  • Starting the tour can notify all recipients automatically by SMS or e-mail with the expected delivery time (per IXOS setting).
  • Each station shows: station number, deviation from the planned time (for example "1 minute early"), customer name, info texts, phone numbers.
  • Map controls: whole-tour map, zoom to the next station, overview, back to the list.
  • Station actions:
    • navigate with the device's navigation app; help;
    • signature: mandatory for prescription-only items or narcotics, otherwise optional; such a station cannot be completed without it;
    • card payment on the device (for example SumUp, 4.16); cash payment;
    • customer not met;
    • courier feedback (free text or predefined texts, sent to IXOS);
    • station completed. Entries are sent to IXOS and the next station appears.
  • End tour: enabled only when all stations are processed; asks for confirmation, offers a route back to the pharmacy, and sends the last data.
  • Revisit: a "not met" station can be expanded and processed again. A completed station can be reopened and a single step changed.
  • Homes/clinics:
    • Residents/patients delivered to a home, care service, clinic or unit (per the "separate delivery" flag) are merged into groups, and only the groups appear as stations; individual recipients are listed in the note.
    • Sub-units show their path (for example "Home > House X > Ward Y").
    • Free texts for the group and for individual recipients are shown.
  • Extras:
    • phone numbers with remarks and one-tap calling (if "call customer" is enabled);
    • the free text and extra field from the sale's pickup/delivery dialog (for example a high-value item, or a signature wanted);
    • a "prescription missing" note if this was marked at the POS;
    • a hint when two customers on the tour share an address (dismissible);
    • the branch code at stations from other branches.
  • Proof of delivery: in the archive, a receipt confirmation with the digital signature can be printed.

4.16 Card payment at the door (SumUp Solo Lite) [GENERIC]​

  • Requires: a SumUp Solo Lite terminal; a device meeting SumUp's requirements; the SumUp app on the device that runs the digital list.
  • Setup: register the app IDs (Chrome iOS, the courier app, Mobile Safari, SumUp app-switch) in the SumUp account. Copy the SumUp developer "affiliate key" into IXOS system settings > Sales > Liefermanagement > cashless payment.
  • Result: card payments are transferred to IXOS. The vendor does not support the terminal itself.

4.17 External route optimisation (ApoTune) [GENERIC]​

Optional per-tour hand-off of tour data to an external optimisation service. Each tour carries a unique ID, so a resend after a failed transfer does not duplicate it.

4.18 Archive tab and archiving legacy delivery notes [GENERIC]​

  • Archive: settled tours with the same three levels.
    • Faulty sales can be corrected via sales management, opened with the sale selected and editable.
    • Search by period, customer name, or document number, plus the general filter.
    • Courier notes appear as tooltips.
    • Statistics export to Excel (see 10).
    • Print receipt confirmations per station/customer, including comments and signatures.
    • Manually archived deliveries are listed separately; their "delivery time" is the archiving time.
  • First use of the module: all old delivery notes and collective delivery notes without a delivery list appear in the deliveries overview. Select them and "archive"; they move to the archive under "Manuell archiviert" with a time stamp.
    • Older orders delivered without a delivery note are not shown.
    • Unresolved POS pickups are shown but cannot be archived this way; they must be resolved one by one at the POS. Resolved ones are not shown.

4.19 Branch and partner-pharmacy tours [GENERIC]​

  • Purpose: one tour filled jointly by several pharmacies; each pharmacy packs and settles its own stations.
  • Setup: set the branch-tour option at creation (one-time or standing). The own pharmacy becomes the start pharmacy; choose the participating pharmacies.
  • Rules:
    • Only the creating pharmacy can edit or delete the tour, and only it can delete stations.
    • Standing tours that are not branch tours are invisible in the branches.
    • A "branch tour" column in all tabs shows own stations as editable and other pharmacies' stations greyed, read-only and with their branch code.
    • In Plan/Pack each participant can move its own stations; only the start pharmacy can move foreign stations to other branch tours. In Deliver/Settle only the start pharmacy can move stations.
    • Optimisation starts at the start pharmacy, then visits branch pickup stations by ascending distance, then deliveries.
    • The standard delivery list shows each station's originating branch.
  • Branch pickup tasks: pickups at a branch appear as courier tasks with their own marker. They cannot be deleted separately, only by the creating branch deleting the whole station. Either side can add a note, which shows as a tooltip in all tabs and in the digital and printed lists.
  • Settlement:
    • Once the tour is stopped or completed (via the delivery list or by the start pharmacy), every participating pharmacy can settle its own stations. Unsettled ones show the branch code and "settlement open".
    • Only the start pharmacy can stop a tour early; undelivered stations then return to Plan/Pack.
    • Digital branch tours in which not every branch has stations move to the archive as soon as the first branch has settled (also for the branches without stations).
  • Archive status texts: see 6.6.
  • Cross-branch sale: a customer buys at pharmacy A an item that pharmacy B delivers by courier. It is marked with its own icon, and B prints a pack list titled for network courier delivery.

4.20 Filters [GENERIC]​

Each tab has its own filter.

  • Tour criteria: delivery date range, tour name (partial match), courier, delivery status.
  • Delivery criteria: customer, item, document date range, document number, courier-delivery number (printed on the delivery list), and settlement status (a text search on the status detail texts; for example "verkaufsv" finds items flagged for later correction in sales management).
  • An active filter is highlighted on the tab. Filters can be cleared and work for branch tours.

4.21 Hand a packed delivery directly to the customer [GENERIC]​

If the customer appears before the courier leaves: at the POS, scan the courier receipt. The pickup appears; resolve it as usual, collect any unpaid money and hand over the goods. Not supported for invoicing sales.

B. Sales menu overview (Verkauf) [GENERIC] (parts [DE-SPECIFIC])​

The Sales menu groups these modules:

  • POS (Kasse): the central front-shop sales module.
  • Invoicing (Faktura): delivery notes and invoices for homes, hospitals and individual on-account patients.
  • Open items (Offene Posten): transactions not yet fully processed or settled: open pickup, prescription debt, advance delivery, open invoice.
  • Prescription management (Rezeptmanagement): holding prescriptions not yet scanned; checking them, including an automatic pre-check and an electronic pre-check through an external service (ApoTI); manual control of deferred or faulty prescriptions; reprinting; holding uncollected prescriptions; archiving those sent to the billing centre. [DE-SPECIFIC] General idea: a prescription pipeline with pre-submission validation before payer billing.
  • Cost estimates (Kostenvoranschlag): estimates to payers; offers to customers and doctors.
  • Delivery management (Liefermanagement).
  • Sales management (Verkaufsverwaltung): view and manage stored POS transactions, re-edit and reprint, provide evidence for tax audits (GDPdU). [DE-SPECIFIC] General idea: an immutable, auditable sales journal.
  • Prescription request (Rezeptanforderung): create, send and manage prescription requests to doctors.
  • Blister management (Blistermanagement): blister packing for home customers via contract orders: release dosages, create blister orders, send them to a blister centre.

C. Customer app and web portal ("Meine Apotheke" App & Web)​

4.22 Product overview and settings locations [GENERIC]​

  • What it is: two front ends, a mobile app and a web portal, sharing one customer account. It is a paid add-on: the licence "App & Web Meine Apotheke" covers both. The web portal requires the pharmacy to have its own homepage.
  • Settings live in three places:
    • module "Meine Apotheke": themed assortments and courier-service options;
    • system settings: availability display, web-portal activation, pickup stations;
    • company master > Connect: imprint and access data, colours and logos for Connect products, documents such as terms and privacy notices.
  • Tips from the help: set a radius for courier deliveries, and supply a photo of the shop front for the app and portal.
  • Prerequisites:
    • the vendor enables IXOS for app internet communication;
    • opening hours maintained in company master (otherwise defaults are shown);
    • the medication-management module, for intake plans;
    • the prices-and-calculation module, for offers;
    • colours and logos configured;
    • optionally, the info code on the receipt;
    • app requires iOS ≥ 16.6 or Android ≥ 10;
    • imprint data maintained; consent declaration and privacy texts editable.

4.23 Customer-side app features [GENERIC] (e-prescription parts [DE-SPECIFIC])​

  • Registration: simple online registration.
  • Ordering: scan the barcode of an existing pack; scan an e-prescription; photograph any prescription; voice input; search by name or product number. The customer gets an automatic order-status message and is told when the order is ready.
  • Availability display: if enabled, the customer sees whether an item is available.
  • Courier delivery: selectable in the order flow, if enabled.
  • Drug information: usage hints from the package leaflet and large pack images.
  • Interaction check when medicines are added to the cart or to "my intake plan". If it finds a risk, the customer is asked to clarify it with the pharmacy and can forward the result to the pharmacy.
  • Intake reminders:
    • manual local reminders on the phone; or
    • if the customer is under medication management at the pharmacy, the plan (items, intake times) is exported from IXOS. The customer sees the plans and their reach (how long the supply lasts), and every change in IXOS is synced. Self-maintained times are then no longer allowed (for therapy safety).
  • Other features:
    • current offers;
    • notifications (order notifications from app version 2.1);
    • "my medicines": items ordered before, bought in the pharmacy before, or on the intake plan;
    • bonus balance shown as points and as an equivalent credit amount in the order overview;
    • e-mail to the pharmacy;
    • emergency-pharmacy finder (list or map);
    • emergency contacts/information stored locally on the device.
  • Pharmacy side:
    • branding with logo and pharmacy image;
    • offers taken from prices and calculation;
    • prices follow the customer's discount model as usual: the cheaper of calculated price and discount-model price, or the discount model first if so configured.

4.24 Installation and registration [GENERIC]​

  • Path 1 — pharmacy QR or pharmacy search:
    • The pharmacy hands out a QR code and password (in ads or on a receipt) and enables access.
    • The customer scans the QR, installs from the store, views what's-new screens, accepts the terms of use, and connects to the pharmacy by its QR or by search.
    • With the QR: enter the initial password, which must be changed (password policy). Entering a valid e-mail is recommended: it allows re-login after logout or reinstall, and lets the customer get mailbox messages. An e-mail verification code is entered at login. "Later" skips straight to home, and the customer can still order.
    • With pharmacy search: enter the pharmacy name and select it. Existing account: e-mail and password. Otherwise create an account with full customer data, accept the privacy and consent texts, and confirm via an e-mail link.
  • Path 2 — online registration in the app.
  • Path 3 — via the web portal:
    • The pharmacy creates the customer in IXOS and hands over a password letter and a registration letter.
    • The customer logs into the portal with the login ID (in the e-mail field) and the password, then sets an e-mail and a new password.
    • Afterwards the customer logs in with e-mail and the new password.
  • App home sections: Shop (search, offers, assortments, pack scan, redeem prescriptions); Prescription (scan e-prescription or photograph a prescription); My area (account, emergency data, orders, medicines, mailbox); Cart.
  • Pharmacy side of online registration:
    • The customer is created automatically as a customer contact, with an info text saying it was app-created.
    • On the next sale (POS or invoicing) for that customer, a message appears. With the customer-info licence (IXOS.Kunde, "customer info at a glance") a task is also created: check the consent declaration and check for duplicates.
    • If the person was already a regular customer, a new contact is still created, and the duplicate-merge function must be run.
  • POS registration-state icon: five states (see 3.7). It prompts staff to offer credentials or help finish registration.
  • Password reset: link in the app > e-mail > link > enter the new password twice. Logout is under Account.

4.25 Enable app access in Contacts [GENERIC]​

  • Requires: access authorisation with a QR code and password.
  • Steps:
    1. Open the contact's access-data page (Zugangsdaten).
    2. Ensure the customer received and signed the consent declaration; file the paper or scan it into the document management system.
    3. Under "Meine Apotheke" set Active, then "assign password". A password-letter preview opens; print it and hand it over.
    4. Saving prompts to print the form with the login QR. The password becomes usable about one minute later.
    5. The customer opens the app, scans the QR and logs in with the password from the letter.
  • Reprint the consent declaration or registration form from the contact's print function.
  • Report: in the customers result category, the master-data field "Meine Apotheke" lists customers with app access.
  • Deactivate then reactivate: the customer must reinstall the app before reconnecting.

4.26 Simplified download and connect (app ≥ 4.9) [GENERIC]​

  • Start: contact > access data > "Meine Apotheke" > "connect Meine Apotheke" opens a dialog with a download QR. It can also be shown on the customer-facing display; it disappears once scanned.
  • Customer side: scan, install, allow notifications (a font-size hint is shown), skip the welcome screens, accept the terms.
    • Android shows a verification code.
    • iOS: "continue" and allow paste; the pharmacy is selected automatically from the QR and the code is shown.
  • Staff: asks for the code and enters it; the dialog's OK becomes active when the code is correct.
  • Finish: the customer sets a password (policy) and confirms the e-mail with a numeric code.
  • Simplest variant: "use the app without password and e-mail" (requires confirmation) connects the customer immediately. Limits: no e-mail notifications (only in-app notifications and mailbox), and logging out of the app is impossible.

4.27 Info code on the POS receipt [GENERIC]​

  • What: a QR code at the bottom of the receipt, with hint text and web address, leading to the app start page.
  • Enabled in the receipt print-form details ("print info code for app"); default off.
  • Printed when: the licence exists, and at least one sub-total of the sale has a stored customer without app access, or no customer at all (walk-ins too).
  • Supported printers: Epson TM-J7500, TM-J7700, TM-T88V. Not the TM-U950: quality is insufficient.
  • The page is visible only with the app licence.
  • Imprint data: in addition to the master data. Pharmacy name and owner are shown read-only and changed in the master data. A warning appears if the data are incomplete.
  • Consent declaration and privacy notice: the texts shown to customers in Connect products. Both are editable and can be reset to the vendor default (with confirmation).
  • General idea: legally required publisher information and consent texts maintained centrally per pharmacy.

4.29 Availability display and courier configuration [GENERIC]​

  • Availability: system parameter group "Meine Apotheke", on/off. When on, the app shows stock availability.
  • Courier via app: system parameter group "Apothekenverzeichnis" (pharmacy directory).
    • "allow courier deliveries via app" (default off);
    • courier radius (depends on the licence). If the delivery address is outside the radius, the courier option is greyed out in the app and portal, with a hint.
  • gematik e-prescription app users: the courier option is offered only if the parameter "Botendienst in Gematik-App" is active. [DE-SPECIFIC]

4.30 Offers in the app [GENERIC]​

  • Source: calculated prices, including offer prices of non-prescription items from prices and calculation.
  • Two kinds:
    • unlimited offers;
    • date-limited price lists, shown on the page "our offers" (Unsere Angebote).
  • Setup: create a usage model with a date-limited price list containing time-limited prices. The customer then sees the offer price and orders at that price.
  • Selection and refresh rules: see 6.8.

4.31 Customer bonus display [GENERIC]​

  • Requires: an account-based bonus model granting credits, assigned to the app customer. Material rewards are ignored.
  • Example: credit 1 = 500 points = a 10.00 EUR voucher, stored as a co-payment with a negative amount. The customer sees points in the order overview.
  • Redeeming: if the customer asks in the order remark, staff use the POS special items > "redeem customer bonus", choose the credit and complete the sale. The balance syncs back to the app and shows at the next order.

4.32 Assortments [GENERIC]​

Themed categories (for example seasonal) are created and changed in the "Meine Apotheke" module and shown when the customer starts a new order. At most six are displayed in App & Web.

4.33 Customer ordering flow [GENERIC]​

  • Inputs:
    • voice;
    • search: a product number finds the exact item; a name lists variants by pack size and strength;
    • pack-barcode scan: shows the image, current price and pack size, details, and add to cart;
    • prescription photo; e-prescription;
    • offers; reorder from "my medicines".
  • Steps: cart > checkout > choose self-pickup or courier (or a pickup station, 4.38) > order overview with an optional question to the pharmacy > order > done.
  • Afterwards: "my mailbox" (orders and digital receipts), "my orders" (over a selectable period), "my medicines".

4.34 E-prescription redemption via app [DE-SPECIFIC]​

General idea: patient-side submission of an electronic prescription token to a chosen pharmacy, either by scanning a printed code or by reading the patient's health ID card.

  • (a) Scan the token QR from the e-prescription printout ("redeem prescription" > "scan e-prescription"). Aim at the collective code or at individual codes. Recognised prescriptions go into the cart; check out; optional message; order. The customer is notified if the items are in stock. Requires the app to be installed and connected to the pharmacy.
  • (b) Health card (eGK) via CardLink:
    • Requires app ≥ 4.6.0, an NFC phone, a connected app, and the pharmacy's GEDISA ID in company master. If GEDISA is not active, the option does not appear.
    • Steps: choose "e-prescription with health card". Add the card in learn mode by entering its 6-digit card access number (CAN), or pick a stored card (quick mode; quick mode can be disabled permanently, then the card must be added each time). Enter a German mobile number, receive a 6-digit SMS code and enter it. Hold the card to the phone. After authentication the prescriptions appear in the cart.
    • Stored cards can be deleted individually.
  • Other apps:
    • The national gematik e-prescription app: the customer assigns the prescription to the pharmacy, and it lands in the order list. Communication runs via that app if the user is logged in with NFC card + PIN, otherwise by e-mail.
    • Alternatively the customer shows the code on the phone in the pharmacy for scanning. Other e-prescription apps: scan the displayed code.

4.35 Manual order of prescription items (no photo) [DE-SPECIFIC] (payer check)​

General idea: allow ordering prescription-only items before the prescription is presented, gated by insurer data and a per-order item cap.

  • How: the customer picks prescription items by search or pack scan.
  • Requires: a payer (Kostenträger) stored in the customer contact.
    • Without a payer the order is not sent; the customer is told to photograph the prescription instead.
    • With a payer the order is sent, and the customer is asked to present the prescription or e-prescription at pickup.
  • Cap: see 6.7. Photo prescriptions can be added as well.
  • In IXOS: classified as a prescription sale. The Notes details show the manually ordered items and any photo. Executing it opens the prescription-scan window, including discount-contract checks.

4.36 Processing an app/portal order in IXOS (Notes > order list) [GENERIC] (prescription checks [DE-SPECIFIC])​

  • Arrival:
    • A "today's tasks" pop-up appears at all workstations; the per-workstation parameter "remind on arrival of order" can switch it off.
    • The order is added to the order list.
    • Prescription photos run through automatic recognition of customer and item data (like a prescription scan) if the image quality allows; otherwise the data are entered manually.
  • Task list:
    • filter by employee;
    • views: Current (overdue, current, next two days, done), Week, Month;
    • task-type filter: standard, evaluation, report task;
    • task kinds include connect tasks: app order, home order, home prescription request, doctor's practice order, web-shop order;
    • columns: subject, series flag, priority (high/normal/low), info flag, responsible/deputy, due date/time;
    • overdue tasks are highlighted, done tasks greyed.
  • Order detail:
    • customer name, mobile number, prescription details, pharmacy info texts, assigned handler, message read/unread;
    • prescription-photo tab: fully processed prescriptions are flagged done. Images can be rotated in 90° steps (needed for readability in the scan window) and are auto-adjusted when quality allows.
  • Functions:
    • Info: internal free text, not sent.
    • Send message/SMS: only for app, gematik-app and call-back orders; SMS only if a mobile number exists. A message window with reusable text modules (add new ones).
    • Set done / set not done.
    • Sales management: the selected customer's orders; edit, reassign to another customer, cancel.
    • Execute: opens the prescription window for prescription items, otherwise the POS. If an item is out of stock, a message window offers to notify the customer. The order then moves to Done and its messages are marked read.
    • Print: the prescription image on A4 (for example for the final check).
    • Edit: task formalities, such as assigning an employee.
  • E-prescription order: Execute > e-prescription window (check/correct) > "release and take over" > POS > complete > done.
  • Photo order:
    1. "Check prescription data": the prescription date must always be checked; it is prefilled with today and highlighted. Set the printed date.
    2. Prescription-scan window: contact data are taken over automatically if quality allows. Otherwise the orderer is taken as the customer (highlighted), but the orderer is not necessarily the patient; find or create the right customer (a consent declaration is offered for new customers).
    3. The prescription status defaults to statutory insurance (GKV) when quality is poor; correct it.
    4. The prescribed item is taken over but always highlighted for re-check; otherwise enter it manually.
    5. All usual prescription checks run (discount contracts, substitution, import rules). Reservation mode is on automatically (customer not in shop).
    6. "Take over to POS". If the customer is under medication management, a medication-details window appears; as-needed and free-text dosing are not transferred to the app.
  • At the POS:
    • The whole order is shown: the prescription sale plus a normal sale built from the sent product numbers or scanned packs. For prescription items among the latter, the prescription status is asked.
    • The customer is prefilled. "Customer not present" flags all items as later-delivery (back-order) items.
    • At the total, the pickup/delivery dialog sets delivery terms (for example courier).
    • Payment is cash by default, unless the customer master says invoicing.
    • "Manage digital receipt": OK sends the receipt as PDF to app/web. If several customers with access are in the sale, choose one to receive the whole receipt (privacy confirmation). Paper printing remains possible.
  • After the sale:
    • Notes reopens and offers an editable message to the customer. The task is filed under Done.
    • Detail status "Erledigt" if all goods were in stock; otherwise "Bestellt" until goods receipt of the full quantity, then "Erledigt".
    • Executing again only processes still-open prescriptions; if all are done, a message says so.
    • A messages tab lists everything sent.
  • Customer view: the order shows "ready for pickup" if fully in stock, otherwise "not ready" until goods receipt. At pickup the pharmacy resolves the pickup at the POS and hands over.
  • Done without sale: an order can be set done without processing (for example handled by phone); there is then no jump to sales management. In this case, and when an app order is deleted from Notes, a message to the customer is offered. The app shows the message and moves the order to history with "closed without sale".

4.37 Notifications to customers [GENERIC]​

  • When: from Notes at any time.
  • Auto-generated, editable proposals for:
    1. order completed with no back-orders ("ready for pickup");
    2. completed but back-orders needed ("not in stock; you will be told on arrival");
    3. back-order booked in at goods receipt;
    4. item exchanged because of a discount contract, a successor item or pack splitting;
    5. order deleted;
    6. order set done manually.
  • Fully automatic sending: see 6.12.
  • Free-text messages: select the task and type in the detail field or the message window, then send.

4.38 Pickup stations (lockers) [GENERIC]​

  • Types:
    • Integrated via interface (picking robot, lockers, BD Rowa pickup terminal): IXOS issues the pickup code and shows it in app/web.
    • Stand-alone: the code must come from that system.
  • Preconditions: online payment (PayPal) configured; the cart must be payable online (no prescriptions) and paid in advance.
  • Configuration: station names are set in the "Meine Apotheke" system settings.
  • Flow: the customer chooses "pickup at pickup station" and the station. The pharmacy gets a Notes task.
    • Integrated: "pickup at terminal" is preset (if configured).
    • Stand-alone: handle like an in-store sale.
    • After payment and processing the customer receives the pickup code.

4.39 Digital receipt (PDF) [GENERIC]​

  • Choice: per sale, print and/or send a PDF. Available for app/web orders and also for in-store or phone sales. The customer must be fully registered.
  • Customer side: a push notification and a badge in My area. The document lands in "my mailbox": thumbnail, full view, export (print/save/forward). Older receipts are kept and filterable.
  • Sales management: an icon at the receipt number shows paper-only vs. paper plus digital.

4.40 Web portal (Web "Meine Apotheke") [GENERIC]​

  • Functions:
    • redeem prescriptions and pre-order products (click & collect);
    • view orders and reorder previous medicines;
    • message the pharmacy about orders;
    • receive digital documents (receipts, co-payment / prescription / purchase evaluations);
    • view the pharmacy-maintained medication plan and/or keep an own intake plan.
    • One account works for both app and portal.
  • Design: company master > Connect > colours and logos. Configure the portal yourself, or have it designed externally by sending a web link (valid 24 hours).
  • Deep links from the homepage:
    • <portal-URL>?START=ANGEBOTE opens offers;
    • ?START=REZEPT opens prescription redemption;
    • ?PZN=<number without leading zero> opens a specific item.
  • Accessibility: the requirements of the German accessibility law (BFSG) are implemented. [DE-SPECIFIC] General idea: statutory web-accessibility conformance.
  • Registration: on the pharmacy website or via the app. Mandatory fields; password policy; activation link by e-mail; then login with e-mail and password. Password reset by e-mail link.
  • Registered order: log in, fill the cart, check out. For a prescription order, choose the prescription type and optionally enter the payer ID (IK number). Choose self-pickup or courier (if offered), accept the terms, add an optional comment, order.
  • Guest order: checkout "as guest", mandatory fields, accept privacy, pickup or courier, accept terms, comment, order.
  • Prescriptions: photographed and e-prescriptions are accepted in the order flow. Mixing formats (for example a photo plus an e-prescription) splits the order into two or more partial orders. On tablets and phones the camera starts automatically.
  • Notification channels: see 6.12.
  • Customer messages: at checkout, on existing orders in my orders, and in my mailbox.
  • Mailbox: all orders and documents sent by the pharmacy (receipts, evaluations). Retention: see 6.13; restore by reprinting the invoice in IXOS, which re-syncs it to the account.
  • Customer data and account deletion:
    • Customers can change their data only through the pharmacy.
    • Self-service deletion: My area > account settings > "delete access" > confirm. The portal-side data are deleted completely; the IXOS contact is not deleted.

4.41 App & Web in pharmacy networks [GENERIC]​

  • What: within an IXOS branch network, an "App & Web network" can cover all or some licensed branches.
  • Behaviour:
    • A customer with access at one pharmacy can see availability in their own pharmacy and in the branches, and order. Availability in cart and shop always refers to the pharmacy currently selected in the cart.
    • Prices are always those of the pharmacy the customer is connected to; they are passed unchanged to the branch and taken over into its POS automatically.
    • Pickup: the customer chooses the home pharmacy or a branch. Courier and guest orders cannot choose a branch; they always go to the connected/portal pharmacy.
    • My orders and my medicines include orders placed at other branches; in-store purchases at branches are not listed in my medicines.
    • Documents (receipts, invoices, co-payment lists) are sent by the processing pharmacy.
    • Messaging goes directly to the pickup pharmacy.
    • Login only at the pharmacy where the account was created (the customer may register at other branches too).
    • Only the registering pharmacy maintains the intake plan and reminders.
  • Preconditions:
    • every pharmacy in the network is licensed and has the parameter "show stock status for App & Web" on;
    • cross-pharmacy use is unlocked for the network;
    • stock, price and contact exchange within the network is active;
    • contact exchange either for all customers (system settings > consulting > contacts > automation, "allow contact exchange automatically") or as a trial for selected contacts (contact master > contact exchange). In the trial case the features are visible only for those contacts.

4.42 Online payment (PayPal) [GENERIC]​

  • Methods (all through PayPal): PayPal; PayPal pay-later (eligibility depends on merchant status; can be disabled in company master); SEPA direct debit; debit or credit card.
  • Setup:
    • Licence, plus linking the pharmacy's PayPal business account in company master > external services, entry "Meine Apotheke: online payment" > details > PayPal linking flow. Status shown red = inactive, green = active.
    • Field colours show unmet prerequisites.
    • Live in the portal/app within at most 3 hours. Avoid doing the setup over a remote client.
    • The PayPal account can be created during setup, but it is better to have it beforehand.
  • Permissions: "Meine Apotheke: Online-Zahlung verwalten" (workstation protection) plus "Firmenstamm: Modul starten".
  • Not offered for: see 6.9.
  • Cancellation:
    • Full: for an online-paid order not yet executed, select it in the order list and "set done". A dialog offers rejection with refund through PayPal ("Zurückbuchen"), plus an optional customer message.
    • Partial: when taking the order into the POS, remove items or reduce quantities, giving a negative total. When the pickup is resolved, at the total IXOS asks whether to refund the difference online or in cash. An online refund must then be executed in the PayPal account itself, not in IXOS.
  • Pricing: see 6.9.
  • Unlinking: "disconnect PayPal account" (confirm); it can be relinked any time.
  • Privacy: the vendor does not see the pharmacy's PayPal turnover, and no health data are passed to PayPal.

D. B2B Connect portals​

4.43 Arzt.connect (doctor's practice ordering) [GENERIC] (practice-supply billing [DE-SPECIFIC])​

General idea: B2B ordering portal for prescribers, with a special billing class for practice-use supplies.

  • Purpose: a doctor or practice staff order practice supplies (Sprechstundenbedarf) online. The doctor gets a generic-equivalent search (aut idem), an active-ingredient search, and free-text ordering. Paid add-on.
  • Pharmacy setup:
    1. Open the doctor contact > "Connect access" page and tick Active under Arzt.connect.
    2. Assign a password agreed with the doctor; it is stored encrypted. The URL is shown.
    3. Save: the user name is generated, and IXOS offers to print an access-data overview (reprintable). Hand it to the doctor.
  • Doctor's side:
    • Browser (Microsoft Edge), URL, login; the password must be changed at the first login.
    • The doctor sees only the home residents assigned to them in IXOS (possibly across several homes) and their medication data.
    • "New order": search by medicine or active ingredient, with filter icons (for example prescription-only). The "in stock" filter is ineffective, because the stock column is not synced with IXOS inventory.
    • Item info by clicking the name; set quantity; save the order as a named template for later; order note to the pharmacy; send.
    • Items show "ordered" until the goods are fully in stock at the pharmacy.
  • Pharmacy processing:
    • The order pops up in today's tasks (with a distinct icon). Open it in Notes, view details, assign an employee.
    • Execute: the POS shows the order as an advance delivery in a normal sale.
    • If the doctor will send practice-supply prescriptions: create a new sub-total, set its prescription status to "Sprechstundenbedarf", and drag the items into it.
    • At the total set pickup mode; payment is preset to cash.
    • After completion the task is done: detail "Erledigt" if in stock, else "Bestellt" until the full back-order quantity arrives.

4.44 Klinik.connect (hospital ward ordering) [GENERIC]​

  • Purpose: clinic staff order ward supplies online.
    • Clinic-side functions: user management, order entry, approval/release and transmission of orders, statistics.
    • Orders are processed in IXOS.
    • The pharmacy can open the web app from IXOS (menu Office > Connect pharmacy login). There are two generations of the web app (current and new). Paid add-on.
  • Pharmacy-side user management (menu Office > Connect user management):
    • Security settings (creating users, rights, passwords) are limited to authorised people; to grant a right one must hold it oneself.
    • Initial setup: first create user groups with permissions (any number of groups and rights levels), then users. Every user belongs to a group; restricted users see only the elements relevant to them.
  • Clinic web access: clinic contact > access data > tick Active under Klinik.connect; set an initial password (the clinic must change it at first login), stored encrypted. User name and URL are generated; print the overview of Connect accesses.

4.45 Rezept.connect (homes send prescriptions in advance) [GENERIC] (e-prescription/Muster-16 [DE-SPECIFIC])​

General idea: care homes scan or forward prescriptions to the pharmacy ahead of time, so supply can be prepared before the paper arrives.

  • What: a web-based link between pharmacy and care homes. Prescriptions are sent ahead of time, encrypted, as e-prescriptions or as scans made at the home. The pharmacy receives them in IXOS as incoming orders. Paid add-on.
  • Setup: home contact > Connect access > Active under Rezept.connect. Assign a password (stored encrypted); the URL and an installation key are shown. Save; print the access overview; hand it over.
  • Installation at the home:
    • On the home PC (Microsoft Edge) open the URL, which shows a support page with system requirements and downloads.
    • Download and run the software. The installer asks for the installation key and the password. The app opens and a desktop shortcut is created.
    • Then install the .NET runtime and the driver for the prescription-scanner model.
  • Scanning at the home:
    • Start the app and enter the password. Insert prescriptions in landscape, front facing forward.
    • Paper prescriptions (Muster-16 form) and e-prescription token printouts are both read, also mixed.
    • Images are shown; single ones can be deleted or enlarged. For e-prescription sheets, the number of recognised prescriptions is shown.
    • "Send prescriptions" transmits them with a progress bar; there is a send log.
    • Unsent scans (new, or left over after a crash or connection loss) stay until sent or discarded. Discard one, or all (with confirmation); discarding deletes the scan file.
  • Pharmacy processing:
    • Signalled by the today's-tasks pop-up.
    • E-prescriptions appear as individual orders (customer name with home assignment; details list the single prescriptions) and are executed one by one into the POS.
    • Paper prescriptions arrive bundled as one "home order" (Heimbestellung). The details show the home and the number of images.
      • With no image selected, actions apply to all images.
      • Quick view; tick several for an enlarged view or a print copy; A4 print for the final check of deliveries; rotate; assign an employee.
      • Execute: "check prescription data" opens if data are missing or unrecognised. Complete them, but wrongly printed data must not be corrected (the doctor's practice must fix those).
      • The prescription-scan window starts with the first prescription. Reservation mode is on by default (goods collected later); it can be switched off to pack immediately with delivery notes. The parameter "Automatisch Reservieren" disables the default.
      • Check contact data and dispensable items. "Take over to POS": all scans are shown one after another, and after the last the POS opens with all prescription sub-totals.
      • "Customer not present" flags everything as back-order. At the total the pickup/delivery dialog sets payment and delivery (for example courier). Payment for homes is preset to invoicing.
      • After completion the order is done: "Erledigt" if in stock, "Bestellt" for back-orders until the full quantity arrives.
      • The images tab gives processed and fully deliverable prescriptions a green check. Executing again processes only the unprocessed ones.
  • Transaction carousel at the POS: open the order list from the cart icon, expand a customer or home, process individual e-prescriptions or scanned home prescriptions through the check window, and complete. Several prescriptions can be collected into one total.

4.46 Heim.connect [GENERIC]​

Homes order medicines or home supplies efficiently, through a web application and a hybrid mobile app ("IXOS Connect Partner App"). The app adds e-prescription scanning and prescription-photo upload for ordering prescription medicines. Paid add-on; documented in a separate help (not in this slice).

E. Other satellite products​

4.47 Media.connect (apoTV / kassenTV) [GENERIC]​

  • What: a content manager for in-store TV screens (apoTV) and the customer-facing display at the POS (kassenTV): slideshows and videos for promotions and information.
  • Licences: paid "apoTV.connect Schnittstelle" and "kassenTV.connect Schnittstelle".
  • Access: visible only to the role "Leiter" (manager) or the right "Media.connect starten".
  • Use: started from IXOS (desktop or Office menu). It opens a web UI for media, playlists and players with automatic single sign-on.
  • kassenTV content is enabled in company master on the "customer display" page. Support requests go through Notes / IXOS.eCall under the category apoTV.

4.48 IXOS.team (staff mobile app) [GENERIC]​

  • What: mobile access to the learning platform IXOS.campus and to IXOS Chat, connected via the operator profile.
  • Licence-dependent extras: packing clinic deliveries (counter-scan mode 4); mobile counting for perpetual inventory.
  • Requirements: iOS ≥ 16.6, Android ≥ 9 (API 28). The FAQ lists iOS 12.5.5, which is inconsistent.
  • Setup: install, register with an activation code (QR) and connect.
  • Courses: start a course or module, page forward/back, progress percentage, table of contents, my courses, search, filter (for example open courses).
  • Chat: via a secure IXOS server, app↔app, app↔workstation and workstation↔workstation, synchronised.
    • 1:1 or group chats with a subject; emojis; photos (taken or stored) and PDF attachments; links; push notifications and badge.
  • Profile: disconnect permanently there; reconnect by scanning a new activation code. The profile image is the IXOS user-account image. Imprint, terms, privacy and version info are in the profile.

4.49 IXOS.view (reporting portal) [GENERIC]​

  • What: a web portal extending analytics. The first stage offers PDF downloads: "Management Report 4.0", "RX 5.0 Erfolgskontrolle" (prescription business success control), "Non-RX Marktbericht" (OTC market report).
  • Registration:
    • personal data; e-mail = user name (a personal address is recommended);
    • password policy and link validity: see 6.13;
    • arithmetic captcha; privacy consent;
    • confirm via the e-mail link (otherwise repeat the registration);
    • then register the own pharmacy or pharmacies and download.

4.50 Artikelscan.mobil [GENERIC]​

  • What: a bundle of a handheld rugged scanner (Xplore DT4100) with an app manager and the app "Mobiler Wareneingang" (mobile goods receipt).
  • Use: capture items and delivery notes, sent in real time over WLAN to IXOS.
    • Pack data go to IXOS.
    • Supplier and item data such as storage locations and storage hint texts come from IXOS to the scanner.
  • Hardware: dust- and water-proof, one-hand touch use.

4.51 Product catalogue page [GENERIC]​

Lists the vendor's satellite products: IXOS.team, app "Meine Apotheke", Rezept.connect, Heim.connect, Arzt.connect, Klinik.connect, Media.connect, Artikelscan.mobil.

F. Web-shop connection​

4.52 Web shops: general, interfaces and licences [GENERIC]​

  • Order types supported:
    • pickup pre-order and mail-order for all non-prescription items;
    • pickup pre-order with prescription image: may contain several prescriptions plus non-prescription items. Only the image is transmitted, not the prescription items.
  • Two interfaces:
    • Standard interface (ADAS): shops GEHE/AHD/ia.de, WAVE, Sanacorp MEA, APOZIN, gesund.de, apotheken.de, Curacado, 1A-GESUND.de, savit, IKS, Zukunftspakt Apotheke, VAYA, BRRY, Pharmagest.
    • Mauve interface: Mauve Aposhop Regional/Business/Individual, easyApotheke.de, AVIE, medi now / ELAC, CURE.
  • Licences:
    • "Click & Collect" (all shops): pickup pre-order with or without prescription image. A courier service can also be offered through the shop.
    • "E-Commerce" (Mauve only): adds full mail-order.
  • ADAS setup: licence, shop access data, interface ADAS version 2.1 or later. The shop is created as an "external order partner" in company master.
  • Notification: per-workstation parameter "remind on arrival of order"; pop-ups in today's tasks.

4.53 Mauve Click&Collect / E-Commerce integration [GENERIC]​

  • Data export to the shop:
    • All items that have storage, stock or price information, with purchase and sale prices.
    • Self-created items (except value vouchers) are exported too; the shop decides visibility.
    • Optional price schemes (Preisschema) in prices and calculation: the synced data include purchase prices and a sale price determined by a price scheme. The default is the standard sale price per scheme. Other schemes must be created and enabled manually in the shop, including customer-specific display.
    • Time-restricted price lists (happy hour) are ignored.
  • Customer order: self-pickup, courier, or shipping. A pickup pre-order may include a prescription image upload (if enabled in the shop). Online prepayment is sensible for courier and shipping. Order confirmation comes from the shop (configured there).
  • Shop back office ("System 3"): the pharmacy views and checks orders there. Transfer to IXOS is manual or automatic per setting.
  • Results in IXOS by type:
    • Pickup pre-order: a POS transaction is created (like "reservation, customer not present"), possibly triggering a purchase order for back-order items. The customer pays at pickup (like a phone reservation).
    • Pre-order with prescription image: a Notes task.
    • Shipping: an invoicing order, flagged fully invoiced (invoicing happens in the shop). The customer receives invoicing permission. Per setting, the delivery note is created on arrival or at goods receipt, and stock goods are deducted on arrival or at goods receipt. Payment does not appear on the pack list.
    • Courier: the delivery is assigned to the next standard tour in delivery management. If prepaid, the receipt notes the online payment.
  • Pack list: can print automatically, marked "pre-order" or "shipping", with a web-shop marker.
  • Customer matching: a new customer is created as a regular customer (default; covered by the shop's terms), or as a walk-in customer if not uniquely identifiable. Walk-in data are subject to the configured deletion routine.
  • Setup:
    • Register the web shop in company master > electronic data exchange.
    • The vendor technician sets it up through a Connect instance (Office > Connect user management > order partner), using the Mauve server URL and login.
    • Data sync uses a key pair: the public key is exported as a file and sent to Mauve; IXOS generates the pair if missing.
  • Processing: all orders arrive as Notes tasks. Execute > release dialog > POS. Prescription-image orders go through the prescription-scan window. The info-text window is multi-line. How availability is displayed is decided by the shop provider.

4.54 Releasing a web-shop order (standard order flow) [GENERIC] (prescription checks [DE-SPECIFIC])​

  • Sequence:
    1. The customer pre-orders in the shop, the shop forwards the order to IXOS, and the shop e-mails the customer a confirmation.
    2. Pharmacy: menu Cooperation > Notes > Tasks, select the order, Execute.
    3. The "release order" dialog shows customer data, order lines, item names, delivery type, and whether a prescription image was sent.
    4. Release continues. Reject (for an obviously incorrect order) moves it to Done.
  • Non-prescription order:
    • Goes straight to the POS. The transaction shows the customer name and a "web-shop order with cart" marker; "reservation – customer not present" is preset.
    • Check the items. At the total, the pickup/delivery dialog has the customer's delivery type preselected (for example pickup). For courier, ensure the address is complete. Finish.
  • Prescription order:
    • Customer data from the shop are taken over. The prescription exists only as an image, so the order data and the insured person on the prescription may differ.
    • "Check prescription data" (hover to zoom), then the prescription-scan window. Check the insured person's data. If they differ from the order data (highlighted), delete the customer assignment and search for or create the right customer.
    • Enter the prescribed items; IXOS checks discount contracts, cost-efficiency rules and so on. Rotate the image; confirm the doctor's signature and the dosage indication by click.
    • E-prescriptions: check the data. To return an e-prescription or keep it for later, delete it from the dialog. "Release and take over". Deferred e-prescriptions remain as Notes tasks.
    • The POS opens. A camera icon reopens the photo; reservation is preset; at the total the delivery type is preselected (for example courier).
  • Partial processing of multi-prescription e-orders: cancel a single scan in the e-prescription dialog, then choose "return to customer" or "keep in tasks" in the "prescriptions – further processing" dialog; the remaining ones are offered next. The same works for one or two prescriptions inside a collective code.
  • Completion: the customer is notified by the shop's e-mail that the items are ready, when all are in stock; otherwise after goods receipt. Whether this is automatic or manual depends on the shop provider. Open tasks are shown automatically at program start or user change. Courier delivery and delivery terms can be set up in the shop (ask the provider).
  • Link removal: the POS–order link is removed if all lines and the customer are removed.

4.55 Pickup pre-order from the web shop (Mauve) [GENERIC]​

  • Import: check the sale in System 3 and "execute" to transfer it. IXOS imports a sale at the processing workstation.
    • The pack list prints automatically if configured, with the external document number as "externe Vorgangsnummer".
    • The sale appears in open items > back-orders. Sales management shows the external transaction number in the total details.
  • Pickup: resolve as usual.
    • If the shop price differs from the current in-store price, a company-master > Webshop setting decides: either take the shop price as a manual POS price, or show a "difference to current sale price" dialog to choose.
    • Verification-required items open the pack-information capture.
    • The receipt prints automatically on resolution.
  • Courier: runs through delivery management with automatic tour assignment. The pack status of each line is re-evaluated continuously from shortage/back-order quantities and goods-receipt quantities until fully packable. If prepaid, the online payment is noted on the receipt.
  • Traceability:
    • Operator on the receipt and in sales management = "System" (imported).
    • Advanced search: created automatically by system; sales channel Webshop; completion type Online.
    • Sub-total details: General tab shows sales channel Webshop; Webshop tab shows the shop name and code, external document number, external customer number, and the customer's info text.
  • Editing at the POS: the sub-total is flagged as web shop.
    • Items cannot be dragged out of a web-shop sub-total into another sub-total, but can be dragged into it.
    • Lines in a web-shop sub-total cannot be split (Stückeln).
  • Cancellations of online-paid sales: IXOS cannot cancel in the shop. Choose payout online or cash; for online, make sure the shop cancels and corrects its side.

4.56 Pickup pre-order with prescription image [GENERIC] (prescription handling [DE-SPECIFIC])​

  • Sources:
    • Mauve: a Notes task is created; the order can contain several prescriptions and non-prescription items.
    • Shop "IhreApotheken.de": a task is created for pre-orders with or without image and fed directly into Notes, without shop software.
  • Urgency: the task's due time is set 15 minutes ahead so it turns overdue then. It is also flagged in the info centre and in today's tasks at operator change. Editing the task shows the external transaction number.
  • Execute: the release dialog shows the details including the external ID, a zoomable image, and tabs for prescription image and positions (when there are non-prescription items too).
  • Release, then "check prescription data": there is no text recognition for these images.
    • The payer is always highlighted red: it must be read from the image.
    • The prescription date is highlighted and initially set to the order date.
  • Prescription-scan window:
    • The customer address is the orderer's; verify that this is the patient.
    • The doctor's signature is always flagged and must be checked.
    • Reservation is active. Enter the prescribed items and check substitutions.
  • "Release and take over" to the POS: a prescription sub-total plus a normal sub-total if needed. The sale is flagged: prescription missing, reservation customer absent, web-shop marker, image attached to the sub-total.
  • On confirming the given amount: a pack list and a reminder slip (Erinnerungsbon) print. Sales management shows the prescription as missing and the image in the sub-total details. The sale appears in open items > back-orders.
  • Pickup: scan the reminder slip, find the sale in open items, or scan the paper prescription. Automatic matching by prescription scan requires the orderer to be exactly the customer on the prescription.
  • Write-back: after completion, the finally chosen items (possibly substitutes) are sent back to the Mauve shop and appear as lines in the shop document.

4.57 Mail-order (shipping) orders [GENERIC] (securPharm note [DE-SPECIFIC])​

  • Import: orders closed in the shop with delivery type shipping are imported as invoicing orders, and the customer automatically gets invoicing permission.
  • Pack list: printed automatically on arrival at a defined workstation (if set in company master > Webshop).
    • It includes the customer's shop info text.
    • No prices (they are set in the shop, not IXOS).
    • No "by invoice" note and no amount due (invoicing is done entirely in the shop).
  • External transaction number: supplied by the shop for shipping and pickup orders, or entered manually. Printed on the pack list and the delivery note. For Mauve the shop order number is transmitted as the external number, but the customer receives an "Auftragsnummer" for pickup.
  • Robot: with automatic stock booking, stock items are retrieved from a connected picking robot on arrival.
  • Finding orders:
    • sales management by external document number (Mauve System 3);
    • the invoicing order overview filter "only orders from web-shop orders" (needs the web-shop licence);
    • the info icon in the order overview shows the customer's info text.
  • Automatic stock booking options: see 6.11.
  • Tub query at goods receipt for shipping orders (Mauve), see 4.60.
  • Audit: with automatic booking no "last editor" is recorded (it is a system import); otherwise it is the person who resolved the back-order or did the goods receipt. Stock control in item management shows the automatic deductions.
  • Delivery note: an internal delivery note "I/xx" is created on the order's delivery-note page but not offered for printing (the shop prints its own). It is created for stock goods and at goods receipt of back-order items; without automatic booking, only at back-order resolution.
  • Open items: without automatic booking the order sits in open items > back-orders with delivery type "shipping from web shop". With automatic booking only stock goods are deducted and the order is delivered with no open item; back-order items get an open-item entry that is removed automatically at goods receipt (if that option is on).
  • No pack verification: securPharm verification is not offered in IXOS for shipping orders; it happens when packing in the shop system.
  • Coupons can be redeemed in the shop for shipping orders but are not evaluated in IXOS.
  • Substitutes:
    • When a substitute, a smaller pack or an import is delivered, neither the shop order nor the IXOS order is exchanged automatically (the order is fully invoiced).
    • A Notes task reports the substitute and asks for the invoicing order to be corrected.
    • On back-order resolution or delivery-note creation, the substitute appears at the POS instead of the original and can be accepted, with quantity and sale price editable.
    • With automatic booking at goods receipt, the order stays "in stock" (not delivered) after a substitute arrives, and a warning marker shows in the invoicing details.
    • Substitutes are never booked automatically.

4.58 Web-shop coupons [GENERIC]​

  • What: coupons issued and managed in the shop can be redeemed in a pickup pre-order. In IXOS they become a "discount after total". They are imported even without the paid coupon-management licence.
  • Rules:
    • If a shop coupon was used, no IXOS value voucher can be redeemed when the pickup is resolved (a message says so).
    • The receipt shows the discount amount and the coupon name or number the customer typed.
    • Self-pickup: the outstanding sum is shown as credit. Courier delivery with prepayment: the online payment is noted on the receipt.
    • Sales management total details list the coupon on a "discount after total" tab. When resolving the pickup, the discount function at the total allows adjusting or removing the coupon value.
    • Avoid resolving such pickups with payment type invoicing: the coupon discount cannot be processed there, and a message asks to remove it.
  • Reports: sales result category, transaction info / key figures field "Rabatt-Coupon-IDs".

4.59 Web-shop sales in reports and goods logistics [GENERIC]​

  • Reports: the sales result category has the fields "sales channel" and "external sales system" (code of the configured shop). Sales channel is also a filter for sale lines.
  • Goods logistics: purchase-order lines caused by web-shop orders carry a customer-reference icon; clicking it opens the ordering customer's contact.

4.60 Tub query at goods receipt (Mauve) [GENERIC]​

  • Context: Mauve's tub-control module packs shipping goods into numbered tubs. Stock goods are scanned directly; ordered goods are handled at goods receipt.
  • Behaviour: at goods receipt IXOS asks Mauve for the tub number and books the items into that tub.
  • Dialog: item name, dosage-form code, pack size, standard pack size, supplier, and a table of tub number and quantity to put in. A row turns green when that tub then contains all of its ordered items.

4.61 Document list query (Mauve) [GENERIC]​

  • System 3 keeps document lists of shop orders; documents due for transfer to IXOS sit in their own lists.
  • IXOS can query the number of documents per configured list and show it in Notes. This is configured in company master (external order partner).
  • At up to 3 configurable times (the help does not say per day or otherwise), if at least one new order has arrived, a Notes task appears with the count per list.

4.62 Search web-shop orders by external number [GENERIC]​

  • Where: sales management overview field "number", or advanced search field "external order no.".
  • Matching: numbers are stored as text, so leading zeros matter. Use % as a wildcard (for example %210%).

5. Workflows​

5.1 Courier delivery end to end (principle flow)​

  1. Create tours. Create standing and/or one-time tours (4.2), with preparation times, customer assignment, courier, and digital or printed list.
  2. Set preferred tours. Store a preferred standing tour per customer or home (contact > specific data).
  3. Create standing courier tasks where needed (4.5).
  4. Mark sales for delivery.
    • At the POS or in invoicing, mark the sale for delivery in the pickup/delivery or delivery-conditions dialog.
    • Check the customer data loaded automatically. If the address was not found, set the point on the map.
    • A POS sale can be closed "with invoicing" for efficient home supply.
    • The tour is proposed automatically (4.3) or chosen manually.
  5. Packing in the back office is optional ("Packen im Backoffice").
  6. Unassigned deliveries appear in Plan/Pack; assign them by drag and drop or "assign to tour" (4.4).
  7. Pack the whole tour, a group or a station (4.8). This includes robot retrieval (4.9) and counter-scan for homes/clinics (4.10), and prints the courier documents.
  8. Add one-off courier tasks if needed.
  9. Optimise the tour when all stations are packed (permission required); the order is shown on the map.
  10. Close the tour. It moves from Plan/Pack to Deliver/Settle.
    • Paper: the delivery list prints.
    • Digital: the courier gets an e-mail link, scans the on-screen QR, or receives a printed QR, then unlocks the tour with the password.
  11. The courier runs the tour in the web app (4.15): start (recipients notified), station by station with signature/payment/feedback, end. Completed tours show a completed marker in the stations column.
  12. Settle the tour (4.13/4.14) at a POS-licensed workstation. Money goes to the Z-report; shortfalls become credit or total discount; undelivered items are re-planned.
  13. The settled tour moves to the Archive, where it can be exported, its receipt confirmations printed, and its sales corrected.
  1. The sale is made with "customer not present": nothing is dispensed from the robot and only the minimum is printed.
  2. After goods receipt, ordered goods go into the tour crate.
  3. Print the tour pack list for stock items outside the robot and collect them. Retrieve robot items per item, station, group or tour.
  4. Open the pack window and scan each pack's securPharm code. IXOS allocates the pack to the right station, verifies and decommissions it, and prints a pack label.
  5. A completed station auto-closes and prints its confirmation, supplementary receipt, courier receipt and bag label.
  6. Close the tour (auto-pack is offered for anything unpacked).

5.3 Home/clinic delivery with counter-scan (Pro, mode 2)​

  1. The tour has counter-scan on, with an average packs-per-container value.
  2. Print the container labels for each group and stick them on the crates.
  3. Open the pack window. A red warning shows that no container is active.
  4. Scan a group's container label to activate it.
  5. Scan items. Each is decommissioned and linked to the active container.
  6. When a container is full, scan the next label; print extra labels as needed.
  7. In the container overview, merge partly filled containers and release unused ones.
  8. Container numbers flow to the invoicing delivery note.

5.4 App order with a prescription photo​

  1. The customer photographs a prescription in the app, chooses pickup or courier, and orders.
  2. Today's-tasks pop-up at all workstations; the task appears in the order list. Recognition pre-fills the data where possible.
  3. Staff open the task and execute it.
  4. In "check prescription data", correct the date.
  5. In the scan window, confirm the patient (not necessarily the orderer), the payer status and the items. The usual checks run.
  6. Take over to the POS. The normal-sale lines are added, the sale is reserved (customer not present), and at the total delivery terms are set (courier puts the sale into delivery management).
  7. Choose a digital and/or paper receipt.
  8. Notes reopens and a message is sent to the customer. The task is done ("Erledigt" if in stock, else "Bestellt").
  9. Goods receipt books the back-orders; the customer is notified automatically.
  10. The customer collects (pickup resolved at the POS) or the courier delivers.

5.5 App e-prescription order​

  1. The customer scans the token QR or uses the health card via CardLink.
  2. Task, then execute: the e-prescription window, then "release and take over", then the POS.
  3. Complete the sale; the task is done; the customer is notified.

5.6 Care-home prescriptions via Rezept.connect​

  1. The pharmacy activates access and hands over the URL, password and installation key.
  2. The home installs the client, scanner driver and runtime.
  3. The home scans paper and e-prescription printouts, reviews the images and sends them. Unsent scans persist.
  4. The pharmacy receives e-prescriptions as single orders and paper scans as one home order.
  5. Paper: execute; complete missing data without correcting printed errors; work through each prescription in the scan window (reservation on by default); the POS gets all sub-totals; payment preset to invoicing; delivery by courier.
  6. Green checks mark processed prescriptions. Executing again handles only the rest.
  7. Alternative: pull orders into the sale through the transaction carousel.

5.7 Doctor's practice order (Arzt.connect)​

  1. The pharmacy activates access and gives the doctor the printout.
  2. The doctor logs in (forced password change), searches, adds items or a template, writes a note and sends.
  3. Task, then execute: the POS shows an advance delivery.
  4. If practice-supply prescriptions will follow, move the items into a "Sprechstundenbedarf" sub-total.
  5. Set pickup mode and complete. The task is done or ordered; the doctor sees "ordered" until the goods are in stock.

5.8 Web-shop pickup pre-order (non-prescription)​

  1. The customer orders in the shop and receives the shop's confirmation.
  2. The order arrives as a Notes task (Mauve: after the check/transfer in System 3).
  3. Execute, then release (or reject).
  4. The POS shows a reserved sale with a web-shop marker. Check it; at the total the delivery type is preselected.
  5. The pack list prints with the external number. The sale sits in open items > back-orders.
  6. The shop notifies the customer when ready.
  7. At pickup, resolve the sale: handle any price difference according to the setting, coupon as discount after total, pack verification. The receipt prints automatically.

5.9 Web-shop pre-order with prescription image​

  1. A task is created with a 15-minute due time.
  2. Execute and release. Check prescription data: read the payer from the image; set the date.
  3. Scan window: verify that the patient matches the orderer; check the doctor's signature; enter the items and substitutions.
  4. The POS sale is flagged prescription-missing, reserved, with the image attached. On payment, a pack list and reminder slip print.
  5. At pickup, scan the reminder slip or the paper prescription, or look the sale up in open items. Complete the sale.
  6. The final items are written back to the shop order.

5.10 Web-shop mail-order (shipping)​

  1. The order arrives as an invoicing order, flagged fully invoiced. The customer gets invoicing permission. The pack list prints at the defined workstation, without prices.
  2. With automatic stock booking: stock is deducted (and robot items retrieved) at once, and the order is set to delivered.
    • Back-order items are booked at goods receipt if "also at goods receipt" is on.
    • The tub query assigns the items to shop tubs (Mauve).
  3. Without automatic booking, resolve the back-order manually. The internal delivery note "I/xx" is created then.
  4. A substitute delivery creates a Notes task to correct the order.
  5. Packing, verification, invoicing and shipping happen in the shop system.

5.11 Customer app onboarding at the counter (simplified connect)​

  1. Staff open the contact's access data and "connect Meine Apotheke", optionally showing the QR on the customer display.
  2. The customer installs the app and reads the verification code aloud; staff enter it.
  3. The customer sets a password and confirms the e-mail, or staff tick "no password and e-mail" for an immediate connection.

6. Business rules and calculations​

6.1 Tour preparation times and automatic proposal​

  • Stock-goods preparation time: a sale completed less than this time before a tour's departure is proposed the following tour. Example: 30 min; a sale 20 minutes before departure goes to the next tour.
    • Option "propose until the tour is closed / handed to the courier": the tour stays proposable within the preparation time until it is actually closed.
  • Ordered-goods preparation time: covers wholesaler delivery plus packing. Example: 180 min; tours departing within 3 hours are not proposed for sales containing ordered goods, and the next due tour is proposed instead.
  • Delivery behaviour for mixed sales:
    • Total delivery: the whole sale is assigned according to the ordered-goods time. At packing with check a partial delivery is still possible. Auto-pack marks everything packed and hands it over.
    • Partial delivery: the whole sale is assigned according to the stock time. At packing the deliverable items form the partial delivery. At auto-pack all stock items are marked packed, and ordered goods move to the next possible tour according to the ordered-goods time.
    • With partial-delivery tours, the automatic proposal for POS sales with stock and ordered goods uses the stock preparation time, not the ordered-goods time.
  • Proposal priority (highest first):
    1. The customer's/home's preferred tour (standing tours only).
    2. The tour's customer assignment by report query (standing tours only). Report-matched tours rank above area-matched tours.
      • With "only for assigned customers" off, besides report customers and customers whose preferred tour this is, any customer for whom this is simply the next tour after the preparation time also gets it.
      • With it on, the tour is limited to customers found by the report, customers with it as preferred tour, and members of a home that has it as preferred tour.
    3. Parameter "propose next tour" (default on): the nearest tour after the sale that respects the preparation time, excluding tours restricted to a customer set.
  • Outcomes: tours past their preparation time are shown greyed/italic but stay selectable; with "propose until handover" they are still proposed automatically within the stock time. If nothing applies, nothing is preselected.

6.2 Standing-tour instances​

  • The number of visible instances equals the display count (defaults 3 weekly, 1 monthly).
  • An instance without deliveries expires after its time has passed.
  • Settling or handing over a tour before its delivery time automatically creates a new unplanned tour for that time.
  • Template edits affect only instances generated later.
  • Instances already generated do not receive standing courier tasks created later.

6.3 Packing quantities​

  • A station counts as fully packed when the packed quantity ≥ the required quantity, whether reached by scan, robot retrieval or manual increase.
  • "Item/station complete" copies the delivery quantity into the dispensed quantity, even for items that are not in stock.
  • A paused packing session resumes only on the same day and the same PC.
  • Unpacking an invoicing station cancels its delivery notes.
  • Editing a delivered item re-flags it for delivery unless the flag is removed.

6.4 Partial deliveries​

  • A remainder goes to the current or next tour according to the ordered-goods preparation time. It can be packed and delivered before the first part is settled.
  • From the creation of the 3rd partial delivery of one delivery, settling the 1st partial delivery allows only: full amount, no money, or settle later. A partial amount is no longer allowed.
  • Courier receipt and bag label show only the open sum of the items actually delivered. The sales-management preview shows the courier receipt for the next delivery.
  • The pack list of the latest entry lists only open items; the full list is printed from the predecessor entry.

6.5 Settlement​

  • The given amount must not be less than the sum due. Collect less only by recording a lower received amount per item.
  • Only visited level-2 stations are settled; residents are settled through their group.
  • Groups: no partial payment, no total discount, credit goes automatically to the resident.
  • Credit-closed amounts appear in the customer's open items. A credit slip is optional (default off).
  • Settlement belongs at a POS-licensed workstation so it reaches the Z-report and cash book.
  • Cash recycler: feeding less than the due sum triggers a warning.

6.6 Branch tours​

  • Ownership: only the creator edits or deletes; only the start pharmacy stops a tour early or moves foreign stations (in Deliver/Settle it is the only one who may move stations at all).
  • Settlement: each pharmacy settles its own stations once the tour is stopped. A digital branch tour moves to the archive when the first branch settles.
  • Archive status texts:
    • digital list: "geliefert + nicht abgerechnet" (delivered, not settled); "teilabgerechnet" (at least one branch settled); "abgerechnet" (all settled, or not a branch tour);
    • printed list: "in Lieferung" (not yet settled); "geliefert + abgerechnet"; "nicht geliefert".

6.7 App orders​

  • Manual prescription orders:
    • require a payer in the customer contact; otherwise the order is not sent;
    • once at least one prescription item is ordered manually, the order is capped at 3 items (the maximum per prescription), and the customer is told.
  • Photo orders: the prescription date must always be checked; the item is always flagged for re-check; the status defaults to statutory insurance on poor quality; the orderer may not be the patient.
  • Order status: "Erledigt" when all goods were in stock at the sale; "Bestellt" until goods receipt of the full back-order quantity.
  • Link removal: the POS–order link is removed when all lines and the customer are removed.
  • New password: becomes usable about one minute after it is assigned.

6.8 App offer prices​

  • Price lists are refreshed once a day (at night) and applied by priority.
  • Without a determined price, the recommended retail price (UVP) is used, otherwise the pharmacy sale price (Apo-VK).
  • Customer discount models apply as usual.
  • Usage models do not distinguish context (POS/invoicing) or sale type (normal, private prescription…), and have no time-of-day (happy hour) prices.
  • Without a date-limited price list, "our offers" automatically shows items that meet all three conditions:
    • stock > 0;
    • recommended retail price > 5 EUR;
    • calculated price (without customer) at least 6 % below the recommended retail price.
  • Items without an offer price: recommended retail price, else pharmacy sale price, else the own sale price set manually in item management.

6.9 Online payment​

  • Not offered for:
    • prescription items on statutory insurance, and prescription images;
    • pickup at another branch;
    • order quantity > 3;
    • order amount > 500 EUR.
  • Pricing: the price paid online is not recalculated at the POS. Exception: the instant discount (Sofortrabatt) is not computed in app/portal but is applied at the POS total. The difference becomes a credit in IXOS and must be paid out to the customer actively.
  • Partial refunds online must be executed in PayPal itself.
  • Availability: live within 3 hours of setup.

6.10 Liefermanagement Pro billing​

Billing is by beds supplied per month. The count is the individual stations within groups delivered to a home or clinic on completed tours, each resident counted once per month regardless of the number of deliveries. A warning appears shortly before the package limit.

6.11 Mail-order stock booking​

  • "Automatische Bestandsbuchung" on: stock is deducted on arrival if available, the order is set to delivered and flagged fully invoiced.
  • "Auch beim Wareneingang" (also at goods receipt) on: back-order items are booked at goods receipt.
  • Neither: the order stays "In Bestellung" / "Teilw. auf Lager" / "Auf Lager" and is resolved manually.
  • Substitutes are never booked automatically; after a substitute arrives the order stays "Auf Lager".

6.12 Customer notifications​

  • Sent fully automatically when the order contains only immediately available non-prescription items, and when goods receipt for back-ordered items is recorded. Otherwise IXOS proposes a message to staff.
  • Portal channel rules:
    • always an e-mail to the stored address;
    • additionally an SMS if the app is not used/connected and a mobile number is known;
    • additionally a push notification if the app is used, connected, and push is allowed.
  • Digital delivery list: starting a tour notifies recipients by SMS or e-mail (per setting).

6.13 Retention, validity and password policies​

  • Mailbox documents are deleted after 2 years; reprinting an invoice in IXOS re-syncs it to the customer account.
  • External design link for the portal: valid 24 hours.
  • IXOS.view confirmation link: valid 48 hours.
  • IXOS.view password: at least 8 characters, with at least 1 lowercase letter, 1 uppercase letter, 1 digit and 1 special character.
  • Web-shop prescription-image task: due 15 minutes after arrival.
  • Assortments shown in App & Web: at most 6.
  • Mauve document-list query: up to 3 configured times.

6.14 Counter-scan matching​

  • An item is accepted into a container only if the container's group matches the item's group (IXOS labels), or if the container is still unlinked (own labels, which then become linked).
  • A container already linked to another tour or group is rejected with the error sound.
  • Separate narcotics containers are possible only with IXOS labels.

6.15 Web-shop orders at the POS​

  • Items cannot be dragged out of a web-shop sub-total, and its lines cannot be split.
  • A shop coupon excludes redeeming an IXOS value voucher at the same pickup.
  • Coupon sales should not be closed with payment type invoicing.
  • Shop price vs. in-store price is handled per setting: manual price, or a choice dialog.
  • Customer creation: a regular customer by default; a walk-in customer if not uniquely identifiable (deleted by the deletion routine).
  • External numbers are text; search them with % wildcards.

7. Configuration and settings​

ParameterScopeEffectDefault
Packen im Backoffice (No / Yes / Yes incl. printing)System (POS settings > print options; Sales > Liefermanagement > Packen)Where and when courier documents print, and whether packing is a separate stepPrint at sale completion (No); "Yes incl. printing" recommended
Druckanzahl BotenbonPOS and invoicing separatelyCopies of the courier receiptPOS 1, invoicing 0
Druckanzahl BotenetikettPOS and invoicing separatelyCopies of the bag labelPOS 0, invoicing 1
Druckanzahl PacklisteSystemCopies of the pack list1
Druckanzahl ZusatzbonSystemCopies of the supplementary receipt1
Zusatzbon trotz bezahlter Botenlieferung druckenSystemPrint the supplementary receipt even when the delivery is paidnot stated
Druckanzahl LieferlisteSystemCopies of the delivery listnot stated
Druckanzahl Lieferliste mit ArtikelSystemInternal delivery list including items0
Druckanzahl Lieferliste für TourstationSystemPer-station patient-level item list0
Empfangsbestätigung druckenSystem settings > Sales > POS > print optionsAuto-print and format of the narcotic/Rx receipt confirmationnot stated
Credit slip on credit (Kreditschein)SystemPrint a credit slip when a shortfall becomes creditOff
Nummernkreis Abholung = EigeneSystemOwn number range for pickups; courier-marked sales still print the supplementary receipt, courier receipt and pack list—
Courier-receipt print form: courier section, amount acknowledgement on customer/courier part, placeholder for customer name, barcode and numberPrint formLayout and content of the courier receipt; barcode needed for scan-to-select-stationCustomer section only
Delivery list print form "Botentour" (expert copy)Print formCustomisable; the vendor no longer validates legal compliance of edited copiesStandard
Nächste Tour vorschlagenPOS system parameter (print options)Propose the next feasible tourOn
Gegenscanmodus (1–4)System (Pro)IXOS or own labels; counter-scan after or before the item scannot stated
Präfix Verpackungseinheit-CodeSystem (Pro)Prefix recognising own container labels—
BtM separat packenSystem (Pro)Separate narcotics container label (modes 1–2)not stated
Gegenscan Gruppe/Verpackung umgehenSystem (Pro)Allow the bypass buttonnot stated
Success/error sounds for counter-scanSystemAudio feedback—
WWKS2-Packungsinformation für securPharm verwendenSystemTake securPharm pack data from robot retrievalnot stated
Split packable vs. back-order items into two stationsSystem (Packen, Pro)Separate stations per availabilitynot stated
Per-tour settings (3.1): counter-scan, avg packs per container, route mode, dwell time, password, courier e-mail, printed/digital list, overview map, ApoTune, customer assignment, exclusive flag, preparation times, delivery behaviour, display countTourSee 4.2 / 6.1Display count 3 weekly / 1 monthly; assignment none
"Kunde anrufen" (call customer)Delivery list settingShow phone numbers with one-tap call in the courier appnot stated
Customer notification on tour start (SMS/e-mail)IXOS settingNotify recipients with the ETAnot stated
SumUp Account (Affiliate Key)System > Sales > Liefermanagement > cashless paymentLink the card terminalEmpty
Separate BelieferungHome/clinic contact structureDeliver to the unit vs. the whole homenot stated
Bevorzugte TourCustomer/home contactHighest-priority tour proposalEmpty
Meine Apotheke: availability displaySystem parameter group "Meine Apotheke"Show stock availability in app/webnot stated
Lagerstatus anzeigen für App & WebSystem (each network pharmacy)Prerequisite for network availabilitynot stated
Allow courier deliveries via appSystem parameter group "Apothekenverzeichnis"Offer courier in app/webOff
Courier radiusSameMax distance for app courier orders (licence-dependent)not stated
Botendienst in Gematik-AppSystemOffer courier to national e-prescription app usersnot stated
Pickup station namesSystem > Meine ApothekeStations selectable by customers—
Infocode für App Meine Apotheke druckenReceipt print formQR to the app on receiptsOff
Bestellung beim Eintreffen erinnernNotes, per workstationPop-up on arrival of online ordersOn (implied)
Automatisch ReservierenSystemDefault reservation mode for Rezept.connect processingOn
Kontaktaustausch automatisch zulassenSystem > Beratung > Kontakte > AutomatisierungContact exchange in the network for all customersnot stated
Meine Apotheke: Online-ZahlungCompany master > external servicesLink PayPalInactive
PayPal pay-laterCompany masterOffer pay-laterDepends on eligibility
Consent declaration / privacy texts / imprintCompany master > ConnectLegal texts shown to customersVendor default
Colours & logos, portal configurationCompany master > ConnectBranding of app/portal—
GEDISA-IDCompany masterEnables health-card (CardLink) e-prescriptionEmpty
Webshop: pack list auto-print workstationCompany master > WebshopAuto-print pack lists on arrivalnot stated
Webshop: Automatische Bestandsbuchung / Auch beim WareneingangCompany master > WebshopStock booking of mail-ordersnot stated
Webshop: price difference handlingCompany master > WebshopManual price vs. choose-price dialognot stated
External order partner (ADAS/Mauve), document-list query times (≤ 3), key pairCompany master > E-Datenaustausch / ConnectWeb-shop link—
Mauve: automatic vs. manual transfer; delivery note / stock deduction at order vs. at goods receiptShop / settingImport behaviournot stated

8. Roles and permissions​

  • "Liefermanagement: Tour optimieren": required to optimise a tour and release it.
  • Media.connect: visible only to the role "Leiter" (manager) or users with the right "Media.connect starten".
  • Online payment setup: "Meine Apotheke: Online-Zahlung verwalten" (workstation protection) plus "Firmenstamm: Modul starten".
  • Klinik.connect pharmacy user management: only authorised persons can create users, rights and passwords; a right can be granted only by someone who holds it. Users belong to groups with rights levels.
  • Branch tours: creator-only editing and deletion; start-pharmacy-only stopping and moving of foreign stations (6.6).
  • Settlement location: a POS-licensed workstation is expected (licence "Kassenarbeitsplatz").
  • External users:
    • doctors see only the residents assigned to them;
    • clinics, homes and doctors log in with generated user names and passwords they must change on first login (doctor, clinic);
    • app customers can only change their data through the pharmacy.
  • Courier: needs the tour password (once per device per tour); no IXOS login.
  • Data protection: the internal delivery list with item names must not be given to a non-pharmaceutical courier.

9. Integrations, hardware and external services​

  • Google Maps: geocoding of addresses, map points, delivery-area polygons, tour maps in IXOS and in the courier app.
  • ApoTune: external tour-optimisation service; per-tour hand-off with a unique tour ID and resend on failure.
  • Courier web app (digital delivery list): a progressive web app on iOS/Android, delivered by e-mail link or QR, protected by a tour password, offline after start. It uses the device's navigation app and phone dialler.
  • SMS / e-mail gateway: tour-start notifications with expected time; order status notifications; app/portal e-mails.
  • SumUp Solo Lite: card terminal via the SumUp app on the courier's device, linked by affiliate key.
  • CashGuard: cash recycler at the settling workstation.
  • Picking robot (Kommissioniersystem, WWKS2 protocol): retrieval per item/station/group/tour, per-group tub assignment for clinics, pack data for securPharm, immediate retrieval for mail-orders with automatic booking.
  • securPharm [DE-SPECIFIC]: verification and decommissioning of serialised packs at packing or counter-scan; batch and expiry capture. General idea: anti-counterfeiting pack serialisation checks at dispensing.
  • Printers:
    • POS receipt printer (courier receipt, supplementary receipt, confirmations); the info code needs Epson TM-J7500, TM-J7700 or TM-T88V;
    • label printer (bag labels; Dymo needs a technical setting; thermal-transfer container labels 90 mm wide);
    • A4 (delivery lists, container labels 4 per sheet, prescription images).
  • Scanners: barcode/data-matrix scanners at packing; QR container labels; the Xplore DT4100 handheld (Artikelscan.mobil) over WLAN; Code-39 / DataMatrix own labels for IXOS.team clinic packing; a prescription scanner at care homes (Rezept.connect, with a vendor driver and .NET runtime).
  • Customer-facing display: shows the app-connect QR; kassenTV content (Media.connect).
  • PayPal: online payment (PayPal, pay-later, SEPA, cards), refunds; no health data is shared.
  • GEDISA / CardLink [DE-SPECIFIC]: health-card-based e-prescription retrieval in the app. General idea: retrieving a patient's e-prescriptions by authenticating with a national health ID card.
  • gematik e-prescription app [DE-SPECIFIC]: national app sending e-prescriptions to the pharmacy's order list. General idea: interoperable national e-prescription routing.
  • Pickup terminals: integrated (robot, lockers, BD Rowa pickup) or stand-alone.
  • Web shops:
    • standard interface ADAS (v2.1+) for many shop vendors;
    • Mauve interface (System 3 back office, tub control, document lists, public-key exchange);
    • "IhreApotheken.de" feeds prescription-image tasks directly.
  • IXOS.campus / IXOS Chat server (IXOS.team); IXOS.view portal; IXOS.eCall (support messages).
  • Document management system (DMS): recommended for scanned signed consent forms and receipt confirmations.

10. Printouts, reports and exports​

  • Courier receipt (Botenbon): POS receipt printer; stapled to the bag.
    • Content: pharmacy data; heading; customer name/address or deviating delivery address; tour name and delivery date/time; phone and mobile (on the courier part, or on the customer part if no courier part); amount the courier must collect; free-text courier notes (for example "ring 3 times"; only text the customer may see); operator; barcode labelled "courier delivery: <pickup number>". For invoicing the barcode carries the delivery-note number (if one exists) or the order number.
    • Default: customer part only, on which the courier acknowledges payment.
    • Optional courier part: carries the missing-prescription note (if there is no courier part, that hint appears on reprints for the customer, not on the first print). Without a courier part the delivery time is on the customer part. The courier may use the courier part instead of, or in addition to, the delivery list to note the prescription received, the amount received and the customer's acknowledgement.
    • Variants: a cold-chain note; a narcotics note with an automatic "hand over personally" hint.
    • Partial deliveries: the receipt shows only the open sum of delivered items. Reprint choices offer the receipt for the packed partial delivery or for the next delivery.
  • Bag label (Botenetikett): label printer. Delivery address (the deviating address from delivery conditions is printed), tour and time, whether a prescription must be handed in, amount to pay. Partial-delivery logic as for the courier receipt.
  • Pack list (Packliste): item and customer data, ordered quantity, storage location, product number, supplier, total.
    • Printed automatically by default for POS courier sales; placed in the pickup shelf, later in the bag so the customer can check completeness.
    • Cannot be reprinted once fully packed (no open quantity); reprint it from the predecessor entry in sales management. From delivery management only open items print.
    • Partial deliveries list only the delivered items.
    • Cross-branch sales print a pack list titled "pack list for courier delivery (branch & partner)" in the dispensing pharmacy.
    • Web-shop pack lists show the external number and a pre-order/shipping marker; mail-order pack lists have no prices or amount due and include the customer's shop text.
  • Supplementary receipt (Zusatzbon): references the POS receipt number. Lists items handed over immediately and items to be delivered, grouped by sub-total, with prices and total. Reprintable from sales management for any POS transaction.
  • Courier receipt confirmation for narcotics and prescription-only items: receipt roll or A4; printed at plan/pack, in Deliver/Settle, or automatically after the sale. The pharmacy stores the signed paper (for example scanned into the DMS with the delivery list). In the archive, a receipt confirmation including the digital signature, comments and notes can be printed per station/customer.
  • Delivery list (printed, "Botentour" form, A4, without item names):
    • customer name and phones, delivery time, amount due;
    • totals of amounts due and of expected prescriptions;
    • tick fields for delivered and for prescription received; amount received; document number; free text; the station's originating branch.
    • No item barcodes: deliveries are resolved by settling the tour.
    • Several deliveries to the same person at the same address are merged into one line.
  • Tour-level print selection in Deliver/Settle: internal delivery list (standard); internal delivery list with items (internal only); delivery list per tour station (patient-level item listing for homes/care services with one crate); overview map in optimised order; QR code for the digital list.
  • Plan/Pack print selection:
    • tour pack list: unpacked stock items, no customer reference, showing unpacked total quantity and the quantity on order although stocked;
    • pack list per group: one page per group;
    • container labels per group/packaging unit: count computed from the average packs per container. Formats: A4 form (105 × 148 mm, 4 per sheet) and thermal-transfer 90 mm single-lane (the help gives 90 × 150 in the form name and 90 × 105 mm in the text).
      • Content: home, home unit, delivery address, tour, date, time, running container number, pharmacy name and address, QR (only when the tour has counter-scan on).
      • Narcotics label marked "BTM" with the running number when narcotics are packed separately.
    • labels for selected (large) items; address labels for own-label containers.
  • Homes/clinics: pack list per group from the print function.
  • Statistics export (Archive) to Excel: "tour list" (all tours) and "tour list with stations" (adds level-2 stations: customer/home/unit name, status info, deviating delivery address in brackets). Save, or open in Excel.
  • Delivery/Settle reprints: delivery list (with preview), documents of a single delivery item.
  • App/portal: password letter and registration form with login QR; consent declaration; Connect access-data overview for doctors, clinics and homes; digital receipt PDF; documents in the mailbox (receipts, co-payment, prescription and purchase evaluations).
  • Order tasks: prescription image on A4.
  • Reminder slip (Erinnerungsbon) for web-shop prescription-image orders.
  • Reports:
    • customers with app access (master-data field "Meine Apotheke");
    • sales fields "Verkaufskanal" (sales channel), "externes Verkaufssystem" (external sales system), "Rabatt-Coupon-IDs".
  • IXOS.view PDFs: Management Report 4.0, RX 5.0 success control, non-Rx market report.

11. Dependencies on other modules​

  • POS (Kasse): source of pickups marked for delivery; pickup/delivery dialog with tour proposal; reservation "customer not present"; pickup resolution; special items for bonus redemption; digital receipt; transaction carousel.
  • Invoicing (Faktura): delivery notes and collective delivery notes, delivery conditions, invoicing permission; mail-orders become invoicing orders; homes are preset to invoicing.
  • Sales management (Verkaufsverwaltung): editing and correcting delivered sales; external-number search; receipt icons.
  • Open items (Offene Posten): credits from settlement; back-orders tab for web-shop and app orders.
  • Prescription debt (Rezeptschuld) and prescription scan / e-prescription handling: missing prescriptions at settlement; photo and e-prescription orders; discount-contract and substitution checks.
  • Contacts (Kontakte): preferred tour, home/clinic structure and separate delivery, phone remarks, app access data, Connect access, duplicate merge, contact exchange.
  • Notes / tasks: order list, today's tasks, messages, text modules.
  • Goods receipt / goods logistics / purchasing: back-order arrival triggers packing eligibility and notifications; customer-reference icon; tub query; substitute handling.
  • Item management: storage locations, storage conditions, own sale price, stock-control journal.
  • Prices and calculation (Preise und Kalkulation): offers, usage models, price lists, price schemes for web shops; customer discount models.
  • Customer bonus models.
  • Medication management (Medikationsmanagement): intake plans pushed to the app.
  • Reports: customer and sales result categories.
  • Company master (Firmenstamm): Connect, external services, web shop, e-data exchange, opening hours, customer display, securPharm "verify packs".
  • Branch/partner network configuration and stock/price/contact exchange.
  • Picking robot and securPharm interfaces.
  • Customer info (IXOS.Kunde) for the duplicate/consent task.
  • Coupon management (not required for shop coupons).
  • Blister management, cost estimates, prescription requests, prescription management: listed in the Sales menu, documented elsewhere.
  • Z-report / cash book: settlement money.

12. Portability notes​

Generic and directly reusable for Shefa:

  • Courier tours:
    • one-time and recurring templates with generated instances;
    • preparation-time cut-offs separately for stock and ordered goods;
    • total vs. partial delivery behaviour;
    • automatic tour proposal with a clear priority order (preferred tour > customer segment by saved query or map polygon > next feasible tour).
  • Three-level station model (tour > stop/group > recipient), so institutional customers are one stop.
  • Packing with scan-to-station allocation, auto-close of complete stations, resumable sessions, partial deliveries chained as successor documents.
  • Container counter-scan for institutional deliveries, with group-bound labels, merge/release, and container numbers on the delivery note.
  • Mobile courier PWA: tour password, offline after start, signature mandatory for controlled items, cash/card capture, "not met" revisits, ETA notifications, proof-of-delivery printout.
  • Settlement: one-step tour settlement into the cash day-end; per-item received amount with credit-to-account or write-off for shortfalls; "correct later" and "settle later" escape hatches; group restrictions.
  • Multi-branch shared tours with ownership rules and decentral settlement.
  • Unified inbound-order inbox for app, portal, B2B portals and web shops: execute into a reserved sale, auto-notify on stock arrival, "done without sale" path, messages with templates.
  • Customer app/portal: QR-based onboarding at the counter, consent capture, pharmacy-network ordering with origin-pharmacy pricing, digital receipts with retention, pickup lockers with codes, online prepayment with explicit exclusions and refund paths.
  • Rules for automatic offers (in stock, price floor, minimum discount vs. RRP).
  • B2B portals: for prescribers (only their own patients), hospitals (group-based rights), care homes (scanner client with an offline queue).
  • Web-shop connector pattern: catalogue/price export, order import as tasks, external order numbers stored as text, sales-channel tagging for reports, coupon as discount-after-total, mail-order invoiced externally with optional automatic stock deduction, write-back of the final items.

Germany-specific, with the idea underneath:

  • securPharm verification at packing: serialised-pack verification and decommissioning at dispensing (useful wherever track-and-trace or anti-counterfeit codes exist).
  • E-prescription token, CardLink/GEDISA, gematik app: routing electronic prescriptions from patient to a chosen pharmacy by token scan or by national ID-card authentication.
  • Statutory-insurance prescription status, payer ID (IK), discount contracts, aut-idem, Muster-16: payer-specific prescription validation and substitution rules applied when converting a remote order into a sale.
  • Sprechstundenbedarf: a separate billing class for supplies ordered by a practice for its own use.
  • Narcotics (BtM) receipt confirmations and separate containers: controlled-substance chain-of-custody evidence.
  • Z-report / cash-book / GDPdU audit: a fiscally auditable cash journal that delivery settlements must flow into.
  • Imprint, consent declaration, BFSG accessibility: legally mandated publisher information, explicit health-data consent, and accessibility conformance for patient-facing portals.
  • Pro billing by beds per month: a vendor licensing model, not needed for Shefa, but the metric "unique residents supplied per month" is a useful KPI.

13. Open questions​

  • Tour states: the exact state machine (beyond unplanned / not packed / fully packed / in delivery / settled / expired) and the column "delivery status" values used in the filter are not listed fully.
  • Defaults not given: delivery-list copies, receipt-confirmation format, counter-scan mode, narcotics separation, bypass, WWKS2 option, call-customer option, ETA notification, mail-order booking options and price-difference handling.
  • "Bestellung beim Eintreffen erinnern": the default is only implied (on).
  • Courier radius: units and licence limits are not stated.
  • Tour optimisation: the algorithm and whether time windows (desired delivery times) are respected are not described; the same for how ApoTune results flow back.
  • Notification wording and timing: what exactly is sent and when, by SMS or e-mail, at tour start (only "per IXOS setting").
  • Digital delivery list offline handling: the help says steps work offline but not how conflicts or late uploads are reconciled.
  • Partial-delivery rule: why the restriction applies from the 3rd partial delivery, and whether it also affects later partial deliveries, is not explained.
  • Container label size: inconsistent (form name 90 × 150, text 90 × 105 mm).
  • IXOS.team OS requirements: inconsistent (iOS 16.6 vs. 12.5.5 in the FAQ).
  • Availability display: what exactly is shown (levels, quantities) — the help only has a screenshot.
  • Online payment: the "order quantity > 3" exclusion is ambiguous (units or lines).
  • Klinik.connect: order approval workflow and statistics on the clinic side, and the difference between the two web-app generations, are not described.
  • Heim.connect: documented in a separate help that is not in this slice.
  • Mauve document-list query: the frequency basis of the "up to 3 times" (per day?) is not stated.
  • Branch tours: how money is reconciled between branches for cross-branch sales is not described.
  • Web-shop notifications: whether "ready for pickup" e-mails are triggered automatically depends on the shop provider; there are no details.

14. Source pages​