Required Information

Convention Clarification

Before implementation, the following conventions must be defined:

• Unique structure for POS IDs
• Unique structure for receipt IDs (program-wide and time-invariant)
• Ideally, the ID should be visible on the receipt
• Mapping of article, merchandise, and merchandise subgroups
  

Required for System Setup at Convercus

Convercus requires the following to set up test and production environments:

• Partner structure, naming, and setup
• Store details (name, address, coordinates, phone, hierarchy)
  • Store identifiers / optional custom properties
  • List of interaction points (typically POS systems)
• Merchandise groups
  • Excluded articles and merchandise groupings (as sent from the POS)
    

Templates are available from Convercus for capturing this information.

Technical Setup Requirements

Convercus will provide the following for API connection setup:

• Integration username
• Integration password
• Organization-ID
• Interaction points for Staging
• Staging Self-Service portal access
• Test accounts