Send orders to merchants

3PL integrations use the standard Create order endpoint. Add targetTeamId at the top level of the request to choose the merchant that owns the order.

curl --request POST 'https://app.yuzu.so/api/orders' \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: YOUR_3PL_API_KEY' \
  --data '{
    "source": "warehouse-east",
    "sourceId": "WE-1001",
    "targetTeamId": "org_exampleMerchant123456789",
    "order": {
      "orderNumber": "#1001",
      "customer": {
        "firstName": "Jill",
        "lastName": "Blogs"
      },
      "lineItems": [
        {
          "name": "Example product",
          "quantity": 1,
          "sku": "SKU-0001"
        }
      ]
    }
  }'

Targeting rules

• Set targetTeamId to a merchant managed by the authenticated 3PL team. Yuzu rejects unrelated team IDs with 400.
• If you omit targetTeamId or send the parent team's own ID, Yuzu creates the order in the parent 3PL team.
• Sending the same source and sourceId to the same merchant updates the existing order.
• Sending that pair to another merchant creates a separate order. Deduplication does not cross merchant teams.
• Yuzu cannot move an existing order between teams. Validate the merchant ID before ingesting the order.

The returned order key is scoped to the merchant team. Store the returned order ID or key for later reads and print requests.

Onboarding orders

You can connect a production feed while a merchant is still onboarding. Yuzu ingests and renders its orders but pauses automatic printing until the merchant goes live.

Use manual print requests for controlled tests during onboarding. Going live does not print existing orders automatically.

Fetch and print merchant orders

The 3PL API key can use the shared endpoints for its managed merchants:

• Fetch order
• Fetch order status
• Print orders
• Fetch order PDF

For orders with several document types, use document-tag filters and print overrides to route each document to the correct printer and tray.