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.

How to compare flash storage supplier quotes with a consistent RFQ

Compare supplier quotes only after aligning product requirements, quantities, packaging, acceptance and delivery scope. Asking three suppliers for a "128GB card price" can produce three different configurations under one capacity label. A low unit price is not a comparable purchasing cost if it excludes a required accessory or does not meet the host's limits.

The first inquiry does not need every technical answer. Mark unknowns and ask for candidate options with assumptions; do not turn a preliminary estimate into an executable order. This guide provides a purchasing method, not customer transaction results or a claim of stock availability.

Image: AI-generated office and workshop illustration, not an actual factory photograph, order or supplier comparison record.

Separate mandatory requirements, options and unknowns

Mandatory requirements are limits that cannot be changed, such as a supported host interface or fixed installation space. Optional items, such as an SD adapter or individual packaging, should be quoted separately. An unknown, such as the host's required sustained write performance, must remain unresolved until supported by evidence.

Do not let an unanswered field silently select the cheapest configuration. Do not copy temperature or endurance ratings from an unrelated product to make a form look complete. Request a candidate, supporting conditions and the required validation instead.

Make each quotation line traceable

Comparison field	Required scope
Product	Type, interface, capacity and exact model or controlled configuration ID
Performance	Claimed class or metric and conditions
Quantity	Per-capacity quantities; samples separate from production
Accessories and packaging	Adapter, reader, physical label and individual packaging inclusions
Acceptance	Responsibility for documents, sampling and system validation
Delivery	Named destination, transport scope, estimated timing and prerequisites
Validity	Quote date, expiry and reconfirmation after expiry
Commercial basis	Currency, payment milestones and included charges
After-sales	Claim evidence, handling method and return-freight responsibility

If internal material details cannot be disclosed, agree a traceable configuration ID and change-notification boundary. An unchanged marketing name is not configuration control. The technical checklist below helps define that configuration before comparing final offers.

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, assess whether the documented change and validation policy fits the application. Do not assume a consumer accessory automatically tolerates every substitution. 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. On authorized samples without unique data, agree a full-address-space write-and-verify method and protect existing files before testing; see our H2testw/F3 procedure. This verification does not prove lifetime endurance or every aspect of system compatibility.

6. Add the commercial fields last

Preliminary commercial questions can be raised during the first inquiry. Final comparison requires the configuration and scope to be sufficiently defined; fields still dependent on validation must remain conditional.

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.

Compare executable cost, not only unit price

Separate sample fees, custom packaging, one-time tooling or setup, freight and other agreed charges. Confirm the selected trade term, named place, version where applicable and the actual scope of taxes and clearance with the parties responsible. A "door-to-door" description alone does not establish which destination costs or services are included.

Payment milestones, MOQ and the event that starts lead time also matter. If timing starts only after artwork approval, retain that dependency in the comparison rather than recording only a number of days. Apply a consistent currency and quantity basis; keep forecasts separate from committed orders.

Rank deviations before deciding

Resolve deviations affecting host compatibility, safety or acceptance before negotiable packaging and split-delivery options. A price advantage cannot cancel a mandatory failure, but a noncritical difference need not automatically disqualify a candidate.

Use three states: meets the requirement with evidence, needs validation, or does not meet it. Record verbal supplier confirmation separately from a report tied to the exact sample. Technical approval, commercial approval and production release remain different decisions; the qualification budget and test-plan guide explains their evidence requirements.

Before turning a quote into an order, reconfirm configuration, quantities, packaging revision, delivery conditions and acceptance ownership against the final offer. If the candidate changes during negotiation, reassess the approval scope. A past quote is not a promise of continuing stock or a substitute for technical approval.

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]
Hardware customization: [physical label, packaging and required device configuration; availability to be confirmed]

Send a short first inquiry to Kalstor

Provide the device or sales scenario, storage type, interface, capacity mix, expected quantity, critical performance and temperature limits, packaging and target timing. Mark unknowns "needs confirmation". Kalstor can help identify hardware candidates and open questions; available configuration, timing and commercial terms require confirmation. Submit the storage hardware RFQ.

Kalstor supplies hardware only. Software installation, image preparation or recovery, licensing, file preloading and application validation remain the customer's or its appointed provider's responsibility. Host software details in an RFQ are compatibility inputs, not a request for included software services.

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.