Overview
In this section, you will learn about which configurations in Brink need to be completed prior to Lunchbox onboarding a restaurant to LB 2.0.
Verifying your restaurant’s information in Brink and getting the appropriate settings in place will ensure that Lunchbox has access to the most up-to-date information about restaurant locations during the onboarding process. Continue reading to learn about the step-by-step onboarding guide:
Prerequisites
Provider certification approved; target environment/endpoint confirmed (Prod vs QA).
Brand defines rollout scope (pilot vs all) and final location list.
Owner: Lunchbox + Brand POS Support
Onboarding step-by-step
Step 1: Enablement request to PAR API Support
Brand/POS customer emails API Support to enable Generic Loyalty for location(s) (batch supported).
Include: Group Name; environment/endpoint; Location Name and/or Location Token list.
Owner: Brand/POS Support (request); PAR API Support (enablement)
Step 2: Admin Portal configuration
Configure PAR POS Admin Portal > Integration Portal > Loyalty at the correct scope (group/location).
Lunchbox provides required values and location-mapping guidance to the brand team.
Owner: Brand POS Support (or designated partner); Support: Lunchbox
Step 3: Pilot validation (minimum)
Lookup/Scan, Redeem, Void, Validate pass end-to-end.
Idempotent/non-destructive behavior verified (retries, reopened checks, provider/API outage).
Capture evidence: order examples (IDs + timestamps), provider logs, screenshots/video if needed.
Owner: Lunchbox + Brand POS Support; Support: PAR API Support as needed
Step 4: Go-live readiness + monitoring
Pilot sign-off; rollout plan and contacts confirmed; escalation path agreed.
First 48-72h: monitor failures; for escalations, provide location token/name, time window, order examples, provider Brink Event logs, and video.
Owner: Lunchbox + Brand POS Support; Support: PAR API Support
Quick Ownership Summary
Party
| Primary Responsibilities
| Notes
|
PAR API Support
| Enable Generic Loyalty for the requested location(s) on the correct environment/endpoint.
| Confirms enablement; assists with platform/enablement issues.
|
Brand/Merchant POS Support
| Configure Admin Portal > Integration Portal > Loyalty; own rollout/store readiness.
| Sends enablement request; maintains config.
|
Lunchbox (Provider)
| Provide config values + mapping guidance; own provider logic/availability and logs.
| Supports testing; supplies transaction logs.
|