Fulfilment
Warehouse release, split shipments, tracking and cancellation acknowledgement.
View filterStatusReleasedAcceptedPickingPacked
- LCT-120: FLF-90430, 15 Oct to 20 Oct, Released
- LCT-140: FLF-74267, 12 Oct to 19 Oct, Accepted
- LCT-130: FLF-17867, 04 Oct to 13 Oct, Picking
- LCT-140: FLF-30732, 13 Oct to 18 Oct, Packed
- LCT-140: FLF-79107, 16 Oct to 19 Oct, Released
- LCT-140: FLF-83717, 18 Oct to 23 Oct, Accepted
Give each warehouse a bounded instruction
The Fulfilment workspace creates location-specific work from approved orders and current reservations. A warehouse instruction names the original order lines and reserved quantities it may pick. It also records an owner, slot and external request identity. A warehouse split changes where work happens while preserving the customer’s purchase and remaining balance.
Warehouse acceptance is an explicit result. Sending a request creates an outstanding handoff, not proof that a partner has accepted it. A timeout leaves the result unknown until the connector queries or reconciles the request. Resending under a fresh identity could create duplicate picking work, so unchanged retries must keep the original command key.
Pack and dispatch only assigned quantities
Picking and packing operate within the quantities assigned to a fulfilment. A partial pack can support a partial shipment while leaving the rest open. Dispatch requires the package’s exact line allocations, evidence and stable shipment identity. The system must validate those quantities and consume the corresponding reservations in the same controlled operation.
| Work state | What it establishes |
|---|---|
| Released | An instruction has been prepared and sent |
| Accepted | The warehouse acknowledged responsibility |
| Packed | Specific assigned quantities are ready for dispatch |
| Dispatched | A confirmed handoff consumed those quantities |
| Delivered | A separate delivery observation was received |
Order status derives from the sum of accepted line outcomes. An order with shipped goods and remaining demand stays partly fulfilled. A tracking event must never close an unrelated line or create additional stock consumption. The split fulfilment process follows these transitions across locations.
View filterStatusReleasedAcceptedPickingPackedCancelRequested
Handle late cancellations explicitly
A customer cancellation can arrive while a warehouse is already picking. Once work has been accepted, the local request becomes a cancellation request awaiting the warehouse response. Reservations remain attached until that response confirms what can actually be stopped. A refused cancellation or a dispatch that wins the race remains visible to the order desk.
The system can then distinguish the quantity cancelled before shipment from the quantity that needs a return. This avoids an order showing no outstanding goods while a live warehouse instruction still exists. Address changes use the same caution: a revised address does not change a package already handed to a carrier, and the new order revision cannot silently amend the previous dispatch evidence.
Keep tracking observations in context
Carrier updates are recorded as observations with their own identity and occurrence time. Duplicate messages do not repeat effects. Late messages do not move a delivered package backwards merely because they arrived last. Conflicting status requires a provider lookup or reconciliation under the connector’s agreed rules.
The customer-facing history should show each package, tracking reference, outstanding balance and exception. A missing delivery event remains unknown. Cost analysis uses actual charges supplied by a configured source; an absent charge is not a free shipment. Carrier label purchasing, warehouse hardware and delivery guarantees are outside this order-management scope.
View filterStatusDispatchedInTransitDeliveredException
Modules
-
Orders
Order intake with channel identity, commercial checks, approvals and traceable amendments.
-
Allocation
Available-to-promise, reservations and backorder resolution grounded in stock authority.
-
Fulfilment
Warehouse release, split shipments, tracking and cancellation acknowledgement.
-
Returns
Return authorisation, inspection, disposition and independently approved refunds.
-
Pricing
Price snapshots, customer agreements, discount exceptions and refund allocations.
-
Reports
Order, stock, delivery and refund reporting with explicit unresolved outcomes.
Reports
All reportsSplit Shipment Cost
Show dispatch count and recorded carrier charges per order when a configured cost source supplies them; missing costs remain unknown.
Roles and permissions
Allocates stock and manages uncovered demand.
Confirms warehouse work and shipment evidence for assigned locations.
Maintains mappings and resolves transport and reconciliation failures.
Related processes
Allocation and backorders
Reservation, uncovered demand, customer promises and consented substitutions.
6 stages · 1 approval
Split fulfilment and tracking
Location-specific warehouse work with partial shipment and tracking reconciliation.
6 stages · 0 approvals
Order changes and cancellation
Revision-bound changes that respect accepted warehouse work and customer commitments.
6 stages · 1 approval