Micros RES (Restaurant Enterprise System) POS is the original Punchh integration
POS Type Config: Cockpit/POS Integration
POS Setup in Cockpkit/POS Integration or on a per location basis should be set as follows:
Has POS Integration?
This setting enables POS integration
Allow for configurable message under the barcode on receipts?
Return qualifying menu items' details to POS?
This setting is not required for Micros RES but may be required when other POS systems are in use with the brand. For POS systems that enable item level discount distribution, this is a required setting to enable that functionality.
Because this is a brand wide setting and not able to be set at the location level:
This setting determines how server will evaluate the content of a scanned receipt token to determine whether is is a valid token. This value is about the content encoded in the token, not whether the token is a barcode or a QR code type of token
Ex. There are some POS systems that user the standard 13 digit Punchh Key value that is printed in a QR Code token. In this case the value should be Barcode
Always Punchh Secure
Display Guest Identity as
The Micros system requires that the POS able to scan a user token that contains alpha-numeric values. Micros is ALSO limited in the size of the user token. To enable user scanner checkin with Micro, the App will need to be able to generate a Punchh Short Scan Code
POS Config Update Interval
For production sites, this value should be set to an hour. For lab sites where changes in dashboard need to be seen sooner, int e lab (ex. Receipt message) this may be set to as low as 5
Set to 60 minutes
Possible Values 0-6
Recommended setting 6
Location POS Setup: Settings/Locations/POS tab
Use the settings above as the guide. Please note that if the entire brand is Micros, then location level settings do not need to be set
If the business is using multiple POS with a brand level POS integration type set for a different POS type, then set the location to the appropriate Micro specific settings.
Micro POS does not have the capability to take a a user redemption code and then assign that user to the check for checkin. In the Cockpit settings: Redemptions/Post Redemption the initiate checkin after redemption must be checked.
As a result of this after a POS redemption occurs, when the user is checked it, it prevents additional earning on additions to the POS check after the redemption is performed.
Please NOTE: this setting is a brand wide setting
If the business is using multiple POS systems, this setting will need to be checked regardless of whether the Brand's default POS is a POS that performs the user checkin when the check is finalized.
Due to this requirement, ALL POS systems in use will have a same behavior that when a redemption is performed on the POS check, additional earning on the check for items that are added after the redemption is performed will not be possible