Nearshoring to Mexico Is an ERP Project Too

The Shift Is Real

The move toward nearshoring is no longer a forecast. U.S. Census Bureau data for the first four months of the year show Mexico overtaking China as the largest source of goods imported into the United States, a change driven by tariffs on Chinese goods, the supply chain lessons of the pandemic, and the advantages of a shorter, overland route to the American market.

For manufacturers, nearshoring decisions usually start with real estate, labor, logistics and incentives. Those are the right places to start. But a new plant in Mexico, or a new contract manufacturer there, also has to be run on systems, and Mexican requirements for electronic invoicing, foreign trade programs and tax reporting are specific enough that an ERP not prepared for them can stop shipments at the border.

Electronic Invoicing Is Not Optional

Mexico requires every business transaction to be documented with an electronic invoice, the Comprobante Fiscal Digital por Internet, or CFDI.

Mexico requires every business transaction to be documented with an electronic invoice, the Comprobante Fiscal Digital por Internet, or CFDI. Invoices must be generated in a defined XML format, digitally signed, and validated in real time by an authorized provider certified by the Mexican tax authority, the SAT, before they are legally valid.

The current version, CFDI 4.0, became mandatory on April 1 of this year after a long transition. It requires more exact information about the recipient than earlier versions, including the recipient's registered name and postal code exactly as the SAT holds them. Shipments moving goods within Mexico also require a supplementary transport document, the Carta Porte, describing the cargo, the route and the vehicle.

An ERP that cannot produce these documents correctly, or that relies on manual workarounds, will create delays and penalties. Many ERP vendors offer localization for Mexico, often through partners. Their completeness varies widely, and it is worth testing the actual documents your operation will need rather than accepting a checkbox on a feature list.

IMMEX and the Inventory You Must Account For

Many export-oriented manufacturers in Mexico operate under the IMMEX program, which allows them to import materials temporarily without paying certain duties and taxes, provided the materials are transformed and exported within set time limits. The program is a major part of what makes Mexican manufacturing economical for export.

It also brings demanding inventory control obligations. Operators must be able to trace temporarily imported materials from entry through consumption to export, reconcile them against customs declarations, and demonstrate compliance under Annex 24 inventory control requirements. That is fundamentally an ERP and data problem. If your system cannot track imported lots, link them to the customs entry, and account for consumption accurately, the program's benefits can turn into significant liabilities.

Cross-Border Flows Need a Clear Design

A US company operating a Mexican plant usually has goods, money and paperwork moving in both directions: materials sent south, finished goods coming north, intercompany invoices, transfer pricing and two sets of tax rules. The ERP design needs to decide early whether the Mexican operation runs as a separate legal entity on the same system, a separate instance, or a different system integrated with the parent.

Each choice has consequences for reporting, intercompany accounting, inventory visibility and the ability to plan across the border. Getting it right at the start is far cheaper than redesigning it after the plant is running.

People and Language

ERP projects in Mexico also have a human dimension. Users on the plant floor will work in Spanish, and the system, the training materials and the support model need to reflect that. Local accounting and tax expertise is essential, because the people who know CFDI, IMMEX and Mexican tax reporting in depth are rarely found at the US headquarters.

The Bottom Line

Nearshoring to Mexico makes strategic sense for many manufacturers, and the shift is already under way. But a Mexican operation comes with specific requirements, real-time electronic invoicing under CFDI 4.0, transport documentation, and the inventory control obligations of IMMEX, that the ERP must handle reliably from day one. Treat the systems as part of the nearshoring plan, not as something to sort out after the building is leased.

At Cherry Street, this is the work we do. We help manufacturers evaluate whether their ERP is ready for a Mexican operation, design how the cross-border entities should run, and test the localization before the first shipment needs to cross.