Locking the Production File Before a Brazil-Bound CKD Batch

On May 17, 2026, BODO published a Brazil-focused export brief discussing CKD and SKD approaches for electric motorcycles and cargo tricycles in last-mile delivery. It raised local assembly, packing density, assembly support, wiring documentation, and spare-parts supply as buyer considerations.

That publication does not prove a freight saving, tax treatment, local-content status, homologation, certification, or approved Brazilian configuration. Its featured image shows a partially disassembled two-wheel vehicle, not a cargo tricycle, so it is not used here.

Consider a Brazilian first-time importer moving one locally tested cargo-tricycle sample toward a small commercial local-assembly batch. The useful task is to lock what was accepted, what may change, how components will be split and packed, and what evidence must arrive before shipment. Local customs, tax, labeling, assembly, and road requirements still need advice from qualified Brazilian parties.

Make the accepted sample the baseline

Open a production file with the sample's model reference, serial or batch identifiers where available, quotation version, receipt date, and intended use. Add dated photographs of every side, the operator area, cargo body, charging point, labels, and visible component references. Store the technical, battery, charger, controller, wiring, manual, packing, and parts files that actually accompanied that sample.

Record local observations without converting them into universal performance claims: route used, goods considered, charging access, assembly or service questions, interruptions, changes made, and the decision that accepted the sample for the next stage. A missing field should remain marked open.

The sample-order comparison pack can help keep these records together before a batch quantity is discussed.

Lock every approved delta

The batch file needs a controlled difference list between the accepted sample and production proposal. Include color and decals, labels and language, manuals, component references, charger and battery identity, accessories, spare parts, component split, packing marks, and any supplier-proposed substitution.

For each delta, record the previous state, proposed state, reason, evidence, effect on assembly or service, responsible reviewer, and approval date. Do not accept a general statement that production is equivalent. If a change affects an observed function or local requirement, decide whether a new document review, media check, or focused physical test is required.

The trial-order export steps provide a useful sequence for separating quotation, sample, document, packing, and shipment decisions.

Define the local assembly handoff

A CKD or SKD label alone does not tell the receiving team what work is required. The handoff should list every component group, quantity per vehicle, fastener and connector reference where needed, required tools, assembly order, wiring guidance, inspection checkpoints, and issue-escalation contact. Use diagrams and current configuration photos that match the locked batch.

Identify which steps the supplier completes, which the local team completes, and where a function check occurs. Include a discrepancy process for missing, damaged, mislabelled, or incompatible components. The process should tell the local team how to quarantine an affected set and report it without borrowing parts from another unit and losing traceability.

Training questions, parts identification, and document revisions should be closed before dispatch where possible. A remote support promise is useful only when the file identifies who responds, what evidence they need, and how revisions are controlled.

Require pre-shipment evidence

Before release, request evidence tied to the purchase order and packing plan:

• Current photos of the approved configuration before separation.
• Component counts and references for each packed vehicle set.
• Packing photos showing marks, set boundaries, and protected items.
• A packing list that reconciles vehicles, components, spares, and documents.
• Supplier-side function-check records for the applicable production stage.
• A dated exception list showing any unresolved difference from the locked file.

These records do not replace an inspection agreed by the buyer. They make the inspection and receiving check more precise. The ODM and SKD planning guide can help connect configuration control to assembly responsibilities and escalation.

Compare the assembled batch with the sample

On receipt, reconcile package marks and component counts before assembly. Give each local set an identifier and link assembly findings, photos, missing items, substitutions, and function observations back to that set. Do not erase deviations after they are corrected; close them with the action and evidence.

After assembly, compare the small batch with the accepted sample and locked production file. The decision should be to scale the accepted file, revise a named delta and retest it, hold affected units, or stop until a blocking discrepancy is resolved.

The May export brief can start a CKD/SKD conversation, but it cannot lock a production batch. That control comes from a traceable sample baseline, approved deltas, an assembly handoff, and shipment evidence that all describe the same cargo-tricycle configuration.