WMSWarehouse Management System

A Warehouse Management System (WMS) is the operational software layer that owns the physical movement of inventory — from the moment a truck backs onto the dock through to the moment a finished pallet leaves the building. Unlike the ERP, which tracks inventory at a financial and high-level quantity-on-hand level, the WMS tracks where every unit physically sits, in which bin, on which pallet, in which licence-plate container, at which storage temperature, against which lot and expiry. The unit of work is the move, the put, the pick and the count — not the journal entry.

A generic WMS is built for distribution centres optimising throughput. A regulated WMS is built for shop floors where the warehouse is a quality control checkpoint as much as a storage building. It enforces quarantine on receipt, holds material out of pickability until a QC person releases it, picks the lot whose expiry is closest (FEFO), and writes an attributable audit row for every status change so that an FDA, MHRA or BRCGS auditor can reconstruct any historical position.

Most regulated manufacturers historically ran the warehouse on paper or a thin module bolted to the ERP, with QC release tracked in a spreadsheet and FEFO enforced by tribal knowledge. That works at low volume but fails at audit. The modern expectation, articulated in 21 CFR 211.142, 21 CFR 820.150 and EU GMP Chapter 5, is that the warehouse system is part of the controlled environment — validated, audit-trailed, role-gated — not an afterthought.

Strip away the regulatory cladding and a WMS performs a finite set of operations. Every WMS, generic or regulated, has to do these nine things competently. The differences emerge in how each is constrained.

1. Receiving against a purchase order — capturing quantity, lot, expiry, supplier, country of origin and licence-plate ID at the dock.
2. Putaway directives — rule-based location assignment that accounts for zone, capacity, segregation rules and replenishment strategy.
3. Lot, sub-lot and serial tracking through every move, parent-child split, repack and consolidation.
4. Bin, pallet and licence-plate management — including nested containers (an SSCC pallet holding ten GS1-128 cases, each with a sub-lot).
5. Cycle counts, ABC counts, blind counts and full physical inventory.
6. Replenishment — line-side stock, forward-pick from reserve, kanban triggers.
7. Picking — by FEFO, FIFO, wave, batch or zone, with mobile or voice-driven workflows.
8. Packing and outbound pallet build, including SSCC label printing and EDI 856 ASN linkage.
9. Shipping — Bill of Lading, carrier integration, freight class, hazmat manifests, customer ASN transmission.

What people forget the WMS also owns

Returns, customer rejections, kit assembly and disassembly, sample pulls for QC, R&D withdrawals, stability programme handling, scrap and destruction with witness signatures, and engineering-change-driven obsolescence write-offs. These are the operations that make a regulated warehouse a regulated warehouse, and they are exactly the ones cheap WMS modules ignore.

The phrase "regulated WMS" is not marketing — it describes a specific set of behaviours that generic distribution-focused systems either lack or treat as optional add-ons.

Few topics generate more confusion in regulated manufacturing than where the WMS ends and the next system begins. The pragmatic answer is that the four systems handle different layers of the same business object, and they have to share data in real time without disagreeing about state.

The boundary that causes most pain is WMS↔MES. The moment a kit leaves the warehouse and arrives at a dispense booth, who owns the lot? In a clean integration the WMS issues the lot to the work order, ownership transfers to the MES, the MES consumes against tare-weighted scale data, and the residual returns to the WMS with a fresh putaway directive. In a bad integration the lot exists in both systems at the same time, the counts disagree by the time the shift ends, and someone manually "recounts" at month-end.

Under 21 CFR 211.142(a) every incoming component must be held under quarantine until released by the quality unit. The WMS implements this not as a label on a shelf but as a status flag on the lot: it exists, it has been received, it has a putaway location, but it is not pickable. Pick lists physically skip quarantined stock; mobile scanners reject attempts to consume it; the only operation allowed is the release-or-reject transition by a QC user with the right role.

A proper WMS supports at least four status states — quarantine, released, rejected and on hold — and lets the QC team apply a hold to any subset of inventory (one lot, one sub-lot, one pallet) without disturbing the rest. Holds are a recall-response tool: the second a deviation, complaint or supplier alert lands, the QC team places affected lots on hold, and the WMS prevents any pick until the investigation closes.

