One order,
one continuous flow.
Intake to recall.

Orders arrive from the partner API, the partner portal, a subscription refill or a marketplace award. The API is idempotent on the partner's own order id, so a retry never creates a duplicate. Before an order is accepted, the ship-to state is checked against your licence table — no licence row, or an expired one, and the order is held rather than let through. A controlled-substance flag tightens the gate further.

• ✓Statuses: Received → Eligibility → Clinical Review → In Production → Packed → Shipped, with On Hold and Cancelled as explicit branches
• ✓Order routing to a facility by rule; brand and facility stamped on the row
• ✓Partner webhook order.received / order.held sent from an outbox with retries

A master formulation generates every strength and fill volume as a controlled variant with its own bill of materials and cost. Planning a batch consumes specific raw-material lots with quantities, so genealogy is a table you can query rather than a list you hope is complete. A batch enters production as In Process and only becomes Released after QC — and its beyond-use date can never exceed the shortest component expiry.

• ✓Formulations, batches, cost & margin per variant (compounding software)
• ✓Purchase orders, receiving, QA & putaway, FEFO lots and locations, inter-site transfers
• ✓Demand & planning from order history (inventory)

At the fill station the line claims a released finished lot (FEFO, atomic — the same unit can never be committed twice), mints a GS1 serial for the unit and writes a commissioning event. Pack and verify each add their own event. An order cannot reach Shipped unless pack-verify passed; that rule lives in the database, not in the screen.

• ✓Production line, dispensing, pack verify and label printing as shop-floor screens sized for touch
• ✓Per-unit journey: commissioned → packed → verified → shipped (how serialization works)
• ✓A Control Tower dispatches receive / putaway / pick / pack tasks to people and machines through one task API (fulfillment automation)

Because every unit is serialized and every batch records which raw lots it consumed, a recall starts from any handle — a raw-material lot, a batch, a finished lot or a single serial — and resolves to the exact units, orders, patients and parcels affected. Disposition is tracked per unit. Trace & Recall and Unit Trace are standard screens, not a services engagement.

• ✓Recall by unit, lot or batch, with per-unit disposition
• ✓Unit Trace: the EPCIS-style event ledger for any serial
• ✓Event log across the tenant for audit