CN

A-50 / Technical Guide

When Does OEM Cleaning-Equipment Lead Time Start? Approval Gates from Specification Freeze to Production

This guide recommends defining OEM cleaning-equipment lead time from a named, time-stamped release event, not from the first inquiry, quotation or informal...

ELEREIN commercial cleaning equipment in a facility environment

Questions this guide answers

Primary question: When does the batch-production lead time begin for an OEM cleaning-equipment order?

  • What are the MOQ, sample cycle and approval steps for a private-label cleaning-equipment order?

Direct Answer

This guide recommends defining OEM cleaning-equipment lead time from a named, time-stamped release event, not from the first inquiry, quotation or informal deposit message. A workable contract can define the start as the point when all required technical, artwork, documentation, sample, commercial and payment gates are complete and the supplier issues written authorization to begin production. It should also define the end event, day-count convention, pause rules and exclusions, because a production-cycle baseline is not a shipping or delivery promise.

Start with the short decision guide

Use the order checklist for commercial approval and this guide to define the lead-time clock and pause events.

OEM/ODM Overseas Order Checklist

Scope and assumptions

This guide controls schedule evidence for private-label and OEM cleaning-equipment orders. It covers requirement freeze, sample approval, batch release, change control and production completion. It does not prescribe payment terms, transfer legal title, allocate delay damages or replace destination-market compliance advice.

The method assumes that buyer and supplier will attach an approval matrix to the quotation, purchase order or contract. Where the signed order differs from a public baseline, the signed order governs. Every date should include a time zone, and every duration should say whether it uses calendar days, working days or factory production days.

Separate the four clocks

The phrase "lead time" often compresses several different intervals. Keep them separate so that a delay can be assigned to the event that caused it.

Clock Starts when Ends when Must not be assumed to include
Sample preparation The quoted sample start conditions are complete The sample reaches the quoted completion or release state Freight, customs, receipt or buyer testing unless stated
Buyer sample evaluation The buyer receives the controlled sample and evidence pack The buyer signs approval, rejection or a conditional disposition Supplier production time
Batch production The contractual production-release event occurs The contractual production-completion event occurs Inspection release, loading, export clearance, transit or delivery unless stated
Logistics The agreed shipment-release event occurs The defined delivery milestone occurs Production or buyer approval time

A quotation that says only "15-day lead time" is incomplete. It should answer at least four questions: 15 of which kind of day, starting after which approvals, ending at which physical or documentary state, and extended by which documented events?

Define the controlled start event

Use one event name, such as Production Release T0. The event should occur only after the release package is complete and the supplier acknowledges it in writing. Receipt of a deposit alone should not be treated as T0 unless the contract explicitly makes payment the final outstanding gate and every other required approval is already closed.

The release package should identify:

  • Contract, purchase order and quotation revision
  • Legal buyer and seller entities
  • Exact base model, quantity and configuration revision
  • Destination market, voltage, plug, charger and labeling requirements where applicable
  • Approved logo, color reference, product label and serial-number format
  • Approved packaging artwork, marks, inserts and packing configuration
  • Approved manual language and governing file revision
  • Accessory and spare-parts combinations
  • Sample or golden-sample identity, approval status and approved deviations
  • Compliance-document review status for the final private-label configuration
  • Inspection plan, defect definitions and acceptance method
  • Payment or deposit condition stated in the contract
  • Named approvers and a time-stamped written production authorization

The EU's official CE guidance is a useful reason to keep product identity and configuration control separate from artwork approval. It states that manufacturers are responsible for conformity assessment, technical documentation and the declaration of conformity; EU guidance also notes that importers or distributors marketing products under their own names may assume manufacturer responsibilities. This does not establish that any ELEREIN model holds a particular certificate. It means the order should not release a private-label configuration until the responsible parties have reviewed the actual applicable documents and market obligations.

Use an approval-gate matrix

The matrix below is a reproducible control. Replace each generic owner with a named person or role in the order record.

