Sample Lead Time OEM: A Two-Week Configured Device Timeline That Holds
Why “7–15 Days” Is a Commitment, Not a Range
The 7–15 day window for configured samples is conditional on three sequential gates: artwork sign-off, firmware binary submission, and packaging proof approval — all required before the hardware revision is frozen. Stock samples ship in 3–5 days because no configuration decisions remain open. For OEM builds, the clock starts only when all three inputs are received and acknowledged. This is why we publish our MOQ, sampling and lead times policy with explicit dependencies, not averages. It removes ambiguity: if artwork arrives on Day 3, firmware on Day 6 and packaging on Day 8, the sample ships on Day 15 — not Day 22.The Golden Sample Is Not the Compliance Sample
A golden sample demonstrates fit, finish, firmware logic and branding alignment. It is not a compliance test article. Regulatory validation — CE RED, FCC, UKCA, RoHS 3, REACH SVHC screening — is booked separately per hardware revision with an accredited laboratory. That booking must happen before the PCB layout is finalised. Without it, the golden sample may pass visual and functional checks but cannot be declared compliant. You can verify the scope and status of any revision using our CE RED document checklist, which maps each standard to its test summary and report reference.Logo, Packaging and Firmware: Sequence Matters
Artwork drives everything. Logo placement affects antenna cutouts; packaging dimensions influence thermal dissipation in the final box; firmware version determines Bluetooth pairing behaviour and OTA update flow. We require logo files in vector format (AI or EPS), packaging dielines with bleed and fold lines, and firmware binaries signed with your private key — all before the sample build begins. Skipping this sequence triggers rework: a misaligned logo means new injection-moulded housings; unapproved packaging leads to repacking costs; unsigned firmware forces a second flash cycle. Our OEM/ODM services page details exactly which files trigger which gate.What the Sample Cost Covers — and What It Doesn’t
Sample cost covers component procurement, assembly, basic functional test and courier shipping EXW Shenzhen. It does not cover lab testing, custom tooling, laser engraving setup, or battery UN38.3 revalidation for modified cell configurations. All sample costs are credited against the first production order — but only if the order meets the published MOQ for that configuration type. For example, a white-label app build requires MOQ 2,000; the sample credit applies only when that threshold is met. Full terms are in our MOQ, sampling and lead times resource.Where to Say No to a Supplier Claim
Do not accept a supplier’s claim that “the golden sample is certified”. Certification is not embedded in hardware — it is a documented test outcome tied to a specific hardware revision, firmware version and antenna configuration. If a supplier states that a golden sample “meets CE RED”, ask for the test report number, lab name and revision ID. WingPhoenix does not issue such statements. Instead, we book CE RED (EN 300 328, EN 301 489, EN 62368-1), FCC Part 15 B/C and UKCA scopes per revision — and supply the reports only after testing completes. You can review our approach to documentation and traceability in how we build and test.How to Vet Your Next Supplier — and Why It Starts Before Sampling
Supplier vetting is not a post-sample audit — it begins at the quotation stage, where you assess responsiveness to technical queries, clarity on revision control, and willingness to disclose lab booking evidence. Our how to vet a supplier guide outlines six non-negotiable checkpoints, including firmware signing authority, antenna performance reporting and UN38.3 traceability. Equally important is understanding whether your engagement is OEM or ODM — a distinction that defines who owns firmware IP, who controls firmware updates and who bears liability for regulatory gaps. See OEM versus ODM for the contractual boundaries that shape your sample timeline and compliance risk.| Decision Point | Required Before Sample Build | Consequence of Late Submission |
|---|---|---|
| Logo artwork | Vector file, placement coordinates, colour PMS references | New housing mould inserts; +5 days |
| Packaging dieline | PDF with bleed, fold lines, barcode zone, regulatory label area | Repacking labour; +3 days |
| Firmware binary | Signed .bin, version number, OTA update path confirmed | Second flash cycle; +2 days |
| Certification scope booking | Lab booking confirmation with revision ID | No compliance report issued; delayed shipment |
| Battery UN38.3 & SDS | Test summary and SDS for exact cell model and watt-hour rating | Hold at customs; no air freight release |
| Toy age grading | Final age statement printed on packaging (e.g., “3+”) | EN 71-1/-2/-3 scope not booked; no EU market entry |
| Skin-contact nickel release | EN 1811 test summary for ring or wearable contact surface | Non-compliant shipment; recall risk in EU/UK |
WingPhoenix’s configured sample process is built for predictability — not speed at the expense of fidelity. To begin, share your specification using our send us the specification form. We will confirm the hardware revision, list required inputs and book certification scope within 48 hours. From there, your 7–15 day timeline is locked. You can explore full hardware options in our product catalogue, read deeper technical insights in the journal, or access compliance templates and checklists in buyer resources.
Questions buyers ask
How long does a configured OEM sample really take — and what makes it stretch beyond 15 days?
WingPhoenix quotes 7–15 days for configured samples. Delays occur only when artwork, firmware logic or packaging proofs arrive late, or when certification scope isn’t booked before the hardware revision is finalised.
Why does finance need to see the MOQ before approving a sample order?
Because sample cost is credited against mass production, and MOQs vary by configuration type — from 300 units for AI glasses to 2,000 for white-label app builds — so the credit value and commercial commitment are tied to the quoted MOQ tier.
Our last golden sample failed EMC testing — whose responsibility is that?
The importer holds responsibility for regulatory import duties, but WingPhoenix books CE RED (EN 300 328, EN 301 489, EN 62368-1), FCC Part 15 B/C and UKCA scopes per hardware revision with an accredited lab — provided the test request is submitted before the PCB layout freeze.
What’s the one claim most suppliers won’t substantiate about their golden sample?
That it represents full production compliance. WingPhoenix’s golden sample reflects mechanical, firmware and aesthetic build fidelity — but it does not include final EMC radiated emissions validation unless the lab booking is confirmed before the hardware revision is locked.
Related: more on sourcing & compliance · buyer guides · customisation tiers