Automatic order import

Technical documentation for the interface connection — for Enterprise customers and their IT.

This interface runs on your own installation, not on our servers — once you have purchased and set up the warehouse system, your shop or ERP system sends orders directly to your own domain. Available with a license that includes the "Interface" module (Enterprise). Only one provider can be active at a time, configured under Settings → Interface in your installation.

Setup

In your installation, go to Settings → Interface and choose a provider — a secret is generated automatically and the matching webhook URL is displayed:

POST https://ihre-domain.de/api/webhook/orders/{anbieter}
X-Webhook-Secret: <automatisch erzeugtes Secret>

Supported providers

🔗 Generischer Webhook

No vendor signature standard exists. The external system sends the "X-Webhook-Secret" header along with the generic JSON format (see below).

🛍️ Shopify

Under Settings → Notifications → Webhooks: event "Order creation", enter the webhook URL. Store the secret as the "Webhook signing secret" — Shopify signs every delivery in the "X-Shopify-Hmac-Sha256" header (HMAC-SHA256, base64).

🛒 WooCommerce

Under Settings → Advanced → Webhooks: topic "Order created", enter the webhook URL as the delivery URL. Store the secret as the secret — WooCommerce signs in the "X-WC-Webhook-Signature" header (HMAC-SHA256, base64).

🧩 Shopware 6

Under Settings → System → Webhooks: event "checkout.order.placed", enter the webhook URL, include the payload with customer/address/line items (incl. SKU). Store the secret as the app secret — Shopware signs in the "shopware-shop-signature" header (HMAC-SHA256, hex).

🅿️ PrestaShop

PrestaShop has no webhook menu in its core — a small module on the "actionValidateOrderAfter" hook sends the order as JSON with the "X-Webhook-Secret" header to the webhook URL. Module template available on request via our contact form.

📊 JTL-Wawi

In JTL-Wawi, set up a workflow that sends an HTTP action with the "X-Webhook-Secret" header and customer/line-item data in the generic JSON format to the webhook URL upon payment receipt.

Generic JSON format

All providers are translated internally into this format. For the generic webhook, PrestaShop and JTL-Wawi, it is also the directly expected format:

{
  // optional, wird sonst automatisch vergeben
  "order_number": "SHOP-10234",
  "kunde": {
    "name": "Muster GmbH",
    "email": "einkauf@muster-gmbh.de",
    "strasse": "Beispielweg 12",
    "plz": "12345",
    "ort": "Musterstadt",
    "land": "Deutschland"
  },
  "positionen": [
    { "sku": "ART-1001", "menge": 3 },
    { "sku": "ART-2044", "menge": 1 }
  ],
  // alle drei optional
  "versandart": "dhl",
  "liefertermin": "2026-09-20",
  "notizen": "Bitte bis 12 Uhr liefern"
}

Response

On success the endpoint responds with HTTP 200 and the assigned order number; on a problem, with a matching error code and a plain-text error message:

// 200 OK
{ "ok": true, "order_number": "SHOP-10234" }

// 401 / 404 / 422 bei Problemen
{ "ok": false, "error": "Artikel mit SKU \"ART-9999\" ist im Lagersystem nicht bekannt." }

Good to know

Every SKU must exactly match the item number or barcode of a product already created in the warehouse system — an unknown SKU aborts the entire import with an error (no partial import).
The interface imports incoming orders — there is currently no inventory feedback to the shop (no automatic stock-level updates in the webshop).
Every import attempt (successful or failed) is logged and visible under Settings → Interface.

Questions about the integration or your ERP system? Get in touch →