Redemption Kiosk OEM Customization: 12-Point RFQ Checklist

Overview

If you have sent a redemption kiosk requirement to three suppliers and received three totals you cannot compare, the problem is usually upstream of the suppliers. One bid covers an enclosure with a screen cut-out. Another covers a note acceptor bolted to a PC. A third covers a full cash-in, ticket-out machine. None of them priced the same scope, so the lowest total is simply the least-scoped bid — not the best value.

The fix is not a better negotiation technique. It is a written configuration sheet, sent identically to every bidder, that forces each one to answer the same twelve questions in the same vocabulary. This page is that worksheet for redemption kiosk OEM customization : mounting, enclosure protection, note acceptance scope, storage versus recycle versus dispense, media capacity, dispense denominations, controller and OS ownership, firmware handover, spares, and commercial terms.

Three quote archetypes you will receive — and why their totals are meaningless side by side

• Enclosure-only quote. Sheet metal, powder coat, VESA or panel PC mounting, branding. No cash path, no ticket path, no firmware responsibility. Cheap, and it transfers every integration risk to you.
• Module bundle quote. A bill acceptor, a ticket printer and a controller listed as line items with no statement of how they interact, who validates a rejected note, what happens to stock levels, or who owns the firmware that binds them.
• Turnkey quote. A complete machine — but frequently scoped against the supplier’s standard build, with your actual denomination set, capacity requirement and site environment left as “to be confirmed.”

Comparing these three numbers tells you which supplier scoped least, not which machine fits your site. The cost of skipping the sheet shows up later: tooling revisions after the enclosure drawing is signed, module swaps mid-project when a dispenser turns out not to support your payout mix, and spare-part gaps in year two when the printer model in your fleet is no longer the one the factory stocks.

Items 1–3: Enclosure, footprint and mounting — where tooling cost hides

1. Mounting type and footprint. Floor-standing, wall-mount and tabletop are three different products with three different cost structures. Wall-mount shifts cost into site works (blocking, power and network drops, ADA-style reach and clearance considerations your facilities team must confirm). Tabletop shifts cost into anti-theft and cable management. Specify the type, the fixed external dimensions, the service-access clearance, and whether the unit must be serviced from the front only. “Standard cabinet” is not a specification.

2. Enclosure material, finish and branding zone. State the steel gauge you expect, whether high-touch surfaces need stainless steel, the finish and colour reference, and exactly which faces may carry a logo, silkscreen or wrap. Vague branding scope is how a supplier ends up quoting a decal when you expected a printed bezel.

3. Environment and ingress protection. An indoor mall concourse, a semi-outdoor vestibule and a gaming floor have different dust, moisture and vandalism exposure. Ask each supplier to state the enclosure’s protection level as published for that model, and confirm it against your actual site conditions with your own facilities or MEP advisor. Do not accept “indoor/outdoor” as an answer; ask for the stated rating and the conditions it was assessed under. If the supplier publishes no rating for the model, record that as a gap.

For a deeper treatment of enclosure-specific scope, see the custom enclosure checklist for unattended retail kiosks .

Items 4–6: The cash path — accept, validate, store, recycle, dispense

This is where most incomparable quotes originate. “Cash handling” is not a specification; it is a nickname that lets four very different machines be priced under one heading.

4. Acceptance scope. List every banknote denomination and currency the machine must accept, state whether coins are in scope, and define what the acceptor must do with a note it cannot validate — return it, escrow it, or retain it for operator review. Each behaviour has a different module and a different reconciliation consequence.

5. Storage and recycling behaviour. Choose explicitly between note storage only (accept and hold), note recycling (accept, validate, re-issue the same notes as payout), coin hoppers for coin payout, and a dedicated dispenser for notes loaded by staff. These are different modules with different service profiles, and a recycler is not a dispenser with a different label. Write the requirement as behaviour — “accept notes of denominations A–D for credit; dispense notes of denominations A and B as payout” — never as a module nickname.

6. Cash-out and reconciliation. State the denominations that must be dispensed, whether payout stock is operator-loaded or recycled from accepted notes, and what audit data the terminal must expose — transaction log, stock-level reporting, error and jam events, and how that data reaches your back office. If your finance team reconciles per shift, say so in the RFQ; the reporting surface is part of the scope, not an afterthought.

Items 7–8: Ticket and voucher output — capacity and denomination set

7. Media type and capacity. Paper ticket, thermal receipt, voucher or card dispensing — name the media, its thickness or stock reference, the loaded capacity you need between refills, and the refill interval your staffing model can support. Capacity numbers are only comparable when quoted against the same media and the same vend mix, so require each supplier to state both alongside the figure.

8. Payout denominations and vend rules. For redemption formats, define the denomination set the machine must issue and the rules that stop a low-stock state from blocking a valid redemption — for example, whether the terminal may substitute a smaller denomination combination, refuse the transaction, or queue it for an attendant. Also specify whether thermal print head replacement is treated as a scheduled wear item in your service plan; ask for the replacement procedure rather than a headline life figure that cannot be compared across suppliers.

Items 9–10: Compute, firmware ownership and remote management

