Updated on February 26, 2025
- Explain how the system support a defined set of participating locations. Explain how a marketer maintain the list of participating locations.3.
- Can user interface/experience be modified based on locale? (e.g. Tier Status more important than point value in Asia; may not be the same in NA/EMEA) How is language translation managed?
- Explain how program elements (earning mechanisms, always on benefits, rewards catalog) can be configured at the global, country, city, state and store level. How can points economy be tailored to different currencies?.
- Does the platform allow members carry a negative points balance? (This is relevant for returns.)
- Can you describe your API’s capabilities in terms of ensuring quick and accurate responses? Please provide details on the average response time and accuracy rate, as well as any measures in place to maintain these performance standards.
- Does your solution provide an API that supports account creation and management capabilities? If so, please detail the functionalities available through the API for managing accounts.
- Protected: Ability to scale and have separation of data, programs, rewards and point structures for different regions (US, EU, APAC and by country or state / province)
- Can scale for growth and program needs
- Is your system capable of rewarding members based on specific events such as birthdays, anniversaries, or other dates specified by ##BRAND##?
- Does your platform support the purchase, gifting, or transferring of points between members? Please provide details on how these processes are managed.