Two quotations can both say "21.5-inch touchscreen kiosk with printer," yet describe different machines. One price may include a fully assembled enclosure, tested touchscreen, operating-system license, printer, wiring, and installation kit; another may omit the PC, application, payment hardware, mounting, freight, and onsite commissioning. The purchasing mistake is to compare those totals as if the quoted scope were identical.
A self-service kiosk RFQ should translate the customer task into measurable system requirements and a configuration-level bill of materials (BOM). The RFQ defines the expected result and how it will be accepted. The BOM identifies the parts, assemblies, quantities, and revisions needed to deliver the specified configuration. This guide provides fields and example wording for buyers preparing a supplier-ready RFQ; it does not present unverified KioskTagScreen model specifications as standard features. The relevant commercial range is the Kiosk Display portfolio.
First Separate Requirements, BOM, Quote, and Acceptance Evidence
These documents answer different questions and should not be substituted for one another. A supplier's component datasheet may demonstrate an interface or rating for that part; it does not show that the assembled kiosk meets a transaction requirement in the intended environment.
| Document | Main question answered | Required owner |
|---|---|---|
| RFQ / statement of requirements | What must the delivered kiosk do, under which conditions, with what evidence? | Buyer with operations, IT, engineering, and service |
| Configuration-level BOM | Exactly which assemblies, options, quantities, and revisions are included? | Supplier, subject to buyer approval |
| Quotation and scope matrix | What is included, excluded, optional, separately billed, or buyer-supplied? | Supplier and commercial buyer |
| Interface control record | Who owns electrical, physical, software, and data connections? | Designated integrator and interface owners |
| Acceptance plan | Which tests and artifacts prove the specified system has been delivered? | Buyer and supplier jointly before award |
The RFQ should use unique requirement IDs and a response status such as compliant, compliant with deviation, optional, not offered, or clarification required. A bare checkbox marked "yes" is not enough for a critical interface. For every mandatory requirement, request the exact quoted configuration, proof source, and planned verification.
Maintain one traceable chain from the purchase need to the accepted serial number
An RFQ should identify its baseline explicitly: RFQ revision → requirement ID → offered configuration/BOM revision → supplier response and deviation → verification method → FAT/SAT evidence → accepted as-built serial/configuration. A bidder should not answer "compliant" without identifying the offered assembly or proof. If a requirement changes after quotations are received, send the same controlled amendment to all bidders and record the response revision.
This traceability principle is also used in established systems-engineering guidance. The NASA Systems Engineering Handbook describes requirement IDs, traceability and assigned verification methods; it is cited here as a method reference, not as a rule that ordinary commercial kiosks must meet NASA program requirements.
Write the User Outcome Before Choosing Components
Start from the kiosk's actual job: ticketing, wayfinding, check-in, ordering, payment, or another defined workflow. Identify who uses it, where it operates, what external systems it relies on, and what happens when a required peripheral is unavailable. This prevents the bill of materials from becoming a collection of attractive hardware brands with no clear acceptance criterion.
| RFQ field | Example of a buyer-owned requirement | Evidence requested |
|---|---|---|
| Use case and transaction boundary | Complete the approved check-in workflow using production-representative records | Reviewed workflow and observed end-to-end test |
| User environment | Fit the approved site plan without obstructing circulation or service access | Installed envelope drawing and site inspection |
| Failure behavior | When a mandatory dependency is unavailable, prevent misleading transaction completion | Fault-injection test and visible user state |
| Maintenance duty | Allow authorized replacement of designated FRUs using documented procedures | Service task demonstration and parts record |
| Configuration handover | Deliver the approved as-built hardware and software revision list | Signed configuration export and serial mapping |
These examples illustrate contract structure; they are not universal performance promises. A live project must supply its own acceptance limits, applicable laws, site constraints, and security policies. Avoid writing unverified numeric values merely to make the RFQ appear precise.
Translate a use case into acceptance-ready requirements
Take a hypothetical unattended check-in kiosk that prints a receipt and relies on a network-based check-in service. The buyer might record the following examples; the exact thresholds and behaviors require project approval and are not asserted product capabilities:
| Requirement ID | Buyer-defined requirement example | Verification and evidence |
|---|---|---|
| KSK-PRN-01 | With the production-equivalent enclosure closed and approved media loaded, the kiosk shall issue the agreed receipt format through the customer-accessible exit without requiring door access. | Demonstrate at the installed slot with the approved printer/media; retain photographs and pass/fail log |
| KSK-SW-02 | After controlled application restart, the kiosk shall reach the buyer-approved ready-to-serve state without an exposed general-purpose desktop. | Repeat agreed restart scenarios using the delivered OS/application image; record startup state and exceptions |
| KSK-NET-03 | When the transaction backend is unavailable, the kiosk shall follow the approved restricted/unavailable transaction rule rather than reporting an unconfirmed operation as successful. | Controlled dependency outage; inspect UI, transaction record and reconciliation trace |
| KSK-SVC-04 | A trained field technician shall be able to replace the designated FRU under the documented isolation/access procedure, then restore the approved customer task. | Observed service demonstration, revision-controlled work instruction, installed configuration and final transaction result |
Each requirement should additionally record the priority (mandatory or optional), owning party, applicable kiosk variants, verification location, acceptance authority, and whether a supplier response is a fully tested implementation or a proposed integration. This is how an operational intention becomes a quotation item and a defendable acceptance decision.
Build a Configuration-Level BOM, Not a Brand Wish List
A workable kiosk BOM should distinguish the top-level assembled unit from its purchased subassemblies, factory-fitted modules, service items, cables, mounting accessories, and optional peripherals. Different supplier options need separate line items or configuration codes, not an ambiguous note such as "printer if needed."
| BOM column | What to record |
|---|---|
| Item / assembly ID | Unique line reference linked to the drawing and quotation |
| Level and parent assembly | Whether it belongs to the top-level kiosk or a subassembly |
| Function / approved description | What the item actually performs, not only a marketing model name |
| Manufacturer, MPN, and supplier SKU | Exact source identity where approved and available |
| Quantity and unit | Per completed kiosk, per site, per shipment, or optional kit |
| Hardware revision and approved alternative | Traceability and substitution boundaries |
| Critical interfaces | Electrical power, data, physical mounting, cable/connector, software driver |
| Included / optional / buyer-furnished | Commercial responsibility for the quoted configuration |
| Verification / drawing reference | Document and test linking the part to system-level acceptance |
| Lifecycle / service classification | Field-replaceable, depot-only, consumable, or not intended for field service |
An illustrative structure might place the enclosure, display-touch assembly, compute module, power distribution, printer, and cable set beneath one kiosk-level assembly. That is a conceptual example, not a declaration that every SKU includes all these parts. If a payment device is supplied by a third party, its mounting provision, electrical interface, security provisioning, and responsibility boundary still need their own RFQ entries even when the reader is excluded from the supplier's price.
For the distinction between a BOM and a general list of desired features, see the definition of a bill of materials: assemblies, components, quantities, and product structure underpin production. A sales brochure alone is not a controlled BOM.
Example: a two-variant configuration-controlled BOM excerpt
The example below uses fictional part identifiers to show how an RFQ avoids a deceptively generic "kiosk with printer" description. It does not represent a KioskTagScreen model or product BOM. Count each component according to the top-level assembly/variant, and define which options are included in the quoted base price.
| Level / item | Variant A: check-in only | Variant B: check-in + receipt | Buyer needs to freeze |
|---|---|---|---|
| L0 KSK-BASE-EX (example assembly) | 1 | 1 | Mechanical build revision and mounting/site constraints |
| L1 DISPLAY-EX | 1 | 1 | Exact touch controller/interface, viewing and access requirements |
| L1 COMPUTE-EX | 1 | 1 | OS image, driver baseline, power/port reservations |
| L1 PRINTER-EX | 0 | 1 | Media specification, paper path, power, service clearance and app driver |
| L1 PRINTER-HARNESS-EX | 0 | 1 | Harness connector, routing and retention revision |
A real supplier response needs part number, revision, quantity per assembly, approved alternate, maker/sourcing status, lead time, supplied-by party, configuration restriction and reference drawing. An assembly BOM, installation kit, software/license schedule and service-spares list may be different documents; they should be cross-referenced, not silently merged into one ambiguous quantity field.

