Cross-store exceptions
See today's stuck orders, mismatched stock, and delivery failures.
The first working result is a cross-store order, inventory, and delivery exception list. The proof case holds USD 25 at risk on a missing package: a delivered scan is not a photo or a signature, so the refund stays pending.
Sign in and you go straight back to the ResolveBay conversation. Work happens in chat. This page never asks for your card details or email address.
Exception manifest
A cross-store order, inventory, and delivery exception list- 01ORDERTriage these delayed and blocked orders
- 02STOCKCompare channel stock with the warehouse record
- 03DELIVERYBuild a resolution timeline for this delivery case
FIRST WORKING RESULT
A cross-store order, inventory, and delivery exception list
One list. Records kept separate. Next owner visible.CONTROLLED PROOF / DEMO-100
A delivered scan is not the end of the investigation.
Order demo-100, USD 25 at risk, carrier marked delivered at 10:00, customer reported the package missing at 12:00, with no delivery photo and no delivery signature.
- Classification
- Delivery Dispute — Missing Package
- Returned route
- human_review
- Refund state
- Pending approval · has_refund=false
HOW THE HANDOFF STAYS TRACEABLE
From crossed records to one reviewable next step.
- 01
ResolveBay validates each supplied record and rejects duplicate local IDs or missing SKU mappings.
- 02
It applies the routing table and keeps the earliest event for each provider and external-event pair.
- 03
It omits delivered orders, maps supported open statuses to next actions, and leaves the handoff pending with the owner.
A route to human approval, carrier refresh, inventory reconciliation, or human review
Separate kept and duplicate event ID lists
A canonical exception that retains provider, external order, source event, and mapped SKU
An owner-pending standup note with open items and their next actions
WHAT YOU SUPPLY
The source records stay named.
Inputs cover refund status, amount, exception types, provider events, SKU mappings, and open-order status.
- 01
Refund presence, order amount, and exception types for routing
- 02
Provider event IDs, external event IDs, and received timestamps
- 03
Provider SKU mappings and source exception identifiers
- 04
Open orders with status and hours since the last update
THE OWNER LINE
A route is not an external action.
- Sending refunds, changing inventory, refreshing a carrier, or contacting a buyer
- Inventing a canonical SKU when the provider SKU has no supplied mapping
- Treating an unsupported order status as a completed resolution
STARTER
Open an exception workspace.
$19.00 is stated here before you register; card payment runs through Stripe Checkout inside the signed-in workspace.
$19.00 per month
Continue to workspace billingBEFORE YOU ROUTE
Questions
Which exceptions require human approval?
Any record with a refund or an amount of at least 200 is routed to human approval before the narrower tracking and stock routes are considered.
How are duplicate provider events handled?
Events are grouped by provider and external event ID. The earliest received event is kept and later deliveries are returned as duplicates.
What does the daily handoff contain?
It contains each non-delivered order, its supported status, the mapped next action, an urgent order ID when present, and a pending-owner status.
Does ResolveBay perform the next action?
No. The engine returns a route and work record; its output does not represent an external refund, stock change, carrier refresh, or customer contact.