For a small procurement and distribution business built around international imports, the back office can quietly become the bottleneck. That was the case for a Johannesburg-based supplier of imported timber and building materials with a lean team of five to ten people. The company had outgrown SYSPRO, long before anyone put a name to why.
The problem wasn't the product. It was the process.
The company’s core business, sourcing timber internationally and distributing it to the local building trade, depends on getting landed costs right. Freight, duties, clearing fees, exchange rate movements: every shipment carries a stack of costs that has to land on the correct product, at the correct value, before anyone can price with confidence.
SYSPRO wasn't built to make that easy. Proforma invoices had to be generated manually for every transaction. Receipting a shipment and allocating its landed costs meant working through a process that was, in the words of the team, unnecessarily complex for a business this size. And underneath it all sat a deeper issue: SYSPRO's accounting module didn't integrate cleanly with the rest of the system. Automation, the thing that actually saves a small team hours every week, was never really on the table.
None of this was a crisis. It was friction the team had simply learned to live with.
What the client actually wanted
When the client approached XRA, an Odoo implementation partner, the brief wasn't a wish list of features. It was a short, specific set of outcomes:
- Simplicity. A system a new hire could learn without a two-week onboarding process.
- Portability. Access from anywhere, not tied to an on-premises server or a specific office machine.
- Proper access control. Different permission levels for different roles, without hacks or workarounds.
- A real audit trail. Every transaction traceable, at the transaction level, not reconstructed after the fact.
XRA recommended Odoo Online, a fully cloud-hosted deployment, on Odoo 19.3. No servers to maintain, no infrastructure to manage. Just a system the team could log into from a laptop, a tablet, or a phone at a site visit.
Building it in the right order
XRA's team, led by a Business Analyst as project lead, with Trishna Misra supporting the accounting configuration and Jayan Kistasami handling data migration, didn't try to switch everything on at once. The implementation ran as a Minimum Viable Product build, and the sequencing mattered.
- Phase one: Purchase, Sales, and Inventory. This is the operational core of an import and distribution business, so it went live first. Getting stock movements, sales orders, and purchasing correct before anything else meant the rest of the system had something solid to sit on.
- Phase two: CRM. With the operational backbone working, customer relationship management was layered in, replacing what had previously been tracked in spreadsheets.
- Phase three: Accounting. Finance came last, deliberately. By the time accounting went live, the transactional data feeding it was already clean and flowing correctly through purchasing and sales.
The whole project, from kickoff to go-live, ran across July and August 2026. Two months, for a full ERP replacement, is tight. It worked because the phasing avoided the common failure mode of implementations that try to configure everything simultaneously and end up debugging the whole system at once instead of one module at a time.
Where the time actually got saved
Ask the client team what changed day to day, and landed costs come up first. A process that used to require manual allocation across multiple line items is now, in their own words, simpler than it's ever been. Costs land on the right products automatically, which means pricing decisions can be made with confidence instead of a spreadsheet reconciliation.
CRM tells a similar story. Customer and lead data that used to live in disconnected spreadsheets is now automated inside the system: visible to the right people, updated in real time, and no longer dependent on someone remembering to update a shared file.
And then there's visibility, the improvement that's harder to quantify but shows up everywhere. Stock levels, purchase status, customer history — all of it sits in one place now, instead of scattered across SYSPRO exports, spreadsheets, and email threads.
The underlying shift
The client’s shortfall going into this project wasn't really about SYSPRO as software. It was about a set of fragmented systems held together by manual processes and institutional memory — the kind of setup that works fine until the person who understands it takes leave, or the business tries to scale.
Odoo didn't just replace SYSPRO's functions one for one. It replaced the manual steps between those functions with automation — at the point of purchase, at receipting, at landed cost allocation, at invoicing. That's the actual difference between an ERP that technically has the features you need and one that removes the work of using them.
What's next
With Purchase, Sales, Inventory, CRM, and Accounting live, the client and XRA are now scoping the Marketing module as the next phase — extending the same automation-first approach into how the business promotes its imports and reaches new customers in the building trade. XRA continues to provide ongoing support as the system beds in and the team's usage matures.