Skip to content

Order refresh

Refresh from Mirakl is a one-off action on a single Mirakl order. It asks the operator for that order’s current state and updates the local copy in Shopware. Use it when scheduled order import has not caught a change yet, or when you suspect Shopware has drifted from what the operator shows.

You can trigger the refresh from two places.

From the Shopware order detail page — open the Shopware order. At the top of the page the plugin shows a Mirakl order info panel; click Refresh from Mirakl.

From the Mirakl Orders detail page — open Mirakl Dashboard → Quick Start → Orders, pick a row, choose View Details from its context menu. On the Order Information card click Refresh from Mirakl.

Either way the page calls the operator, updates the local order data and shows a progress dialog. When the refresh completes you get one of two notifications: Order data refreshed from Mirakl. on success, Failed to refresh order data. on failure.

There is no multi-select “Refresh selected” button on the Mirakl Orders list — refresh is always one order at a time.

Refresh pulls the operator’s current view of the order and updates:

  • the Mirakl Status of the order (for example a move from waiting acceptance to shipping),
  • the shipping and billing addresses (in case the buyer corrected them),
  • the full raw data the operator returns,
  • the Shopware order’s state if the Mirakl status maps to a different Shopware status under your order-status mapping.

It does not re-create line items. If the buyer modified the items themselves (cancelled a single line, added a line — depending on the operator), verify and adjust those by hand from the operator’s seller panel.

  • Before invoicing — make sure the buyer has not requested a refund or address change between the order placement and your invoicing run.
  • After you got an external notification — if the operator sent you an email or push notification that a buyer cancelled, but the order in Shopware still shows the old status, a refresh closes the gap immediately rather than waiting for the next scheduled run.
  • Debugging address issues — if the shipping carrier rejected the delivery address, refresh first so you are looking at the operator’s current data and not a snapshot from the moment the order was imported.

Refresh shares the same per-operator request budget as the regular bulk import — a refresh waits its turn if too many other operator calls are in progress at the same time. In practice this is invisible: the refresh just completes a moment later when the budget clears.

A single refresh is one small request and has no real impact on the operator quota, even if you fire it many times a day.