A custom self-service terminal sample is not a demo unit. It is the physical reference that decides whether your bank, metro, or government service center deployment can be repeated at scale, whether your certification path is realistic, and whether your rollout schedule survives the first real production run. This guide covers what to confirm before sampling, how OEM terminal sample making affects the schedule, what a sample report should and should not claim, and how an approved kiosk pre-production sample becomes the basis for custom kiosk trial production and mass production. Cases from Greece, Romania, Australia/New Zealand, and Austria show how these decisions work in real public-service deployments.
Most sampling delays do not come from the production line. They come from open questions that were never settled before tooling and material orders began. A self service terminal sample built on unclear inputs cannot be approved as a production reference, because no one can say which configuration was actually validated.
Not every sample can anchor a mass production order. An early engineering sample proves basic fit and operation, but only a kiosk pre-production sample — built with production-intent materials, production-intent peripherals, and a production-intent assembly path — can serve as the Golden Sample for bulk orders. The commercial difference matters: a buyer who signs off on a hand-built engineering unit is signing off on something the factory has not yet shown it can repeat.
| Sample stage | What it confirms | Material and process source | Can it anchor mass production? |
|---|---|---|---|
| Muestra de ingeniería | Basic fit, layout, and subsystem operation | Mixed sourcing, engineering assembly | No |
| Pre-production sample | Full configuration, assembly sequence, test readiness | Production-intent BOM and process | Yes — as the Golden Sample candidate |
| Trial production unit | Consistency across multiple units, fixture readiness | Production tooling, pilot line | Yes — validates the production system |
Before a sample PO is issued, the following should be confirmed in writing, not agreed verbally:
Utilice el Pre-Sampling Confirmation Checklist to verify these inputs before your next sample PO.
El OEM terminal sample making sequence is predictable. What matters for a bank, metro, or government buyer is knowing where their confirmation is required and what each stage delivers.
A useful lead-time answer separates build time from waiting time. The time spent on the production line is usually a smaller share of the schedule than buyers expect; the larger share is drawing revisions, outsourced surface treatment, peripheral kitting, and re-test cycles.
| Nivel de personalización | What changes | Indicative schedule range | Main time driver |
|---|---|---|---|
| Existing base model with logo, color, or peripheral change | Cosmetic and accessory-level change | Typically 10–20 working days | Peripheral availability and artwork approval |
| Structural modification to an existing platform | New cutouts, internal bracket, display size change | Typically 20–35 working days | Sheet-metal rework, touch integration, re-test |
| New enclosure or new architecture | Full industrial design, new tooling path, new thermal design | Project-specific; scheduled after design release | Tooling, first-article inspection, engineering iterations |
Ranges above are planning references, not contractual commitments. The binding schedule should be built from the confirmed input checklist and the supplier's confirmed material lead times.
For overseas buyers, the approval clock starts when the self service terminal sample is powered on at the destination, not when it leaves the factory. International freight, customs clearance, and local power verification belong on the same timeline. A buyer who plans the rollout from the shipment date will usually find the gap two weeks before installation.
A realistic approval timeline therefore looks like: input confirmation → sample build → internal test and report → export packing → international transit and clearance → on-site power and workflow verification → written approval or revision request. Treating the transit segment as zero is one of the most common planning errors in cross-border terminal projects.
A sample report that only says "all functions normal" is not a decision document. It should state what was tested, under what conditions, with what result, and — critically — what the test does no prove.
| Test category | What to verify | Typical output |
|---|---|---|
| Structure and appearance | Gap and flush, coating finish, touch feel, label and branding position | Photo set and dimensional check record |
| Peripheral function | Card reader, ID scanner, passbook printer, receipt printer, camera, speaker output | Per-peripheral pass/fail with test conditions |
| Software and workflow | End-to-end transaction or service flow, error states, recovery after interruption | Workflow test script and observed results |
| Continuous operation | Thermal stability, touch drift, peripheral timeout under sustained use | Duration log and any anomaly record |
| Acceso al servicio | Paper change, card stock replenishment, cable access, module removal time | Serviceability notes and photos |
| Scenario-specific | Outdoor readability, wet touch, vibration, unattended restart | Condition-specific result sheet |
Functional testing on a sample does not equal CE, FCC, or UL compliance. Those are separate conformity paths with their own laboratory schedules, documentation packages, and configuration requirements. UL in particular depends on the exact construction and component set, and a later peripheral or enclosure change can reopen the evaluation.
The correct position at the sample stage is: prepare for certification, do not claim it early. Pre-compliance testing can reveal obvious emissions or safety issues, but the formal certificate is issued through the relevant conformity assessment route, not through a factory sample report.
EEAT-relevant distinction: A supplier that says the sample "meets CE" without naming the directive, the test standard, and the notified body or test laboratory is not giving you a certification statement. It is giving you an opinion. The sample report should clearly separate functional results from conformity status.
An approval signature is only as strong as the record behind it. The approved kiosk pre-production sample should be identified by a version set, not by a serial number alone.
The Golden Sample is a physical reference for color, texture, assembly gap, touch feel, and peripheral mounting state. It is not proof that every future unit will perform identically. Mass-production consistency comes from tooling, fixtures, SOPs, and process control — the Golden Sample is the target those controls point toward, not the control system itself.
Custom kiosk trial production exists because one unit proves feasibility, while a pilot run proves consistency. These are different questions, and the second determines whether a multi-site deployment across bank branches or metro stations is safe.
A single sample can be hand-fitted, individually debugged, and selectively tested. A trial run must show whether the same result can be achieved across multiple units using the same fixtures, the same SOP, and incoming material from the same or equivalent batches.
A pilot run is not "buying a few more units." It is the verification step that turns a Golden Sample into a production release. Skipping it does not usually cause a "cannot build" problem; it causes a "built inconsistently and found out at deployment" problem.
The handoff from approved sample to mass production is a configuration-control exercise. The sequence that protects the buyer is:
After sample approval, any change to a peripheral, material, enclosure, or software version should move through a written ECN that records the old revision, the new revision, the effective production batch, and the disposition of existing stock. A supplier without an ECN process is not flexible; it is uncontrolled. The buyer's protection is not a promise that nothing will change, but a record that shows what changed and when.
The commercial terms around a self service terminal sample are where many otherwise technical discussions stall. The buyer needs to know what the sample fee covers, whether it is recoverable, how the pilot run connects to mass-production MOQ, and what the landed cost of the sample actually is.
A sample fee typically covers single-unit or small-batch material, labor, engineering time, and packing. For custom configurations, the sample is usually not resalable, which is why refund conditions are stricter than for standard products. Refund and deduction are not the same thing: a refund returns money; a deduction credits the sample fee against a later bulk order. The buyer should ask for written terms covering:
Standard configurations and fully custom builds often carry different MOQ policies, and the trial-production quantity may sit between a single sample and the mass-production MOQ. Clarifying this before the sample PO avoids the common surprise where the pilot run is approved but the following bulk order triggers a different pricing tier or MOQ threshold.
The final stage of sample delivery includes export crating, customs documentation, and destination power verification. Many terminals are designed for wide-voltage input, but the specific power configuration, plug type, and any local safety requirement should be confirmed before shipment. A sample quotation that looks inexpensive can become expensive once freight, insurance, duties, and customs clearance are added — and those costs should be visible before the PO, not after.
Send your deployment market and expected volume — we will return a sample scope and commercial terms in one response.
The following cases are drawn from typical project patterns in specific markets. They show where the confirmation checklist, the testing boundary, and the trial-production decision change the outcome — not as testimonials, but as decision references for bank, metro, and government buyers.
A Greek metro operator needed a self-service ticketing and card top-up terminal for a busy city-center station with heavy summer passenger flow. The self-service terminal sample confirmation checklist had to settle the protection rating, display brightness, and anti-corrosion coating before the enclosure drawing was released. The sample report included readability under station lighting and continuous unattended operation, but the buyer was told clearly that CE marking would require a separate conformity assessment — the sample test did not replace it.
El kiosk pre-production sample was approved with a deviation log noting that the card reader bezel needed a gasket revision. Because the deviation was recorded in writing, the custom kiosk trial production run incorporated the revised gasket and validated it across ten units before mass production was released. The lesson: scenario testing belongs in the sample scope, but the certification claim does not.
A Romanian public service integrator required a self service terminal sample that could run their own application and connect to an existing queue-management system. The confirmation checklist defined the software responsibility boundary: the integrator supplied the application and the API, the terminal supplier owned driver integration and peripheral compatibility. The OEM terminal sample making process included a full workflow test using the integrator's actual software build, not a demo app.
During sample approval, the integrator requested a change to the ID scanner model. Because the approval record had already listed the BOM revision and software version, the change triggered a formal ECN rather than a verbal substitution. The kiosk pre-production sample was rebuilt with the new scanner and re-tested before the Golden Sample was signed. The trial production run then confirmed that the new scanner batch performed consistently across units.
A bank group deploying across Australian and New Zealand branches required a self-service terminal with a card reader, passbook printer, and an accessible interface height. The self-service terminal sample confirmation checklist settled the coating, the operating temperature range, and the card reader model before fabrication. The sample report included a thermal test and an accessibility check, but the supplier separated these functional results from the RCM compliance path, which required its own testing and documentation.
El custom kiosk trial production run was scheduled for twelve units across two voltage configurations. The pilot run revealed a variance in the card reader bezel fit from one batch, which was corrected before mass production. The buyer's approval record included the pilot-run deviation and the corrective action, so the mass-production release had a traceable basis rather than a verbal assurance.
An Austrian public transport operator needed a ticketing and wayfinding terminal that met local accessibility requirements for screen height, touch target size, and audio output. The OEM terminal sample making process included an accessibility review at the drawing stage, not after the sample was built. The kiosk pre-production sample was tested with the operator's multi-language application and a simulated passenger workflow covering ticket purchase, route lookup, and assistance request.
The sample approval record noted that the audio output level needed adjustment for the station's ambient noise profile. The revision was logged, the sample was re-tested, and the Golden Sample was signed with the revised audio configuration. The trial production run validated the audio setting across units and confirmed that the CE conformity documentation package matched the approved configuration. The lesson: accessibility and conformity depend on the exact configuration, and the sample record must reflect the configuration that will be certified.
The points below summarize what a bank, metro, or government buyer should review before releasing a bulk order. They follow the process, testing, approval, and trial-production sections above and serve as a final internal check.
Yes, provided the drawings are at a releasable revision and the reference images are supported by dimensional or functional specifications. A reference image alone is not a manufacturing input; it is a design intent. The confirmation checklist exists to turn intent into a buildable specification before the self service terminal sample PO is issued.
Yes. The sample stage should include a workflow test using the buyer's actual application build, not a generic demo. The software responsibility boundary should be agreed in advance: who supplies the application, who owns driver integration, and who resolves compatibility issues found during the sample test.
Akiosk pre-production sample is a single unit built with production-intent materials and process, used to establish the Golden Sample. A trial production unit is part of a small pilot run that verifies consistency across multiple units, fixture readiness, and SOP executability. The first proves feasibility; the second proves reproducibility.
Deduction is common in custom terminal projects, but the conditions should be written: the trigger (minimum PO value or quantity), the deduction method (full or partial credit), the time window, and what happens if the bulk order does not proceed. Refund and deduction are different mechanisms and should not be treated as interchangeable.
Not necessarily, but the certification path should be defined before mass production. The sample stage prepares for certification; it does not replace it. CE, FCC, UL, RCM, and other conformity routes have their own testing, documentation, and configuration requirements, and a later configuration change can reopen the evaluation.
The change should move through a written ECN that records the old and new revision, the effective batch, and the disposition of existing stock. The substitute component should be evaluated against the same test matrix used for the approved sample, and the buyer should receive the updated test record before the change is released to mass production.
The purpose of OEM terminal sample making is not to produce a machine that can be demonstrated to stakeholders. It is to establish a reproducible manufacturing reference — a Golden Sample backed by a confirmed BOM, a recorded software version, a documented test report, and a trial-production run that proves consistency. Buyers who treat the sample as a demo often discover the gap at deployment; buyers who treat it as a production baseline close that gap before the bulk order is placed.
The decision chain is straightforward: confirm the inputs, build the kiosk pre-production sample against a production-intent process, test what the sample can actually prove, separate functional results from certification claims, approve with a versioned record, validate consistency through custom kiosk trial production, and release mass production only after the configuration is confirmed. Each step protects a different risk, and skipping any one of them shifts that risk to the bank branch, metro station, or service center where the terminal is installed.
Ready to scope your self-service terminal sample? Send your application scenario, target market, expected volume, and deployment timeline.
CEO | Experto en soluciones interactivas de visualización y colaboración
Soy el fundador de Qtenboard y aporto más de 17 años de experiencia práctica a la industria de las pantallas táctiles. Basándome en la perspectiva de gestión global obtenida a través de mis estudios de EMBA en la Universidad de ShenZhen, dirijo a mi equipo en la optimización de cada etapa de nuestras operaciones, desde la definición del producto hasta la gestión de la cadena de suministro de alta eficiencia, asegurando que nuestras capacidades de fabricación permanezcan a la vanguardia de la industria.
Como el líder de Qtenboard, me especializo en el abastecimiento de las soluciones adaptadas de OEM/ODM para los whiteboards interactivos, las paredes video del LCD, la señalización digital, y los terminales del tacto del industrial-grado. Con el respaldo de nuestro moderno parque industrial de 330.000 m² en Shenzhen, mantenemos el control del ciclo de vida completo sobre el diseño industrial, la fabricación de precisión y las rigurosas pruebas de rendimiento.
Con casi dos décadas de experiencia en proyectos, las soluciones de visualización de Qtenboard ahora se implementan en más de 120 países y regiones, y se ganaron la confianza de más de 15.000 clientes empresariales en todo el mundo. Si está buscando un socio receptivo con una base de fabricación profunda para sus proyectos personalizados de pantallas táctiles, mi equipo y yo estamos listos para respaldar su visión con excelencia profesional.
spa
EN 
pt 
th 
vie 
aze 
bel 
est 
lav 
ukr 
ru