The DODA (Documento de Operación para Despacho Aduanero) is the document used to present an operation physically at customs to trigger the automated selection mechanism. It integrates into one number (the integration number, with its QR code) the pedimentos, vehicle data, seals when applicable, and the customs section where it will be presented.
- integration
- QR
- min cross-check
- 10
- DODA=CP=real
- Plates
- the module
- Before
If DODA data does not match module reality, the operation stops at the most expensive point.
Cluster: pedimento · Carta Porte · release.
What the DODA integrates
Integration number, pedimentos, vehicle, seals, and section: each is cross-checked against an operational source.
What the DODA integrates
One integration number (QR) ties pedimentos, vehicle, seals, and section.
| Element | What it is | Cross-check against |
|---|---|---|
| Integration # | Unique folio + QR | Your correct operation |
| Pedimentos | Covered declarations | All shipment pedimentos |
| Vehicle | Unit data | Real plates + Carta Porte |
| Seals | Fiscal seals | Physical seal + photo |
| Section | Presentation customs | Route and instructions |
Ten-minute cross-check
Five checks before presenting. The natural moment is unit release.
Ten-minute cross-check before presenting
The pre-check takes minutes; the module error costs hours.
Select a step to see detail
Step detail · 01
Integration
Correct DODA
Whose review it is
Broker generates, carrier carries, you absorb the stopped operation. That is why the cross-check is yours.
Whose review it is
The broker generates; the carrier carries; the stopped operation is yours.
01
Broker
Generates the DODA and owns normative content.
02
Carrier
Carries the document and the physical unit.
03
You
Cross-check unit, plates, seals, and section in your file.
DODA and customs examination
A correct DODA does not avoid random selection; it keeps incongruent data from complicating a routine exam. Related: release, prevalidation.
What OCL runs
OCL Cargo is an autonomous TMS with agents and computer use (operating screens and portals like an analyst). It builds the trip file per shipment, cross-checks evidence, and leaves exceptions to humans. It coexists without a day-one TMS migration. OCL can stamp invoice and Carta Porte. On the Mexico–US corridor, the value is closing the trip file before paying.
Trip file
Flow control
Integrate
QR
Match
Plates
Seal
Photo
Present
Section
6–8 week pilot (DODA)
Month crossings stopped at the module for document incongruence. Goal: 100% with a ten-minute cross-check at release.
Elige un paso para ver el detalle
Detalle del paso · 01
Correct integration number
Key takeaways5 points
- DODA = presentation ticket with an integration number (QR).
- It integrates pedimentos, vehicle, seals, and customs section.
- Match DODA plates = Carta Porte = real unit before the module.
- The broker generates; you cross-check operational congruence.
- The natural moment is release, not the customs house.
Do your crossings depend on “the broker already checked it”?
Related reading
Frequently asked questions
No. The pedimento is the declaration; the DODA is the presentation document that integrates one or more pedimentos.
A correct DODA does not avoid examination, but it keeps a routine exam from escalating on incongruent data.
Yes: unit, plates, seals, driver, and destination customs are yours. Normative content is the broker’s.
When you change unit, pedimentos, or section. The classic fail is a last-minute unit swap.
Pre-presentation cross-check file tied to release and Carta Porte. It can stamp invoice and Carta Porte.