Skip to main content

Module for Odoo 17 · 18 · 19

Carta Porte 3.1 in Odoo: SAT-ready manifests from your orders and deliveries, with Ley Aduanera retention

Generates the Carta Porte 3.1 complement from Odoo: SAT catalogue goods, road transport with SCT permit and insurance, up to three trailers, rail block, locations and the full lifecycle down to the CartaPorte31 XML, with the 10-year retention required by Article 89 of the Ley Aduanera.

  • Odoo versions: Odoo 19.0Odoo 18.0Odoo 17.0
  • Migration to Odoo 20 the day it ships
  • Price: 49 € · one-time payment, source code included
Mexico Carta Porte 3.1 - Ley Aduanera Compliance module cover for Odoo

What it does

  • SAT catalogue goodsBienesTransp catalogue preloaded and importable from CSV, with automatic risk classification and lines with quantity, weight, value and product key.
  • Road transport and trailersVehicle, SCT permit, insurer and vehicle configuration, plus up to three trailers with plate and subtype, validated on the manifest.
  • Rail transportThe 3.1 rail block for train moves, with its equipment and route data.
  • LocationsOrigin, destination and intermediate stops linked to your warehouses and customer addresses.
  • Lifecycle and SAT XMLDRAFT → PREPARED → BOUND → CANCELED states with cascade cancellation from the CFDI, RFC/CURP validation and CartaPorte31.xml export.
  • 10-year retentionKeeps shipment data for the period Article 89 of the Ley Aduanera requires.
Source code included Odoo 17, 18 & 19 Complies with Art. 89 Customs Law Direct engineer support No middleware

The pains that bring buyers here

We are not talking about isolated functions. We talk about the operational problem that causes a logistics or foreign-trade team to end up looking for this solution.

Shipments without a Carta Porte on board

Without the correct complement, any customs inspection can hold up the goods and trigger penalties for the company.

The SAT goods catalog is not under control

Classifying each good by hand is slow and error-prone on unit of measure, product code and declared risk.

Vehicles, trailers and rail outside the ERP

When transport does not live in Odoo, vehicle data and shipment tracking are managed separately, with no traceability or double-check against the CFDI.

Every block of the 3.1 complement, inside Odoo

The module covers the real blocks of the SAT schema: goods, road transport, trailers, rail, locations and the full lifecycle through to the final XML.

Goods & SAT catalog

Merchandise lines with quantity, weight, value and product code, selected from the SAT BienesTransp catalog pre-loaded in the module.

Road transport

Vehicle data, SCT permit, insurer and vehicle configuration required by the SAT for road transport.

Trailers & semi-trailers

Up to 3 trailers per transport unit, each with its own plate and subtype, as required by the 3.1 schema.

Rail transport

Ferroviario block introduced in version 3.1 for rail-based transport operations, with its own equipment and route data.

Locations

Chain of origin, destination and intermediate stops, linked to your warehouses and customer addresses inside Odoo.

Lifecycle & XML

DRAFT → PREPARED → BOUND → CANCELED states with cascading cancellation from the parent CFDI and CartaPorte31.xml export.

The module actually running, not mockups

Screenshots taken directly from a real Odoo 19 install with the module active.

Overview of the Carta Porte 3.1 module in Odoo
Overview
List of Carta Porte manifests generated in Odoo
Carta Porte list
SAT BienesTransp catalog pre-loaded in the module
SAT BienesTransp catalog
Origin, destination and intermediate stop locations
Locations
Vehicle data in the Autotransporte block
Road transport (vehicle)
Merchandise lines with SAT classification
Merchandise lines

How a Carta Porte 3.1 is generated, step by step

A real walkthrough of the module: manifest creation, goods, locations, vehicle and final export. With Spanish subtitles.

Not a loose interpretation, the actual regulation

Every block of the module maps to a specific official article or schema, not to assumptions.

Ley Aduanera — Art. 89

Mandatory Carta Porte on board plus 10-year retention of shipment data.

CFF — Art. 29-A

Retention of the fiscal records of the CFDI the complement is attached to.

LFPDPPP — Art. 17

Right-to-erasure request workflow, reconciled with the mandatory retention under the Ley Aduanera.

SAT CartaPorte31 schema

Validation of the generated XML against the official schema published by the SAT.

What the one-time payment includes

No monthly fees, no empty boxes: everything the module includes is real operational capability.

Source code included

OPL-1 license per instance, no black box: you can audit and adapt the module.

Odoo 17, 18 & 19 · 12 months of updates

Fixes and improvements for the same series for 12 months, at no extra cost, via the Odoo App Store.

Direct engineer support

No middlemen, no call centers: the person who built the module answers.

Self-host or cloud, no middleware

Works directly on your Odoo instance, with no third-party dependency.

Carrier that must generate a Carta Porte on every shipment

The typical pattern is a company that already invoiced CFDIs in Odoo but generated the Carta Porte by hand or outside the ERP, risking inconsistencies between the CFDI and the complement. The module connects the real shipment to the manifest with no double entry.

21functional requirements
10 yearsArt. 89 retention
3.1current SAT schema

It connects with your operation in Odoo

Road transport, rail, the Pedimento for cross-border operations and the rest of the Mexican fiscal backoffice live together in the same Odoo, ready to grow into other localizations as the business needs.

Questions that usually arise in this phase

What is Carta Porte 3.1 and who needs it in Mexico?

It is the complement attached to the CFDI that proves the transport of goods across Mexican territory. Any company that transports its own or third-party goods by road or rail needs it, including foreign-trade operations subject to the Ley Aduanera.

What does article 89 of the Ley Aduanera require?

It requires the Carta Porte to be carried on board the vehicle during transport and the shipment data to be kept for 10 years for inspection by the customs authority when requested.

Does it cover road transport and rail transport too?

Yes. The module includes the Autotransporte block (vehicle, trailers, SCT permit, insurance) and the 3.1 Ferroviario block for rail shipments, plus the full chain of origin, destination and intermediate stop locations.

Does it generate XML valid against the official SAT schema?

Yes. The module serializes the document as CartaPorte31.xml following the schema published by the SAT, with RFC/CURP validation and automatic classification of the transaction type (domestic or cross-border).

What does the one-time payment include?

The complete module with source code included, an OPL-1 license per instance, for Odoo 17, 18 and 19. No monthly fees and no third-party middleware.

Are updates included?

Yes. You receive updates and fixes for the same Odoo series for 12 months at no extra cost through the Odoo App Store.

What support do I get after buying?

Direct support from the engineer who built the module, by email, with no middlemen or call centers.

Can I try it before buying?

You can watch a live demo of Odoo with FlexigoTech modules running and email us any question about Carta Porte 3.1 before deciding.

Mexico requires a Carta Porte 3.1 on every shipment.

If you already invoice with Odoo, it makes sense to generate the manifest from the same place where the order and the CFDI are born, with no double entry or risk of inconsistencies.

Talk to FlexigoTechSee full catalog