A retail powerhouse running on manual effort
Carpet Court isn’t a business trying to find its footing. With 200+ stores across Australia and New Zealand, a 50-year reputation as the country’s leading flooring specialist, and a customer base that spans residential, commercial, and trade — they’re operating at serious scale.
What they were dealing with wasn’t weakness. It was the complexity that comes with growing fast and layering systems on top of each other over time. Every expansion brought a new tool. Every tool solved one problem and created two handoff points.
Five platforms. Zero conversation between them.
By the time Carpet Court reached out, their operations team was managing five core systems: an ERP for financials, a POS platform across all stores, a Magento e-commerce site, a standalone inventory management tool, and a customer database. None of them talked to each other natively.
The downstream effects were predictable, but painful. Store managers were manually exporting CSVs and reconciling spreadsheets just to get a read on daily stock levels. The operations team was generating weekly reports that required pulling data from four different systems — a process that took two to three full business days and still produced numbers nobody fully trusted.
Inventory discrepancies were showing up at the worst possible time: during customer conversations. The system wasn’t broken. It was just friction compounding at scale — and the cost was measured in hours, errors, and customer trust.
“We knew we had a data problem when our state managers were spending more time in Excel than on the floor. That’s not a people problem — that’s a systems problem.”
One integration layer to run them all
We started where most teams don’t — with a two-week audit of data flows, not a proposal. Every system, every handoff point, every manual step that existed because two tools couldn’t talk.
What emerged was a clear integration architecture using Odoo as the central ERP layer, connected to their POS via a real-time sync module, their Magento storefront via a bidirectional product and order connector, and their existing inventory system through automated daily reconciliation jobs built in n8n.
The customer database was migrated into Odoo’s CRM module, consolidating purchase history, trade account status, and service records — for the first time, any store associate could pull up a customer’s full profile during a conversation, not after it.
Odoo ERP
Magento
n8n Automation
WordPress CMSNumbers the operations team actually uses
Six weeks after kickoff, the first store cluster went live. By week 14, the full network was running on the integrated stack.
- 60% reduction in manual processing time — the 3-day weekly reporting cycle dropped to under 3 hours, fully automated
- Real-time inventory visibility across all 200+ stores — no more CSV exports, no more reconciliation lag
- Stock discrepancy rate dropped 78% in the first quarter post-launch, reducing customer complaints and write-offs
- Full customer 360 view in Odoo CRM — trade accounts, purchase history, and service records unified at store level
- 14-week full rollout across the entire national network — zero trading disruption
Phase two is already in motion
The integration is live, trusted, and running at scale. But this engagement didn’t end at launch.
Supplier portal & automated procurement
We’re connecting the inventory system to Carpet Court’s top 12 supplier portals, automating purchase orders based on real-time stock thresholds. When a product drops below a configurable minimum, the system raises a PO, routes it for approval, and tracks fulfillment — without a human in the loop for routine orders. The goal: eliminate procurement lag and reduce out-of-stock incidents by a further 40%.
