Refund before cancelling, not after, with compensation on failure

cancelOrderItem committed the cancellation (freeing the Machine slot,
marking the item cancelled) before calling the payment provider's
refund — so a refund failure (gateway timeout, provider outage) left
the item cancelled with no refund ever issued, and no record that one
was owed. placeOrder already avoids the equivalent problem by charging
before its DB transaction and refunding if the transaction then fails;
apply the same pattern here for consistency.

Refund now happens first; the DB transaction's atomic queued-status
check (added for the earlier cancellation race) doubles as the signal
that the refund needs to be undone if this transaction loses the race
or otherwise fails, so the catch block re-charges to compensate.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

src/domain/ordering.ts

@@ -400,9 +400,8 @@ export const cancelOrderItem = async (
   orderItemId: number,
   access: OrderAccess,
 ) => {
-  const result = await db.transaction(async (tx) => {
   const orderItem = firstRow(
-      await tx
+    await db
       .select()
       .from(schema.orderItems)
       .where(eq(schema.orderItems.id, orderItemId)),
@@ -410,7 +409,7 @@ export const cancelOrderItem = async (
   if (!orderItem) throw new Error('Order item not found')
 
   const order = firstRow(
-      await tx
+    await db
       .select()
       .from(schema.orders)
       .where(eq(schema.orders.id, orderItem.orderId)),
@@ -425,15 +424,26 @@ export const cancelOrderItem = async (
     throw new OrderItemNotCancellableError('it is already done cooking')
   }
 
-    const currentStep = await getCurrentStepInstance(tx, orderItemId)
+  const currentStep = await getCurrentStepInstance(db, orderItemId)
   if (!currentStep || currentStep.status !== 'queued') {
     throw new OrderItemNotCancellableError('it has already started cooking')
   }
 
+  // Refund before touching any state, mirroring placeOrder's charge-first
+  // pattern: if the refund itself fails, nothing about this cancellation is
+  // ever recorded, exactly like a declined charge leaves no Order behind.
+  if (order.paymentChargeId) {
+    await paymentProvider.refund(order.paymentChargeId, orderItem.priceCents)
+  }
+
+  try {
+    await db.transaction(async (tx) => {
       // Re-check status = 'queued' as part of the delete itself, atomically:
-    // a Machine may have claimed this Step (assignQueuedStepsForTag) between
+      // a Machine may have claimed this Step (assignQueuedStepsForTag), or a
-    // the read above and this statement. If so, zero rows match and we must
+      // concurrent cancelOrderItem call may have already deleted it, in the
-    // not refund a Step that's already cooking.
+      // time since the read above (which can include the refund call, an
+      // external network round trip). If so, zero rows match and the catch
+      // below re-charges to undo the refund we already issued.
       const deletedSteps = await tx
         .delete(schema.preparationStepInstances)
         .where(
@@ -445,7 +455,9 @@ export const cancelOrderItem = async (
         .returning({ id: schema.preparationStepInstances.id })
 
       if (deletedSteps.length === 0) {
-      throw new OrderItemNotCancellableError('it has already started cooking')
+        throw new OrderItemNotCancellableError(
+          'it has already started cooking',
+        )
       }
 
       await tx
@@ -454,15 +466,12 @@ export const cancelOrderItem = async (
         .where(eq(schema.orderItems.id, orderItemId))
 
       await updateOrderCompleteIfEverySiblingIsDone(tx, orderItem.orderId)
-
-    return { order, orderItem }
     })
-
+  } catch (error) {
-  if (result.order.paymentChargeId) {
+    if (order.paymentChargeId) {
-    await paymentProvider.refund(
+      await paymentProvider.charge(orderItem.priceCents)
-      result.order.paymentChargeId,
+    }
-      result.orderItem.priceCents,
+    throw error
-    )
   }
 }
 

tests/ordering.test.ts

@@ -249,6 +249,44 @@ describe('cancelling an Order Item', () => {
     ).rejects.toThrow(ordering.ForbiddenError)
   })
 
+  it('recharges the customer if the DB transaction fails after the refund has already gone through', async () => {
+    await placeGuestOrder([{ menuItemId: seed.menuItems.pizza.id }]) // occupies the only oven
+    const order = await placeGuestOrder([
+      { menuItemId: seed.menuItems.pizza.id },
+    ])
+    const itemId = (await getStatus(order)).items[0].id
+
+    let rechargedAmountCents: number | undefined
+    const spyingPayment: typeof payment = {
+      ...payment,
+      charge: async (amountCents) => {
+        rechargedAmountCents = amountCents
+        return payment.charge(amountCents)
+      },
+    }
+
+    const dbWithFailingTransaction = Object.create(
+      testDb.db,
+    ) as typeof testDb.db
+    dbWithFailingTransaction.transaction = () => {
+      throw new Error('simulated DB failure after refund')
+    }
+
+    await expect(
+      ordering.cancelOrderItem(
+        dbWithFailingTransaction,
+        spyingPayment,
+        itemId,
+        accessFor(order),
+      ),
+    ).rejects.toThrow('simulated DB failure after refund')
+
+    expect(payment.refundsFor(order.paymentChargeId!)).toBe(
+      seed.menuItems.pizza.priceCents,
+    )
+    expect(rechargedAmountCents).toBe(seed.menuItems.pizza.priceCents)
+  })
+
   it('gives an accurate message for a double-cancel', async () => {
     await placeGuestOrder([{ menuItemId: seed.menuItems.burger.id }]) // occupies the only grill
     const order = await placeGuestOrder([