Gate Minimum evidence Pass boundary Failure or hold condition
G1 Base product Model, configuration, quantity, destination and revision One unambiguous order identity Conflicting model names, missing options or unresolved destination requirements
G2 Engineering Approved configuration list and feasibility disposition Every requested change is accepted, rejected or excluded Unreviewed electrical, component or accessory change
G3 Brand assets Final logo, color, labels and serial format Approved files have revision and approver Email preview without source-file identity or legal-mark review
G4 Packaging Pack specification, marks, inserts and artwork Physical and document scope agree Dimensions, language, marks or protection remain open
G5 Manual Language, model scope, warnings and revision Final supplied configuration matches the document Generic or previous-model manual used as approval evidence
G6 Sample Sample ID, test record, deviations and disposition Signed approval or explicit written waiver Verbal approval, unidentified sample or unresolved failure
G7 Compliance Actual document scope and responsible-party review Market and configuration disposition is recorded Certificate name or logo without model, holder and scope evidence
G8 Commercial Price, quantity, payment, Incoterm or delivery term and change rules Contract conditions are satisfied Conflicting quotation and purchase-order revisions
G9 Quality release Inspection plan, defect criteria and controlled reference sample Factory and buyer use the same acceptance basis No controlled sample, no waiver and no measurable defect rules
G10 Authorization Signed production-release notice T0 timestamp and schedule baseline issued Production starts from chat messages or assumptions

Intertek's official inspection materials describe pre-production, during-production and final inspection as different controls and list order information, product data, golden-sample status and defect criteria among inspection inputs. That industry framework does not prove ELEREIN production performance; it supports the method of freezing inspection evidence before the batch clock begins.

Define when the production clock ends

Use one named end event, such as Production Complete T1, and write its evidence requirements. Common alternatives are not equivalent:

Possible end event Evidence required What remains afterward
Assembly complete Quantity and production record Testing, packing, inspection and release may remain
Production and packing complete Completed quantity and packing record Final inspection and shipment release may remain
Ready for buyer inspection Supplier release notice and inspection-ready lot Inspection, corrective action and reinspection may remain
Final inspection passed Signed inspection disposition Loading, export and transit remain
Handover to carrier Carrier receipt or shipping document Customs and delivery remain

The parties should select one state instead of using "finished" loosely. ELEREIN's confirmed 15-day baseline is a batch-production cycle after configuration and order details are confirmed. It should not be presented as a guarantee of final inspection, shipment, customs clearance or arrival unless those events are explicitly included in the order-level commitment.

Control pauses, stops and changes

A clock should not be paused retrospectively by an unexplained email. If the contract allows a pause, issue a numbered schedule event containing:

  • Event ID and order revision
  • Date, time and time zone
  • Gate or deliverable affected
  • Reason and supporting evidence
  • Responsible party
  • Work that can continue and work that must stop
  • Pause start and restart conditions
  • Schedule impact approved by both parties

Typical events requiring a documented schedule review include a buyer artwork revision, configuration change, manual-language change, new destination-market requirement, failed sample disposition, inspection nonconformity or a request to change quantity. These are examples of change-control triggers, not automatic ELEREIN contractual exclusions. The signed order must state which event pauses or resets the clock.

Use a new configuration revision when the change can affect the bill of materials, instructions, labels, compliance scope, packaging, spare parts or test basis. Do not overwrite the prior approval file. Mark it superseded and preserve the decision trail.

Reproduce the schedule calculation

First define the day unit. Then maintain an event log and calculate:

Controlled production duration = count of included day units from T0 to T1
                              - documented excluded intervals

Adjusted target = original target
                + approved pause units
                + approved change-order units

Do not mix working and calendar days in the same column. Record local factory closures, buyer-review periods and inspection windows as separate schedule layers rather than hiding them inside an unexplained contingency.

Illustrative change-control example

This example explains the arithmetic only; it is not an ELEREIN delivery result.

Assume an order-level schedule defines a 15-calendar-day production cycle beginning at T0 and ending when the packed lot is ready for final inspection. On the fourth day, the buyer requests a label revision. Both parties issue a hold at 15:00. The revised file is approved and the release restarts 2.0 calendar days later. If the contract says approved buyer changes extend the target by the documented pause, the adjusted target is the original target plus 2.0 calendar days. If the contract does not define that rule, the parties must agree the impact; the worksheet cannot create a contractual extension by itself.

Apply ELEREIN's confirmed commercial baselines carefully

ELEREIN's current baselines can support early planning, subject to the final engineering review, quotation and contract:

