Articles in this section

See more

Qu Beyond POS Integration Setup Guide

Avatar
Scott Morgan
Updated Print PDF

Qu Beyond Store POS Setup for Punchh Integration

Enterprise Intelligence Configuration Steps

Qu POS supports Punchh Loyalty integration for both in-store transactions and those orders placed via Qu Beyond web ordering.  Separate platform setting configuration for each is required at both the Global and Store levels for the brand. In order to apply rewards from Punchh Loyalty across the Qu platform, the Punchh API will submit a $dollar amount based on the total redemption amount (regardless of the reward/discount type) and the type of rewards program the brand uses with Punchh. To receive the redemption amount properly, there must be a global-level discount set up and mapped with the Punchh Internal Discount platform setting.

The Qu Beyond Ops team currently owns the process of creating this discount so that it is hidden from the normal discount groups and cannot be altered by the customer.
Send an email to Qu Ops (devops@qubeyond.com) during setup to get this Discount item created.

Configuring the Punchh Loyalty Discount Global Platform Setting

The ID of the Open $ Discount for Punchh to apply for redemptions and rewards provided by Qu Implementation team.  This one Discount ID is required as a company level global platform setting for all In Store and Web Ordering transactions.

In Store POS Configuration - Store Group, Store, or Terminal level Platform Settings

To configure Qu POS to support Punchh in store transactions, you’ll need to enable the store level platform setting “Punchh POS & Kiosk”:

Punchh Provided Settings

  • Punchh URL - This is the communication endpoint for all live Punchh loyalty transaction requests
    https://pos.punchh.com/  ← Confirm with your Punchh implementation manager

  • Receipt URL - This is the communication endpoint for all POS final receipts to send to Punchh (Loyalty and non-loyalty assigned transactions)
    https://pos.punchh.com/  ← Confirm with your Punchh implementation manager

  • Location Key - This is the location specific Punchh API key. Each Qu Beyond POS site will have a unique key generated by Punchh on the Punch Portal
    Found in Punchh Portal / Settings / Locations / POS / Location Key
    (See the Qu Beyond POS Integration Setup for detailed instructions)

  • Short Key - This is a location specific 4 digit id assigned to each Qu Beyond site in the Punch Portal
    Found in Punchh Portal Settings / Locations / POS / ShortKey

All other settings on this page are deprecated and scheduled for removal from this dialog. There is no need to set them and any entries in these fields will have no effect

Other Punchh Provided Setting

  • Cockpit/POS Integration/Business key - This business key will need to be provided to Qu Beyond. THis setting may be set at the above store setting since it will be the same for all locations of the brand

Troubleshooting

For submission of Loyalty support tickets to Punchh or Qu, please gather and send the log files for the date of the transaction in question. The logs may be located here:

  • POS Terminal

    • C:\Users\<LocalUserName>\AppData\Local\Packages\QuBeyondPOS_3x5bkgewp3n9r\LocalState\<TerminalGUID>\Logs

  • Depending on the generation of the Qu terminals <LocalUserName> will be "Gusto" or "Qu"

    • It may also vary if Qu accepted 3rd party hardware with local user already configured

    • Generically in PowerShell it is $env:username

  • The "QuBeyondPOS_3x5bkgewp3n9r" should stay fixed, unless any critical piece of business information changes that requires updates from Qu

  • <TerminalGUID> will be unique on every terminal, but is discoverable from ~\Documents\Qu.txt