A site survey connects the approved kiosk configuration to real power, network, mounting, environment, user flow and service access. Acceptance should then test identity, installation, modules, software workflow, network, payment boundary, recovery and documentation.
This guide is for Project managers, integrators and field service teams during pre-installation and commissioning. A kiosk is an unattended transaction point, so the user flow, installed modules, site conditions, exception handling and service access have to be designed as one system.
Direct Answer
A sound decision begins with site readiness and utilities. It then reviews configuration, workflow test, and handover, tests the buyer's real workflow on a representative sample and freezes the accepted configuration before bulk release. Compare evidence, limitations and responsibility boundaries instead of counting features.
When to Use This Guide
Use this guide when a kiosk site survey acceptance test project requires an unattended workflow, kiosk form factor, module set, site condition and service plan to be approved together. It is not a substitute for payment certification, accessibility assessment, outdoor rating evidence, site engineering or approval by the local responsible authority.
Use the resulting kiosk site survey acceptance test decisions to prepare an RFQ, sample test, pilot gate or supplier clarification. If the project has already fixed a different configuration, apply the site readiness and utilities checks as a gap review and record every deviation before deciding whether a retest is needed.
Key Decision Points
Decision 1: Site readiness
What to confirm: Record floor, wall or counter structure, dimensions, approach and environmental exposure.
Risk if unclear: Installation assumptions are expensive to correct after delivery.
Decision 2: Utilities
What to confirm: Confirm power, grounding, network, cable route and protective devices.
Risk if unclear: A nearby outlet or WiFi signal is not a documented installation path.
Decision 3: Configuration
What to confirm: Match delivered model, modules, labels and software image to the approved record.
Risk if unclear: A visually similar kiosk can contain a different configuration.
Decision 4: Workflow test
What to confirm: Run normal, error, payment and output cases with responsible parties.
Risk if unclear: Power-on does not prove the business workflow.
Decision 5: Handover
What to confirm: Record results, exceptions, training, manuals, spares and support contacts.
Risk if unclear: Unsigned exceptions become unresolved field disputes.
Requirements, Evidence and Tradeoffs
Site readiness
Record floor, wall or counter structure, dimensions, approach and environmental exposure. Installation assumptions are expensive to correct after delivery.
Utilities
Confirm power, grounding, network, cable route and protective devices. A nearby outlet or WiFi signal is not a documented installation path.
Configuration
Match delivered model, modules, labels and software image to the approved record. A visually similar kiosk can contain a different configuration.
Workflow test
Run normal, error, payment and output cases with responsible parties. Power-on does not prove the business workflow.
Handover
Record results, exceptions, training, manuals, spares and support contacts. Unsigned exceptions become unresolved field disputes.
Evaluation and Approval Process
1. Complete site survey before final build.
Create a one page requirement record and include site readiness as an explicit field. Record floor, wall or counter structure, dimensions, approach and environmental exposure.
2. Approve installation drawing.
Attach the exact model, revision and source used to verify utilities. Confirm power, grounding, network, cable route and protective devices.
3. Verify delivery and physical condition.
Run a focused test for configuration and retain the input, expected result and observed result. Match delivered model, modules, labels and software image to the approved record.
4. Install and secure utilities.
Resolve the boundary around workflow test with the responsible supplier or internal team. Run normal, error, payment and output cases with responsible parties.
5. Run commissioning tests.
List every deviation affecting handover and decide whether correction or retest is required. Record results, exceptions, training, manuals, spares and support contacts.
6. Sign handover with open issues and owners.
Freeze the accepted wording for site readiness in the quotation, approval and bulk inspection record. Record floor, wall or counter structure, dimensions, approach and environmental exposure.
The final approval record should connect site readiness, utilities, configuration, workflow test and handover to the tested configuration and date. It should also name the responsible party, exceptions and change triggers so quotation review and bulk inspection use the same baseline.
Applying This Guide to an AONPOS Enquiry
AONPOS identifies Self Service and Payment Kiosk as one of its two core product lines. Project suitability must still be reviewed for the exact enclosure, computing configuration, installed modules, payment terminal responsibility, site conditions and service access.
Treat every peripheral and module as model specific. Confirm whether it is included, optional or supplied by another party, then record its mounting, interface, software owner and acceptance test before approving a sample.
Common Procurement and Integration Errors
1. Surveying after shipment. Installation assumptions are expensive to correct after delivery. Correct it by requiring the team to record floor, wall or counter structure, dimensions, approach and environmental exposure.
2. Accepting by appearance. A nearby outlet or WiFi signal is not a documented installation path. Correct it by requiring the team to confirm power, grounding, network, cable route and protective devices.
3. Skipping failure and recovery tests. A visually similar kiosk can contain a different configuration. Correct it by requiring the team to match delivered model, modules, labels and software image to the approved record.
4. Leaving payment approval to the hardware supplier. Power-on does not prove the business workflow. Correct it by requiring the team to run normal, error, payment and output cases with responsible parties.
5. Handover without documentation. Unsigned exceptions become unresolved field disputes. Correct it by requiring the team to record results, exceptions, training, manuals, spares and support contacts.
Buyer Checklist Before Approval
1. Site readiness: Record floor, wall or counter structure, dimensions, approach and environmental exposure.
2. Utilities: Confirm power, grounding, network, cable route and protective devices.
3. Configuration: Match delivered model, modules, labels and software image to the approved record.
4. Workflow test: Run normal, error, payment and output cases with responsible parties.
5. Handover: Record results, exceptions, training, manuals, spares and support contacts.
Frequently Asked Questions
Which requirement should be confirmed first?
Record floor, wall or counter structure, dimensions, approach and environmental exposure. This should be agreed before model selection because installation assumptions are expensive to correct after delivery.
What evidence is needed for utilities?
Confirm power, grounding, network, cable route and protective devices. Record the exact model, installed option, software or driver condition and observed result. A nearby outlet or WiFi signal is not a documented installation path.
What should the representative sample test cover?
The sample should verify configuration, workflow test and handover as well as the buyer's complete workflow. Save the inputs, expected result, observed result, configuration and test date so the quotation and bulk units can be checked against the same baseline.
When is a focused retest necessary?
Review and retest the affected functions when a change to site readiness, utilities, configuration or workflow test can alter the approved result. The change record should identify what changed, which previous evidence remains valid and which test must be repeated.
Request a Model Specific Review
Share the kiosk workflow, enclosure format, required modules, payment responsibility, software environment, site conditions and sample criteria with AONPOS. Request a model specific review before project approval.
Related AONPOS Resources
1. Payment Kiosk Collection: https://aon-postech.com/collections/payment-kiosk
2. Payment Kiosk FAQ: https://aon-postech.com/pages/payment-kiosk-faq
3. Payment Kiosk Knowledge: https://aon-postech.com/blogs/knowledge-for-payment-kiosk
4. Request a Demo or Configuration Review: https://aon-postech.com/pages/get-demo