Case Study — B2B Marketplace & Heavy Machinery — Luxembourg 🇱🇺

20 Million SKUs. 5 Country Storefronts. Fully Automated — On Odoo 18 Enterprise.

A high-growth Luxembourg B2B marketplace digitising the global supply chain for heavy machinery spare parts needed Odoo to handle scale nobody had built for before. Here's exactly what we built — and what it took.

Auto-Import Live

Magento & eBay orders flowing automatically across all storefronts

SH Costs Reduced

Significant Odoo SH cost savings through intelligent product archiving

5 Country Storefronts

UAE, UK, Germany, France, Netherlands — all live and syncing

70+ Tasks Delivered

Delivered under structured Agile project management

Who the client is

A technology-first marketplace tackling one of the most complex supply chains in the world.

Our client is a high-growth, Luxembourg-based B2B marketplace purpose-built to digitise the global supply chain for heavy machinery spare parts. Their mission is ambitious: make it as easy to source a replacement part for a 20-year-old excavator in Germany as it is to order something from Amazon.

The scale of the problem they're solving is enormous. The heavy machinery spare parts market is fragmented, analogue, and slow — dominated by legacy distributors running on phone calls and paper catalogues. Our client is building the digital infrastructure to replace that — indexing 20 million unique SKUs accurately across multiple supplier catalogues, connecting buyers and sellers across geographies, and processing orders from 5 country-specific Magento storefronts simultaneously.

They chose Odoo 18 Enterprise on Odoo SH as their operational backbone — managing orders, customers, products, and financials centrally while Magento and eBay handle their customer-facing storefronts. The challenge: making Odoo the reliable, lean, cost-efficient hub of a 20M+ SKU operation across 5 countries — with VAT rules, currency differences, and platform-specific logic all handled automatically.

When Rootlevel came in, the hub wasn't working the way it needed to.

Operational Snapshot

Location

Luxembourg (HQ) & 5 global markets

Catalogue Scale

20 Million Unique SKUs

Storefront Channels

5 Magento Stores + eBay Connector

UAE, UK, Germany, France, Netherlands

System Stack

Odoo 18 Enterprise on Odoo SH

"Indexing millions of products across multiple channels pushes traditional ERP databases to their limit. Managing scale is not just about server memory — it's about database architecture design."
Where things stood when we arrived

A high-growth marketplace built on Odoo 18 Enterprise, facing major hurdles at the intersection of scale and international commerce.

When Rootlevel was brought in, the marketplace was live on Odoo 18 Enterprise but struggling to support its rapid international expansion. They were managing five storefronts across different European and Middle Eastern countries, but silent VAT logic conflicts, unmanaged product data growth, and a backlogged requirements queue were threatening to halt operations.

Magento Order Import Breakdowns

Order imports from their five Magento storefronts were failing silently. International transactions involving complex VAT rules across multiple European jurisdictions were triggering strict Odoo validation exceptions, blocking valid sales orders and requiring hours of manual data entry to correct.

Massive Database Scale & Bloat

Managing over 20 million unique product SKUs from global supplier catalogues led to extreme database inflation. Odoo SH hosting and storage charges were ballooning out of control, and system memory limits were pushed to the edge, slowing down inventory searches and transaction processing.

eBay Integration Gaps

Their secondary sales channel, eBay, was operating in a partial silo. Gaps in product field mapping between eBay and Odoo caused inventory mismatches, forcing staff to manually cross-reference and verify listings to avoid overselling.

Development Backlog of 70+ Tasks

The client's operational team was struggling with a backlog of over 70 critical development, automation, and refinement requests. Without a structured prioritization framework or dedicated Odoo engineering resource, essential updates remained perpetually delayed.

The Odoo SH and Magento Integration Challenge

