Skip to main content

Kiosk, Yield, Marketing & Hardware pilot acceptance

Use this guide when a Store is ready to move from software testing to a controlled real-world pilot. A healthy Docker stack or successful build is not evidence that a physical Kiosk, real Store data, Email Provider or installed device works in practice.

warning

Run one exact Store, build and pilot window at a time. Stop for cross-Store data, unconsented Email, exposed credentials, wrong financial state or unrecoverable Customer data. Record BLOCKED and NOT RUN honestly; do not convert them to PASS.

Record before starting​

  • pilot ID, environment, Git SHA/image tag and Store time zone;
  • exact Tenant and Store, operators and final approver;
  • whether data is synthetic, staff test data or approved representative Store data;
  • device model/OS, Email Provider and device-management method when applicable; and
  • rollback owner, evidence location and incident contact.

Keep Customer contact details, intent/health text, device credentials and Provider secrets out of screenshots and ordinary support messages.

Kiosk​

  1. Run on the actual mounted device in supervised/fullscreen mode.
  2. Complete a same-day booking, intent/body-map entry and pay-at-Store confirmation.
  3. Add two Sale lines, remove one and compare the amount with the Sale claimed in POS.
  4. Interrupt the network, retry, claim the handoff once and confirm duplicate/expired claims are rejected.
  5. Finish/reset, then verify back/forward, autofill and power-cycle recovery reveal no previous Customer data.
  6. Check EN, 中文 and ไทย, physical tap targets, seated reach and the short status-code flow. The result must not show a therapist, queue position or wait-time promise.

See Sales & checkout for the counter-side Sale flow.

Yield Intelligence​

  1. Confirm the Store has representative appointments, service capabilities, roster, time off, station configuration and denied-demand observations.
  2. In Admin → Roster → Coverage Planner, run both 7-day and 14-day horizons.
  3. Reconcile appointment demand, denied-demand, gap-day and suggestion counts with the exact Store's source records.
  4. Switch Store/horizon and confirm old or late results never replace the current one.
  5. Review every suggestion with the Store manager. Applying one is optional and still requires roster.schedule.manage; the planner never changes the roster itself.

Record useful, rejected, false-positive and false-negative suggestions. Do not treat the planner as payroll, Award, qualification, revenue or automatic staffing advice. See Appointments & roster.

Email Marketing​

Only Email is operational. Do not start without an approved sender, Provider, consent wording and explicit consenting test cohort.

  1. In Admin → Lifecycle marketing, verify the exact Store and Channel readiness.
  2. Generate one fixed lifecycle candidate, review its aggregate audience, edit it and obtain independent approval before scheduling.
  3. Revoke one test recipient's consent before delivery and prove that address is not sent while approved recipients proceed.
  4. Record redacted MMOS delivery IDs and Provider outcome; never record API keys or a full recipient list here.
  5. Test the signed unsubscribe link and a later Email-address change; both the frozen delivered address and reconciled current address must remain suppressed.
  6. Disable Email and prove new preparation and prepared delivery stop before Provider egress. WhatsApp, WeCom and SMS must remain unavailable.

See Marketing automation.

Marketplace, hardware and devices​

  1. Submit a real controlled quote/order and verify frozen items, notes and status history. A status must never imply payment or shipment.
  2. Super Admin manually reviews/quotes the order; Tenant explicitly confirms it.
  3. Register and assign the physical asset to the exact Tenant/Store.
  4. For Kiosk hardware, prepare fulfilment, place the one-time credential directly into the approved device secret store and prove it cannot be read back.
  5. Enroll the device, send a heartbeat, compare expected software/config and then test only the approved update, restart or maintenance commands on the controlled device. Remote shell, camera, microphone and Customer monitoring are never allowed.
  6. Prepare a Hardware Support handoff, then explicitly submit and progress the ticket; the handoff itself must not submit anything.
  7. Attach physical installation, network recovery, supervised-mode, commercial terms, shipping and EMM/MDM evidence—or mark each missing item BLOCKED/NOT RUN.

See Platform marketplace & hardware support.

Sign-off​

For every track, record each step as PASS, FAIL, BLOCKED, NOT RUN or NOT APPLICABLE, with an evidence reference, owner and retest date. Store manager and technical owner must sign the exact Store/build/window. Marketing/privacy and Platform Owner approval are also required for the tracks they govern. A conditional sign-off must list its expiry and cannot be reused for another Store, build, Provider or device model.