Order import

Order import is the inbound side of the integration. It checks the operator for new and changed orders, creates them as Shopware orders, and on the very first run also pulls in everything that hangs off those orders (messages, documents, invoices, transaction logs).

Scheduled import (the default)

In normal operation you don’t need to do anything. By default the plugin checks each active connection for new orders every 30 minutes (configurable: 2, 5, 10, 15, 30 or 60 minutes under Order Import Interval in Mirakl → Settings → Sync).

On each run, for every connection where order import is on:

1. The plugin asks the operator for orders that changed since the last successful check.
2. Each returned Mirakl order is turned into a Shopware order:
   • If the matching Shopware order doesn’t exist yet, it’s created in the connection’s sales channel.
   • If it already exists, its Mirakl status and stored data are refreshed.
3. The next check picks up where this one left off, so the same orders aren’t re-processed.

Manual full import

From Dashboard → Quick Actions → Import Orders Now — runs a one-off import for the chosen connection straight away. Useful when you’ve just changed mappings and want to verify the result, or when you’ve moved the initial import date back.

First run: related data also imported

The first time a connection imports orders, the plugin also chains four follow-up imports automatically:

• Order messages — every message thread for the imported orders.
• Order documents — every document attached to those orders.
• Invoices — every operator invoice in scope.
• Transaction logs — every transaction record.

Each follow-up runs in the background with its own progress. After this initial sweep, each topic gets handled by its own scheduled task (see Order messages, Order documents, Invoices, Transaction logs).

How far back to import — the initial import date

You decide per connection how far back the first order import should look:

• Setup wizard, step 12 (Import Orders) — choose Import all historical orders (no date filter) or Import orders from a specific date with a date picker. Clicking Next saves the choice on the connection and starts the first import immediately.
• Need to change it later? Re-open the wizard from Mirakl → Settings → Connections → row context menu → Run Setup Wizard, then skip ahead to Import Orders.

The safest choice is the day before the operator’s go-live for your account. Earlier dates can pull years of historical orders that the operator may have left in a draft state — those usually fail to materialise cleanly because the products they refer to no longer match anything in your shop.

Where to configure

Mirakl → Settings → Sync tab, Sync Settings card:

• Enable Order Import — master switch. Default: on.
• Order Import Interval — how often the scheduled check runs. Default: 30 minutes.

What the Shopware order looks like

• Line items come from the Mirakl payload, matched back to Shopware products through the operator’s product references.
• Shipping and billing addresses are copied as-is from the Mirakl order.
• The order state matches the operator’s status, translated through the Order Status Mapping you configured on the connection (wizard step 9 or row context menu → Order Status Mapping). When you later transition the Shopware order, those changes go back to Mirakl via the Reverse Status Mapping (wizard step 10) — see Order state sync.

You can view imported Mirakl orders from Dashboard → Quick Start → Orders (the Imported Orders list).

Tips & gotchas

Tip

Set the initial import date to the day before the operator’s go-live for your account. Earlier dates pull historical orders the operator may have left in a draft state for years — those usually fail to materialise cleanly because their product references no longer resolve.

Caution

If you delete a connection, the records linking its Mirakl orders back to Shopware are removed. The Shopware orders themselves are kept, but they lose the connection to Mirakl — state changes will no longer push back to the operator. Once a connection has imported orders, pause or rename it instead of deleting it.

Note

The initial follow-up imports (messages, documents, invoices, transaction logs) run in sequence per connection, not in parallel — each one talks to its own operator endpoint. On a connection with years of history this can take a long time. The imports run in the background, so you can close the wizard right after the final step.

Caution

If the operator is rate-limiting you, the current run finishes early with a note in the logs (“Rate limited, will resume on next scheduled run”). The next scheduled check picks up where this one stopped — no manual action needed.

Related

• Order state sync — push ship / refuse / track / accept from Shopware to Mirakl
• Order messages — pulled automatically on initial import
• Order documents — pulled automatically on initial import
• Invoices — pulled automatically on initial import
• Transaction logs — pulled automatically on initial import
• Order refresh — refresh a single order on demand
• Background tasks — how the scheduled checks decide what to run