KommandHub Docs

Appearance

Order Export ​

Send your Shopware orders to the systems that fulfil and account for them — an ERP, a warehouse, an accounting tool or any HTTP API — in exactly the format that system expects, with retries, protection for systems that are down, and confirmation that each order arrived.

Install · Set up targets · Write a mapping · Export orders · Troubleshoot · Developer docs

Version0.9.0-beta.1 · Beta
Shopware6.6, 6.7
PHP8.2+
Plugin nameKmhOrderExportSW
Composer packagekommandhub/order-export-sw
LicenceProprietary
Get itZIP upload, or Composer from the Git repository

What does it do? ​

You describe the document another system expects as a mapping, test it against a real order, and publish it. You configure the receiving system once as an export target with its URL and credentials. Orders are then exported automatically from Flow Builder (for example when an order is placed or paid) or on demand from the order page. Each export is tracked on the order, including whether the other system acknowledged it.

Who it is for: merchants who need orders in an ERP, WMS, accounting or fulfilment system, and the agencies and integrators who connect them.

How it fits into Shopware: it adds three screens under Settings → Extensions, an Order export card on the order page, and an Export order Flow Builder action. Background exports run on Shopware's message queue; acknowledgement timeouts run as a scheduled task.

Key features ​

  • Export targets — endpoint, HTTP method (POST/PUT/PATCH), timeout, TLS check, authentication.
  • Encrypted credentials — API key, Basic, Bearer or OAuth2 client credentials; secrets never leave the database.
  • Testable, versioned mappings — JSON definitions with paths, expressions, filters and functions; render against a real order; publish immutable versions.
  • JSON or XML output.
  • Automatic or manual — Flow Builder action or the order page.
  • Immediate or background per target, with automatic retries for temporary failures.
  • Acknowledgements — none, read from the response, or an asynchronous signed callback with timeout.
  • No duplicates — unchanged orders are not sent again.
  • Circuit breaker — pauses calls to a target that keeps failing.

Requirements ​

Shopware6.6 or 6.7
PHP8.2+ with the sodium extension (bundled by default)
Receiving systemAn HTTP(S) endpoint that accepts JSON or XML, and its credentials
EnvironmentA stable ORDER_EXPORT_ENCRYPTION_KEY (or APP_SECRET)
Background targetsA running message-queue worker
Asynchronous acknowledgementsScheduled tasks running, and the receiving system able to call back

Quick start ​

  1. Set ORDER_EXPORT_ENCRYPTION_KEY, install and activate — Installation.
  2. Create a credential and an export target — Credentials & targets.
  3. Write a mapping, Test mapping against an order, Publish — Mappings.
  4. On any order, Order export card → choose the target → Export.
  5. Add Export order to the Order placed flow — Exporting orders.

Important limitations ​

  • One transport ships: HTTP(S). Other protocols need a developer extension.
  • A target's Sales channels field is not enforced in 0.9.0-beta.1 — scope exports with a flow condition.
  • tax_rate() returns 0 for a list of taxes; use the documented workaround.
  • The receiving system must recompute a payload hash for asynchronous acknowledgements.
  • Uninstalling does not remove the plugin's tables or data.

All known issues: Troubleshooting → Known issues.

Documentation ​

For shop owners and administrators

For integrators

For developers

Shopware resources ​

Support ​

info@kommandhub.com · kommandhub.com/support

Independent integrations. Paystack, Flutterwave, Termii, Sendexa, Africa’s Talking, Twilio and Shopware are trademarks of their respective owners.

© Kommandhub Limited