Overview
Lunchbox supports an in-store loyalty flow through Brink POS that allows cashiers to look up a guest’s loyalty account at checkout, apply eligible rewards, and complete payment. This article explains what the Lunchbox system supports in that flow, the prerequisites and dependencies required for it to work, the register workflow, and the known limitations observed in the provided materials.
Limitations
Brink does not support removing one reward at a time, and reversals currently require a full refund/void conceptually.
Brink POS can display Loyalty Error because Lunchbox refund processing took longer than Brink expected, while the backend refund completed successfully. The error can be dismissed. If Brink displays an error during refund/void, verify the final state in Lunchbox because backend reversal may complete after Brink times out. This is a current limitation, and it's currently being worked on.
Prerequisites and dependencies
A client-specific webhook URL must be configured in the Brink dashboard as part of the Brink POS integration setup.
Loyalty must be enabled for each service type and participating location
Guests must have a registered account with the restaurant partner via the Lunchbox ordering platforms.
Brink integration must be used with Lunchbox to support lookup, reward retrieval, and void/refund flows.
Brink must be using the Brink Open Loyalty API.
If lookup shows “no rewards,” try alternate identifiers (phone vs email), since identifiers may map to different guest records.
Supported functionality
Account and rewards lookup
Brink supports searching for a guest’s Lunchbox Loyalty account by phone number or email address from an in-store Brink device
Reward redemption, points accrual, and refund handling
Redeeming Lunchbox Loyalty rewards on an in-store order
Accruing Lunchbox Loyalty points on an in-store order
Marking a reward as redeemed when Brink notifies that the in-store order was placed
Awarding loyalty points based on the in-store subtotal amount
Reversing points accrual and reward redemption when Brink notifies of a voided/refunded order
Rewards visibility and mapping support
External IDs come from Brink, and reward/coupon configuration co-exists in the Lunchbox Loyalty section, and it's mapped with rewards/coupons in Brink
Item association is handled on the ordering/config side
In-store loyalty experience
Similar to the Toast In-store loyalty experience, the guest must be registered with Lunchbox. Now we are going to break down the general workflow:
Cashier rings items in Brink POS and creates an order
Look up the guest’s loyalty account at checkout (via phone number or email address)
Brink retrieves available rewards and supports viewing and applying them to the in-store order.
Upon order placement/finalization, Brink sends loyalty progress to Lunchbox. In the Admin dashboard, we can see the status of the redeemed reward and earned points
Additionally, when an order is voided, Brink notifies Lunchbox, and we can track reverses of:
Reward redemption
Points accrual