Record Every Interface Between the Kiosk and Someone Else's System
Interfaces are where quoted scope frequently breaks down. A scanner can be mechanically installed but have an incompatible software driver; a receipt printer can run on the bench while the installed paper path is blocked; a payment reader can be present without the responsible party having approved its backend integration.
For each interface, document source, destination, connector or protocol, data owner, power budget, mounting constraint, firmware/driver dependency, security responsibility, test owner, and change-control route. Mark the responsible party: kiosk manufacturer, buyer, application integrator, payment provider, facility team, or another named organization.
- Display and touch: diagonal, resolution, orientation, touch technology, controller and host compatibility, viewing conditions, and accessibility requirements derived from the site.
- Compute and OS: actual board or module, storage, memory, interfaces, licensed OS or image, boot behavior, and who maintains security patches.
- Printer and scanner: exact supported media, service access, cable/power needs, SDK or driver, and what happens when a mandatory peripheral fails. Detailed printer geometry belongs in the printer paper-path design guide.
- Payment integration: supplied-by status, reader mounting, transaction workflow owner, integration test access, security and certification evidence for the exact scope; do not infer complete payment compliance from a component logo.
- Enclosure and mounting: finished dimensions, mass, anchoring, cable exits, service-door swing, thermal and ingress conditions, and site installation owner.
- Network and management: physical media, provisioning, recovery rules, credential custody, logging access, and division of remote-support responsibilities.
A dedicated kiosk accessibility guide addresses the actual hardware and interaction design work. The RFQ page should specify which requirements and evidence the supplier must quote, not reproduce all accessibility standards in a generic checklist.
Clarify ownership at each handoff, not just component supply
For example, a payment terminal may be buyer-supplied but kiosk-integrated. The quote still needs a mounting/space/power allowance, an owner for cabling, a provider responsible for security provisioning, and a test environment owner. Use a responsibility matrix for this exact procurement:
| Interface outcome | Kiosk fabricator | Buyer / application integrator | Third-party service |
|---|---|---|---|
| Payment reader physically mounts, can be safely serviced | Proposes cutout, bracket, cable route and mounting evidence | Approves reader configuration and site workflow | Supplies accurate reader drawings where applicable |
| Reader is provisioned to accept transactions | Provides installed hardware access as contracted | Names acceptance lead and end-to-end test cases | Owns credential/security setup where contracted |
| Receipt correctly represents completed transaction | Supports agreed printer hardware/interface | Owns application output and failure behavior | Provides gateway/payment status and test data |
These are illustrative role splits, not universal responsibility assignments. The real contract should name one accountable integration owner per outcome and one party responsible for producing acceptance evidence. "Device supplied by others" is an exclusion only for the specified item-not automatically for its cutout, power, cabling, SDK, provisioning, testing, or compliance coordination.
Compare Quotations on a Common Scope
Before comparing unit prices, build a normalization matrix. Ask every bidder to price or explicitly exclude the same configuration and to disclose which components and services are included in the unit, site, and recurring fees. Missing items are commercial uncertainties, not presumed savings.
| Scope item | What to normalize |
|---|---|
| Complete assembled kiosk | Quoted build code, enclosure, display, computer, PSU, cables, and included peripherals |
| Software and licensing | OS image, app, MDM/remote management, runtime licenses, renewal obligations |
| Installation and commissioning | Freight, unloading, mounting, power/network hookup, provision, site acceptance |
| Service and training | Warranty start and exclusions, onsite coverage, tools, service manuals, training |
| Spare modules and consumables | Starter kit, unit of issue, location, lead time, shelf life, revisions and return rules |
| Testing and documentation | Sample build, FAT/SAT scope, engineering drawings, BOM release, as-built records |
| Commercial conditions | Currency, Incoterms if used, tax, MOQ, price validity, forecast assumptions, delivery schedule |
Make inclusions and exclusions visible beside each price. A low unit quote with unsupported interfaces, separately billed commissioning, unclear replacement parts, or absent test evidence may be the higher total-risk offer. Do not fabricate a cost comparison using unsourced market prices; request supplier responses for the real project.
Worked comparison: the lower unit price can produce the higher normalized cost
Suppose two vendors quote a fictional order of 100 identical kiosk configurations over a 24-month comparison horizon. Assume all stated figures use the same currency and that applicable taxes, energy, connectivity, transaction processing, financing and later repairs are excluded consistently. These are example arithmetic inputs, not market prices or vendor quotations.
| Comparable scope line | Bid A | Bid B |
|---|---|---|
| 100 complete kiosks | 100 × $2,300 = $230,000 | 100 × $2,600 = $260,000 |
| Installation and commissioning | 100 × $250 = $25,000 | Included in configured unit price |
| Required management license for 24 months | 100 × $15 × 24 = $36,000 | Included for the same 24-month term |
| Delivery / freight | $8,000 | $6,000 |
| Approved initial spares kit | $6,000 | $5,000 |
| Normalized comparison subtotal | $305,000 | $271,000 |
Bid A looks cheaper on the hardware unit price but is $34,000 more expensive on the stated scope. This is not yet a complete total-cost-of-ownership comparison. Before choosing B, verify that management capabilities, supplied peripherals, implementation obligations, support response, warranty exclusions, and acceptance evidence actually match. If B excludes a required integration or cannot substantiate a mandatory requirement, do not convert the omission into a zero-dollar savings.
Every comparison row should have a response state: included / separately priced / customer-supplied / not offered / clarification required. Keep assumptions beside the spreadsheet cell and obtain a revised quote when a bidder resolves an exclusion.
Specify the Change and Substitution Rules Before Award
A substitute component can preserve a headline attribute while changing integration behavior. A replacement display with the same diagonal might require a new touch driver; a revised power supply might alter connector location and thermal load. The contract should say which changes are notification-only, which need engineering approval, and which require requalification of an affected subsystem.
Ask for a controlled BOM revision, change notice with reason and affected line items, interchangeability statement, updated drawings, impacted test list, and serial/build traceability. Require approval before implementing a material substitution that affects safety, performance, fit, compatibility, availability, or the approved software image. Specify how end-of-life events and last-time-buy decisions will be communicated to the buyer.
Replacement-parts stocking and service-level inventory are separate operating decisions covered in the kiosk spare-parts planning guide. Here, the RFQ should establish the information, supplier commitments, and configuration controls that enable that later service plan.
Example change impact: a same-size touch display is not automatically interchangeable
Assume the accepted build uses display controller revision A, and the supplier proposes a same-diagonal panel with controller revision B. Before approval, compare touch interface enumeration, driver and OS-image support, cable location, mechanical mounting/glass geometry, power and thermal implications, service replacement instructions, and any affected test evidence. A supplier statement that both panels are "the same size" is not proof of interchangeability.
Record the engineering change as: original/alternate part IDs, affected kiosk serial range, reason, known differences, drawing and BOM revision updates, software image changes, retest owners, approval status and disposition of in-stock spares. ISO 10007:2017 provides general configuration-management guidance from concept to disposal; this citation is a method reference rather than a claim that a particular kiosk or supplier is certified.
Write Acceptance Clauses That Survive Supplier Interpretation
"Commercial-grade," "accessible," "secure," and "easy to maintain" are not stand-alone acceptance criteria. A defensible clause names the condition, required behavior, responsible party, test method, and evidence. The following are illustrative clauses, not ready-made legal terms:
| Ambiguous statement | Better RFQ wording pattern |
|---|---|
| Printer included | Supply the approved printer and media path for the stated receipt format; demonstrate paper loading and printing in the closed production-equivalent enclosure. |
| Software ready | Provide the agreed OS image, approved application build, drivers, and startup policy; demonstrate return to the specified ready state after controlled restart. |
| Easy to service | Demonstrate the agreed FRU replacement using the documented tools and site clearance; record access, disconnection, reassembly, and end-to-end functional verification. |
| Network resilient | Under a controlled network interruption, demonstrate the approved user message, permitted operations, and recovery without misreporting transaction success. |
| Compliant product | List applicable requirements for the target market and installation, the exact scope of each report/certificate, issued document and revision, and any deviations. |
Factory acceptance testing (FAT) and site acceptance testing (SAT) serve different purposes. A factory test can validate the delivered build under controlled conditions; the installed site test checks access, mounting, network, user path, and local constraints. The RFQ should identify which evidence is generated at each stage and who signs off, without expanding this purchasing guide into a full acceptance-test manual.
Convert a sample clause into observable evidence
Take the draft statement "printer shall be accessible for paper refill." It lacks an operating condition, service role, test result and record. A stronger buyer-defined example reads: "Using the production-equivalent kiosk, a trained service person shall replace the approved paper roll without removing the kiosk from its specified mounting. After the door is secured, the system shall issue the approved test receipt through the customer exit. The supplier shall provide the service instruction revision and witnessed pass/fail record."
That clause still needs the project-approved access limits, media, tools, applicable safety/isolation steps, sample count and witnessing location. These are not universal kiosk limits. A specific acceptance matrix should link the requirement to the FAT or SAT script, the configuration tested, the record ID, any deviations, and the buyer sign-off. Never treat one successful showroom demonstration as proof of every deployment site condition.

