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.
- E-commerce Fulfillment SCM
- Who it's for
- Marketplace operations
Marketplace operations
Marketplace teams often receive the same order or shipping notice more than once. The order's channel and external order ID identify the selling source. Fulfillment events carry external event IDs, and operation receipts carry operation keys. Together these records help the team distinguish a retry from new work while keeping the customer order as the operating anchor.
How E-commerce Fulfillment SCM is set up for you
Order identity
Check the marketplace order ID and current revision before confirming a draft.
Delayed messages
Preserve the event's occurrence date and external ID when a pick or shipping notice arrives after another update.
Exception review
Inspect pending, failed and needs-review operation outcomes against external references before sending another action.
Return evidence
Connect a Returned event to the shipped order and check the provider refund event separately.
Marketplace teams often receive the same order or shipping notice more than once. The order's channel and external order ID identify the selling source. Fulfillment events carry external event IDs, and operation receipts carry operation keys. Together these records help the team distinguish a retry from new work while keeping the customer order as the operating anchor.
Pilot one marketplace feed with known order IDs and a small product set. Include an import retry, a delayed shipping event and a parcel that is partly shipped. The coordinator should find the original order, the operator should reconcile the line quantities, and the reviewer should trace a failed operation through its receipt. Test a duplicate provider event before using payment evidence to explain a refund. Agree which marketplace messages are observations and which require an operator decision.
[Plan the rollout](/scm-for-e-commerce-fulfillment/implementation), [review event history](/scm-for-e-commerce-fulfillment/modules/fulfillment-events), and [map integrations](/scm-for-e-commerce-fulfillment/integrations).
Features to start with
Fulfillment events
Record actual allocation, picking, shipping, delivery and return events by order and product.
Order lines and products
Compare ordered, allocated and shipped units by SKU on each customer order.
Review and operations
Keep review decisions and operation outcomes attached to the order they affected.
Roles on the team
- Order Coordinator
- Owns order entry and checks identity before confirmation.
- Fulfillment Operator
- Records allocated, picked, shipped, delivered and returned quantities.
- Operations Reviewer
- Reviews failed operations and authorizes compensating actions.
- Finance Reviewer
- Checks provider payment evidence and refund requests.
Set up E-commerce Fulfillment SCM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.