Sample pulls and stability allocations

QC pulls samples from incoming lots for identity, potency, microbial and stability testing. A regulated WMS lets the QC team withdraw a documented sample quantity from a specific lot, transfer it to a QC location, and link the sample to the test request. The remaining lot continues quarantined; the sample is consumed against the test request, not the production work order; if the lot ultimately rejects, the sample residual rejects with it.

Pick rules look academic until you watch an operator standing in front of two pallets of the same raw material with different expiry dates. The WMS resolves the question for them. In regulated manufacturing the default is FEFO — First Expired, First Out — because the shorter-dated material has to clear the building before it crosses its expiry. FIFO (First In, First Out) is the fallback when expiry is absent or identical.

• FEFO is mandatory for dietary supplements (21 CFR 111), pharma raw materials with expiry, and most food categories.
• FIFO is acceptable for stable items with no expiry — packaging, hardware, indefinite-shelf-life chemicals.
• LIFO is rare and usually a finance-only construct that does not drive physical movement.
• Manual override must be possible, but every override must capture a reason code and an e-signature.

The WMS should also let the production planner reserve specific lots against a future work order — a campaign-by-campaign strategy used to keep allergen production grouped or to honour customer requests for a specific country of origin. Reservations are soft until the work order releases; once released, the lot is hard-allocated and unavailable for other picks.

A licence plate is a unique barcode applied to a container — a pallet, a tote, a case — that carries everything inside it. Scan one barcode and the WMS knows the contents, the lot, the expiry, the supplier, the receipt date and the current location. Without licence plates, an operator scans every carton on every move; with them, one scan moves the whole pallet.

The dominant standard is GS1-128 (the barcode format) carrying an SSCC (the unique container identifier). The combination is used worldwide and is required by major retailers and most pharmaceutical wholesalers. EDI 856 ASNs reference the SSCC so the customer can scan the inbound pallet and resolve directly to its line items.

Parent-child relationships

A pallet contains cases, a case contains units, a unit contains components. Each level has its own licence plate, and the WMS holds the parent-child tree explicitly. When a finished case is built it is associated with its parent pallet; when it ships it is associated with its outbound shipment. Recall queries traverse this tree in either direction — forward ("this raw lot went into which finished cases?") or backward ("this finished case contained which raw lots?") — and produce a defensible answer in seconds.

Some materials cannot share storage. Allergens — peanut, dairy, gluten, soy, egg, fish, shellfish, tree nut, sesame — must be physically separated from non-allergen stock and from other allergens. Incompatible chemicals (oxidisers vs. flammables, acids vs. bases) must be physically separated. Controlled substances live in cages with restricted access. Cold-chain material lives in walk-in coolers or freezers with continuous monitoring. The WMS expresses each of these as zone attributes and refuses to direct putaway across incompatible zones.

Environmental monitoring sits naturally next to the WMS. Every cold-chain location has at least one calibrated probe logging temperature; many also log humidity, pressure differential or light. The WMS reads the probe feed and tags every move with the environmental conditions at the time of the move, so that excursion reviews can identify which lots were exposed.

An annual full physical count is expensive, disruptive and statistically inferior to a continuous cycle-count programme. A modern WMS supports ABC analysis — classifying items by movement velocity or value — and schedules cycle counts at frequencies appropriate to each class. A-class items might be counted weekly, B-class monthly, C-class quarterly. Discrepancies generate adjustment journals that route to a controller for approval; the adjustment becomes a CAPA trigger if it exceeds a threshold.

Best-in-class manufacturers track inventory accuracy as a top-line KPI alongside OEE and OTIF. Anything below 98% lot-level accuracy is a quality risk: it means picks are going to the wrong lot some fraction of the time, which means the production record contains lies. 99.5%+ is achievable in a well-run regulated warehouse.