Field Confirmed baseline Required order-level condition
MOQ 10 units Confirm model mix, configuration, packaging and quotation scope
Sample cycle 7 days Define start event, completion event and whether freight or buyer testing is excluded
Sample workflow Selection, detail confirmation, contract signing, payment, shipment, receipt, sample confirmation receipt Assign dates and owners; do not assume the 7-day cycle covers every listed logistics and approval step
Batch production cycle 15 days after configuration and order details are confirmed Define T0, T1, day unit, pause rules, quantity and inspection state
Customization Logo, color, packaging, manual language, configuration and accessory combinations Subject to model-level engineering, document and contract review
Outside confirmed customization scope New mold opening Treat any broader engineering request as a separate feasibility project, not routine private label

The base-product identity should remain linked to the governing quotation. The E60 is a walk-behind floor scrubber, while the E100 and E130 are ride-on floor scrubbers. Those pages identify the starting model, but they do not freeze battery, charger, brush, electrical, accessory, packaging or private-label details.

Acceptance and failure boundaries

Release production only when all mandatory gates show approved or an authorized written waiver. A gate marked not applicable needs a reason and approver; it is not the same as a blank field.

Reject or hold the schedule baseline when:

  • The model, configuration, quantity or destination is ambiguous.
  • Artwork, labels, packaging or manual files have no revision identity.
  • Sample approval does not identify the physical sample and accepted deviations.
  • Compliance evidence is represented only by a logo, claim or unrelated model file.
  • The buyer and supplier use different inspection criteria or reference samples.
  • T0, T1, day-count convention or pause rules are missing.
  • A later change affects the approved configuration but no change record is issued.

Buyer evidence checklist

  • Signed quotation, purchase order and contract revision
  • Gate matrix with owner, status, date and evidence link
  • Exact model and configuration list
  • Approved artwork, labels, packaging and manual-language files
  • Sample ID, test report, deviation list and approval or waiver
  • Compliance-scope review for the destination and private-label identity
  • Inspection plan, golden-sample status and defect criteria
  • Payment-condition confirmation without exposing sensitive payment data in the operational pack
  • Written Production Release T0 notice
  • Schedule event and change-control log
  • Written Production Complete T1 notice and stated physical completion condition
  • Separate inspection, shipment and delivery records

Limitations

No workflow can turn a screening baseline into an unconditional promise. Order quantity, engineering review, materials, market documentation, buyer changes, inspection and logistics can affect the final schedule. This guide defines an evidence method; commercial remedies, pause entitlement and delay responsibility belong in the signed contract and applicable law.

Sources and evidence boundaries

These sources separate ELEREIN-published context from external regulatory, safety, inspection and maintenance guidance.

Supports
ELEREIN sets out order controls for approved specifications, samples, artwork, compliance files, inspection, packing and change approval.
Boundary
The checklist does not alter the signed order; contract language must define acceptance, delay, change and remedy obligations.
Supports
ELEREIN publishes its stated OEM/ODM, documentation, configuration and overseas service-support scope on this evidence page.
Boundary
This is first-party capability evidence; a purchase order, approved sample and project record must confirm the scope, timing and deliverables for a specific order.
Supports
The European Commission describes manufacturer responsibilities for conformity assessment, technical files, declarations and CE marking.
Boundary
The responsibility summary does not validate a technical file or establish conformity for any individual cleaning machine.
Supports
The European Commission identifies CE-related checks and responsibilities assigned to EU importers and distributors.
Boundary
The page does not discharge an operator duty or confirm that a supplier document, model or shipment meets those duties.
Supports
Intertek describes an online inspection workflow for booking, tracking and receiving inspection reporting across supply-chain orders.
Boundary
The workflow description is not proof that an inspection occurred, passed or covered the acceptance criteria in a specific order.
Supports
Karcher demonstrates a model-oriented download channel for manuals and product documentation used as a handover-record reference pattern.
Boundary
The presence of a competitor download portal neither supplies ELEREIN files nor proves that a buyer received the correct document revision.

How to use these sources: Use ELEREIN pages for first-party product and decision context. Use external sources only for the regulatory, safety, inspection or maintenance principle they actually cover; none of them certifies an untested ELEREIN configuration.