Articles in this section

See more

SICOM POS Integration Punchh Portal Configuration

Avatar
Scott Morgan
Updated Print PDF

Xenial SICOM Encounter POS

POS Type Config: Cockpit/POS Integration

Cockpit

POS Setup in Cockpkit/POS Integration or on a per location basis should be set as follows:

  1. Has POS Integration?
    This setting enables POS integration
    Always checked

  2. Allow for configurable message under the barcode on receipts?
    Always checked

  3. Create a new guest based on phone number if the guest doesn't exist (via POS/SMS)?
    To enable new user signup, it requires both Punchh Portal setting here to be checked and enabling in POS setting (SICOM).
    If any user profile fields other than phone/email are marked as required (ex. age) the new user creation will fail at the POS
    Optional

  4. Return qualifying menu items' details to POS?
    This setting is not required for SICOM. If enabled, the specific item targeted by the redeemable will be reported with the type D item as a modifier to the discounted item. If there is more than 1 item returned to the POS as discountable for the redeemable, then only the first item will be tagged with the typ D discount as a modifier
    Un-Checked

  5. Reflect Program Structure via POS API?
    This setting enables dynamic support of different program types (Points Unlock, Bancked Rewards, etc.). SICOM currently supports only Points Unlock but this setting should be enabled
    Checked

  6. Validation Type
    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 encoded algorithm used to create the token, not whether the token is a barcode or a QR code type of token
    SICOM prints a QR CODE but this setting should be set to
    Barcode

  7. POS Type
    Currently the POS type should be set to the generic POS type Quardzilla. DO NOT USE SICOM. The SICOM POS type will be updated by EOY 2020 to properly reflect the correct QR Code algorithm for the POS type and this document will be updated accordingly
    Currently Quardzilla

  8. 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
    QR Code

  9. 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

  10. Log Level
    Possible Values 0-6
    Recommended setting 6

  11. Coupon Length
    Brand requirement


Location POS Setup: Settings/Locations/POS tab

Use the settings above as the guide. Please note that if the entire brand is SICOM, 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 SICOM specific settings.

Cockpit Settings

Earning/Checkin Validations

  1. Validate checksum of barcode?
    Unchecked

  2. Validate receipt details presence in POS Data Sink?
    Checked

  3. Use Checksum of barcode to find location?
    Checked

  4. Enable Idempotency for Checkins?
    Checked

  5. Validate bar code multiple use?
    Checked

  6. Validate age of receipt?
    Checked

  7. Recycle Barcodes After
    0 (Forevever, they will never repeat)

Redemptions/Post Redemption

SICOM automatically checks in a user after redemption, this setting should remain unchecked