A useful display RFQ explains the product, the integration boundary and the requirements that must be verified. “Custom screen, three inches, best price” leaves the supplier guessing about the host interface, mechanical fit and supplied parts. A short, structured requirements package helps both teams identify a suitable standard module, a feasible adaptation or a requirement that needs further investigation.
Not every field must be final at the first inquiry. Mark unknowns explicitly and distinguish mandatory requirements from preferences. This is more useful than presenting an assumed interface or bend radius as an approved specification.
1. Describe the application and project stage
State the device type, intended user interaction and environment. Explain whether the display is used continuously, intermittently or mainly for status feedback. Include representative screen layouts and identify persistent icons, animations, expected update rate and viewing distance.
Specify whether you are evaluating a concept, building prototypes, replacing an existing module or preparing a production design. An engineering sample request and a production quotation need different levels of documentation.
BINTU’s smart-speaker application examples show display integration concepts. A request for such a module should describe your own host and enclosure; it is not a request for a finished BINTU speaker.
2. Define what “custom” means
Separate three possible scopes:
- Select an existing module: evaluate published references against the product requirements.
- Adapt the integration: review FPC routing, connector arrangements, cover, touch or mechanical parts where the chosen platform permits changes.
- Evaluate a new display platform: requirements outside an existing panel’s capabilities need a separate feasibility discussion.
Suppliers such as Newhaven and US Micro Products describe customization by subsystem. This is a useful way to structure an RFQ; it does not mean that every modification is available on every BINTU module.
3. Provide separate optical and mechanical requirements
Include the preferred diagonal, resolution, active image area, viewing-window requirements and available assembly envelope. Attach a drawing when available, with units, datums and tolerances. Keep module outline and cover lens outline distinct.
For a curved concept, provide the proposed shape, support method and intended use. State whether the display remains in a fixed position or is expected to bend repeatedly. Do not assume an allowable radius from a photograph or the word “flexible.”
Identify cable exit direction, available connector space, assembly access and any frame or adhesive responsibilities. A cover drawing alone cannot define the module integration. See flexible AMOLED integration for the project discussion path.
4. Identify the host, display bus and touch requirements
Provide the processor or host platform, operating system, available display interfaces, power rails and any existing driver constraints. Where a module has already been selected, request its electrical and initialization documentation before fixing the PCB.
Record touch requirements separately: active touch region, cover arrangement, intended interaction and environmental constraints. Specify display and touch buses independently. MIPI DSI, for example, identifies a display interface; it does not establish the touch controller or a module’s SPI capability.
For BINTU-P-0002, use the public 3.26-inch, 382 × 720 specification as the starting reference and request the project details needed for integration. Do not infer a complete saleable touch configuration from the module’s public description.
If this reference is relevant, request P-0002 integration information with the model already identified in the inquiry link.
5. Agree how the sample will be evaluated
List the measurements and observations needed before design approval. Typical topics include readability with the intended UI, host communication, startup and sleep behavior, touch response where applicable, mechanical fit and operation under the planned environmental conditions.
Define the sample configuration and revision. Record who supplies the host board, firmware, cover parts and test fixtures. A successful bench image test does not by itself qualify a bonded assembly or establish a production lifetime.
For cover and touch integration, identify which team approves the optical stack and assembly criteria. If a requirement involves certification, provide the applicable requirement and ask what evidence is available; do not assume a medical or automotive qualification.
6. Separate commercial assumptions from commitments
Provide an estimated sample quantity, expected order pattern, forecast range and target schedule. Label forecasts as estimates. Ask the supplier to distinguish recurring unit cost, engineering work, tooling, sample costs and any minimum-order conditions in the quotation.
Stock, MOQ, lead time and NRE must be confirmed for the actual configuration. A catalog listing is not a commitment that a customized assembly can ship immediately. Discuss revision control, change notification and replacement planning before a long-lived product reaches production.
Copyable OEM display RFQ checklist
| Requirement | Your input |
|---|---|
| Application and project stage | Device type; concept / prototype / redesign / production planning |
| Display reference | Existing model if known; preferred technology; alternatives allowed |
| Image requirements | Diagonal, resolution, active area, UI examples, update behavior |
| Mechanical boundary | Module envelope, cover outline, mounting, cable route, drawing revision |
| Host electronics | Processor, OS, display interface, power rails, connector constraints |
| Touch and cover | Included / optional / customer-supplied; interaction and cover requirements |
| Usage environment | Duty cycle, lighting, temperature and other required conditions |
| Validation | Sample configuration, tests, acceptance criteria and responsibilities |
| Commercial planning | Sample quantity, forecast range, target dates, quote assumptions |
| Open items | Questions requiring supplier confirmation before design release |
Leave unconfirmed values as “to be confirmed.” Do not reuse a specification from a similar-looking module without verification.
Frequently asked questions
Can I inquire before every technical parameter is known?
Yes. Start with your application, approximate display size, project stage and the information you already have. Mark the remaining requirements as open questions. A complete specification is not required for an initial discussion.
Are active area, module outline and cover lens outline interchangeable?
No. Active area describes the image-producing region. Module outline describes the supplied module envelope. The cover lens is a separate component with its own outline and tolerances. Review all three against the enclosure.
What should I provide about the interface or controller?
Identify the host processor, operating system, available display bus and any driver or power constraints you know. If the controller is not selected, say so. The display interface and touch-controller interface must be confirmed separately for the proposed configuration.
Do estimated quantities commit me to an order?
An early forecast is a planning input. State sample needs and an estimated order-volume range; pricing, MOQ and delivery are confirmed separately in a project quotation.
Does a custom module quotation include the cover and touch assembly?
Only when these components and their validation scope are explicitly included. Identify required cover glass, touch interaction, mounting and bonding responsibilities so the quotation can distinguish included, optional and customer-supplied parts.
Send a qualified inquiry to BINTU
Start with the AMOLED catalog if a standard reference may fit. For a broader project, use custom OLED engineering to frame the required integration work.
Start an OEM display inquiry with a short requirements summary and the model reference, if selected. Ask BINTU to separate confirmed module facts, project-dependent options and items requiring validation. Confirm the appropriate channel before sharing confidential drawings.
