Split fulfilment and tracking
Location-specific warehouse work with partial shipment and tracking reconciliation.
6 stages · 0 approvals
Roles and responsibilities
-
Step 2Obtain warehouse acceptance
Message NumberChannelPurposeCommand KeyStock Read
-
Step 3Confirm picked and packed quantities
Fulfilment NumberOrderLocationStatusAccepted
-
Step 4Record partial dispatch
Shipment NumberFulfilmentCarrierTracking Number
-
Step 5Reconcile delivery observations
Shipment NumberFulfilmentCarrierTracking Number
-
Step 6Resolve the outstanding balance
Backorder NumberOrder LineQuantityResolutionAlternative Location
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Prepare the warehouse instruction
Inventory Planner groups eligible reservations by order and location. Each work line retains its reservation and original order line. The sum of active assignments cannot exceed the reserved quantity, and a reservation cannot be reused by a second concurrent split.
Obtain warehouse acceptance
Integration Operator sends the stable fulfilment request. A confirmed acknowledgement moves the instruction to Accepted. A timeout leaves an unresolved handoff to reconcile under the original identity; a second request with a new identity is not a safe recovery strategy.
Confirm picked and packed quantities
Fulfilment Operator records the quantities actually prepared at the assigned location. Short picks leave demand open and trigger an allocation exception. The operator cannot increase the assignment, substitute another SKU or edit the customer's commercial values through the packing action.
Record partial dispatch
Fulfilment Operator confirms a shipment's exact line allocations and handoff evidence. The server consumes those reservations and increments shipped quantities once for the stable shipment identity. It retains a pending stock debit until the authority confirms the same movement. Remaining lines keep the order partly fulfilled.
Reconcile delivery observations
Integration Operator records carrier events and checks their source identity and ordering rules. Duplicate events do not repeat effects; late events cannot regress a known delivered state without a verified correction. Order Desk follows each exception and communicates the remaining obligation to the customer.
Resolve the outstanding balance
Inventory Planner reviews shortages, unused allocations and replenishment. Order Desk submits any customer-requested cancellation through the commercial change process. Closing the order requires every line and external handoff to reconcile; a delivered package does not erase another location's unresolved work.
Approvals and exception handling
0 approvals required in this process
- This preparationExecution process adds no discretionary approval gate; commercial exceptions use the separate Order Manager decision.
- A shipment identityChanged line quantities is a conflict, not another dispatch.
- Warehouse cancellation after acceptance requires an acknowledged outcome before quantities or stock are released.
- Test a partial packMultiple locations, a lost warehouse acknowledgement, repeated dispatch and out-of-order tracking observations against the same order.
When the process needs attention
-
shortage
Confirm picked and packed quantities
Short picks leave demand open and trigger an allocation exception.
-
variance
Reconcile delivery observations
Duplicate events do not repeat effects; late events cannot regress a known delivered state without a verified correction.
-
shortage
Resolve the outstanding balance
Inventory Planner reviews shortages, unused allocations and replenishment.
One purchase across several dispatches
An order can be allocated across locations or shipped in parts as goods become available. The process retains the original order-line obligation while separating each warehouse instruction and package. A customer should be able to see what shipped, which package contains it and which quantities remain open. Preparing or releasing work does not by itself establish dispatch.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Prepare the warehouse instruction | ReservationsFulfilmentsFulfilmentLines | Assign bounded work to a location |
| 2 Obtain warehouse acceptance | IntegrationMessagesFulfilments | Record the actual external acceptance |
| 3 Confirm picked and packed quantities | FulfilmentLines | Establish the packed quantity available to ship |
| 4 Record partial dispatch | ShipmentsReservationsOrderLines | Consume only the confirmed dispatched quantity |
| 5 Reconcile delivery observations | ShipmentEventsShipments | Update verified tracking outcomes |
| 6 Resolve the outstanding balance | BackordersOrdersChangeRequests | Keep remaining demand accountable |
Process reports
All reportsOrder Fill Rate
Compare accepted units with shipped units by order cohort, channel and SKU; show cancellations separately and never silently remove unmet demand.
Backorder Age
Show uncovered quantities, first unresolved date, next review date and supply evidence by owner.
Promise Reliability
Compare first accepted promise and latest agreed promise with evidenced delivery; retain revised commitments and exclude unconfirmed tracking outcomes from on-time claims.
Split Shipment Cost
Show dispatch count and recorded carrier charges per order when a configured cost source supplies them; missing costs remain unknown.
Order Cycle Time
Measure source acceptance to release, dispatch and delivery separately, with holds and unresolved stages visible.
Run by an agent
Agent support
The assistant cannot approve its requester's own commercial exception or refund, invent stock or provider evidence, assume customer consent, or treat a timeout as a failed payment. It cannot expand its permissions or treat a credit export as a confirmed accounting posting. Product substitutions, commercial exceptions and refunds retain their specified human decisions.
# Example after configuration
curl -fsSL https://www.erp.ai/skill.md
# Paste the output into your agent
split fulfilment and tracking · prepare the warehouse instruction on Reservations, Fulfilments, FulfilmentLines
Inventory Planner groups eligible reservations by order and location.
split fulfilment and tracking · obtain warehouse acceptance on IntegrationMessages, Fulfilments
Integration Operator sends the stable fulfilment request.
split fulfilment and tracking · confirm picked and packed quantities on FulfilmentLines
Fulfilment Operator records the quantities actually prepared at the assigned location.
split fulfilment and tracking · record partial dispatch on Shipments, Reservations, OrderLines
Fulfilment Operator confirms a shipment's exact line allocations and handoff evidence.
split fulfilment and tracking · reconcile delivery observations on ShipmentEvents, Shipments
Integration Operator records carrier events and checks their source identity and ordering rules.
split fulfilment and tracking · resolve the outstanding balance on Backorders, Orders, ChangeRequests
Inventory Planner reviews shortages, unused allocations and replenishment.
Other processes
4 moreOrder intake and approval
Capture, duplicate checks and independent commercial approval before release.
5 stages · 1 approval
Allocation and backorders
Reservation, uncovered demand, customer promises and consented substitutions.
6 stages · 1 approval
Order changes and cancellation
Revision-bound changes that respect accepted warehouse work and customer commitments.
6 stages · 1 approval
Returns and refunds
Independent return, inspection and refund decisions with provider reconciliation.
6 stages · 2 approvals