A B2B buyer who decides to launch a private-label RF remote program hits a single bottleneck: how fast can the factory take my concept to a sample I can hold? The honest answer for a true manufacturer is 15 days from kickoff to functional prototype, 30 days from approved prototype to mass production. The dishonest answer — from a trading company — is a quote followed by a 60-day escalation, then another 60-day round. This guide walks through what an actual 15-day prototyping sprint looks like inside a manufacturer’s engineering team.
Table of Contents
- 1. Why 15 days is the real number, not the optimistic number
- 2. The first 7 days: PCBA + firmware + schematic
- 3. The next 7 days: shell tooling + CE pre-scan
- 4. Days 15-30: pilot batch + functional test
- 5. Days 30-45: mass production ramp
- 6. Where private-label projects slip (and how to avoid)
- 7. What to ask for from the engineering team
- Frequently Asked Questions
1. Why 15 Days Is the Real Number
A factory’s claimed lead time and its actual delivery slip are often separated by 30-50%. The 15-day claim from a capable factory is, however, broadly accurate because the work is decomposed into parallel tracks that run simultaneously once the kickoff meeting ends:
- Track 1: PCBA layout (3-5 days) — schematic → BOM → PCB layout → Gerber
- Track 2: Firmware (5-7 days) — code structure → learning algorithm → rolling-code enrollment → EEPROM persistence
- Track 3: RF calibration (5-7 days) — band-specific antenna tuning → transmit-power measurement → modulation validation
- Track 4: Shell 3D print (3-5 days) — STL → SLA print → bench sample
- Track 5: CE-RED pre-scan (7-10 days) — wideband scan in accredited lab (parallel to firmware work)
Each track is independent. The critical-path bottleneck is firmware, which is why a factory with deep firmware experience can hold the 15-day line and a junior factory cannot.
2. The First 7 Days: PCBA + Firmware + Schematic
Day 1 is the kickoff. The buyer brings a reference design (or the factory’s pre-engineered platform). The factory’s engineering lead produces a project plan: who owns the PCBA, who owns the firmware, who owns RF calibration, who owns the shell.
Day 2-3 is the schematic capture. The factory’s hardware engineer produces the schematic for the buyer’s specification — frequency (315 / 433 / 868 MHz), code family (fixed / rolling), button count (2 / 4 / 6), battery type (CR2032 / AAA), and any custom requirement (e.g. unique FCC ID for a North American retailer). This step is fast because the factory has a reference platform to start from.
Day 3-5 is the PCB layout. A 4-layer board with SMT passive + IC layout for an aftermarket RF remote typically takes two days to draft and one day to review internally. The board goes to the factory’s in-house SMT line for a fast-turn prototype batch — typically 5-10 boards, enough for engineering validation and CE pre-scan.
3. The Next 7 Days: Shell Tooling + CE Pre-Scan
Day 8-10 is the shell 3D print. If the buyer wants a custom shell, the factory’s industrial designer produces a SolidWorks model from sketches or photos. An SLA 3D print delivers 1-5 shell prototypes in two days. If the buyer is willing to take a stock shell with a custom silk-screen, this step is skipped.
Day 8-12 is the CE-RED pre-scan in parallel. The factory’s compliance engineer sends the prototype to an accredited lab (in-house or local to Shenzhen) for wideband scan against EN 300 220 limits. Most aftermarket 433 MHz / 868 MHz remotes pass pre-scan on the first try because the platform PCBA already holds the certification for similar products.
Day 12-14 is the firmware bench test. The factory’s firmware engineer validates the learning algorithm against the target receiver, validates the rolling-code enrollment procedure, validates the EEPROM persistence across 100,000 button presses, and validates the battery life over 12 months of standby.
4. Days 15-30: Pilot Batch + Functional Test
Day 15 is the prototype delivery to the buyer. Two to five functional units, full documentation pack, FCC ID label affixed, CE-RED DoC draft, RCM registration initiated in the ACMA register.
Days 16-25 is the buyer’s validation window. The buyer tests the prototype against the reference receiver fleet, validates the user-facing ergonomics, signs off on the silk-screen and packaging, and approves the production tooling.
Days 25-30 is the pilot batch. The factory runs a 50-100 piece pilot through the production line — SMT, AOI, conformal coating, functional test, drop test, aging test — and delivers the pilot batch to the buyer for field test. Field failures, if any, feed back into a design revision before mass production starts.
5. Days 30-45: Mass Production Ramp
With pilot batch approved, the factory transitions to mass production. The production ramp is decomposed into:
- Days 30-35: SMT line ramp to full speed, daily output target reached by day 32-33
- Days 35-40: Assembly + functional test + drop test, batch-level AQL 5% sampling
- Days 40-45: Final QC, packaging, serial number binding, warehouse inbound
For a 1,000-piece first production run, the lead time is typically 35-40 days from prototype approval — which means the buyer’s total program timeline from kickoff to first commercial shipment is 50-55 days. For a 5,000-piece production run, 45-50 days. For a 50,000-piece annual program with multiple POs per year, the timeline compresses because the second PO runs against a calibrated line.
6. Where Private-Label Projects Slip
The top 5 slip causes in private-label RF remote projects, in order of frequency:
- Frequency band conflict discovered late. The buyer specified 433 MHz, but the target market is actually 868 MHz primary — caught at the field test stage, not the schematic stage. Avoid by writing a target-market frequency table into the kickoff document, not just “433 MHz”.
- Custom shell tooling push-out. An SLA print is fast; an injection-molded production tool is 30-45 days, and the buyer wants a tool. Resolve at kickoff: stock shell with logo, or custom tool with explicit 45-day ETA.
- FCC label artwork. The buyer sends the artwork on day 14 of the 15-day sprint. Verify it at kickoff.
- Compliance documentation back-and-forth. The lab rejects a test report for missing one signature. Avoid by using a lab the factory has used at least three times before.
- Packaging revisions. The buyer wants the retail box redesigned after the pilot batch. Plan two packaging rounds: alpha (in the pilot batch) and beta (in the production batch).
7. What to Ask for From the Engineering Team
The 6-minute engineering readout is the difference between a 15-day factory and a 60-day factory. Ask for these from day 1:
- The reference platform PCBA model. Most aftermarket RF remote factories use one of 4-5 reference platforms. Knowing which one your project lands on tells you the firmware maturity.
- The compliance lab partner. A factory that has shipped four-cert product for 5+ years has a standing relationship with one or two accredited labs. A trading company does not.
- The firmware engineer’s named responsibilities. “Our firmware lead is [name]; they own the rolling-code algorithm” is a strong signal. “Our engineering team will handle it” is a weak signal.
- The pilot batch history. Ask for the 3 most recent pilot batch results. The factory should be able to name the SKU, the date, the field failure rate, and the revision number.
- The AQL sample size formula. A factory that has QC engineers thinks in AQL. A factory that thinks in “we inspect every unit” has either no QC or no statistical literacy.
- The export licence coverage. Some RF equipment (especially 868 MHz in the EU) requires a one-time export license. Verify the factory has this on file before the kickoff, not after the first shipment.
Frequently Asked Questions
Q: Can the 15-day line hold for a 100% custom PCBA, not a reference platform?
No — and any factory that claims it is lying. A 100% custom PCBA adds 30-45 days at the schematic stage plus 30-45 days at the tooling stage. The realistic lead time for a 100% custom PCBA from a true RF remote factory is 90-120 days from kickoff to first commercial shipment. The 15-day line holds only when the project lands on a reference platform with minor customization.
Q: What is the cost difference between a stock PCBA and a 100% custom PCBA?
Stock PCBA: 1x unit cost. 100% custom PCBA: 3-5x unit cost at MOQ 1,000 because the tooling cost amortises over fewer units, and the engineering time is dominant at low volumes. The crossover happens around MOQ 5,000 — above that, custom tooling is competitive with stock. Below it, stock is the economical answer.
Q: Can the 30-day mass production line hold for 50,000 pieces?
For a stock PCBA on a calibrated line, yes. For a 100% custom PCBA, expect 60-90 days for 50,000 pieces because the SMT line has to be re-calibrated to the new board. The factory’s bench-throughput test (units per hour) drops 20-40% during the first day or two on a new board, recovering to the calibrated rate by day 3-4.
Q: How does the factory handle field failures during the first 90 days?
A reputable factory offers a 1-3% replacement allowance (the buyer keeps this in stock and writes it off against the field failure rate), plus a 90-day root-cause investigation for any field failure above 0.5%. Anything beyond 1% field failure triggers a joint engineering review. Trading companies defer this to “talk to the factory” — that is the moment the factory-versus-trading line becomes operationally meaningful.
Where the 15-Day Sprint Begins
For B2B importers and wholesale distributors planning a private-label aftermarket RF remote program, the 15-day functional prototype sprint is the producer-side commitment to make the buyer’s roadmap real. The factory that can deliver this sprint on a reference PCBA, with a transparent engineering team, four-cert compliance, and a 1,000-piece MOQ, has the profile of a long-term supplier. For importers comparing shortlist, ask the factory for a written project plan with named engineer accountability — the answer tells you everything.
Leave a Reply