What to Put in an RFQ for Custom microSD Cards (Buyer's Checklist)

By Cathy, Sales Engineer · Published 2026-11-16 · 13 min read

A practical RFQ checklist for custom microSD cards: capacity, speed class, controller and NAND, marking, packaging, testing, QC terms, and the clauses that stop silent substitutions.

microSD cards with an SD adapter and protective cases, the accessories an RFQ has to specify

TL;DR

A good RFQ for custom microSD cards is not a wish list — it is a specification plus a rulebook. It needs to answer four questions unambiguously: what physical card am I buying, what performance must it hit, how will we both verify it, and what happens if the supplier wants to change something mid-order.

If your RFQ only says “32GB microSD, class 10, custom logo,” you will get quotations you cannot compare and cards you cannot audit. The list below is the checklist to build your RFQ around. It is written for a purchasing manager or product engineer, not for a firmware team.

Two framing notes before the list:

  • Separate standards from supplier claims. Speed Class, UHS Speed Class, Video Speed Class and Application Performance Class are SD Association definitions (sdcard.org). “Up to 100 MB/s” on a datasheet is a marketing number, not a standard. Your RFQ should ask for the class you need and the test method you will use to confirm it.
  • Separate what you require from what WINTEL has confirmed. This article describes general procurement practice and what to ask any supplier. It does not attribute specific speed classes, endurance figures, temperature ranges, MOQs, lead times or certifications to WINTEL unless stated.

Why most microSD RFQs fail before the first quote

The failure mode is almost never price. It is ambiguity that only surfaces after the PO is signed. Three patterns recur:

  1. The RFQ specifies a class but not the test. Two suppliers both quote “U3.” One card sustains it in a 4K dashcam loop; the other drops frames at 20 minutes. You cannot tell from the quote.
  2. The RFQ names a capacity but not the controller/NAND pairing. Capacity is a result, not a specification. The same 64GB label can sit on different NAND grades and controllers with very different real-world behavior.
  3. The RFQ has no substitution rule. Six weeks later the controller is swapped for a cheaper one, the card still boots, and you find out from a customer return.

The checklist below closes each of these gaps. Use it as the skeleton of your RFQ document and as the agenda for your first supplier call.


The RFQ checklist

Work through these in order. Each item is something to write into the RFQ, not something to ask verbally and hope gets remembered.

1. State the use case and the host device

Open the RFQ with one sentence on what the card goes into: a phone shop’s retail stock, a dashcam line, an IoT logger, a set-top box, a promotional bundle. This single sentence changes which performance and endurance questions matter. A card for a 4K dashcam and a card for a photo-frame bundle are not the same product even at the same capacity.

Why it matters: it lets the supplier flag a mismatch before quoting, and it gives you a defensible reason to reject a substitution later (“this does not meet the stated use case”).

2. Specify capacity with the file-system and usable-capacity rule

Write the nominal capacity (e.g. 32GB, 64GB, 128GB), the file system you want pre-formatted (FAT32 vs exFAT — see Microsoft’s exFAT specification and Apple’s file-system documentation for cross-platform notes), and the minimum usable capacity you will accept after formatting.

Why it matters: capacity labels are nominal, and the formatted usable figure is always lower. If you do not state the floor you will accept, you have no basis to reject an under-performing batch. State the measurement method too (which tool, which host, formatted or raw).

3. Specify speed by class and by test method

Name the standard class you require — Speed Class, UHS Speed Class, Video Speed Class, or Application Performance Class (A1/A2), all defined by the SD Association — and then specify how you will verify it:

  • Sequential read/write test tool and block size
  • Random read/write (IOPS) test if you are using an A-class card for app hosting
  • Sustained-write duration (e.g. a continuous write for a defined period, not a 5-second burst)
  • Host device used for the check

Why it matters: a class is a minimum sustained definition, not a peak. Without a stated test, “meets U3” is unverifiable.

4. Specify interface and bus mode

State UHS-I or UHS-II (and the pin/contact expectation), and whether the card must work in a legacy (non-UHS) host. If the card ships with a reader or is part of a combo product, reference the relevant USB-IF specification for the interface side.

Why it matters: a UHS-II card in a UHS-I host falls back, and a buyer who expected the higher number will call it a defect. Put the fallback expectation in writing.

5. Name the controller and NAND — as an approved list, not a single part

This is the item most RFQs get wrong. Do not lock a single controller part number. Instead specify:

  • An approved controller family/list (two or three acceptable parts)
  • An approved NAND type and grade (e.g. TLC vs MLC, and the grade tier you will accept)
  • The pairing rule: which controller may be paired with which NAND
  • A requirement that the supplier disclose the actual pairing on the batch record

Why it matters: a single locked part can be discontinued mid-order, forcing either a delay or a silent swap. An approved list with a disclosure rule gives continuity and traceability. For background on why pairing matters, see flash brand and controller pairing and what the controller does with bad blocks.

6. Write the no-substitution and change-notification clause

This is the clause that protects the whole order. State plainly:

  • No controller, NAND, firmware or major component change without written approval before shipment.
  • Any proposed change triggers a re-qualification (sample + your test method) at the supplier’s cost.
  • The supplier must notify you in writing of any change, including a change forced by component shortage, with lead time to react.

Why it matters: shortages and end-of-life parts are real (see controller shortage and the semiconductor cycle). The clause does not prevent change — it prevents undisclosed change.

7. Define batch traceability and the record you will receive

Ask for a per-batch record that includes: controller part/family, NAND type and lot/die marking, firmware version, production date, line, and the test results for that batch. Reference JEDEC device standards (jedec.org) where part-number traceability is relevant.

Why it matters: traceability is what lets you isolate a bad batch from a good one and argue a claim with evidence. See flash memory lot traceability and die marking for what a usable record looks like.

8. Specify marking, printing and packaging

State exactly what goes on the card (logo, capacity, class, batch code, serial if variable data), the print method and colors, and the retail packaging. If you are doing custom printing, note the artwork format up front — see artwork formats we accept. If back-side printing is in scope, see printing a logo on the back of a microSD card.

Why it matters: marking and packaging are where “custom” usually lives, and where hidden charges and rework appear. Define them in the RFQ, not after the sample.

9. State the test and acceptance plan — the same one for sample and bulk

Write the acceptance test into the RFQ so the sample and the bulk order are judged by one rule:

  • Capacity check (formatted usable)
  • Sequential and random speed against the stated class
  • Sustained-write test
  • Re-format and re-mount cycles
  • Visual/marking inspection
  • Any host-specific test (e.g. record-and-playback in your dashcam)

Why it matters: a sample that passes a different test than the bulk order proves nothing. Use the sample acceptance checklist as a starting point and paste the criteria into the RFQ.

10. Define the QC and remedy terms

State your incoming inspection plan, the defect rate you will treat as a claim trigger, and the remedy (replacement, credit, or refund) and its timing. Be explicit about who pays return freight on a confirmed defect. For how to think about remedies, see credit, replacement or refund.

Why it matters: a defect clause without a remedy is decoration. Decide the remedy before you need it.

11. Put commercial terms and validity in the RFQ

Include quantity and any tiering, Incoterms, currency and the validity period you expect the quote to hold, payment schedule, and requested lead time. Ask the supplier to state quote validity explicitly — flash pricing moves, and a quote with no validity date is a number, not an offer. See currency clauses and where price moves and freight quote validity in peak season.

Why it matters: comparing two quotes with different validity windows is comparing two different things.

12. Ask for the compliance documents you actually need

List the documents you require (e.g. RoHS declaration, a certificate of conformance, a material declaration for packaging) and the destination market, so the supplier quotes the right paperwork. See what a certificate of conformance says. Do not assume a certification exists — ask for the document by name and check it.

Why it matters: missing paperwork at import is a cost and a delay, and it is avoidable if it is in the RFQ.


A purchase-order-ready clause set (prose, not a form)

When you convert the winning quote into a PO, these clauses should appear in the terms — written as sentences, not blank lines:

  1. Specification by reference. “The goods shall conform to RFQ [number] and the supplier’s quotation dated [date], including the approved controller/NAND list and the acceptance test in Section [x].” This makes the RFQ legally part of the order.

  2. No substitution without written approval. “No change to controller, NAND, firmware or major component is permitted without the buyer’s prior written approval. Any approved change requires re-qualification against the acceptance test at the supplier’s cost.”

  3. Batch traceability. “Each shipment shall include a batch record stating controller family, NAND type and lot, firmware version, production date and line, and the batch test results.”

  4. Acceptance and remedy. “The buyer may inspect on receipt against the acceptance test. Confirmed defects above [rate] entitle the buyer to replacement, credit or refund at the buyer’s election, with return freight borne by the supplier on confirmed defects.”

  5. Quote validity and price basis. “Prices hold for [period] from quotation date under the stated Incoterm and currency. Changes to either require written agreement.”

  6. Documentation. “The supplier shall provide [list of documents] with each shipment, valid for the destination market.”

Keep these as prose in the PO. They are meant to be read and enforced, not filled in.


How to compare two quotations line by line

Once quotes come back, do not compare the headline price. Compare these rows:

RFQ itemSupplier ASupplier BWhat a mismatch means
Capacity + file system + usable floorDifferent usable capacity = different product
Speed class + test methodA class without a test is unverifiable
Interface (UHS-I/II) + fallbackFallback behavior differs by card
Controller/NAND approved listA single locked part = continuity risk
No-substitution clauseMissing clause = silent swap risk
Batch traceability recordNo record = no claim evidence
Acceptance testDifferent test = sample proves nothing
Marking/packaging specHidden charges and rework live here
QC/remedy termsA defect clause without remedy is decoration
Quote validity + Incoterm + currencyDifferent validity = different offer

If a supplier leaves a row blank, that is your first follow-up question — not a reason to pick the cheaper quote. For a fuller walkthrough, see how to compare two microSD quotations line by line.


What to check on the sample and on the first batch

The RFQ is only as good as the check behind it. On the sample, run the acceptance test you wrote and record the numbers. On the first bulk batch, repeat the same test and compare. If the sample and the batch diverge on speed, capacity or sustained write, treat it as a substitution signal and pull the batch record.

For the sample stage specifically, see flash sample fee and what to test on one and can I get free samples. For timing expectations around a custom microSD order, see how long a custom microSD order takes.


Where WINTEL fits — and what to confirm directly

WINTEL (Shenzhen Wintel Digital Technology Limited) manufactures custom TF/microSD cards, USB flash drives, UDP modules and semi-finished boards for OEM/ODM buyers. Its confirmed profile includes a 5,000 m² factory, 200+ employees, 50+ export markets, and a stated monthly capacity of 500,000+ units (over 20,000 units a day). RoHS and SGS documents are cited as available on request.

This article does not attribute specific speed classes, endurance/TBW figures, temperature ranges, MOQs, lead times, test results or certifications to WINTEL. Those are exactly the items you should confirm in writing during the RFQ — which is the point of the checklist. Send the RFQ through request a quote and ask for the specific figures you need against each item above.

For product context, see TF/microSD cards and semi-finished boards. If you are weighing order size against per-piece price, see is a bigger order really cheaper per piece.


FAQ

How detailed does an RFQ for microSD cards need to be? Detailed enough that two suppliers quoting it would deliver the same physical card. At minimum: capacity, speed/application class, interface, controller family or approved list, NAND type and grade, marking, packaging, test method, and the substitution rule.

Should I name a specific controller or NAND brand? Name the performance you need and, where it matters, an approved controller/NAND list rather than a single part number. A single locked part can be discontinued mid-order; an approved list plus a written change-notification clause gives continuity without silent swaps.

What is the difference between “class” and real-world speed? Class ratings (Speed Class, UHS Speed Class, Video Speed Class, Application Performance Class) are minimum sustained-write definitions from the SD Association. Real-world speed depends on the host, file size and card state. Specify the class and the test method you will use to verify it.

Can I ask for a sample before a production order? Yes, and you should. Ask for samples from the same production line and controller/NAND pairing as the bulk order, and define what you will test. Put the acceptance criteria in the RFQ so the sample and bulk order are judged by the same rule.

What clause protects me if the supplier changes the chip later? A written no-substitution-without-approval clause, a change-notification requirement, a defined batch traceability record (controller and NAND lot), and a re-test trigger on any change — paired with incoming inspection on your side.


Sources

Illustrative only — not WINTEL data: any example capacity, speed, rate or period in this article is for explanation and does not describe WINTEL products.

Sources

Frequently asked questions

How detailed does an RFQ for microSD cards need to be?

Detailed enough that two suppliers quoting it would deliver the same physical card. At minimum specify capacity, speed/application class, interface (UHS-I/UHS-II), controller family or approved list, NAND type and grade, marking, packaging, test method, and the substitution rule. Vague RFQs produce quotes you cannot compare.

Should I name a specific controller or NAND brand in the RFQ?

Name the performance you need and, where it matters, an approved controller/NAND list rather than a single part number. A single locked part number can be discontinued mid-order; an approved list with a written change-notification clause gives you continuity without silent swaps.

What is the difference between "class" and "real-world speed" in an RFQ?

Class ratings (e.g. Speed Class, UHS Speed Class, Video Speed Class, Application Performance Class) are minimum sustained-write definitions set by the SD Association. Real-world speed depends on the host, file size, and card state. Specify the class you need and the test method you will use to verify it.

Can I ask for a sample before committing to a production order?

Yes, and you should. Ask for samples from the same production line and controller/NAND pairing as the bulk order, and define what you will test (capacity, sequential and random speed, sustained write, re-format, temperature behavior). Put the acceptance criteria in the RFQ so the sample and the bulk order are judged by the same rule.

What clause protects me if the supplier changes the chip later?

A written "no substitution without approval" clause plus a change-notification requirement, a defined batch traceability record (controller and NAND lot), and a re-test trigger on any change. Pair it with incoming inspection on your side so a swap is caught at receipt, not after your customers return cards.

← All guides

WhatsApp / WeChat Request a quote