EuromasterAutodistribution2021 → 2026
Connect Euromaster, from order to invoice
Euromaster centres see Autodistribution's stock and place top-up orders without leaving Atelio, their workshop software. Every order generates a purchase order dropped at Euromaster and loaded into their SAP, so each invoice can be matched to its order.
- API
- Key account
- Multiple ERPs
- Accounting
- Cross-functional project
Impact
- Tens of €Mof annual revenue to secure and reconcile in the accounts
- 4distributor ERPs covered
- 3 yrsof support, live in production
- Atelio, Euromaster's workshop tool, does not talk to Autodistribution
- For top-up orders, centres go through another channel
- Orders don't show up in their accounts: invoices are hard to match
- Atelio calls Autodistribution's APIs directly
- Stock, prices and ordering, across the network's 4 ERPs
- One purchase order per order, loaded into their SAP
Centres buy from their own tool, and Euromaster has the document that reconciles its purchases and invoices. The test framework is now the model for other integrations.
Metrics trackedActive centresOrder success rateShare of orders with their purchase orderPurchase / invoice matching incidents
The engagement Autossimo, Autodistribution's B2B e-commerce platform: 23,000 automotive professionals, 3 million catalogue parts, €700M in annual business, several interconnected management systems (ERPs). Freelance Senior Product Owner from January 2021 to October 2026, with business teams, IT, the integrator SQLI and partners.
The brief
Let Euromaster centres check stock and order from Autodistribution in Atelio, across every management system (ERP) in the network, and generate for each order a purchase order loaded into their SAP, to match invoices and avoid unpaid bills.
The context
Euromaster orders from Autodistribution as a top-up supplier, when its centres need a part quickly. It wanted to do so from Atelio, its workshop software published by Infopro Digital, its integrator, without changing its processes. Two difficulties: the network's distributors use four different ERPs, and a delivered order stays invisible in Euromaster's accounts if no document links it to the invoice. A highly structuring project: tens of millions of euros of annual revenue to secure and reconcile.
The challenge
Three years of cross-functional work, from sales to accounting, on both sides. Euromaster's, Autodistribution's and each ERP's identifiers had to move between systems without getting mixed up; part numbers and brands had to match from one catalogue to the other. And an accepted order was not enough to pass a test: the purchase order had to reach Euromaster and load into their SAP.
What I did
Scope the need with Euromaster and Infopro Digital
Workshops with the Key Accounts team, Euromaster and Infopro Digital: from Atelio, see Autodistribution's stock, place a top-up order, then find every order in Euromaster's accounts. All without changing their processes.
- Key Accounts
- Atelio
- Workshops
Cover the network's 4 ERPs
Decided to cover the distributors' four ERPs rather than one: limiting it to one ERP would have left some centres out. Mappings of part numbers, brands and each system's own identifiers.
- 4 ERPs
- REST API + OpenAPI
Design the purchase order for their SAP
For every order, an automatically generated purchase order: the items ordered, their prices, their descriptions, and many business rules. It is dropped straight onto Euromaster's FTP for loading into their SAP. The aim: match every invoice to its order and avoid unpaid bills. Epic and user stories: document content, mappings, identifiers, dates, incidents.
- Purchase order
- SFTP
- SAP
Coordinate a three-year cross-functional project
Euromaster, Infopro Digital, the integrator SQLI, the API teams and IT operations, across sales, accounting, finance and IT, for nearly three years.
- SQLI
- Sales, accounting, finance, IT
Test until the document arrives
Pilot centres, price, availability and order tests for each ERP. A test only passes once the purchase order reaches Euromaster. Orders without a purchase order are tracked, so silent anomalies become visible and get fixed.
- Pilot centres
- Acceptance testing
Go live and keep the flow running
Go-live, then rollout centre by centre. The flow is monitored (Moesif) and maintained in production. The test framework now serves as the model for other key-account integrations.
- Moesif
- In production
My role on this project
Driven end to end, all the way to production.
- UnderstandNeeds gathered with the business, the field and partners.
- ScopeScope, business rules, specs and user stories.
- PrioritiseBacklog ranked by value, shared roadmap.
- Build3-week sprints, coordinating business, IT and vendors.
- TestFunctional acceptance testing by journey, in Qase.
- ReleaseGo-live, change management, progressive rollout.
- RunSupport, incident triage, improvements, tracked indicators.
Testing, properly tooled Acceptance test suite restructured in Qase, test cases generated and automated with AI, every fix retested and every incident turned into a regression test.
