Odoo implementation, custom modules and migration for Mexican companies
iTechDev is a Mexican software factory founded in 2018, with teams in Monterrey, Guadalajara and Laredo, TX. We do Odoo consulting and implementation, migration from CONTPAQi or Aspel, CFDI 4.0 localization and custom modules: we do not subcontract development — we write it in Python/OWL and the code stays 100% yours.
Still unsure whether you need Enterprise? Settle it in 4 minutes, no data required →
- Odoo Ready partner
- 100+ projects
- 5.0★ Clutch
- MTY · GDL · TX nearshore
iTechDev, Ready level in the official Odoo directory, with 100+ projects delivered since 2018 and 5.0★ on Clutch.
A single platform: the sale draws down inventory and posts to accounting on its own, and CFDI 4.0 is stamped when the invoice is confirmed.
Illustrative view of a real Odoo flow, not a customer data point.
CLIENTS WHO TRUST OUR ENGINEERING








What do you need to solve with Odoo?
Seven jobs, one team. Pick yours — each lands on the technical analysis, not on a long questionnaire.
Get Odoo actually running
Phased method, native or adapted. Native-vs-adapted criteria and a dated go-live.
View service CFDI 4.0 localizationStamp from the ERP, SAT-compliant
l10n_mx, CFDI 4.0, payment complement, DIOT and Carta Porte with your PAC.
View service MigrationLeave CONTPAQi, Aspel or Excel
Validated ETL, parallel run and 100% reconciliation before cutover. No blackout.
View service CustomizationWhat the standard cannot solve
Custom Python/OWL modules. We are the factory, we do not subcontract. Code 100% yours.
View service IntegrationConnect what you already use
Payments, e-commerce, banks and POS wired to Odoo, no double entry, no data islands.
View service Support / AMSStop depending on one person
Rescue an inherited Odoo and SLA maintenance by contract. A clear boundary of what we cover.
View service ConsultingDecide before you spend
Fit-gap, TCO and the Community vs Enterprise call without license bias. The $7,500 analysis.
View serviceBefore hiring, settle the decision
Two self-service exits: which version applies to you (free, no data) and how much it costs (published price). The hub routes; the number and the tier live on their pages.
Which Odoo version do I need?
Online, Odoo.sh or self-hosted; Community or Enterprise. Settle it in 4 minutes, no data required — what changes to stamp CFDI 4.0 in Mexico.
Open the versions guide CHECK THE NUMBERPublished prices and packages
The fixed-price packages in pesos, what each includes and what is quoted separately — ordered by tax regime, not by size.
See prices and packagesWe use it ourselves
We run all of iTech on our own Odoo 19: sales, projects, timesheets and invoicing. We wrote the CFDI stamping module ourselves and audited it against the SAT's Anexo 20 — we run it, we do not subcontract it.
erp.itechdev.com.mxProof of competence, not a client case: we do not sell an ERP we do not use.
See it in a live demoSAT (Mexican tax authority)In force since
The SAT replaced the catalogs the Carta Porte complement consumes: transport product and service keys, units, hazardous materials and vehicle configurations. An Odoo left on the previous catalogs does not fail "sometimes": the PAC rejects the stamp and the shipment does not leave the yard.
Current as of July 30, 2026. If the SAT publishes a later change, this page is updated before our commercial proposal is.
The criterion is binary: it stamps or it does not.
If your l10n_mx_edi has not been updated since 2025, you are already having transfers rejected. Checking which version your catalogs are on takes fifteen minutes and we do it in the analysis.
Carta Porte complement catalogs (SAT) ↗How it is configured, step by stepCFDI 4.0 localization
Why Odoo with a software factory?
There are three profiles in the market. We tell you where we stand and why it matters when you need more than configuration.
Configures and subcontracts the development
Many consultancies configure Odoo well, but when you need a real module they subcontract the code. The knowledge lives outside and every change goes through a middleman.
The development is not theirsMay disappear and leave you a black box
A solo developer solves it cheaply today, but if they disappear you are left with no support, no documentation and an Odoo nobody else understands.
Risk of being left aloneSoftware factory (us)
We build the modules in-house in Python/OWL, with code 100% yours, documented processes, a fixed budget and AMS support with an SLA. What others outsource, we fabricate — and document.
The code and the knowledge stay with youPeople say Odoo "depends on the local developer", "hides costs" or "is hard to standardize". With a software factory behind it, none applies: the code is yours and documented, the budget is fixed after the analysis, and documented processes standardize every delivery.
What we do not do
Five things others will offer you and we will not. We tell you before the call.
We do not re-stamp already-issued invoices
The SAT does not allow re-stamping a CFDI: it is cancelled and a new one is issued to replace it. If someone offers to fix old invoices, they cannot deliver it.
Carta Porte for road transport only
Odoo covers the native Carta Porte 3.1 complement for road transfers, type T. Sea, air and rail require development and are quoted separately.
Payroll ships in no edition of Odoo
Neither Community nor Enterprise includes stamped payroll for Mexico. Anyone including it out of the box is quoting something Odoo does not have.
Sometimes the answer is a new PAC, not a new ERP
If your PAC is not among those your deployment accepts, switching PAC is usually the right answer: cheaper than forcing development. We say so even when it means a smaller project.
And sometimes the answer is SAP, not Odoo
We are a partner of the SAP ecosystem (PartnerEdge) and we also implement Odoo. If your headquarters already runs SAP, the right answer is SAP Business One — even though the Odoo project would leave us a better margin.
And one more, an uncomfortable one: we still do not have our own Odoo case with publishable metrics. What you can see is our own Odoo 19 running —iTech sales, projects, hours and invoicing. We are not going to invent a client number for you.
Verifiable credentials, not a decorative logo
iTechDev is listed in the official Odoo directory as ITECHDEV MX, Ready level. We say so before you check. Everything else is verifiable too: 100+ projects delivered since 2018, 5.0★ on Clutch with third-party verified reviews and a real Mexican localization.
100+ projects · 5.0★ on Clutch
Over 100 projects delivered since 2018 and a 5.0★ rating backed by third-party verified reviews on Clutch. Not a number we gave ourselves.
5.0★ ClutchDocumented processes
Development with documented processes: 2-week sprints, functional demos and verifiable deliverables at every phase, with no surprises at go-live.
2 wksReal Mexican localization
l10n_mx, CFDI 4.0 and native Carta Porte complement (type T), DIOT and trial balance, OCA community modules and stamping via authorized PAC (Finkok · Factura.com).
CFDI 4.0 · l10n_mxCode that is 100% yours
The custom modules are yours, with repository and documentation. No black box, no vendor lock-in: if you ever leave, you take everything with you.
No lock-inNearshore Monterrey, Guadalajara + Texas
A bilingual team in your own time zone (CST), with an entity in Laredo, TX to contract in USD and a headquarters you can actually visit.
MTY · GDL · TXFrequently asked questions
Can't find your question? Talk to an engineer — no sales script.
Contact us →Who implements Odoo in Mexico, and what should you verify before hiring?
Odoo's official directory lists partners in Mexico by level: Gold, Silver and Ready (odoo.com/es/partners/country/mexico-150). iTechDev appears there as ITECHDEV MX, Ready level. Check any provider's level on that page before believing a badge published on their own site, and ask for three things in writing: which package stamps CFDI 4.0 and which does not, who writes the custom modules —your provider or a third party— and who owns the code when it is done.
Community or Enterprise to invoice in Mexico?
The criterion is binary: the module that stamps CFDI 4.0 natively (l10n_mx_edi) is Enterprise. Community ships the Mexican chart of accounts and taxes (l10n_mx), not the stamping; you can invoice from Community, but someone has to build and maintain the connector to the PAC. The full decision —with the Online/Odoo.sh/Community hosting tree— lives in the "Which version do I need?" guide.
Odoo or SAP Business One?
We implement both and charge similarly for both, so the recommendation does not depend on which suits us. SAP Business One is the right choice when your headquarters already runs SAP or your corporate processes require it. Odoo usually wins on flexibility and code ownership, because it is open source and the custom code stays 100% yours. What we will not do is give you an invented savings percentage.
Why "Odoo Ready" and not "Gold" or "Silver"?
Odoo Ready honestly states what we are: a firm that implements, customizes, migrates and integrates on Odoo and develops custom modules in Python/OWL. The Silver/Gold tiers depend on the volume of Enterprise subscriptions a partner resells each year — a commercial model, not a measure of technical capability. We prefer to compete on engineering: code 100% yours, 100+ projects, 5.0★ Clutch.
Start with the technical analysis
A closed budget in writing, yours even if you implement with someone else, and credited to the project if you move forward. No free assessment that later quotes a fortune: a number you can defend to your board.
Request your technical analysis
Three fields and we coordinate. The analysis hands you scope, an edition decision and a fixed budget in writing.
What we do guarantee
- The analysis document is yours, whether you implement with us or not.
- Odoo Ready: no license bias, 0% markup.
- Code and configuration 100% yours, no lock-in.
- Zero cold calls: we book nothing without your permission.
