Decision summary
Choose a custom payment-terminal board when a documented standard configuration cannot meet the required display, peripherals, power, enclosure or software scope. Treat the result as approval of a recorded configuration, not every variant in a product family.
When is customization justified?
List the requirements a documented standard configuration cannot meet. Separate necessary interface, mechanical and software changes from preferences. Prototype the specific changes before making a production commitment.
What belongs in the requirement matrix?
Record the display, touch, scanner, printer, payment module, network, power, enclosure and application. Assign an owner, an evidence source and acceptance criteria to each requirement.
What should be agreed for the pilot?
Define the hardware revision, BSP build, samples, procedures, measurable results and failure handling. Keep an open-issue register; a demonstration is not approval of every operating condition.
What evidence should be requested?
- Current model specification, drawings and interface definitions.
- Board revision, software release and connected-equipment list.
- Test procedures, conditions, results and known limitations.
- Applicable model-specific compliance documents.
- Written deliverables, support, quotation and change-control terms.
No customer deployment, certification or test result is established by this guide. Review document availability, read the source policy, or send the project requirements.