After you install.

An installer success screen proves that files and database migrations completed. It does not prove that the operating path is ready. Finish these checks before inviting a business or printing a QR code.

1. Run the real smoke test

Use a real inbox and disposable test records.

1. Request an admin sign-in code and prove the OTP arrives in the intended inbox.
2. Sign in to the admin dashboard with that OTP.
3. Create or use a test business, staff account, member, and one simple loyalty program.
4. Complete a staff checkout and confirm the test member receives the expected credit.
5. Upload an image and confirm it renders after a new request.

Stop and repair any failed check. A dashboard that opens while OTP or staff checkout fails is not a live installation.

2. Configure the scheduler

Open Cron Jobs or Scheduled Tasks in the hosting control panel and configure the Reward Loyalty scheduler to run every minute when the host allows it. If the plan offers only a longer interval, use the shortest interval available. Scheduled work runs when it is due, and normal dashboard traffic provides a traffic fallback for core loyalty work between scheduled runs.

Check the Health Center after the scheduler has had time to run. A regular schedule is still the most predictable path. If the form asks for a path or setting you do not recognize, contact hosting support and ask them to configure the scheduler for the application domain. You do not need to work it out in a terminal.

3. Confirm the panel settings

Confirm that the application domain still shows PHP 8.4.1 or newer and the required extensions in the hosting control panel. Then check Health Center after the scheduler has run. If Health Center reports a different runtime or a scheduler problem, send the result to hosting support instead of trying terminal commands.

4. Choose the queue mode

Keep the sync queue for a simple installation when inline delivery time is acceptable. For a multi-partner installation or work that should not block a web request, use the database or Redis queue with a worker managed by the host or a technical operator. Confirm failed jobs are monitored and workers restart after a server reboot or deployment.

5. Prove backup and restore

Create a database backup and a copy of uploaded files, application configuration, and protected files. Then restore them into the private staging installation. Sign in and repeat the smoke test against the restored copy.

A downloaded archive is not a proven backup until a restore succeeds. Record who owns the restore procedure, where encryption keys and credentials are kept, and how long recovery took. Contact hosting support if the panel does not provide a safe staging restore path.

6. Inspect Health Center

Open Administration > Health Center and review PHP, database, storage, scheduler, queue, and mail status. Treat warnings as operating work, not as decorative notices. Health Center does not replace the PHP 8.4.1 and full-extension parity checks in Requirements because its runtime summary can cover a smaller compatibility set. Use the JSON endpoint described in the Health Center guide if an external monitor needs a machine-readable check.

7. Check OPcache after changes

OPcache can continue serving old PHP bytecode after files change. Use the host's supported PHP restart or OPcache reset after an installation or update. Then open the application in a new request and rerun the smoke test. Do not add an unauthenticated public script that resets OPcache.

8. Verify the update path

Test dashboard updates on staging only when a safe, applicable Reward Loyalty update package exists. Take a fresh backup first, run the update, reset OPcache through the supported host path, inspect Health Center, and repeat OTP, admin sign-in, staff checkout, and image upload.

If no applicable package exists, record dashboard updates not verified here. Do not convert absence of a test package into a compatibility claim. Rehearse the manual update path on staging so production still has a controlled route.

Ready for the first program

Start with one loyalty mechanic and one worthwhile reward. Configure the relevant business, staff, program, branding, and analytics procedures in the public documentation before opening the counter.