Because they were operating a highly custom, large-scale B2B marketplace on Odoo SH, any solutions had to be highly performant, robust, and cleanly integrated. We had to ensure Magento's customer-facing experience remained completely synchronized with Odoo's ledger and inventory, while optimizing the database to prevent catastrophic scaling costs.

Specific pain points

Four distinct problems.
All interconnected. All solvable.

A large-scale international marketplace requires absolute synchronicity between channels and the core database ledger. Minor validation errors or database bloat don't just slow the system — they directly lock cash flow and customer trust.

01

Magento VAT Validation Failures

As orders were imported from Magento storefronts across different countries, international tax validation rules clashed. Since Odoo enforces strict VAT checks on customer creation, tiny mismatches between Magento's addresses and Odoo's required formatting caused silent import failures, stopping the order pipeline.

02

eBay Connector Gaps & Silos

The client's eBay integration lacked proper product attribute maps. Listing categories and custom parameters failed to synchronize correctly with Odoo ERP fields. Staff were forced to spend hours cross-referencing listings, manually fixing inventory sync, and risking overselling.

03

20 Million SKUs Database Bloat

Importing extensive vendor catalogs pushed the Odoo database into massive bloat. Odoo SH hosting charges ballooned due to the data footprint size, while standard search queries and stock validations struggled under millions of rows, slowing down daily business operations.

04

70+ Backlogged Development Tasks

Without structured sprint priorities or an expert Odoo partner to guide them, the client's internal operations faced an overwhelming backlog of 70+ technical requests, ranging from minor UI fixes to critical bookkeeping custom reporting tasks.

Technical depth — what was actually delivered

Four core solutions. Standard connectors customized.
All automated. All built to scale.

By extending Odoo 18 Enterprise's native connector framework and adding high-performance database cron routines, we stabilized active synchronization and eliminated infrastructure bottlenecks without custom overrides that would break future updates.

01

Custom Configurable VAT Tolerance Rules

The Requirement

Magento orders involving complex VAT rules across multiple European jurisdictions were failing to import, generating silent validation exceptions in Odoo.

What We Built

Developed custom VAT tolerance rules integrated directly into the Magento connector order processing layer. Odoo now automatically normalizes address structures, resolves country codes, and validates international VAT IDs under customizable rules without rejecting the sales orders, keeping the import pipeline running flawlessly.

Engineering Context

We configured standard connector layers and augmented them with custom Python-driven tolerance scripts to allow order generation and auto-routing to accounting, eliminating manual intervention completely.

02

eBay Product Parameter Mapping Rules

The Requirement

Integrate products across multiple listing configurations on eBay cleanly, matching custom categories without losing transactional attributes.

What We Built

Consulted and configured best-in-class connector settings and written custom mapping logic. Gaps between eBay product categories and Odoo inventory products are seamlessly bridged, aligning fields such as manufacturer codes, parts condition, and pricing rules automatically.

Engineering Context

Standard connector logic was re-mapped to custom tables within Odoo v18, avoiding manual field cross-referencing and ensuring real-time stock-count adjustments on sold parts.

03

Intelligent Scheduled Product Archiving Engine

The Requirement

Catalog scale of 20 million SKUs created massive Odoo SH database inflation and ballooned monthly hosting and server infrastructure costs.

What We Built

Engineered an automated product lifecycle archiving engine. Products with zero sales history or zero supplier inventory are automatically archived in batches, freeing millions of active database rows. If a customer orders an archived SKU, the connector unarchives it instantly on-the-fly.

Engineering Context

Leveraged Odoo Scheduled Actions and optimized SQL index batch updates to clean the catalog during off-peak hours. Reduced storage and memory constraints significantly, lowering monthly SH hosting bills.

04

Full Agile Delivery Sprint Framework

The Requirement

Overwhelming backlog of 70+ technical, customization, and bookkeeping report requirements stalling operational progress.

What We Built

Implemented a rigorous Agile sprint delivery process. We audited, prioritized, and grouped the 70+ backlogged tasks into two-week sprints. Working closely with their internal product leads, we established QA staging procedures and delivered every requirement systematically.

