Skip to content

ReturnsAutodistribution2021 → 2026

Put returns in the same place as orders

IT was building a returns platform; on the Autossimo side, I worked on its screens with them, opened direct access from Autossimo and scoped how returns would appear in V4, on the “My orders, my returns” screen. Garages track every return where they place their orders.

  • Customer journey
  • SSO
  • API
  • Logistics
  • Cross-functional project
With

Impact

  • 1.38Mreturned order lines a year nationwide (project context)
  • 1single login, the Autossimo one
  • 0returns left untracked in the digital journey
Before
  • Wait for the next truck to return a part
  • No record of the request, no tracking
  • Returns kept apart, far from orders
After
  • Access from Autossimo, no new sign-in
  • An online return request, tracked to credit note or refusal
  • Orders and returns in one place, in V4

Direct access and activation are live. Garages reach after-sales from their daily tool, and every return is tracked from request to closure.

Metrics trackedUse of the digital journeyReturn processing timesDocument views (credit notes, refusals)

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

Make Autossimo the entry point to IT's new returns platform, then bring return information into V4, next to orders, all the way to production.

The context

A return involves the garage, the distributor, the warehouse and accounting. Before, garages waited for the next delivery to hand the part back to the driver, with no tracking at all. Nationwide, that is around 1.38 million returned order lines a year. IT launched a dedicated platform, led by my counterpart; my role was to connect it to Autossimo on both sides: access, and showing returns.

The challenge

Two products, two teams, one journey for the garage. Returns had to make sense where orders are placed, by fetching information from IT's platform through APIs. And three similar-looking checks had to be told apart: seeing the button, being recognised, having the right. A visible button can lead to a refusal if the garage is not yet registered on the platform.

What I did

  1. Work on the screens with IT

    Took part in the business and functional workshops with my IT counterpart, who led the platform: the return journey's screens, rules and edge cases, from request to credit note, through to the ERP and logistics.

    • Business workshops
    • IT
  2. Open direct access from Autossimo

    Single sign-on (SSO) from Autossimo to the Returns platform through the Okta account: garages get in without re-entering their credentials, from their everyday tool.

    • Okta
    • SSO
  3. Let distributors control activation

    Activation rules in the back office: per garage, in bulk per distributor, with exceptions, and a setting applied automatically when a customer is created. Progressive opening, distributor by distributor, garage by garage, at the platform's pace.

    • Back office
    • Progressive rollout
  4. Bring returns into “My orders, my returns”

    In V4, returns join the orders screen: Autossimo calls IT's platform through APIs to fetch the garage's return information (status, receipt, credit note or refusal) and shows it next to its orders.

    • API
    • V4
  5. Test and go live

    Testing of the access journey and activation, the three checks (see, be recognised, have the right) kept separate so each incident reaches the right team, go-live, then support for the network and the help desk.

    • Acceptance testing
    • Go-live

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.