Integrating Mirakl with Shopify can mean two different things: connecting your catalogue as a seller to marketplaces, or using Shopify as the storefront of your own Mirakl-managed marketplace. The choice changes architecture, costs and responsibilities.

The Mirakl Platform connector for Shopify targets the second scenario: building a marketplace with third-party sellers' products. Installing an app does not provide a universal list of channels on which you can publish.

First decide your company's role

ProjectWhat you doWhat needs resolving
SellerOffer products on another company's marketplace.Commercial onboarding, channel requirements, catalogue, stock, orders and fees.
OperatorOpen a marketplace where third parties sell.Seller onboarding, offers, mixed carts, service and financial flows.

A brand wanting to sell on El Corte Inglés or Carrefour usually starts with the first case. A retailer expanding its range through partner sellers is proposing the second. Both may use Mirakl technology, but need different projects.

What the operator connector offers

Mirakl's documentation describes a connector compatible with Shopify Plus for marketplace operation. It covers the required synchronisation between the systems, storefront components and headless integration possibilities.

Before considering implementation, review fit with your commercial model. The connector does not decide seller selection, complaint handling or who finances returns. Turn those rules into testable processes and settings.

Questions an operator must answer

  • Will one order contain your own and third-party products?
  • Can several offers exist for the same product?
  • Who fulfils, invoices and supports each order line?
  • What seller information will buyers see?
  • What happens when part of a mixed purchase is returned?

If you want to sell on other marketplaces

Start with each marketplace's commercial admission and terms. Check supported integrations and whether the chosen seller connector covers that operator, country and category. Not every marketplace uses Mirakl, and not every connector covers every field or event.

Prepare a channel matrix covering required attributes, identifiers, images, prices, availability, shipping and returns. A valid Shopify product may be rejected for lacking a marketplace-specific attribute.

For a strategy covering other channels, the Amazon, TikTok Shop and Miravia synchronisation guide helps establish which system owns each datum. Direct Amazon integration is covered in this focused guide.

Designing the data flow

  1. Choose each datum's source. The ERP may control stock and prices; Shopify, content; and Mirakl, offers or marketplace rules.
  2. Define identifiers. Relate SKU, variant, product and offer without relying on the commercial name.
  3. Document transformations. Units, categories, attributes and pricing rules must be explicit.
  4. Design retries. A connection error must not duplicate orders or lose updates.
  5. Make failures visible. The team needs to know which products or orders are blocked and why.

Synchronisation may be asynchronous. Check delays and statuses rather than promising that everything happens “in real time” under every circumstance.

Tests before opening

  • Create and update a product with variants.
  • Reject an offer missing a required attribute or using an incorrect category.
  • Make simultaneous purchases with little stock remaining.
  • Place a mixed order with several fulfilment parties where the model supports it.
  • Test partial shipping, cancellation, return and partial refund.
  • Recover from a temporary connector failure without duplicates.

Include operations and customer support. A technically correct integration can be difficult to operate if only developers understand the error messages.

Requesting a useful scope and budget

Supply a systems list, representative catalogue, commercial rules and priority channels. Separate standard connection, adaptations, testing, training and maintenance. Request written exclusions: they help compare proposals and prevent dependencies being discovered during launch.

There is no universal implementation time or saving percentage for every catalogue. Through architecture and integration consultancy, we can help identify the project you need and decisions to make before development.

Editorial review: the Migraciones.io team · 30 October 2026. Features, plans and availability are checked against the linked sources.