Crunchy PlumCrunchy Plum

Merchant guide

Learn onboarding, operations, redemption, and settlement workflows.

Redemption success

After the app confirms redemption—avoid double redemption and mis-rings.

Description

Cashier: the success screen is your receipt of record for handing food or marking a bill paid. Manager: align training so staff never taps success before service is actually delivered when policy requires post-service redemption.

Steps

  1. After you confirm redemption, read the success confirmation—note redemption ID or timestamp if your audit SOP requires writing it on a ticket.
  2. Tell the guest they are all set on the app side; any store upsell follows house rules—keep app redemption separate from card taps unless integrated.
  3. If your POS integration exists, complete the matching POS step (discount reason, open-table closure)—follow internal checklist.
  4. For pickup, notify kitchen or expeditor using your venue’s ticket system; do not rely on the guest’s phone alone.
  5. If the flow offers email or SMS receipt, ask whether the guest wants it—some builds skip when offline.
  6. Do not scan the same code again for the same visit unless your manager explains a rare split-check scenario—double scans create disputes.
<!-- IMAGE: Success screen with reference code -->

Screenshot: success state with optional share receipt button.

If something goes wrong

  • Success shown but kitchen has no order: check if you redeemed before firing—some venues redeem at pickup; coordinate with manager to avoid duplicate meals.
  • Guest insists they paid twice: pull Redemption history while they watch—never argue from memory.

Next

Collect tip · Orders tabs