Do Not Confuse a Component Certificate With Whole-Kiosk Approval
A compliance claim must identify the product or assembly, applicable region and requirement, test configuration, issuing organization, evidence number where relevant, and any exclusions. A power supply's certificate is not automatically a certificate for the finished kiosk. The same applies to radio modules, payment readers, accessibility features, enclosure ingress ratings, and software security assessments.
The RFQ should ask suppliers to separate evidence already available, testing included in the quote, testing contracted elsewhere, and requirements that need buyer or authority review. Do not state that an unspecified kiosk is UL, CE, FCC, ADA, PCI or any other form of compliant merely because a supplier normally sells products in those markets. Applicable obligations depend on the final configuration, region, use, and contractual responsibilities.
Check the Supplier Response for Gaps Before Release
Run a short clarification meeting with engineering, service, IT, and procurement present. Their output should not be "supplier looks good"; it should be a closed set of decisions and remaining risks. Specifically, confirm whether every mandatory requirement has an exact offered configuration, whether the BOM identifies options and exclusions, whether interfaces have named owners, and whether acceptance is tied to an observable result.
Resolve high-impact deviations before purchase order issue. If a major interface or compliance requirement cannot be confirmed, record it as an explicit qualification or hold point rather than approving the quote and expecting the installation team to solve it at no cost. Where a buyer wants to permit an alternative, document the approval conditions and required re-test.
Release gates that prevent unresolved scope from being buried in the purchase order
| Decision gate | Evidence required | Hold condition |
|---|---|---|
| Technical configuration frozen | Signed BOM/variant matrix with exact approved revision and exceptions | Mandatory component or option still described only by a product family |
| Integration accountability closed | Named owner for each required hardware/software/third-party interface | Payment, network, identity or printer outcome has no end-to-end test owner |
| Commercial comparison complete | Normalized price and recurring costs with all exclusions recorded | Material missing fee, licensing period or installation responsibility |
| Acceptance evidence agreed | Requirement-to-test matrix, test location, witness and sign-off owner | Mandatory criterion cannot be objectively verified |
| Supply and lifecycle support bounded | Lead times, approved substitutions, warranty, spare parts and change notices | Critical component substitution allowed without review |
For IT-connected kiosks, supplier due diligence should also address component provenance, software vulnerability handling and supply-chain resilience as appropriate to the procurement. NIST SP 800-161 Revision 1 is a useful source for ICT supply-chain risk practices; it does not mean every retail kiosk procurement automatically falls under U.S. federal requirements.
Require an As-Built Handover That Matches the Purchase Order
The final packet should connect the approved RFQ revision to the accepted physical system: controlled BOM, model and serial configuration, hardware/firmware/OS/software versions, approved deviations, interface drawings, FAT and SAT evidence as contracted, spare-parts applicability, operator and service instructions, and a named owner for future changes.
Before signing off, verify the delivered part revisions against the frozen quote and assess every approved substitution. A prototype demonstration may be persuasive, but the commercial goal is to make production units equivalent to the evaluated configuration and supportable after handover.
A well-written self-service kiosk RFQ does not attempt to predict every hardware failure or create a generic 100-item wish list. It defines the business task, exact delivered configuration, boundaries of responsibility, price scope, change rules, and evidence needed for a buyer to say whether the system was delivered as promised.
