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.
- OMS for Grocery and Supermarkets
- Features
- Pick and delivery
Pick and delivery
Follow release events, local delivery and store handoffs against each grocery order.
OverviewPicked and Delivered Events×
OMS for Grocery and Supermarkets · Pick and delivery
New
Picked and Delivered Events
Pick and delivery events
| Event number | Grocery order | Event type | Event status | Occurred at | Quantity | |
|---|---|---|---|---|---|---|
| PAD-90310 | GO-97247 | Picked | Planned | 11 Oct | 620 | |
| PAD-75154 | GO-52787 | Delivered | Recorded | 10 Oct | 330 | |
| PAD-56675 | GO-54596 | Picked | Confirmed | 06 Oct | 590 | |
| PAD-54435 | GO-51908 | Delivered | Failed | 11 Oct | 360 | |
| PAD-83592 | GO-35423 | Picked | Planned | 14 Oct | 540 |
6 of 6 records
GO-97247Pick and delivery events · PAD-90310
PickedEvent statusPlanned
Occurred at11 Oct
Quantity620
What you can do
Move approved work into fulfillment
Once an order is Approved, a Fulfillment Associate can release it for store pick and local delivery. The release reads the basket lines, writes an Out for Delivery event for each line, marks lines Picked, advances the order to Completed and writes a fulfillment receipt for the run. Those records show the released scope. An actual delivered event can then be recorded separately with its occurrence time and quantity.
How the work is organized
- Event trail. Pick and delivery events identify the order, store, event type, status, quantity and time.
- Channel handoff. A handoff records the store, fulfillment channel, status and optional provider reference.
- Order receipt. A fulfillment receipt preserves the operational result and the associate who recorded it.
The status on a handoff describes its own transfer between fulfillment channels. It does not replace the status of the grocery order or a physical delivery event. A store may choose curbside or local delivery as a channel, but the team should record the actual handoff and event rather than assuming that an approved order has reached its recipient.
What to agree during setup
Store Operations Manager decides who can release an approved order and who records delivery events. Agree which handoff status the store uses before goods change hands, how provider references are entered, and who checks the quantity against the order. A delivery provider or driver process may send updates from outside the app; those updates need a connection and a clear rule for matching them to an order.
The team should also decide what to do when an event fails or a delivery is late. Fulfillment Associate records the event state and opens a fulfillment exception for the affected order. The exception then has an assignee and a resolution trail. Keeping that trail separate from the order status lets customer service explain the actual event without rewriting completed order history.
Check the handoff on an actual case
A store has an approved order with produce and pantry lines. Fulfillment Associate verifies the basket and runs the release. Each line receives an Out for Delivery event, the lines become Picked, and the order becomes Completed with a new revision and one receipt for the run. The associate records a handoff for local delivery and gives it the applicable channel status. When the recipient confirms delivery, the team records the Delivered event and its time.
Suppose the produce bag is missing during the handoff. The associate records the event condition and raises an exception with the order and assigned associate. Store Operations Manager sees the issue in the open exception queue and can direct a correction or customer contact. The existing release receipt remains part of the order history.
What your team sees
- Picked and Delivered Events — The event trail for picked and delivered work, with quantity and time.
- Completed Grocery Orders — Released orders to compare with the later event trail.
Follow the work through
See release and delivery and exception follow-up.
What it keeps track of
Data model- Grocery orders
- Grocery and supermarket orders from capture through store pick, local delivery, substitution and returns.
- Basket lines
- Individual grocery basket lines linking an order to a perishable or center-store SKU with substitution consent.
- Pick and delivery events
- Store pick, pack, out-for-delivery, delivered and returned events against a grocery order.
- Fulfillment handoffs
- Handoff of a grocery order between fulfillment channels such as store pick, curbside and local delivery.
- Fulfillment receipts
- Recorded, verified, failed or corrected fulfillment receipts that evidence each grocery order operation.
- Fulfillment exceptions
- Grocery fulfillment exceptions: stock shortage, substitution issue, spoiled item, address and late delivery.
Who uses it
Permissions- Fulfillment Associate
- Records release, handoff and actual events.
- Store Operations Manager
- Follows exceptions and assigns work.
- Customer Service Associate
- Reads the event trail when a shopper asks about delivery.
Set up OMS for Grocery and Supermarkets your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.