SELECTED WORK · CASE STUDY

One storefront, several ERPs

Connecting Adobe Commerce to Pronto, MYOB EXO, MYOB Advanced, Akeneo and PunchOut for a national automotive parts and service network selling to retail and trade customers.

Platform:
Integrations: , , , ,
  • Client National automotive parts and service network
  • Platform Adobe Commerce, Pronto, MYOB EXO, MYOB Advanced, Akeneo, PunchOut
  • My role Technical lead: integration design and delivery
  • Focus Multi-ERP integration, B2B and B2C

The context

A national automotive parts and service network sells to retail customers and to trade buyers, through a business made up of different entities that don’t all run the same back-office systems. The commerce platform had to work with all of them.

The integrations

  • Pronto as an ERP for orders, stock and pricing.
  • MYOB EXO and MYOB Advanced for the parts of the business that run on MYOB.
  • Akeneo PIM as the single source of truth for product data across the catalogue.
  • PunchOut, so trade buyers can shop from inside their own procurement systems and send the cart back for approval.

Key decisions

  • One integration layer, several back ends. The storefront talks to a single, consistent integration model; differences between ERPs are handled behind it.
  • Product data from one place. Content and attributes come from the PIM, while stock and pricing come from the ERP that owns them.
  • Design for failure. Every sync is logged, retried safely and visible, so a problem in one system doesn’t silently affect orders in another.

This case study is anonymised. Client names, systems and figures are withheld; architecture details are simplified for illustration.