From CONTPAQi to Odoo 18: How a Monterrey Lighting Distributor Got the Real Margin on Every Sale
We moved Intelliswitch, a Monterrey lighting distributor founded in 1991, from CONTPAQi and spreadsheets to Odoo 18: sales, commissions, purchasing, eight warehouses and accounting in one system. Here's what we built, the numbers behind it, and what is still in progress.
An ERP migration succeeds when management can trust the numbers, not when the software is installed. We moved Intelliswitch, a lighting and energy distributor founded in Monterrey in 1991, from CONTPAQi and a set of spreadsheets to Odoo 18. Sales, commissions, purchasing, inventory across eight warehouses and accounting now live in one system. The central result: every customer invoice now records the revenue and the real cost of the goods sold in the same journal entry, including freight and import duties. For the first time, management sees the actual margin of each sale when it is invoiced, not at month-end. Here's how we got there, the numbers behind the work, and what is still being finished.
The starting point
Intelliswitch sells luminaires, poles, ballasts, own-brand LED products imported from China and full public lighting projects for municipalities. Before Odoo, its operation ran across several tools:
- CONTPAQi for accounting and invoicing.
- A separate sales system and spreadsheets for quotes, commissions and purchasing.
- Manual month-end adjustments to work out the cost of what had been sold.
When we mapped the current processes, we found nine points where the same data was typed into two different systems. The project started as a CRM for the sales team. After the first assessment, connecting a CRM to the old tools was not viable, so the scope became a full Odoo ERP implementation in three phases: sales, purchasing and inventory, and accounting.
What we built, in numbers
| Area | What is in Odoo now |
|---|---|
| Product catalogue | 17,887 products migrated and classified into 15 product families, each with its own income, inventory and cost accounts |
| Chart of accounts | 2,594 accounts built from a 6,824-account CONTPAQi catalogue, keeping the client's numbering and the SAT grouping codes |
| Customers and suppliers | 4,072 sub-accounts replaced by one account for customers and one for suppliers, with each balance kept on the contact |
| Sales team | 11 salespeople on Odoo with automatic commissions and margin alerts |
| Warehouses | 8 warehouses: the main one, five job sites, Durango and a direct-delivery warehouse |
| Import costs | 19 landed-cost concepts (freight, customs, duties, insurance and others) added to the product cost |
| Banks and cash | 17 bank and cash journals, including two in US dollars, with daily Banxico exchange rates |
| Expenses | 52 employees set up with approval flows and 12 expense categories |
Real-time margin: the decision that mattered most
Intelliswitch's accountant used periodic inventory: purchases went to an expense account, and at month-end a physical count produced the cost of sales by difference. It works, but until the month closes nobody knows how much was made on each sale.
We configured Odoo with average cost (AVCO) and perpetual valuation:
- The supplier invoice arrives. The material goes straight to the inventory account, not to expenses.
- Import costs are added. Freight, duties and customs fees are spread over the received goods and raise their average cost.
- The customer invoice is posted. In the same journal entry, Odoo records the revenue and moves the average cost of the goods sold from inventory to cost of sales.
We validated the full cycle in a test environment before touching real data: purchase, receipt, import costs, supplier invoice, sale and customer invoice. The cost that reached the customer invoice included the capitalised freight, to the cent. The month-end count still exists, but now it only corrects shrinkage and capture errors through a dedicated inventory differences account.
Commissions and margin alerts, automated
Commissions were the first thing the sales team asked about, and the rules were not simple:
- Own-brand products pay commission by profit tier: 42% profit pays 8%, 35% pays 5.5%, 28% pays 4.25% and 20% pays 3%.
- Third-party products pay by margin on a separate scale, with a different table for one senior salesperson.
- Freight and handling absorbed by the company reduce both the margin and the commission.
We built this with computed fields and automation rules in Odoo Studio, without custom modules. Mixed quotes work: each line calculates its own commission and the order adds them up. We tested seven scenarios, including a negative control, a healthy quote that must not raise an alert. Directors receive an email alert when a third-party sale falls below 10% margin or when an extra discount is applied to own-brand products.
Accounting migration without losing history
The accountant set one firm requirement: keep the CONTPAQi account numbering. We kept it, adapted to Odoo's format and prefixed with the SAT grouping code so the localisation produces the correct electronic accounting XML.
Before the official load we ran a full rehearsal with July's balances. Of the accounts compared against the CONTPAQi trial balance, 470 matched to the cent. The remaining differences were limited to customers, suppliers and inventory, and each was traced to its source file. We fixed those files at the source and loaded the official opening balances as of September 30, 2026.
Two lessons from this phase apply to any CONTPAQi to Odoo migration:
- Test one record before any bulk import. That is how we found that Odoo rejects hyphens in account codes, before it affected 2,594 accounts.
- When something fails silently, compare working and failing cases. For days, payments were registered with no accounting entry and no error. Comparing payments that worked with those that didn't showed that 16 of the 17 bank journals were missing one configuration account.
Change management: the part software doesn't solve
Intelliswitch's team has years of experience with its current tools. What worked:
- Training by process, not by module. Six short guides covering sales invoicing, supplier invoices, payments and banks, expenses, imports and accounting. The team saw each process working before deciding who would do each step.
- Showing, then asking. Meetings with the accountant started with the result on screen, and questions went one at a time.
- Parallel operation. Since October 26, 2026, the company has run Odoo alongside CONTPAQi, so every figure can be checked against the old system before it is switched off.
Still in progress
- Accounting. The ledger is being reconciled month by month against CONTPAQi before Odoo becomes the only source of truth.
- E-invoicing. CFDI 4.0 stamping has been tested successfully in a sandbox. Live stamping from Odoo starts once the stamping provider (PAC) account is active.
- Data clean-up. Duplicate products inherited from the old catalogue are being consolidated with the purchasing team, starting with the five suppliers that cover most of what the company sells.
- Management dashboard. Sales, real margin, inventory and collections in one view, built on the validated data.
When Odoo is the right move from CONTPAQi
| If your company… | Consider |
|---|---|
| Only needs accounting and invoicing | Staying on CONTPAQi |
| Sells, buys and stocks goods and needs to know the margin per sale | Odoo with perpetual valuation |
| Imports and needs freight and duties in the product cost | Odoo with landed costs |
| Pays commissions on margin or discount levels | Odoo with automated commission rules |
The pattern isn't specific to lighting. Any distributor that buys, imports, stocks and resells, and today closes its margin by hand at month-end, can use the same design.
At ScaleWave we implement Odoo for companies in Mexico and Spain, from the CONTPAQi migration to the commission rules and the team training. If your margin only shows up at month-end, we'd be happy to review your operation and show you what an Odoo implementation would change.

