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.
- Consumer Electronics OMS
- Features
- Allocation and shipping
Allocation and shipping
Record allocation and shipment per eligible line and keep each run receipt with its order.
OverviewShipped and Delivered Events×
Consumer Electronics OMS · Allocation and shipping
New
Shipped and Delivered Events
Fulfillment events
| Event number | Order | Event type | Status | Quantity | Occurred at | |
|---|---|---|---|---|---|---|
| FE-24399 | CO-94911 | Shipped | Planned | 460 | 11 Oct | |
| FE-70833 | CO-81974 | Delivered | Recorded | 40 | 24 Oct | |
| FE-81570 | CO-17574 | Shipped | Confirmed | 700 | 10 Oct | |
| FE-31556 | CO-73740 | Delivered | Failed | 920 | 20 Oct | |
| FE-86764 | CO-83223 | Shipped | Planned | 390 | 17 Oct |
6 of 6 records
CO-94911Fulfillment events · FE-24399
ShippedStatusPlanned
Quantity460
Occurred at11 Oct
What you can do
Move the order through evidenced work
A confirmed order gives Fulfillment Operator a selected source for execution. Allocation reads the order and its lines. For each Draft or Open line, it creates an Allocated fulfillment event when an equivalent event is not already present, then marks the line Allocated. One operation receipt records the allocation run. The operator can distinguish a request to allocate from an event already recorded.
Release and shipping start from an Allocated order. The workflow loops the lines, creates a Shipped event per device line, marks each order line Fulfilled, moves the order to Shipped with its next revision and records one receipt for the run. Each event has a type, state, occurrence date, quantity and optional location. Its order reference keeps physical progress tied to the customer request.
How the work is organized
- Allocation event. The event shows the selected order, quantity and recorded state for an allocation action.
- Line progress. The line moves from Draft or Open to Allocated, then to Fulfilled after the shipping action.
- Run receipt. The receipt holds the operation status, source order, owner, date and event description for reconciliation.
What to agree during setup
Decide who may initiate allocation and which order states qualify for release. Keep device categories consistent because shipping creates events for device lines. Agree how operators record event location and respond to a Failed event. Agree how to investigate a partial result from a release run by comparing each line and event before another action.
Connect physical stock and carrier acknowledgements to the systems that own them. The product’s inventory tracking flag and fulfillment event history coordinate the order work. Operators still need appropriate physical evidence before treating a recorded event as proof of inventory custody or delivery.
Check the handoff on an actual case
Use a reviewed order with two device lines. Run allocation and compare eligible lines with allocation events and the receipt. Run it again and confirm that an existing event is not repeated. Release the order. Each device line should have a Shipped event with the expected quantity. Check that all order lines become Fulfilled and remain attached to the parent order. The parent order should reach Shipped on a new revision, with one receipt for the release.
If the events and line states disagree, keep the recorded evidence and investigate before another release. Operations Manager reconciles the order by reading events and receipts together. If an order already shipped, correction follows an escalation decision and compensating receipt while preserving prior shipment evidence.
What your team sees
- Shipped and Delivered Events — Shipping and delivery events with order, quantity and event state.
- Allocated order lines — Product lines ready for release review.
- Shipped Customer Orders — Shipped and partly shipped orders for follow-up.
Follow the work through
What it keeps track of
Data model- Customer orders
- Customer orders moving through draft, review, approval, execution and cancellation.
- Order lines
- Product lines belonging to a customer order with quantity, price and line total.
- Fulfillment events
- Allocation, pick, ship, delivery and return events recorded against an order.
- Operation receipts
- Durable receipts for each executed operation with status and source record.
- Products
- Sellable products with SKU, pricing, unit of measure and inventory tracking.
Who uses it
Permissions- Fulfillment Operator
- Initiates allocation and shipping and checks the events.
- Operations Manager
- Reconciles and handles failed receipts.
- Order Coordinator
- Retains customer context for corrections.
Set up Consumer Electronics OMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.