Define a Customization Project with the Manufacturer
Unapproved changes can require price and timing to be reassessed. Define the configuration, artwork and interface version before approving an OEM scope.
Prepare an OEM briefWorkstream overview
On a small screen, scroll the table horizontally if needed.
| Workstream | Useful input | Acceptance item to agree |
|---|---|---|
| Cabinet branding | Artwork, placement and finish reference. | Approved visual proof and an agreed sample or inspection method. |
| Interface and voice | Language, screen list, terminology and audio requirements. | Review of normal, error and recovery flows in the requested language. |
| Payment integration | Provider, hardware, merchant setup and connectivity. | Test scope for payment, cycle start, interruption and refunds. |
| Electrical configuration | Site supply and destination requirements. | Matching technical sheet, identification and applicable test documentation. |
| Packaging and manuals | Shipping marks, accessory list and document language. | Packing list and versioned instructions matching the configuration. |
Scope and limits
Multilingual interface support is confirmed. Color, branding, electrical configuration, payment, packaging, software, minimum quantity, development charges and timing require order-specific review. Certification, integration, samples, NDA terms and support deliverables are not commitments until agreed in the project documentation.
Turn an OEM request into a defined equipment project
A usable customization brief identifies what changes, how the change will be checked and what the buyer receives. Separate appearance changes from electrical, payment and software work so the quotation can show their different dependencies.
Specify the deliverable for each requested change
For artwork, provide the editable source, reference colors, placement and required finish. For language work, include all screens and messages, not only the start screen. Error messages, payment failures and support instructions are part of the user experience. Takeaway: tie each requested change to a deliverable and an acceptance item.
Agree scope, sample review and change control
Identify one person on each side who can approve revisions. Keep an agreed version of the configuration, artwork and interface copy with the quotation. Decide which checks require a physical sample and which can be reviewed remotely.
Record requested changes after approval with their effect on price, production timing, documentation and spare parts. A change to a payment terminal or enclosure may affect other work even when the external appearance remains similar.
Minimum order quantity and development charges depend on the requested work. Ask whether a fee is one-time, per order, per machine or recurring. Do not assume that a logo-only order and a new payment integration have the same commercial terms. Takeaway: approve a dated version and reassess price and timing before authorizing later changes.
Include handover and ongoing support in the brief
Agree which manuals, configuration records, parts references and software access are supplied. Specify who maintains translations, payment settings and customer-support details after delivery. Ask how future replacement parts will be matched to the customized version.
If the project needs confidentiality or design ownership terms, discuss those before sending restricted material. The review starts with the operating need and proposed changes; final technical and commercial commitments belong in the order documentation. Takeaway: match manuals, parts references and support owners to the delivered version.
Prepare an OEM brief
Review the payment workflow · Compare quotation scope
Send the logo files, screen and language list, payment provider, power, packaging requirements and version owner to discuss the OEM configuration and quotation scope.
Prepare an OEM briefDiscuss your requirements
Contact us about an OEM customization brief.
We reply within 24 hours.
Prepare an OEM Brief
Share branding, interface, payment, power and packaging requirements on WhatsApp or by email.
We reply within 24 hours.
WhatsApp opens in a new window. You can share your model, quantity, destination, and technical requirements directly with the factory.
OEM FAQ
OEM scope, approvals and project responsibilities.
What is the minimum quantity?
Can local payment be integrated?
Does the factory sign an NDA?
What to send us
| Item | Why we need it | Example format |
|---|---|---|
| Brand assets | Define the visual scope | Logo file; color references |
| Screens and languages | Identify interface changes | Screen list; languages; audio list |
| Payment and power | Identify compatibility requirements | Provider; voltage; frequency |
| Packaging and approval owner | Define packaging and version approval | Packaging brief; revision; approver |
We reply within 24 hours.