Skip to main content

Brink POS - Loyalty Integration Setup (LB 2.0)

Written by Marija Golubovic

Overview

This article covers Brink POS loyalty integration setup and provides the requested values needed for the integration.

Important: If a previous loyalty provider is setup it will need to be removed in the settings editor under Options/Loyalty, set it to none>Ok and publish it.

Stores migrating from 1.0 to 2.0 cannot have this integration enabled. If they do then 1.0 orders will not close. 1.0 orders can be manually closed by removing the customer from the 1.0 order.

Configuring the Generic Loyalty Integration

To get to the Loyalty integration page, we must be logged into the partners' PAR Portal.

Example: https://admin3.parpos.com/, this URL changes per client and can be found in 1Password by searching Brink.

Step 1: From the left sidebar, select Configurations> Integrations Portal

Step 2: Click All

Step 3: Find Solutions> Click Loyalty

Step 4: Select Type > Generic

Step 5: Add in the following details

  • Allow PAR Customer Usage: Toggle On

  • Endpoint URL: Generic Brink incoming endpoint, which will be set for all chains that use Brink in-store. The endpoint URL should be... https://api.novadine.com/api/v2/sync_incoming/80e1ea5b-6991-4ccb-83ae-c18fe6f335ed

  • Store ID: This is a URL encoded version of the token set in the Site ID field on the location in Lunchbox. If the storeID contains any special characters (for example: /, =, etc.), they must be replaced with their URL-encoded versions. We can use the following reference for encoding W3schoolsW3Schools.com

    • Step 5A: Scroll down to Try It Yourself and paste the Store ID in this Field and click Submit

    • Step 5B: Next copy the value in the field not including the text=

    • Step 5C: Paste this value into the Store ID Field and into your configuration workbook.

  • Default Discount: Choose the Lunchbox Loyalty Discount.

Note: For a discount to appear in this drop-down, the Loyalty Checkbox must be enabled on that discount in Brink. Any updates to discounts require a restart of the POS Register application to take effect. In Cabin Coffee's case, the discount appeared the following day after the system's scheduled overnight restart.

  • Enable Payment: Leave unchecked

  • Authentication Type: API Key

  • API Key: This is the unmodified version of the token set in the Site ID field on the location in Lunchbox and click Save.

IMPORTANT: Once Configured the overnight system reboot is required before loyalty lookup can be successfully completed.

Coupon Creation for Loyalty Usage

Lunchbox does not have the ability to set its in store lookup coupon to connect with your LB Loyalty Discounts. This means a new in store coupon will need to be created to work with the integration.

Button Creation for Loyalty Usage

Clear Customer Button set with Clear Customer Behavior and Panel - Payments, Top Bar Panel or Bottom Bar Panel - This button allows you to clear a customer from the order.

Lookup Customer Button set with Clear Customer Behavior and Panel - Payments, Top Bar Panel or Bottom Bar Panel - This button allows you to look up a customer to add them to the order.

Redeem Rewards Button set with Redeem Rewards Behavior is a setting that can be - Payments, Top Bar Panel or Bottom Bar Panel - This button can be used for looking up the users rewards.

Closing Orders Stuck In Unclosed

In the event that an order passes through the integration and it cannot be closed to Lunchbox. This issue most commonly occurs if you were migrating from 1.0 to 2.0 and there are still pending orders coming from 1.0, simply clear the customer and close the check. You will need to retype their name on the order.

Integration Validation

  • 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

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

Did this answer your question?