Fulfillment Webhook Mapping & Tracking Sync - Salp

Fulfillment Webhook Mapping & Tracking Sync

Complete payload guidelines for mapping tracking numbers, carrier codes, and multi-warehouse fulfillment updates back to Saleor.

Last updated: June 3, 2026

The 'warehouseId' parameter is mandatory on all ingestion webhooks to prevent order status synchronization lockups.

Fulfillment Sync Workflow

When you fulfill an order inside your primary e-commerce system (e.g., Lightspeed, Shopify), a fulfillment webhook is triggered and captured by our background worker threads. The tracking number and carrier code must map perfectly to ensure the end customer receives timely, accurate notifications.

Each partner brand is assigned a primary warehouse ID during onboarding. If fulfilling from multiple nodes, ensure the warehouseId passed in the payload matches one of your active profiles.

json

{
  "orderId": "ORD-772910-EU",
  "warehouseId": "wh-amsterdam-primary",
  "fulfillment": {
    "trackingNumber": "1Z999AA10123456784",
    "carrier": "DHL_EXPRESS",
    "shippedItems": [
      {
        "sku": "ELEC-SKU-990",
        "quantity": 1
      }
    ]
  }
}

We support standard codes: DHL_EXPRESS, POST_NL, DPD, UPS, and FEDEX. Using an unsupported code will fallback to general tracking.

Once the webhook payload is parsed, the portal generates a tracking URL and updates the customer storefront order status automatically. This triggers a localized shipment confirmation email.