Appearance
Exporting orders
For merchants
Manually, from the order
On the order's General tab, the Order export card lists every target the order was exported to, with its state and revision.
- Choose an export target.
- Click Export.
The result is shown immediately. A manual export from this card always runs immediately, even for a target set to asynchronous.
- Retry — try a failed export again.
- Re-export — send the order again even though it was already exported (for example after correcting it in the other system). It creates a new revision.
Automatically, with Flow Builder
- Settings → Flow Builder (Shopware: Flow Builder) → open or create a flow, e.g. Order placed or Order payment: Paid.
- Add the action Export order and choose the target.
- Save.
The flow uses the target's execution mode — immediately, or queued for a background worker. A failing export never stops the rest of the flow; the failure is recorded on the order.
Pick the right moment
Export on Order placed if the receiving system needs every order; on Payment paid if it should only see paid orders. Use Flow Builder conditions (rules) to export only certain orders.
Limit exports to certain sales channels
Targets have a Sales channels field, but in 0.9.0-beta.1 it is not checked when an export runs. To export only one sales channel's orders, add a condition to the flow — for example a rule Sales channel is … — before the Export order action. Creating rules: Shopware: Rule Builder.
Export states
| State | Meaning |
|---|---|
| Open | Created, not sent yet. |
| Exported | Sent and accepted. |
| Awaiting acknowledgement | Sent; waiting for the other system's callback (asynchronous acknowledgement). |
| Acknowledged | The other system confirmed it. |
| Failed | Not delivered, rejected, or not acknowledged in time. |
After an export the card shows the outcome: exported; exported and acknowledged; exported and awaiting acknowledgement; already up to date — nothing to send (the rendered order is identical to the last successful export); or failed.
Retries and failures
For asynchronous targets:
- Temporary problems — connection errors, timeouts,
408,429,5xx— are retried automatically with increasing delays. - Permanent problems — a mapping that cannot render the order, a deleted order, invalid credentials — are not retried; the message goes straight to Shopware's failed queue.
- If a target fails 5 times in a row, the plugin stops calling it for 60 seconds (circuit breaker) so a backlog does not hammer a system that is down. Exports in that window fail fast and are retried later.
For synchronous targets the export is tried once; use Retry on the order card.
An export waiting for acknowledgement longer than its Acknowledgement timeout (default 1 hour) is marked Failed by a scheduled task that runs every 5 minutes.