Engineering Context

Used collaborative project management boards synchronized with git releases. We maintained high speed and zero regression throughout, training their team to handle releases alongside us.

What changed

A high-performance Odoo hub, ready to support global scale.

By optimizing database architecture and resolving international tax synchronization issues, we turned the client's Odoo ERP into a seamless operations hub capable of scaling with their ambitious growth.

Order Automation

Automated Order Import Across 5 Stores

Order flows from Magento country-specific stores (UAE, UK, Germany, France, Netherlands) and eBay now automatically generate valid Odoo ledger and invoice records without silent connector drops.

Compliance

VAT Validation Issues 100% Fixed

Standardised international VAT validation checks across all geographies, resulting in zero blocked or failed imports for overseas customers.

Cost Optimization

Odoo SH Infrastructure Costs Reduced

Cleaned the database and freed millions of unnecessary rows with our custom product archive cron rules, directly lowering database hosting fees on Odoo SH.

Project Delivery

70+ Development Backlog Tasks Delivered

Sprinted and cleared their deep operational backlog, shipping critical ledger adjustments, UI improvements, and customized reports under stable Agile management.

Future-Proof

Scalable Foundation for Future Growth

Re-architected catalog schemas and connectors in standard patterns, making Odoo v18 ready to integrate new supplier channels and country storefronts smoothly.

Under the hood

Technical Snapshot

The architectural configurations, module specifications, and engineering compliance levels defining this deployment.

Odoo Version

v18 Enterprise

Hosting

Odoo SH (Optimized Dedicated Cloud)

Modules Used

Sales, Purchase, Inventory, Accounting, eCommerce, Connectors

Integrations

Magento (5 storefronts), eBay

Custom Development

VAT tolerance rules, product archive automation, connector customisation

Automation Tools

Odoo Native Automations, Scheduled Actions, Python scripts

Scale

20 Million+ Unique SKUs, 5 Country Storefronts

Geographies

UAE, UK, Germany, France, Netherlands

Project Management

Agile sprints — 70+ large-scale tasks delivered

Proven Scaling to 20 Million+ Product Records on Odoo SH
What this project taught us

Three key insights on scaling enterprise marketplace ERP setups.

Recommending a competitor's module is sometimes the right answer

Standard Odoo connector modules are incredibly powerful, but many vendors refuse to use them out of a prideful desire to build custom integrations from scratch. We recommend standard modules first, and only write custom extension layers where necessary. This approach saved the client months of development time and built-in compatibility.

Database architecture is a business model decision at scale

Managing over 20 million SKUs in Odoo is not simply about acquiring a larger cloud server. It requires logical database lifecycle planning. Archiving unused items programmatically is a highly efficient way to preserve search speed and drastically lower hosting charges, keeping operations lean and viable.

Agile delivery discipline matters as much as technical capability

When faced with a backlog of over 70 complex tasks, arbitrary priority lists break down quickly. Rigorous sprint structures, collaborative backlog grooming sessions, and dedicated QA staging procedures are what turned the client's operation from chaotic delays into continuous, reliable releases.

If you recognised your business in this case study:

Here are the specialised services, industry configurations, and regions related to this deployment.

Related Industries

  • Odoo for eCommerce
  • Odoo for Trading & Distribution
  • Odoo for Import & Export
  • Odoo for Wholesale

Similar Geographies

  • Odoo ERP for UAE Businesses
  • Odoo ERP for UK Businesses
  • Odoo ERP for German Businesses
Let's solve your Odoo challenges

Running a marketplace, eCommerce operation, or multi-storefront business on Odoo — and recognise any of this?

Whether you're dealing with broken integrations, database scale challenges, or a backlog of requirements with no delivery structure — we've solved all three. Book a free discovery call.

No commitment required
Response within 24 hours
NDA before any discussion