Skip to content

Key-account APIsAutodistribution2021 → 2026

Connect key accounts to Autodistribution's APIs

Networks of car service centres (Euromaster, First Stop, Vulco, BestDrive…) plugged into Autodistribution's APIs to check prices and stock and order from their own tools. Eight key accounts supported, from first contact through to rollout.

  • API
  • Key accounts
  • Partner integration
  • Okta
With

Impact

  • 8key accounts supported
  • 4networks live: Euromaster, First Stop, Vulco, BestDrive
  • €Mseveral million in annual revenue per connected partner
Before
  • Each key account's internal tool doesn't talk to Autodistribution
  • Every integration handled case by case
  • Access based on a user's credentials
After
  • The key account's tool calls Autodistribution's APIs: price, stock, order
  • One API contract, documented and tested with its provider
  • Access tied to each application, and usage tracked

Several networks use Autodistribution services from their own tools. Integrations are understandable, testable and monitored, and one account's specifics stay isolated instead of complicating the others.

Metrics trackedRequests over 30 days per partnerBrowse / order splitInactive partnersIncidents per integration

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

Understand what each key account needs, open the right APIs with a clear interface contract, then support it all the way to rollout, without multiplying custom developments.

The context

Repair networks have their own software. To buy from the Autodistribution network, they want to check prices and stock and order without going through Autossimo, while respecting each centre's specifics and the management system (ERP) of the distributor that supplies it. The bridge between their system and ours is built on their side, by their own provider, on their own schedule.

The challenge

Each key account comes with its own problem, provider, catalogue and way of authenticating. An API contract (what the API accepts and returns) had to be explained in plain terms, each partner had to commit to a reliable estimate and schedule for its share of the development, its application's access had to be secured, and an open connection had to be checked for real use.

What I did

  1. Understand each key account

    With the Key Accounts team, understand each partner's problem: what it wants to do from its tool, which centres are involved, which APIs it needs (prices, availability, ordering). Euromaster, First Stop, Vulco, BestDrive… eight key accounts supported.

    • Key Accounts
    • Workshops
  2. Hand over the interface contracts

    A standardised API offer: one contract, account-specific needs kept separate. APIs presented to partners and their providers, documentation (OpenAPI) and ready-to-use sample requests (Postman), technical workshops in English.

    • OpenAPI
    • Postman
    • In English
  3. Lock the partner's estimate and schedule

    The bridge between their system and ours is built on their side: get a realistic estimate and schedule from their provider, align both calendars and track progress at the Key Accounts committee.

    • Key Accounts committee
    • Shared schedule
  4. Secure access with Okta

    Partners moved to access specific to their software (OAuth2, via Okta) instead of a user's credentials: no user password stored at a partner any more.

    • Okta
    • OAuth2
  5. Test with them all the way to rollout

    Access, centre and part-reference set-up, end-to-end testing with the partner, pilots, then general rollout and go-live. Four networks in production: Euromaster, First Stop, Vulco, BestDrive.

    • Pilots
    • Go-live
  6. Track usage and incidents

    Usage indicators defined (requests over 30 days, share of lookups versus orders, inactive partners), tracked in Moesif. Incidents analysed with the API teams and the integrator SQLI.

    • Moesif
    • SQLI

My role on this project

Driven end to end, all the way to production.

  1. UnderstandNeeds gathered with the business, the field and partners.
  2. ScopeScope, business rules, specs and user stories.
  3. PrioritiseBacklog ranked by value, shared roadmap.
  4. Build3-week sprints, coordinating business, IT and vendors.
  5. TestFunctional acceptance testing by journey, in Qase.
  6. ReleaseGo-live, change management, progressive rollout.
  7. 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.