⚙️ Introduction

This job allows the creation and update of Orders via CSV import or API Connector.

You can:

• Create new External Orders
• Add Order Lines to existing Orders
• Update existing Order Lines
• Update the status of an Order
• Remove Order Lines

💡

Order Data Model

In DJUST, an Order is composed of two key components:

• Order Logistic: A logical grouping of one or more Order Lines
• Order Line: Represents a single purchased product, including its offer and quantity

📂 Import model

CSV Structure

The CSV file must contain one row per Order Line. Multiple rows may belong to the same Order Logistic.

📄

Template

You can use the following spreadsheet as a template to structure your import:

Orders - Template

API Connector

The API Connector sends data as a JSON payload. The JSON must always be a list of objects, regardless of the use case (create, update, delete).

[
  {
    "orderExternalId": "string",
    "orderReference": "string",
    "orderStatus": "string",
    "accountExternalId": "string",
    "customerExternalId": "string",
    "supplierExternalId": "string",
    "shippingAddressFullName": "string",
    "shippingAddressCountry": "string",
    "shippingAddressStreetName": "string",
    "shippingAddressCity": "string",
    "shippingAddressZipCode": "string",
    "shippingAddressState": "string",
    "shippingAddressAdditional": "string",
    "orderLines": [
      {
        "orderLineExternalId": "string",
        "orderLineId": "string",
        "offerPriceExternalId": "string",
        "variantExternalId": "string",
        "variantName": "string",
        "variantDescription": "string",
        "classificationExternalId": "string",
        "orderLineQuantity": 0,
        "netUnitPrice": 0,
        "grossUnitPrice": 0,
        "taxAmount": 0,
        "markOrderLineForDeletion": false
      }
    ]
  }
]

📋 Fields

☑️

Conditionally required

¹ These fields become required if at least one of them is provided. This rule does not apply to Shipping Address State or Shipping Address (Additional).

⚠️

Required Custom Fields

Any custom fields configured as required in DJUST must also be included.

Order Identification

Each order must be identified using at least one of the following fields:

If both are provided, Order Reference takes precedence.

💡

Order External Id is mandatory when creating an order. Order Reference can only be used when updating an existing order.

Order Line Identification

Each order line must be identified using at least one of the following fields:

To create a new line, Order Line External Id is required. To update an existing line, provide at least one of these fields.

🧠 Key Business Rules

Use cases and required fields

Create an External Order

Required fields: Order External Id, Account External Id, Customer External Id, Supplier External Id, Order Line External Id, Offer Price External Id (or Variant External Id), Order Line Quantity, Net Unit Price.

Update an External Order or its Lines

Required fields: Order External Id (or Order Reference), Order Line External Id (or Order Line Id).

Update an Internal Order

An Internal Order is an order created natively in DJUST (not imported from an external system). You can update it by providing Order Reference to identify it, along with the fields to update. Order External Id and Order Line External Id can be set on an Internal Order at any time.

Update an Order Status

Provide Order External Id (or Order Reference) and set Order Status to the desired target status. Status updates must follow the order lifecycle sequence.

Data format

• Net Unit Price and Gross Unit Price must be numeric, using a dot (.) as decimal separator. Example: 12.50
• Order Line Quantity must be a positive integer. Example: 3

Uniqueness

• Order External Id and Order Line External Id must be unique across all orders.

Import execution order

The processing of imported data does not follow a strict FIFO order. If the same Order Line appears multiple times within a single import with different values, the final result may not reflect the last occurrence. Avoid sending duplicate Order Lines with conflicting updates within the same import execution.

Dependencies

• If both Offer Price External Id and Variant External Id are provided, the variant must exist in DJUST and be linked to the provided offer.
• If any shipping address field is provided (Full Name, Country, Street Name, City, or Zip Code), then all of them become required.

Update rules based on Order Logistic status

General requirements

• An Order must contain at least one Order Line.
• An Order Line from an External Order can reference a product not imported in DJUST.
• An External Order must reference at least one Supplier and one Account existing in DJUST.

📌

Best Practices

✔️ Always use Order External Id when creating orders from an external system.

✔️ Ensure the mapping matches DJUST's fields before running the import.

✔️ Validate data format (prices, quantities) before upload.

✔️ Avoid duplicate Order Lines with conflicting values in the same import file.