Track record with the SAT
The first criterion to evaluate a CFDI system isn't on the provider's website: it's how many years it has been stamping for the Mexican SAT without interruption. Every mandatory SAT migration — CFD 2.0 to CFDI 3.0, 3.0 to 3.2, 3.2 to 3.3, 3.3 to 4.0 — demands deep software re-engineering. Platforms that went through all those migrations have a team that knows the operational traps. Recent platforms barely know one CFDI version.
Longevity also means the platform has seen SAT failures (outages, validation delays, last-minute catalog changes) and learned to operate despite them. A platform with more than a decade in production usually has retry and fallback processes that a young project is still building.
Why it matters: electronic invoicing does not tolerate downtime. A platform that has been through several SAT migrations knows where things break before they do.