Prepare the server, install the application, and launch the first program in a controlled order.
Product behavior, requirements, pricing, and integrations can change. The contextual link in each answer is the maintained next step.
Answer 1
Direct linkUse the current requirements page for runtime, extensions, databases, SSL, and web-server guidance. Marketing pages do not repeat those version numbers because the supported stack changes with releases.
Answer 2
Direct linkPrepare a server that meets the current requirements, configure the domain and database, run the documented installation flow, set up mail and scheduled work, and test the roles on staging before production.
The installation guide carries the complete order, security notes, backup guidance, and demo-mode warning.
Answer 3
Direct linkChoose one core mechanism: points for variable eligible spend, stamps for similar repeat purchases, or a prepaid pass for a defined package of future uses. Set economics and the staff action before design.
The launch guide covers configuration, QR placement, staff briefing, and the first 30-day review.
Answer 4
Direct linkReward Loyalty does not ship a general importer for another vendor’s customer files, balances, and history. A full data move needs a source inventory, mapping, consent review, reconciliation controls, and scoped custom work against the current data model.
Use the migration guide. The achievements history import recognizes activity already present inside Reward Loyalty; it is not a customer migration tool.
Open the cluster that matches the next decision instead of stretching one answer beyond its evidence.