IN SHORT: Odoo ships native connectors for three PACs: Solución Factible, Quadrum and SW Sapien. If you already work with another — factura.com, Finkok, Facturama, Edicom — you cannot use it on Odoo Online, because connecting it means installing code and that tier does not allow it. Your options are switching PAC, moving to Odoo.sh or self-hosted, or building the connector. And before signing anything, you can test the full stamping flow for free with the test environment Odoo includes.
The PAC (Proveedor Autorizado de Certificación) is who stamps your invoices with Mexico's tax authority. Picking one looks administrative, but in Odoo it constrains which tier your ERP can run on. Better to settle it before signing with anyone.
What full configuration costs: see our package pricing; Empresa MX already includes stamping with your PAC.
The three PACs Odoo integrates
Odoo's Mexican localization ships native connectors for:
- Solución Factible
- Quadrum
- SW Sapien — Smarter Web
With any of the three, stamping is configuration: load your certificates, enter credentials, done. No development, no extra modules, no maintenance of your own when regulation changes.
If you are starting fresh with no prior contract, pick one of these three. It saves you the entire conversation.
What if you already have a different PAC
This is where it gets complicated, and where many people find out too late.
Connecting a different PAC means installing a module. And Odoo's documentation is explicit: "Odoo Online is incompatible with custom modules or modules from the Odoo Apps Store."
Meaning: on Odoo Online there is no way to add your PAC. Not by buying a module in the official store, not by developing it, not by asking support. The tier takes no outside code.
You have four real ways out:
1. Switch PAC (usually the cheapest)
If your contract is not locked in, moving to one of the three supported providers usually takes one phone call. Solución Factible and SW Sapien are established, affordable providers. Before spending on development, evaluate this: in most cases it is the right answer.
2. Move to Odoo.sh
You stay in Odoo's cloud but with code access, so you can install your PAC's connector. It is the middle ground for teams that do not want to run servers but need modules.
3. Self-hosted
Full control. It is also the only tier where you can run Community — which, note, does not ship native stamping either. We explain it in Community vs Enterprise.
4. Build the connector
If your PAC is non-negotiable (an active annual contract, corporate policy, integrations already built on that side), the module gets developed. It is serious work: stamping, cancellation with the SAT's reason codes, payment complement and credit notes — and then maintaining it.
We did it: iTechDev runs on Odoo 19 Community with our own PAC connector, built and audited against Anexo 20. So we can say from experience that it is not trivial, but it is not impossible — and that it is worth doing only when switching PAC is off the table.
How stamping is configured
With Enterprise and one of the three supported PACs, the flow is:
1. Prerequisites with the SAT. A valid RFC, your Digital Seal Certificate (the .cer and .key files with their password) and a PAC contract. Your company handles these, and they usually drive the project calendar more than the configuration itself.
2. Company details. Under Settings → Users and Companies → Companies: RFC, address with postal code, and the name exactly as registered with the SAT.
3. Tax regime, certificates and PAC. All in Accounting → Configuration → Settings, Mexican e-invoicing section. There you select the regime, upload the .cer, the .key and its password, and enter the PAC credentials.
4. Catalogs. Every product needs its SAT ClaveProdServ and ClaveUnidad; every customer their RFC, tax regime and CFDI use.
5. Invoice. You issue normally from Accounting and Odoo generates the XML and sends it to the PAC.
Test it free before signing
A detail few people use: Odoo ships a test environment. You tick the PAC test environment box, select Solución Factible, and it asks for no username or password.
It validates the full stamping flow — including your catalogs and tax data — before signing with a PAC or spending a peso. If you are evaluating Odoo, it is the most honest way to confirm invoicing works with your real operation.
Two stones everyone trips on
The legal name must be exact. The company name has to match the SAT registry character for character. It is the number one cause of stamping rejections, and we learned it in our own operation: one "S.A. de C.V." too many or too few and the CFDI is rejected.
Decide the localization before invoicing. Odoo's fiscal localization package can only be changed while no accounting entries have been posted. Start operating with the wrong setup and fixing it stops being an adjustment and becomes a project.
Before signing with a PAC, ask yourself
- Is it among the three Odoo supports? If yes, everything else gets simpler.
- Which tier will my Odoo run on? If it is going to be Odoo Online, your PAC has to be one of the three. Period.
- Do my customers require addendas? If so, you need a tier with modules anyway, and the PAC stops being the binding constraint.
Next step
To see how the PAC choice intersects with edition and hosting, we have the full comparison: which Odoo version you need.
And if you would rather we review your case — your PAC, your customers, your catalogs — the Odoo assessment is free and you leave with scope in writing.
Frequently asked questions
Can more PACs be added to Odoo Online? No. Adding a PAC means installing code, and Odoo Online takes no custom or Apps Store modules. The options are switching PAC, Odoo.sh or self-hosted.
Which of the three PACs is best? All three comply with the SAT and ship integrated. The decision usually comes down to price, support quality and whether you already work with one. With no preference, Solución Factible has the advantage of allowing tests without credentials.
How long does building a connector for another PAC take? It depends on how well documented their API is and whether you need cancellation, payment complement and credit notes on top of stamping. It is serious development with recurring maintenance. Before going down that road, price out switching PAC.
Does iTechDev sell the PAC? No. The PAC contract is yours, directly with the provider. We configure the integration or, when needed, build the connector.