Outbound is where the WMS meets the customer. The pick list is generated from the sales order, FEFO-sorted, mobile-driven; the pack station builds the outbound carton or pallet, applies the SSCC label, and stages the load. Shipping prints the Bill of Lading, transmits the EDI 856 ASN to the customer, and closes the shipment. Carrier integration adds the freight booking and tracking number.

• Pick — FEFO-driven, with mobile or voice workflow, and refusal of any quarantined or held stock.
• Pack — case-build, SSCC label, weight verification, optional carton-level photograph for evidence.
• Manifest — outbound pallet labelled, BOL printed, hazmat documentation attached if applicable.
• Ship confirm — physical departure logged, lot consumption posted, customer ASN sent.
• Track and trace — outbound shipment linked to carrier reference and delivery confirmation.

The EDI 856 ASN is the digital handshake. It tells the customer exactly what is on the truck, at what hierarchy (pallet > case > unit), with which lots, which expiries, which serial numbers and which SSCC licence plates. A failed ASN means the customer cannot scan-receive and your invoice gets short-paid. Modern WMSes generate the 856 automatically from the ship confirm and validate it against the customer's variant of the spec before transmission.

A regulated WMS is GxP-impacting and must be validated. The classical evidence stack is URS (User Requirements Specification) → FS (Functional Specification) → IQ (Installation Qualification) → OQ (Operational Qualification) → PQ (Performance Qualification), with traceability matrices linking every URS line to its OQ test case. GAMP 5 provides the framework, and EU GMP Annex 11 + 21 CFR Part 11 set the rules for the electronic-record side.

Part 11 in WMS terms means: every status transition is attributable (who did it, when, why), the record is time-stamped to a synchronised clock, the audit trail cannot be edited by the user, e-signatures are non-repudiable, and the system enforces role-based access. Modern cloud-hosted WMSes can satisfy all of this if the vendor commits to it; pre-cloud on-prem WMSes from the 2000s often do not.

Most WMS proposals look the same on the cover page. The real differences emerge when you ask hard questions about quarantine, FEFO, validation, integration and audit defence.

1. Show me the quarantine status flow. Can a QC user release one sub-lot without releasing the parent?
2. Show me FEFO in action. What happens if the operator overrides? Where is the override captured?
3. Show me a forward and backward trace for a recall scenario. How long does it take? Where does the report come from?
4. Show me the audit trail. Can a user edit it? Can an admin? What does export look like for an FDA Form 483 response?
5. Show me the validation pack. URS, FS, IQ, OQ, PQ — do you provide it, or do I write it?
6. Show me the ERP integration. Two-way? Real-time? What happens if the ERP is down for an hour?
7. Show me the MES integration. Where does the lot transfer happen? Who owns the count at any moment?
8. Show me the EDI capability. 856? 940? 945? GS1-128? SSCC? What's manual versus automatic?
9. Show me the mobile experience. Offline tolerance? Scanner support? Voice picking?
10. Show me the cost on day three of an FDA inspection. Concretely: which screen do I open, and what do I export?

V5's WMS is not a separate product. It is the inventory surface of the same platform that runs your shop floor execution, your quality system and your release. That choice has consequences both architectural and commercial.

Architectural consequences

• One Postgres schema for inventory, work orders, batch records and quality events. No data sync, no two-system disagreement.
• One audit trail. Every move, status transition, adjustment, pick and ship writes one tamper-evident row that the same auditor view consumes.
• One identity. The user logged into the kiosk is the user signing the receipt is the user releasing the lot. No SSO bridge, no parallel user database, no orphaned accounts.
• One label engine. GS1-128 / SSCC / Datamatrix labels render from the same template store the kiosk prints from at dispense.
• One mobile surface. The same kiosk shell runs receiving, putaway, picking and the cycle count — operators don't learn three apps.

Commercial consequences

Customers do not buy and integrate three products (ERP, WMS, MES) plus a QMS plus a label printer plus a validation consultant. They buy V5 Ultimate, keep their ERP for finance, and have the rest in one bill. For a Validated Enterprise multi-site customer this typically replaces three to five separate line items in the IT budget and removes the integration project entirely.