Payment retries are crossing an order-state boundary twice.
Fast cancellation handling protects customers while duplicate financial events erode the order record.
Who you’d be doing this for
“I got two refund emails for the same order, and now I’m checking my bank again.”
Ploy Wattana · Household grocery shopper
A parent managing a weekly grocery delivery after an order was canceled.
What is at stake
Duplicate refunds reached 0.34% of canceled orders during a six-hour spike. You have to weigh a quick workflow change against preserving every valid payment retry.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- refund speed vs financial correctness
- local suppression vs durable invariants
- event retries vs auditable history
Why Instacart
Orders Platform histories connect cancellations, payments, and refunds across grocery delivery orders.
Written with these in mind
Not your kind of problem? 41 more at Instacart, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.