Allocation and fulfillment

Allocation Lead works from the order’s individual style variants, not a single order total. The allocation action considers lines marked Draft or Open. It records an Allocated event for each eligible line when that event is not already present, marks the lines Allocated and writes a receipt for the run. The action also approves the parent order. Review the decision history and receipt before treating that status as a separate human approval.

Fulfillment Lead releases an Approved order. The release action walks the lines, creates Shipped events, marks the lines Fulfilled and advances the order to Executed. One receipt covers the release run. Event records also accommodate pick, pack, delivery and return or exchange activity, with a location, units and occurrence date. Keep those events tied to the source order so a support agent can reconstruct the order’s movement.

• Line allocation. Check each style, color and size line and its existing allocation events.
• Shipment release. Confirm the Approved order and record Shipped events against the lines.
• Event history. Read units, location, event type and status alongside the operation receipt.

Agree how the team identifies the DC or store location and who can record a shipment event. Decide how quantities on order lines are checked against event units before release. Set ownership for a shortage exception when the requested variant cannot be supplied. Because the allocation action can approve the parent order, the team must agree where a human review decision is required in its operating procedure and test that handoff during setup.

A channel handoff and a shipment are different facts. The handoff captures the channel and external reference; the shipment event records units and occurrence. Keep their source order aligned. A carrier or warehouse system may return additional detail through a connection, while the order record remains the team’s common reference.

Use a two-line apparel order with separate colors. Run allocation once and inspect the Allocated events and line statuses. Run it again and confirm it does not create a second event for the same eligible line. After the required review, release the Approved order. Check that both lines are Fulfilled, each has its Shipped event, the parent is Executed and the receipt describes the release. If one variant cannot be fulfilled, log a stock shortage exception and resolve the scope before relying on a shipment total.

• Shipped, Delivered and Returned Events — Movement history for orders and support follow-up.
• Open Apparel Orders — Orders whose release still needs attention.
• Open Order and Support Exceptions — Shortages and shipping issues with named owners.

Use allocation and release and returns and support.