TUODI OEM and ODM product development and production process
A factory development process becomes safer for the buyer when every stage has a written input, output and approval gate.
Short answer. Sample to prove the exact configuration. Pilot to prove launch operations and early demand. Replenish to prove that the winner can be repeated without unapproved changes. Scale only after quality, service, documentation and sell-through have evidence behind them.

Building a cabinet-light sample brief? Start with the Rechargeable PIR Cabinet Light (TDL-6110X) specifications, Detachable-Battery Sensor Light (TDL-6111) configuration and furniture integration checklist. Record the selected configuration before comparing quotations.

The four order gates

Sample

Does this exact product work in the intended application?

Pilot

Can the buyer launch, receive and support a limited first run?

Replenish

Can the accepted configuration be repeated predictably?

Scale

Is the programme ready for larger inventory and commitment?

Gate 1: sample the configuration, not only the catalogue model

A model number is not a complete specification. The sample record should identify the sensing variant, power format, dimensions, finish, light settings, accessories, labels, packaging assumptions and any firmware or component revision that matters.

Acceptance areaWhat the sample should answer
Sensing behaviourSensor type, trigger/presence distance and angle, hold time, daylight threshold, re-triggering, through-panel boundary, adjacent-unit interference and false activation in the real installation.
Light outputBrightness, colour temperature, diffusion, dimming behaviour and visible consistency between units.
Power and chargingCell chemistry, rated capacity, pack dimensions, protection, connector, charge indication, while-charging behaviour, realistic runtime method, low-battery behaviour and heat.
Electrical integrationInput/output voltage, dry-contact or relay logic, actual lamp/driver/contactor load, inrush/derating, wiring, override and state after power loss.
MountingFit, alignment, magnet or clip retention, adhesive surface and access after installation.
EnvironmentIndoor/outdoor boundary, operating temperature, humidity and any IP marking with the named test report—or an explicit note that no third-party ingress test is available.
Controls, data & firmwareButtons, remote, protocol/version, target hub, pairing count, app/API, event and timestamp requirements, offline buffer, firmware ownership/update path, linked-light behaviour and what happens after power or network loss.
PackagingProduct protection, accessory count, labels, barcode fields, instructions, destination-language requirements, unit box and master-carton quantity/dimensions/gross-net weights.
DocumentsWhich issued record names the exact model/build and cell, who holds it, which market or freight route it supports, its current validity and what is still only proposed.

If the project involves one wireless sensor controlling several bars, a hotel-room presence controller, a custom sound library or an altered battery pack, add the protocol/pairing count, I/O logic, audio-file map or cell/report map as a named configuration field. A supplier saying “supported” is not the same as that field being frozen.

Gate output: a dated sample approval record and a list of open items. The approved unit can become the golden sample only when both sides agree what it represents.

Gate 2: pilot the launch system

The pilot is not simply a smaller production order. It tests whether purchasing, packaging, receiving, installation and early support work together.

  • Limit the number of variables. A pilot containing many lengths, sensors, finishes and packs may be too small to produce a useful signal for any one variant.
  • Test the real carton. Include the intended accessory count, label fields, instructions and protective packaging—not a hand-carried engineering sample.
  • Record receiving data. Capture carton condition, unit count, visible defects, function checks and the time needed to inspect.
  • Track use by application. Returns from a wardrobe programme and a corridor retrofit do not mean the same thing.
  • Do not assume flexibility. Mixed models, neutral stock, later-applied packaging and small pilot quantities vary by product and order. Put each requested condition on the quotation.

Gate output: a launch report that separates product performance, packaging, logistics and user-fit issues.

Gate 3: prove replenishment before the stock runs out

A successful pilot can still fail on the repeat order if the accepted configuration is not controlled. Replenishment needs its own written checks:

Configuration

Repeat the approved reference

Quote the same model, variant, dimensions, finish, accessories, packaging and labelled revision. List any requested change separately.

Change control

Define what needs re-approval

Battery, sensor, LED, driver, connector, firmware, adhesive, housing or packaging changes may need a new sample or document review.

Documents

Documents still match the model

Confirm the issued document still maps to the exact model and destination. A proposed lab route is not an issued authorization.

Timing

Order from a dated lead time

Ask when the unchanged order can be repeated, what starts the clock and which materials or custom packaging sit on the critical path.

Gate output: a repeat-order specification with approved substitutions, re-sample triggers, a dated quotation and a confirmed shipping/document path.

Gate 4: scale when the pilot results agree

Scale is a commercial decision, not a quantity threshold. Larger commitments make sense when the pilot has enough evidence on sell-through, field performance, support burden and replenishment control.

  • The winning variants are clear enough to avoid spreading stock across weak options.
  • The acceptance plan catches the failure modes that matter in the intended application.
  • The replacement or service path is workable for the expected programme life.
  • The exact model-to-market documents and shipping requirements have been confirmed.
  • Forecasts, custom packaging or buffer stock have an agreed owner and trigger.

A concise RFQ brief for the first conversation

Product and use: application, installation, sensor behaviour and power format.

Commercial path: sample quantity, intended pilot, expected repeat order and target launch market.

Customisation: finish, logo, packaging, manual language, accessories and any function change.

Acceptance: the five tests that must pass before the pilot or production order is approved.

Commercial options for each order

Mixed models, neutral stock, delayed packaging, pilot quantities, buffer stock and repeat lead times vary by model and order. Ask which options are available for your selected configuration and record each agreed condition in the quotation.

Start with the sample gate. Send the intended application, destination, quantity path and required customisation. The team can help turn it into a configuration and acceptance list. Build the order path on WhatsApp →