← All case studies

Multi-country retail

Seven brands on a single e-commerce integration backbone

Multinational retail group. Bidirectional orchestration across PIM, ERP, e-commerce and marketing platform for a multi-country e-commerce operation.

  • My rolePrincipal Project Manager — integration flow design and delivery coordination
  • DurationOngoing
  • AreasBoomi · Shopify · SAP · PIM · Marketing automation
Context

A multinational retail group was migrating its e-commerce operations onto a new platform, brand by brand and country by country. Each brand has its own catalogue, pricing, languages and assortment, but they all draw on the same central systems.

The real problem

The risk in a migration like this is not technical: it is multiplication. If every brand builds its own integrations, by the seventh brand you have seven separate setups to maintain and no way to fix a problem once. What was needed was a single design that could absorb the differences between brands and countries without duplicating itself.

How we got there
  1. 01

    Understand

    Mapping the key e-commerce processes and how the central systems — product information, ERP, storefront, marketing — actually behave across countries and brands.

  2. 02

    Design

    Definition of bidirectional integration flows on an iPaaS platform: one parametric backbone instead of one integration per brand.

  3. 03

    Deliver

    Coordination of delivery and of the progressive brand migration, with flows going live as each brand moves onto the new platform.

What went into production
  • Bidirectional flows across product information management, ERP, e-commerce platform and marketing platform.
  • Processes covered: catalogue, pricing, images, stock, catalogue translations, reconciliation, order and return transmission, email communications.
  • Seven of the group’s brands migrated onto the new platform and served by the same integration backbone.
When this pattern recurs

Whenever several business units share the same central systems but want autonomy over the storefront. The decision that matters is made at the start, when it is cheap: a parametric backbone rather than a series of near-identical integrations. By the third brand the difference is already visible; by the seventh it is decisive.

The client is not named, for confidentiality. Sector and scale are real, as is everything else here.

Recognise the situation?

If something here resembles your case, send me a couple of lines. If it is not my ground, I will say so straight away.