Custom e-reader ODM
Custom e-reader ODM from specification to shipment
One team owns the panel, the board, the firmware and the line, so a change to the screen does not wait on a second supplier to re-qualify the software.

- Screen formats
- 6–13.3 in
- Full ODM project
- 14–18 wks
- Units per model
- 500
- Quality system
- ISO 9001:2015
What an e-reader ODM project covers
In a full ODM engagement the product decisions, the electronics, the firmware and the build all sit with one team. You keep the brand, the market position and the commercial relationship with readers; we keep the schedule, the test plan and the paperwork that proves each unit was checked.
- Industrial design and mechanical structure
- Panel, front light and touch selection
- Mainboard, driver and power design
- Android or RTOS firmware and reading software
- Pilot build, tooling and volume production
- Certification files and retail packaging
The decisions that shape the device
Four choices drive most of the cost and most of the schedule: screen size, panel type, platform and enclosure. We walk through each one with samples and measured data before design freeze, so the specification you approve is the specification we build.
- Screen sizes from 6 to 13.3 inches
- Carta panels for text, Kaleido for colour covers
- Front light colour temperature and uniformity
- Capacitive touch or stylus with palm rejection
- Housing texture, buttons, mould and colour
- Boot logo, pre-installed apps and language packs
How the schedule is held
Work moves through five gates: scope review, quote, design freeze, pilot build and volume production. Each gate has a written output, and nothing starts the next stage until the previous one is signed off. A full ODM project typically runs 14 to 18 weeks from design freeze to shipped pilot.
- Samples from 10 to 15 working days after freeze
- New tooling in 25 to 35 days
- Pilot build in 4 to 6 weeks
- Production batch in 4 to 6 weeks after approval
- Volume from 500 units per model
- Repeat orders from 300 units on existing tooling
Testing before a batch leaves the building
Every unit boots, turns pages, charges and responds to touch before packing. Results are logged by station and tied to the batch, so a fault reported in the field can be traced to a build date and a fixture result instead of a guess.
- Incoming panel sampling for contrast and ghosting
- In-process fixture test before the case is closed
- End-of-line functional test on every unit
- 72-hour refresh loop on each batch sample
- Batch records released only after quality sign-off
- ISO 9001:2015 quality management system
How to compare ODM partners
Ask for the same five things from every supplier and the comparison becomes much easier: who owns the panel relationship, which parts of the firmware are theirs, what the pilot gate requires, how batch records are kept, and what happens when a defect appears after shipping.
- Panel allocation and second-source plan
- Firmware ownership and update path
- Written pilot acceptance criteria
- Traceability from unit to batch record
- Warranty and corrective action process
- Named engineer for each discipline
Related pages
E ink tablet manufacturer
Panel types, size classes and the production steps behind an e-paper tablet.
Read moreE-reader white label
Launch under your own brand on proven hardware with a shorter path to market.
Read moreOEM and ODM overview
Compare full ODM, build-to-print OEM and design-partner arrangements.
Read moreQuestions buyers usually ask
Can you build an e-reader from our industrial design?+
Yes. If you already have ID and mechanical drawings we review them for panel fit, tolerance stack and assembly access, then quote a build-to-print OEM run. If the design is still open, the same team can develop it as an ODM project.
Who owns the tooling and the design files?+
Ownership is agreed in the contract before work starts. Tooling paid by the customer is normally held for that customer and not used for other brands; design file ownership follows the same clause rather than an assumption.
Can the software keep our own app store and reading app?+
On Android builds you can keep your application layer, store and account system. We handle the panel driver, timing, front light and power management underneath. On RTOS builds we deliver a firmware image and agree the update path in advance.
What is the smallest order you will quote?+
Sample builds start at one unit. Pilot builds start at 50 units, and volume production typically starts at 500 units per model, dropping to 300 for repeat orders on an existing tooling set.
Start with the specification you have
Screen size, target market and volume are enough for a first feasibility reply.