Success stories
Six Oracle projects: from a close that wouldn't balance to a stable production operation
Six projects on Oracle, including Grupo Avándaro, Zuma Energía and Smart Fit. Each started with a concrete symptom: a month-end close that wouldn't balance, a supply chain running outside the system, or a tax reform bearing down. Here is how each one was resolved.
They are told as they happened: what was there before, what we did and how it ended. When a timeline was measured, we state it; when it wasn't, we don't invent one.
- 6
- Documented casesFive cases name the client and one is anonymous for confidentiality, all with documented modules and scope.
- 8 weeks
- The fastest rolloutZuma Energía: Oracle Fusion Cloud ERP implementation on the structure they already ran in their other companies.
- 7 weeks
- From kickoff to productionSmart Fit: the SAT (Mexico's tax authority) changes for CFDI 4.0 e-invoicing, solved in APEX and coordinated with the PAC (authorized e-invoice certification provider).
- 4
- Oracle technologies across our casesNetSuite, Oracle Fusion Cloud ERP, Oracle SOA and APEX.
Six projects
The cases at a glance
Each card leads to the full story: what was there before, what we did and how it ended.
NetSuiteAudit and remediationGrupo AvándaroTheir NetSuite was already in place, but its output didn't match the operation. Three audits later, the group has an architecture with a roadmap.Read the story
NetSuiteCFDI 4.0 e-invoicingMarcas ExtraordinariasNetSuite implementation with CFDI 4.0 e-invoicing and the Walmart, City Market and Costco addenda.Read the story
Fusion Cloud ERP8 weeksZuma EnergíaRead the story
Fusion Cloud ERPERP recoveryCenmexRead the story
APEX7 weeksSmart FitInvoices, credit notes and payment complements in CFDI 4.0, within the window of the 2022 tax reform.Read the story
SOA on Fusion Cloud ERPFirst phase in 6 monthsMexican retail chainOracle SOA between their systems: millions of transactions, with the status of each one by component.Read the story
How to read these cases
The timelines shown (8 weeks, 7 weeks, 6 months) belong to those projects, with that scope and that installed base. They are not a schedule promise: they are evidence that a well-defined scope closes in weeks. The first job is always to define it.
Does one of these sound like your situation?
If the ERP is already in place and not performing, the starting point is an audit, not a reimplementation. That is what we did at Cenmex and Grupo Avándaro.