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
- Exceptions and correction
Exceptions and correction
Assign stock, substitution and delivery issues while preserving completed order history.
OverviewOpen Fulfillment Exceptions×
OMS for Grocery and Supermarkets · Exceptions and correction
New
Open Fulfillment Exceptions
Picked waits for the fulfillment associate
| Exception number | Grocery order | Exception type | Raised at | Assigned to | Exception status | |
|---|---|---|---|---|---|---|
| FE-37669 | GO-22842 | Stock Shortage | 27 Oct | SA-8034 | Open | |
| FE-92708 | GO-75807 | Delivery Address Issue | 18 Oct | SA-1507 | Open | |
| FE-53350 | GO-92744 | Payment Hold | 05 Oct | SA-3695 | Open | |
| FE-47138 | GO-22206 | Damaged or Spoiled Item | 18 Oct | SA-3655 | Open | |
| FE-90424 | GO-75855 | Late Delivery | 07 Oct | SA-5687 | Open |
6 of 6 records
GO-22842Fulfillment exceptions · FE-37669
Stock ShortageRaised at27 Oct
Assigned toSA-8034
Exception statusOpen
What you can do
Keep the problem with the order
A fulfillment exception links a problem to its grocery order and an assigned associate. The type distinguishes a stock shortage, delivery address issue, payment hold, damaged or spoiled item, late delivery, food safety compliance issue or other problem. The detail explains what happened; status and resolution show what the team did next. Store Operations Overview gives store operations an open exception queue alongside the order book.
How the work is organized
- Exception queue. Open Fulfillment Exceptions keeps unresolved issues visible by order, type and assignee.
- Order context. The team reads basket lines, shopper preferences, events, documents and earlier decisions before acting.
- Correction trail. Uncompleted order scope can be cancelled in place; completed scope receives an escalation decision and fulfillment receipt.
The status of an exception is its own work state. An Investigating exception can exist while the grocery order is Approved or Completed. Customer Service Associate can explain the issue to the shopper, while Store Operations Manager assigns the owner and checks the recorded resolution. The team should not close an exception simply because the order moved forward.
What to agree during setup
Agree who raises each type of exception and when to escalate it. A spoiled item needs detail that identifies the affected order and what was observed. A delivery address problem needs an assigned person who can confirm the correct recipient and route. Store Operations Manager decides who can resolve or close an issue and which supporting document or event must be attached to the order.
For correction requests, decide who authorizes the requested scope and how the team identifies the current order revision. The correction workflow reads the order, lines, review decisions and receipts before branching on status. Draft, Awaiting Review and Approved scope can be cancelled in place. Completed scope needs a compensating escalation decision and receipt, because the release history remains relevant.
Check the handoff on an actual case
A shopper reports a spoiled item after the order is Completed. Customer Service Associate raises a damaged or spoiled item exception, describes the item and assigns the case to a store associate. Store Operations Manager checks the order lines and delivery event. If a correction is requested for the completed scope, the correction workflow creates an escalation decision and operation receipt. The order’s earlier Completed status and fulfillment receipt remain traceable.
For a draft order with a wrong delivery address, Order Coordinator can request cancellation before fulfillment. The order is marked Cancelled and the team can create corrected terms under the appropriate operating process. Customer Service Associate records the resolution on the exception so the open queue reflects the actual outcome.
What your team sees
- Open Fulfillment Exceptions — Assigned problems that still require investigation or resolution.
- Returned or Rejected Order Decisions — Decisions to explain before an order proceeds.
- Failed or Corrected Fulfillment Receipts — Operational evidence needing closer review.
Follow the work through
What it keeps track of
Data model- Fulfillment exceptions
- Grocery fulfillment exceptions: stock shortage, substitution issue, spoiled item, address and late delivery.
- 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.
- Order review decisions
- Independent review decisions on grocery orders that need approval, return or escalation.
- Fulfillment receipts
- Recorded, verified, failed or corrected fulfillment receipts that evidence each grocery order operation.
- Pick and delivery events
- Store pick, pack, out-for-delivery, delivered and returned events against a grocery order.
- Order documents
- Documents and attachments supporting a grocery order, such as substitution notes and delivery proof.
Who uses it
Permissions- Store Operations Manager
- Assigns and oversees exceptions.
- Customer Service Associate
- Records shopper contact and follows resolution.
- Order Reviewer
- Checks prior order decisions when a correction is requested.
- Order Coordinator
- Cancels uncompleted order scope after checking its revision.
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.