What information should I give a flash storage supplier first?

Give the host device and interface, operating system or controller, workload, daily writes, required life, temperature, power-loss conditions, capacity, performance floor, annual volume and project timing. A model number or host sample is better than saying only “industrial 128 GB.”

Should an RFQ require a specific NAND type?

Only when the application or qualification requires it. State the endurance, retention, latency and lifecycle outcome you need, then ask the supplier to disclose and control the proposed NAND configuration. “TLC” alone does not define the controller, firmware, over-provisioning or actual drive endurance.

How do I make sure mass production matches the sample?

Record the approved part number, BOM or controlled items, firmware revision and sample lot. Require written notification before NAND, controller, firmware or other critical items change, plus a new revision, requalification sample and agreed notice period.

Flash storage RFQ template: 15 questions to ask before requesting a price

“Please quote 128 GB microSD” is not a complete RFQ. It invites suppliers to quote different products under one capacity label: different NAND, controller, firmware, write life, temperature range and test coverage. The cheapest line may be cheap only because it solves an easier problem.

A useful flash-storage RFQ first defines what the host will do to the device and what failure costs. Price comes after a supplier identifies a configuration that meets that job.

1. Identify the host, not just the form factor

Tell the supplier the exact host or as much of it as you can disclose:

device type and model;
interface: SD, microSD, USB, SATA, PCIe/NVMe, eMMC or raw NAND;
host controller or chipset;
operating system and filesystem;
boot, application, logging, video or general data role;
whether you can provide a host unit or validation board.

Compatibility problems often appear below the connector: initialization timing, power-up current, device identifiers, command support or firmware behavior. A physical fit is not a qualification.

For SD products, specify the capacity family and host support. SD Association defines SDHC as above 2 GB through 32 GB with FAT32, and SDXC as above 32 GB through 2 TB with exFAT [1]. Do not assume a host that accepts one family accepts every capacity.

2. Describe the workload in numbers

“Heavy use” is not measurable. Provide:

average and peak data rate;
read/write ratio;
sequential versus random access;
transfer sizes, if known;
daily host writes in GB;
expected service life and duty cycle;
percentage of the device normally filled;
number and frequency of power cycles.

For a recorder, include bitrate, channels, resolution and hours per day. For an OS or database, include random-write intensity, queue depth where available and whether the drive is a boot, cache, log or data device.

Endurance depends on workload. Micron explains TBW as total terabytes written and DWPD as the portion of drive capacity written each day over a stated period [3]. Ask which workload and warranty period sit behind the number; do not compare two TBW figures without their conditions.

3. State the acceptance floor

Ask for minimum or guaranteed values, not only “up to” peaks:

Requirement	What to specify
Capacity	Labeled and minimum usable capacity after the agreed format
Sequential performance	Minimum sustained read/write over test duration and fill state
Random performance	Required IOPS/latency, block size, queue depth and read/write mix
Video recording	Required U/V/E class and host mode
Endurance	TBW, DWPD, rated hours or workload-specific life
Retention	Required time, temperature, power state and end-of-life condition
Operating range	Minimum/maximum operating temperature for the finished product
Power loss	Data-at-rest/in-flight expectation and recovery behavior

Speed Class marks provide defined minimum writing classes for SD recording products [2]. They are more useful than an isolated maximum read number, but the host and workload still need to match the class.

4. Define configuration control

Ask the supplier to disclose the proposed:

NAND manufacturer, family and type;
controller;
firmware revision;
over-provisioning or usable-capacity policy;
components covered by a fixed or controlled BOM.

Then ask what happens when one must change. A proper answer includes a Product Change Notification, identifiable new revision or part number, advance notice, requalification samples and a last-time-buy path. Delkin describes controlled configuration and managed lifecycle as central to maintaining host compatibility and consistent OEM behavior [4].

If the supplier reserves the right to use “equivalent NAND” under the same part number, decide whether your application can accept that. Consumer accessories often can. A qualified embedded product often cannot. Read our fixed-BOM guide before deciding.

5. Agree on test and traceability

Specify which evidence arrives with the sample and production lot:

full-capacity write/read verification method;
sustained-performance test conditions;
burn-in, temperature or power-cycle test, where required;
firmware and device-identification report;
lot code and production date traceability;
certificate of conformance or inspection report;
RoHS/REACH and other applicable declarations;
golden sample and acceptance limits;
RMA analysis process and response time.

A quick operating-system capacity check does not catch a controller programmed to report more NAND than exists. For cards and USB drives, include a full-address-space write-and-verify test; see our H2testw/F3 procedure.

6. Add the commercial fields last

Once the technical configuration is clear, request:

sample quantity, cost and timing;
MOQ by capacity/configuration;
pilot and mass-production lead time;
monthly capacity or allocation method;
quote currency and validity period;
Incoterm and shipping point;
payment terms;
packaging, label, serial/lot code and OEM artwork;
warranty term and RMA responsibility;
forecast, blanket-order and rescheduling rules.

If flash cost is moving, a long quote validity may be impossible. Ask how and when cost is locked rather than treating an expired price as a supply commitment.

Copy-and-send RFQ template

Project / host: [device, model, controller, OS]
Storage type / interface: [microSD / SD / USB / SATA / NVMe / eMMC]
Use case: [boot / video / logging / database / removable data]
Capacity: [required capacities and minimum usable capacity]
Workload: [read/write mix, sequential/random, block size, GB written per day, duty cycle]
Performance floor: [sustained MB/s, IOPS/latency conditions, required speed class]
Life requirement: [years, TBW/DWPD/rated hours, retention condition]
Environment: [operating/storage temperature, vibration, humidity if applicable]
Power behavior: [unexpected power-loss scenario and recovery requirement]
Configuration control: Please state NAND, controller, firmware and controlled-BOM/PCN policy.
Testing / documents: [full-capacity test, inspection report, traceability, compliance]
Sample acceptance: [quantity, test plan, golden sample and pass/fail limits]
Volume: [pilot quantity, annual forecast and monthly schedule]
Commercial: [MOQ, lead time, quote validity, Incoterm, payment, warranty]
Customization: [label, packaging, VID/PID, firmware or other OEM requirement]

Bottom line

The best RFQ does not ask a supplier to guess the product behind a capacity. It defines the host, workload, failure risk and measurable acceptance floor; then it locks the approved configuration to production. With those facts in place, price comparisons become real comparisons instead of four different flash devices sharing one “128 GB” line.