These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Size & Fit Recommendation
- Features
- Fulfillment and Returns
Fulfillment and Returns
Follow the product quantities handed over for an order and retain physical return evidence for later review.
OverviewFulfillment History×
Size & Fit Recommendation · Fulfillment and Returns
New
Fulfillment History
Fulfillment events
| Id | Parent | Product | Event type | Quantity | Occurred at | |
|---|---|---|---|---|---|---|
| IDD-486 | SO-80589 | PRD-4368 | Allocated | 240 | 23 Oct | |
| IDD-679 | SO-13651 | PRD-9795 | Picked | 770 | 14 Oct | |
| IDD-361 | SO-42073 | PRD-4196 | Shipped | 740 | 17 Oct | |
| IDD-638 | SO-83187 | PRD-8972 | Delivered | 250 | 26 Oct | |
| IDD-738 | SO-44107 | PRD-2084 | Allocated | 30 | 12 Oct |
6 of 6 records
IDD-486Fulfillment events · FE-87875
AllocatedParentSO-80589
ProductPRD-4368
Quantity240
Occurred at23 Oct
External event IDEEI-631
What you can do
Check the stock owner's entitlement before handover
Fulfillment Coordinator follows the order’s product scope with the actual owner of the stock. The guarded fulfillment action checks entitlement before recording allocation, picking and shipping events. Each event identifies the order and product with its quantity, occurrence date and external event identifier.
The order becomes Fulfilled only when every eligible unit has been handed over. Delivered and Returned events add further evidence to the physical history. Commerce Operator and Commerce Reviewer can use that history when discussing a customer question, while payment evidence separately establishes the financial outcome.
How the work is organized
- Eligible scope. Review the accepted order and its quantities before requesting fulfillment. Resolve the intended catalog product and stock owner’s authority so the handover uses the right merchandise.
- Movement history. Allocated, Picked, Shipped and Delivered describe successive stages. Keep their event identities and quantities distinct instead of adding each stage as though it were another sale.
- Return evidence. Returned events identify the product quantity received back in the physical process. Returned units on the sales lines support the order review, while a refund still needs its independent decision and provider evidence.
What to agree during setup
Connect the actual stock owner and agree how entitlement is checked. Define which handover event establishes completion for the customer’s fulfillment process. Decide how partial handovers are represented and reviewed before the order is marked Fulfilled.
Agree the relationship between sales-line SKU text and the catalog product referenced by a fulfillment event. Review duplicate or ambiguous SK us before starting the pilot. Set a reconciliation process for repeated external events and define how returned quantities reach the sales-line review. Keep the physical evidence available even when the associated financial action is still pending.
Check the handoff on an actual case
Use an accepted jacket order and confirm its eligible quantity with the stock owner. Fulfillment Coordinator follows allocation and picking into the handover record. Each stage retains its own event identity while referring to the same order and intended product.
Rehearse a partial handover and check that the remaining eligible units are still recognized before the order can become Fulfilled. Then resend an existing shipping event and confirm that it does not create another handover quantity. A missing stock entitlement needs resolution with the stock owner before execution proceeds.
Finally, record a returned garment and review the quantity against the original order scope. Commerce Reviewer can consider that evidence in a refund decision, but the return record should not be treated as confirmation that money has already been refunded. Keep the customer discussion clear about the physical and payment outcomes still being checked.
What your team sees
- Fulfillment History — Product movement events show quantity, stage and external identity for the order.
- Returned Product Events — Returned quantities remain visible for the physical-outcome review.
- Sales Order Board — The coordinator can follow the accepted order while reviewing its current state.
Follow the work through
What it keeps track of
Data model- Fulfillment events
- Allocated, picked, shipped, delivered and returned events
- Products
- Apparel product catalog with standard pricing
- Sales orders
- Priced sales orders carrying fit recommendation scope
- Sales lines
- Product lines belonging to a sales order
- Operation receipts
- Stable operation keys and persisted effect results
Who uses it
Permissions- Fulfillment Coordinator
- Works with the stock owner on handover.
- Commerce Operator
- Provides the order context.
- Catalog Manager
- Resolves product identity.
- Commerce Reviewer
- Reviews downstream refund evidence.
- Auditor
- Reads authorized movement history.
Set up Size & Fit Recommendation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.