Kiosk-X Cabinet Handbook — from factory sign-off to first sale
Start with the illustrated installation atlas. It contains 27 illustrated flows and a 60-row checklist that you open for the actual cabinet serial. The checklist stays in this browser; exporting it creates a handover record, not a server certificate or permission to sell.
This handbook connects the current detailed guides. Use coordinated approved cabinet, gateway and Operator releases and the verified download choices. The release record identifies the published ZHZN APK. The Operator platform comparison separates Flutter, native Android, web and the older Apple release.

1. Executive summary
The manufacturer proves and signs the cabinet it built. The receiving operator checks the delivery, claims that exact serial, reviews its address, separately confirms being on site, loads real products and witnesses payment and delivery. Every handover keeps its evidence. A green screen, a simulation, a signed APK or a completed browser checklist cannot replace those observations.
| Your job | Open this guide |
|---|---|
| Learn Android, Wi-Fi and first-day operation | Newcomer course and step checklist |
| Install, secure or update the cabinet APK | Android operation |
| Manufacture and sign ZHZN | Manufacturer guide, 中文版, detailed sign-off |
| Receive and install a machine | First-time install |
| Operate Reyeah | Reyeah guide |
| Run a fleet | Fleet operations |
| Help a shopper | Shopper guide |
2. Actors, systems and terms
| Person or term | What it means |
|---|---|
| Manufacturer technician | Installs the approved APK and configuration and tests the actual cabinet. |
| Manufacturer QA signer | Reviews observed results and completes the required factory signatures with authorized credentials. |
| Warehouse receiver | Matches crate, cabinet and evidence; records damage, shortages and shipping status. |
| Operator owner | Controls the intended tenant and grants supported access. Performs restricted actions when a crew role lacks them. |
| Installer or restocker | Uses their own named account and assigned machine access. Never borrows passwords or MFA codes. |
| Shopper | Buys or uses only experiences enabled and accepted for this cabinet. |
| Serial / machineNo | Physical cabinet identity. Match it in the crate, APK, cloud record and staff app; never copy a sample serial. |
| Device credential | Cabinet authentication issued through authorized provisioning/enrolment. An Operator claim alone does not issue it. |
| Android diagnostic and certificate | On-cabinet test evidence plus the technician's handwritten acceptance against an eligible run. |
| Partner FAT build signature | Separate manufacturing record covering physical subsystem tests and build/shipping evidence. |
| Operator delivery acceptance | Receiving operator's separate decision after checking the signed build and physical delivery. |
| Reviewed address | Explicitly selected and confirmed address match; a label or GPS pin is insufficient. |
| On-site installation | Authorized operator's separate physical-presence statement for the same serial. |
| Planogram | Actual product, price, capacity and lane map, checked against the physical contents. |
3. Factory acceptance (manufacturer)

Follow Android manufacturer sign-off in full:
- Match serial, board, model, ports, firmware, destination and approved APK. Verify SHA-256 and signer, then install in place. Preserve identity and data.
- Use the approved credential handover to open the service menu. Configure network, gateway and device authentication; complete authorized enrolment arming where required. Confirm the cabinet's fresh cloud record.
- Test every lane, actual delivery, fitted payment path, faults and recovery. Record all required physical FAT dispositions, including absent optional parts.
- Run the Android diagnostics and upload them. An offline queue is not proof that the cloud accepted a report or signature.
- Complete and read back the Android handwritten acceptance certificate and the separate Partner FAT factory signature. Retain both identifiers and the physical test evidence. The receiving operator signs their own acceptance later; no factory record substitutes for it.
4. Shipping and the USA warehouse

Match the signed records to the cabinet and fitted accessories. Include the traveller, versions/digests, lane map, destination configuration, accessory IDs, recovery procedure and unresolved restrictions. Transfer credentials through an approved secure channel, separately from public paperwork.
The receiver checks crate and serial, damage, accessories and saved records. Resolve discrepancies before acceptance. A warehouse status badge does not prove the machine survived shipment or was installed correctly at its venue.
5. First-time install at the venue (operator or employee)

Use the full first-install manual, then save the completed atlas checklist for this serial:
- Inspect the delivery. Follow the cabinet manufacturer's placement, electrical, clearance, anchoring and ventilation requirements with a qualified installer.
- Power on, open authorized Android Settings, join venue Wi-Fi and return Home to the kiosk. Confirm a fresh gateway heartbeat for this exact serial.
- Sign into the staff Operator app with your own authorized account. Confirm tenant and permissions, then claim the matching unclaimed cabinet. Resolve ownership conflicts through the authorized owner; do not create a new identity.
- Review and confirm the suggested address match. At the actual cabinet, separately confirm on-site installation with its exact serial and placement.
- Bind the fitted reader by its correct Device Number, or use the supported configured QR-only path. Set real products/prices and record actual filled quantities. Read back saved state after a timeout before repeating an action.
- Review readiness, physical vend/payment/refund evidence and the distinct acceptance records. Fix incomplete checks; do not force them green.
- Go live only when the required evidence and gateway checks pass. Verify the saved live state, cold reboot, recovery and the operator's support procedure.
Reyeah uses its own approved vending APK and controller protocol. The staff app is a different app. Preserve a commissioned Reyeah machine's identity and use the Reyeah migration and acceptance procedure.
6. What was done on 5 September 2026
The earlier handbook and live-demo narrative are retained as historical source
records under docs/reviews/, with 2026-09-05-historical in their filenames.
They describe an older build and simulated records, not current cabinet
acceptance. Use the current guides above for installation and release evidence.
7. Demo
Use the supervised training walkthrough. A disconnected tablet or staging simulator can teach navigation. It cannot prove a vend, charge, refund, factory signature or shipping readiness. Keep training identities and data separate from production.
8. Known gaps and recommended next steps
Physical cabinet acceptance has not been executed by this software audit. Each cabinet still needs the witnessed tests and signatures in the guides. A source merge or downloadable APK does not deploy the production API or start a fleet OTA rollout. Verify the actual installed release before relying on a control. The platform guide documents interface and Apple-release differences.
Payments are qualified per destination, processor account, currency and fitted reader. A successful test in one configuration is not global payment approval. If a staff account lacks an action, have the authorized owner perform it or provide supported access. Offline acceptance and update/recovery depend on the actual cabinet hardware and approved policy.
9. What it looks like once installed — the machine, the phone, Operator X

The shopper guide covers payment, cancellation, failed or partial delivery, refund tracking and optional experiences. A refund owed is not a completed return; reconcile the original order before collecting another payment.

Daily staff review online state, stock, product dates, prices, cleanliness and unresolved money or hardware issues. Fleet operators prioritize affected machines, assign supported work, verify results and roll out approved updates in monitored stages. Follow fleet operations and shopper support for the full sequence.