9. Controller and OS responsibility. Write down who supplies the CPU, who supplies and licenses the OS, who owns the application layer, and — critically — who is accountable when an OS or driver update breaks the cash module. If your own software team owns the application, the supplier’s obligation is to keep the hardware abstraction stable and documented. Say that in the RFQ.

10. Firmware and integration surface. Demand a documented API or SDK, and written firmware ownership terms. Ask directly: can we hold and deploy firmware builds ourselves? Are remote monitoring, alerting and over-the-air updates included, licensed separately, or not offered? A supplier that cannot hand over interface documentation creates the same lock-in risk that pushes multi-site operators to demand non-proprietary designs in the first place — a theme worth reading alongside this comparison of OEM cash-handling platforms and proprietary bill-pay designs .

Field-upgradability belongs in this item, not in a footnote. If you expect to swap payment readers in three years, the enclosure, mounting bracket and firmware interface must be specified for that now.

Items 11–12: Spares strategy and commercial terms

11. Spares and serviceability. Name the wear items — print heads, belts, acceptor sensors, dispenser rollers, ticket path guides — and ask for a written spare-part availability statement, the minimum stocking recommendation, and whether each module is field-replaceable without returning the whole unit. Depot-by-depot consistency depends on this: an operator running a fleet across regions cannot afford a module that only the factory can service.

12. Commercial terms in writing. Ask for MOQ, sample terms, per-unit and tooling cost lines separated, lead time stated per named model, warranty scope and what voids it, and who pays freight and duties. Accept a MOQ or lead-time figure only when it is attached to a named model and marked as subject to final configuration. Any supplier that gives a range without a model reference has not answered the question.

Copy this configuration sheet

Send the identical table to every bidder, and instruct them to write “not offered” in any cell they cannot fill rather than leaving it blank. Blanks are where quotes become incomparable; a named gap is a negotiation lever, a silence is not.

What public multi-site deployments show about specifying up front

Vendor-published case studies are useful here as illustrations of what a good spec request looks like — not as proof of performance. Olea’s published OEM manufacturing case study ( olea.com ) describes two programmes worth reading as examples:

• Greyhound Lines , described in that case study as carrying 16 million passengers annually, asked for a non-proprietary kiosk design and footprint with modifications for cash storage capacity, heightened security and software compatibility. Each of those is a line item on the sheet above — a design constraint (item 10), a cash path decision (items 5–6), and a security requirement (item 3).
• The Habit Burger Grill specified printer omission, a named card reader, brand-aligned colour, and field-upgradable kiosks so future payment devices could be swapped. That last requirement is item 9 and item 11 of this worksheet, stated as a purchase condition rather than a preference.

These are vendor-published customer examples, not independent test results, and nothing on this page should be read as a performance guarantee or as Usingwin’s own deployment data. No independent test data is claimed for either programme or for any Usingwin model. The lesson is procedural: in both examples, the operator described behaviour and constraints, which is what made bids comparable and rollout consistent.

Where customization should stop

Customization inflates cost and schedule in predictable places: new tooling for a bespoke curvature, non-standard bezel openings around a module the factory has never integrated, and one-off module combinations that require fresh engineering validation. If your requirement can be met by reconfiguring a standard platform — different fascia, standard module bay, different branding — you are usually buying speed rather than novelty. Treat a supplier’s willingness to say “that needs new tooling” as a good sign, not an obstacle.

Redemption payouts, and any lottery-adjacent or gaming configuration, may be regulated in the jurisdiction where you deploy. Confirm the applicable local rules with your own counsel before the RFQ is issued; this page makes no legal determination and no compliance claim for any configuration.

Map the sheet to a starting platform

The twelve items collapse quickly onto published hardware families. A 32-inch wall-mount cash redemption configuration suits concourse and space-limited sites where floor area is at a premium; a floor-standing cash-dispensing platform suits retail and mall sites where payout is the primary transaction. Usingwin publishes a wall-mount self-service kiosk platform , a freestanding cash-handling self-service kiosk , a currency exchange kiosk and larger gaming cabinet platforms , each described on its own product page as OEM/ODM configurable in enclosure, hardware, peripherals and branding.

Two caveats you should hold us to. First, specifications that Usingwin publishes per model are in the model’s own documentation; anything not published there requires project confirmation in writing, and you should ask for that confirmation rather than infer it. Second, any MOQ or lead-time figure belongs to the individual model and remains subject to final configuration — never carry one model’s figure across a family, and never accept it verbally.

If cash-handling hardware will dominate your bill of materials over a multi-year fleet, the budgeting logic is worth reviewing separately in this analysis of hardware share in kiosk procurement and replacement budgeting .

Before you issue the RFQ

Fill the sheet, mark every cell you cannot answer as “buyer to confirm”, and send it unchanged to every bidder with a stated response deadline. When the quotes return, compare cell by cell, not total by total. The supplier that answers all twelve — including the ones that cost it margin — is the one whose number you can actually trust.

Send us your filled-in configuration sheet for a like-for-like quote and sample arrangement. We will return a response against your own line items, flag which specifications are published per model and which need project confirmation, and arrange a sample where the configuration allows it.