Standing up a new FMCG trading business on Odoo from day one.
Abq Alahlam Almutamayiz is a newly established Saudi Arabia trading company specializing in FMCG brands. Rather than building operations on spreadsheets and migrating later, they made the right call: stand the business up on Odoo before opening for business. Galaxy Weblinks implemented the full operational platform — financial structure, compliance, inventory, and costing — before the first transaction was processed. Their choice of Odoo for trading business helped them scale seamlessly.
Most Odoo implementation case studies are about companies fixing what's broken. This one is about a company avoiding the brokenness in the first place. Abq Alahlam Almutamayiz was being set up as a new FMCG trading entity in Saudi Arabia. There was no legacy system to migrate from, no spreadsheets to clean up, no entrenched workflows to rewire. There was also no operational scaffolding of any kind — and that's its own kind of problem.
Greenfield ERP work has a different shape than migration work. The challenges aren't about replacing something — they're about building correctly from zero. Three things had to be true on day one of operations:
Financial structure had to comply with Saudi Arabian tax law and Zakat regulations from the first transaction. There's no grace period for new entities — the first invoice the business issues needs to be compliant. Vendor and customer master data had to be loaded and organized before the business could transact with anyone. And inventory, costing, and multi-currency import handling had to work correctly before the first shipment arrived, because correcting valuation errors retroactively in accounting is significantly harder than getting it right at receipt.
The cost of getting this wrong is hidden but real. New businesses that launch on weak systems spend their first two years cleaning up the mess. Errors compound. Compliance gaps surface during the first audit. Working capital decisions get made on bad data. Doing it right from day one is dramatically cheaper than doing it wrong and fixing it later.
Greenfield implementations aren't easier than migrations. The challenges shift — instead of fixing legacy, you have to anticipate operational reality before any data exists to validate against.
Abq Alahlam Almutamayiz had the same options every new trading business has. Start on QuickBooks plus spreadsheets and migrate later. Pick a vertical FMCG distribution tool. Go straight with a larger option like Odoo ERP implementation. Each path has different cost-and-risk tradeoffs.
QuickBooks would have been cheaper upfront but couldn't have handled Saudi tax compliance, Zakat reporting, multi-currency imports, or landed cost properly. The business would have outgrown it within 18-24 months and faced a costly migration. SAP Business One or NetSuite were over-engineered for a brand-new entity and represented licensing commitments that didn't fit a business still establishing operational rhythms. Vertical FMCG tools existed but came with their own integration debt and limited customization headroom.
Odoo's structural fit was clear: a single platform covering accounting, inventory, vendor and customer management, and multi-currency operations — with the configuration flexibility to align with Saudi compliance from the outset. The licensing math worked for a new entity. The customization headroom meant the system could be shaped to match how the business intended to operate rather than forcing operations to fit a rigid template. This made Odoo the best ERP solution for international expansion with multi-currency support.
The work itself was real configuration and setup, not customization-heavy development. Greenfield implementations lean more on careful setup than on custom modules — the system doesn't need to be reshaped, it needs to be built correctly from the foundation up. That's where Galaxy came in to implement Odoo ERP for their trading business.
The implementation ran across three workstreams that had to land before the first transaction was processed. Each one solved a category of operational risk that, left unaddressed, would have produced expensive cleanup work months later.
Full company configuration within Odoo — legal entity setup, operational structure, user roles, and security rules calibrated for a small but growing team. Comprehensive import and organization of vendor and customer master data, structured so partnerships, payment terms, and supplier relationships were live from the first day of operations. The business was operationally ready to transact before it opened, rather than scrambling to load data after the first orders came in.
Rapid operational readiness on day one. New business relationships and partnerships organized in a single system from the start.
Built a Chart of Accounts tailored for FMCG trading operations, configured journals with seamless synchronization to the accounting module, and implemented tax configurations in strict accordance with Saudi Arabian law. Zakat calculation and reporting set up natively in Odoo so the business could meet local regulatory obligations from day one. The first invoice the company issued was compliant, audited-friendly, and tied directly to the GL — not assembled after the fact and reconciled back.
100% compliance with Saudi financial and regulatory requirements from day one. Real-time financial insights replacing the manual entry that typically defines a new business's first year.
Comprehensive setup of the Inventory module with product categories defined to match the way an FMCG trading business actually operates — by brand, by category, by movement velocity. Costing methods synchronized with corresponding accounting entries so product valuation was accurate from inbound receipt onward. Multi-currency capabilities configured to support international vendor transactions. Landed cost functionality implemented so duties, freight, and import-related charges were assigned at receipt rather than booked to spreadsheets and forgotten. This created a more reliable ERP for import export operations with accurate cost visibility across international procurement workflows.
Accurate inventory valuation and transparent landed cost from the first shipment. Real profitability analysis available immediately, not after months of historical cleanup.
Greenfield implementations succeed or fail on different dimensions than migrations. There's no legacy data to clean, no existing workflows to rewire, no users to retrain off old habits. But there's also no real-world feedback to validate against — every decision has to anticipate operational reality before it exists. Three things mattered for this implementation to land.
Anticipating operational reality without overengineering. The temptation in greenfield work is to build for every imaginable future scenario. The right move is to build for the operational reality the business actually intends to run — and leave clear extension points for what comes next. Abq Alahlam's first-year operations are well-served by what we built; the platform is positioned to scale into multi-warehouse, additional brand portfolios, and more complex pricing without rework.
Compliance as a foundation, not a feature. Saudi tax law and Zakat regulations weren't bolted on after the rest of the system was built — they were the foundation the rest of the system was configured around. New businesses that treat compliance as a downstream concern spend their second year cleaning up the consequences. Treating it as foundational eliminates that category of cleanup work entirely.
One operational system from day one. The biggest temptation for a new business is to start with QuickBooks plus a few point tools and "scale into" a real ERP later. That path costs more in total — the migration to real ERP later is significantly harder than starting on it. Abq Alahlam skipped the patchwork phase entirely with Odoo for their trading business. Day one of operations was day one on a real ERP.
Most ERP implementations are clean-up projects pretending to be construction projects. Greenfield work is the rare case where you actually get to build right the first time. New trading businesses that skip the patchwork phase save themselves a year of pain.