Software for customs brokers, binational trucking and import/export on the border
An operation that crosses the border lives split in two: the pedimento on one side, the CFDI on the other, and in between a chain of email, Excel and WhatsApp nobody can audit. iTechDev builds the system that joins both sides, with a Texas entity (iTech Dev Corp) and operations in Mexico. We are not a customs broker and we do not sell a pedimento module: we build the system around that operation and connect it to what you already run.
- Texas entity and Mexican operation, same CST time zone
- Carta Porte and CFDI 4.0 solved in production
- Integrates with the customs software you already run
5.0★ on Clutch · 200+ projects · Monterrey, Guadalajara + Texas · Code 100% yours
The three profiles we serve on the border
Customs broker
Your customs system handles the pedimento, but not the client file, not the status people call you about ten times a day, and not the invoicing of fees and disbursements. That is what we build: the client portal, crossing traceability and the connection to the system you already have. We do not replace it.
Binational carrier
The problem is not dispatching: it is that the truck crosses and control breaks. On the Mexican side you need a transfer CFDI with the Carta Porte complement; on the US side, documentation and collection in dollars. We build unit tracking, Carta Porte from your real operation, and invoicing on both sides.
Importer or exporter
Your inventory and costs live in two currencies and two accounting systems. What Odoo can solve we solve with Odoo, Mexican localization included; what your particular operation demands —import costing, freight and duty allocation— is built on top.
What we do NOT do, said up front
We are not a customs broker, we do not file pedimentos and we do not sell customs clearance software. If that is what you need, a specialised vendor serves you better and we will say so on the first call.
What the free assessment includes
A deliverable that serves you even if you build with someone else.
The decisions that define the project
One system or two connected?
A single system for both countries is rarely the answer. What is worth defining is which one owns each piece of data and how it travels: decide it up front or it decides itself, badly.
What gets integrated and what gets replaced?
The customs system is rarely replaced: it gets integrated. Invoicing and operations usually are replaced. Decided with the list of what you already pay for in front of you.
Where does costing live?
The real cost of an import shows up weeks later, when freight, duties and handling arrive. Defining where that is allocated determines whether your margin is a number or a guess.
Who captures at the crossing?
Operations, dispatch or the broker. It changes how error-proof the screen must be, and whether it has to work on a phone next to the gate.
How we build custom software
Fixed pricing, delivery every two weeks, code and repository 100% yours from the first commit. Integrating with what you already run instead of replacing everything.
Assessment for your border operation
An operation that crosses the border lives split in two: the pedimento on one side, the CFDI on the other, and in between a chain of email, Excel and WhatsApp nobody can audit. iTechDev builds the system that joins both sides, with a Texas entity (iTech Dev Corp) and operations in Mexico. We are not a customs broker and we do not sell a pedimento module: we build the system around that operation and connect it to what you already run.
- A map of your crossing operation: where it breaks today and what breaks it
- What Odoo configuration solves and what requires custom development
- What Carta Porte requires for your transfer scenario
- How to connect with the customs or clearance software you already run
5.0★ on Clutch · 200+ projects · Monterrey, Guadalajara + Texas · Code 100% yours
Assessment for your border operation
Frequently asked questions
What software do customs brokers on the MX–US border use?
Almost all of them run specialised clearance software for the pedimento, and around it a layer that is usually improvised: files in shared folders, status over WhatsApp and fee invoicing in another system. That is where custom development comes in: a client portal with real crossing status, a digital file per operation, and fee and disbursement invoicing connected to the customs system you already run. We do not replace the pedimento system, we integrate it.
What system does a binational trucking company need?
It must cover three things that rarely live together: unit and trip control, the transfer CFDI with the Carta Porte complement on the Mexican side, and dollar invoicing on the US side. Odoo covers operations, inventory and Mexican invoicing well through its localization; unit tracking and reconciliation between both entities usually requires development on top. Carta Porte is what stalls go-lives most, because it demands vehicle, driver and SAT catalogue data that is rarely captured.
Is an ERP worth it for an import/export company on the border?
Yes, with one condition: that someone solves import costing and dual-currency operation, because that is where a generic ERP falls short. Odoo covers purchasing, inventory, sales and the Mexican tax side, and on top of that you build what your operation demands —allocating freight, duties and handling into product cost, and reconciling the Mexican and US entities—. If your operation is simple and one-sided, a standard ERP without development is probably enough.
Can you invoice in Mexico and the United States from the same system?
From the same base system yes, but not with the same document or the same process. In Mexico the CFDI 4.0 is stamped through an authorised PAC and follows rules that do not exist on the other side; in the US the invoice is a commercial document with no stamping. What you do is run both entities in the same system with their own configuration, and reconcile between them. We have a Texas entity (iTech Dev Corp) and operations in Mexico, so we live this problem too.
Does it integrate with the customs system I already have?
That is the route we recommend. Most clearance systems allow exporting or exposing data, and when they do not, it is solved with an agreed file exchange. What matters is defining up front which system owns each piece of data: if two systems can edit the same field, in three months you will not know which one holds the truth.
Assessment for your border operation
5.0★ on Clutch · 200+ projects · Monterrey, Guadalajara + Texas · Code 100% yours