“Can you send pricing for an e-paper display?” is a question a supplier can’t actually answer — not because they’re being difficult, but because e-paper pricing depends on enough variables that a real quote requires real specifics. The gap between a vague RFQ and a detailed one is usually the difference between a quote in a day and a quote in two weeks of back-and-forth.
This is the checklist we’d ask for internally before quoting a project — organized so you can pull the answers together once, rather than fielding follow-up questions one at a time.
Many quotation delays happen because buyers contact suppliers at the panel level while the actual project requires much more:
- display module selection
- TCON and waveform optimization
- firmware integration
- communication architecture
- enclosure design
- mass production support
An experienced e-paper OEM partner quotes the complete system — not just the panel.
What Actually Affects a Quote
Panel Specification
Size, technology (monochrome, color, or ChLCD), and whether it’s a standard catalog size or something requiring custom tooling all move price and lead time independently of each other. If you don’t have a final size yet, our display size guide covers what’s standard versus custom across the range; our color technology comparison covers the difference between E Ink’s color options if color is in scope— or browse monochrome, color, and ChLCD product lines directly.
The panel isn’t the whole spec, either — the TCON driving it affects refresh behavior, power draw, and what’s actually achievable for partial refresh or transition effects, and it’s worth specifying alongside the panel rather than assuming any TCON will do. Our TCON board explainer covers what this component actually does if you’re not sure what to ask for yet.
Deployment Environment
Indoor or outdoor, expected temperature range, and required IP rating all affect enclosure design and cost — and they’re often the difference between a standard configuration and one needing real engineering work. Our outdoor deployment guide covers how to work these out for a specific site if you haven’t already.
Power Source
Wired, battery, or solar — this affects enclosure design, BOM, and in some cases the panel/TCON pairing itself. If you’re not sure yet, say so and describe the site constraints (is wiring available? is this a retrofit?) rather than guessing at an answer.
Customization Scope
Be specific about which layer you actually need: cosmetic only (housing, branding), hardware configuration (size/connectivity/power options within an existing range), firmware behavior (CMS integration, refresh transitions), or TCON-level driving electronics. These carry very different cost and lead-time implications, and “we need it customized” without specifying the layer is one of the most common sources of quote delay. Full breakdown in our customization guide.
Connectivity Requirements
Wi-Fi, cellular (LTE-M/NB-IoT), LoRaWAN, or a local gateway architecture (Sub-1GHz/BLE Mesh/Zigbee) — or “open to a recommendation based on deployment density,” which is a perfectly reasonable answer if you’re not sure yet. Our connectivity architecture guide covers how this decision usually gets made.
Volume and Timeline
Quantity for the initial order, whether this is a pilot/prototype run or a production commitment, and your realistic timeline. MOQ, tooling amortization, and lead time all depend on where a project actually sits between “we want to test five units” and “we’re placing a 2,000-unit production order” — both are legitimate starting points, but they lead to different quotes.
Target Market(s)
Certification requirements — CE, FCC, RoHS, UL, CB Scheme, UN38.3 for battery-containing units, and the EU’s Cyber Resilience Act for connected products — depend entirely on where the product will actually be sold or deployed. This affects cost and timeline meaningfully enough that leaving it out of an RFQ is one of the more expensive omissions to correct later. Full breakdown in our certification guide.
Content and Software Integration
Will you integrate your own backend via SDK/API, or do you need a content management platform included? This affects both the quote and the project timeline, and it’s worth stating even if the answer is “we haven’t decided yet, tell us what’s typical” — our system architecture guide covers how this decision usually fits into the rest of the project.
RFQ Checklist
| Category | What to Provide | If You Don’t Know Yet |
|---|---|---|
| Panel | Size, color/monochrome/ChLCD, standard or custom | See our size guide |
| Environment | Indoor/outdoor, temperature range, IP rating | See our outdoor guide |
| Power | Wired, battery, or solar | Describe site constraints instead of guessing |
| Customization | Which layer — cosmetic, hardware, firmware, or TCON | See our customization guide |
| Connectivity | Radio/protocol, or deployment density if undecided | See our connectivity guide |
| Volume & timeline | Pilot quantity vs. production quantity, target dates | State both if unsure which stage you’re at |
| Target market(s) | Countries/regions of deployment | See our certification guide |
| Content/software | Own backend (SDK/API) or need a CMS included | State “undecided” rather than omitting it |
| Supplier capability | Confirm the supplier can support TCON/waveform tuning, firmware integration, and enclosure design — not just panel supply | See our supplier vetting guide |
Ready to Submit an RFQ?
You don’t need every answer above finalized to start the conversation — partial specifications are normal, especially around customization scope and connectivity, where “here’s what we’re trying to accomplish” is often more useful to us than a guess at the technical answer.
Send us your current specifications, application scenario, target market, and estimated volume. Even if some details are still undecided, our engineering team can help define the right panel, electronics, and system architecture before production — get in touch to start.
FAQ
Do I need to answer every item on this checklist before requesting a quote?
No — partial information is normal, and it’s better to flag what’s undecided than to guess. The goal is reducing back-and-forth, not requiring a fully finalized spec before the conversation starts.
How does volume affect the quote beyond simple per-unit pricing?
Volume affects MOQ thresholds, whether custom tooling costs get amortized or charged separately, and lead time — a pilot order and a production order aren’t just different quantities of the same quote, they’re often genuinely different pricing structures.
What’s the most common reason an RFQ takes longer than expected to quote?
Vague customization scope — “we need it customized” without specifying which layer (cosmetic, hardware, firmware, or TCON) usually triggers a clarifying round before pricing can even start.
Should I request a quote before or after deciding on certifications?
Before is fine — flag your target market(s) even if certification specifics aren’t finalized, since market alone is usually enough to scope the relevant certification requirements into an initial quote.