Template
OEM reader requirement template
Interface, firmware, enclosure, compliance, branding and volume planning template.
Summary
Use this template when a standard reader cannot fully match your device, enclosure, host protocol, brand or production plan. A clear OEM brief reduces sample cycles and avoids late-stage redesign.
Requirement fields
| Area | Questions to answer |
|---|---|
| Product role | Is the reader sold as your own product, embedded in equipment or used inside a project? |
| Interface | TCP/IP, serial, USB, TTL, Wiegand, GPIO, HTTP, MQTT, Modbus or private protocol? |
| Firmware | Trigger logic, filtering, memory operations, local buffer, heartbeat and upgrade method |
| Mechanical | Board size, housing, connector direction, mounting holes, heat and installation limits |
| Branding | Logo, label, packaging, manual, UI text and product naming rules |
| Compliance | Frequency region, certification, test report, quality documents and target market |
| Volume plan | Prototype quantity, pilot quantity, annual forecast and delivery schedule |
Sample stage
Agree on what the sample must prove: read range, multi-tag count, SDK demo, firmware behavior, enclosure fit, documentation and packaging.
Next step
Send the completed brief with drawings, interface notes and expected volume so LITTT can judge whether standard customization or a deeper ODM path is needed.