Configuration

Delivery settings overview

Delivery configuration is spread across two areas in Omnium:

• Delivery-specific settings — Delivery numbering, status management, and export connectors (documented on this page)
• Purchase order settings — Goods reception behavior, internal transfers, and ETA propagation (documented under Purchase Order Configuration)

Most delivery-related settings are configured through Settings > Purchase Order Settings in the Omnium UI.

Delivery numbering

Delivery IDs are generated automatically using the Number Options system. The number type used for deliveries is DeliveryNumberOptions.

When a delivery is created without an explicit ID, Omnium looks up the number options configuration:

1. Check the selected market for a DeliveryNumberOptions entry
2. If not found, check the generic number options
3. If no configuration exists, fall back to a sequential number starting at 1

Default behavior

If no DeliveryNumberOptions is configured, deliveries use the following defaults:

Configuration

Delivery numbering is configured as a number option entry on the market or in the generic number options. See Number Options for the full configuration model.

Sample

{
  "NumberType": "DeliveryNumberOptions",
  "Key": "DeliveryNumber",
  "StartSequence": 10000,
  "Prefix": "DEL-",
  "Service": "SequentialNumberService",
  "IsReadOnly": true
}

This produces delivery IDs like DEL-10000, DEL-10001, DEL-10002, etc.

Goods reception settings

These settings control what happens after goods reception is processed. They are part of PurchaseOrderSettings and configured through Settings > Purchase Order Settings in the Omnium UI.

Purchase order completion

When configured, the purchase order workflow is executed for the new status, running any configured workflow steps (e.g., ATP recalculation, export).

Shipment order status update

After goods reception, Omnium can automatically update the shipment-level order status for customer orders that were waiting for the received goods. This is useful for triggering downstream workflows (e.g., moving orders to a "Ready to ship" status).

When GoodsReceptionRunShipmentWorkflow is enabled (the default), setting the shipment order status also triggers the order type's workflow for that status. This allows you to chain actions — for example, automatically sending a "ready for pickup" notification when goods arrive.

When disabled, only the status value is updated without running the workflow. This is useful if you want to update the status for visibility but handle further actions separately.

Sample

"PurchaseOrderSettings": {
  "GoodsReceptionCompletedStatus": "Completed",
  "GoodsReceptionShipmentOrderStatusUpdate": "ReadyToShip",
  "GoodsReceptionRunShipmentWorkflow": true
}

Estimated time of arrival

When the ETA is set on a delivery, it is used by the ATP system to calculate when inventory will become available. This affects customer-facing delivery estimates and order allocation decisions.

Sample

"PurchaseOrderSettings": {
  "SetEstimatedTimeOfArrivalFromPurchaseOrder": true
}

Internal transfers for pickup warehouses

When goods are received at a central warehouse but customer orders are destined for a different pickup location, Omnium can automatically create internal transfer purchase orders to move the stock.

How it works

During goods reception, when this setting is enabled:

1. Omnium identifies customer orders reserved against the received purchase order lines
2. For orders where the shipment's PickUpWarehouseCode differs from the delivery warehouse, a transfer is needed
3. For each unique target warehouse, an internal transfer purchase order is created
4. Line items are copied with the required quantities (grouped by SKU)
5. Customer order reservations are reallocated from the original purchase order to the new internal transfer
6. The order line keeps IsAwaitingPurchaseOrder = true until the internal transfer is completed

Sample

"PurchaseOrderSettings": {
  "CreateInternalTransfersForPickUpWarehouses": true,
  "CreateInternalTransfersForPickUpWarehousesStatus": "New"
}

Automatic order line splitting

When a delivery is created and the available quantity for a purchase order line is less than what is reserved by customer orders, the order lines with excess reservations are automatically split. The portion matching the available quantity can proceed to fulfillment, while the remainder stays reserved against the purchase order.

This only applies to orders with an order type included in this list. If the list is empty or not configured, automatic splitting is disabled.

Sample

"PurchaseOrderSettings": {
  "OrderTypesWithAutomaticLineSplitting": ["Online", "ClickAndCollect"]
}

Delivery status management

Delivery status is automatically calculated based on the quantities on the associated purchase order lines. See Delivery Lifecycle for details on how statuses are determined.

Disabling automatic status

Automatic status calculation can be disabled per delivery by setting IsAutoDeliveryStatusDisabled to true on the delivery. This is a per-delivery setting, not a tenant-level configuration.

When disabled:

• The delivery status is not automatically updated during goods reception
• The status must be managed manually via the API or UI
• The status must be a valid delivery status (New, Confirmed, InProgress, Completed, OnHold, Cancelled)

This is useful when external systems manage the delivery lifecycle and Omnium should not override the status.

Delivery exports

Deliveries can be exported to external systems using delivery export connectors. When a delivery is created or updated, configured exporters are triggered automatically.

Delivery export connectors are configured as part of the connector setup in Omnium. The available connectors depend on which integration modules are enabled for your tenant.

Delivery exports can also be triggered as a purchase order workflow step using the ExportDeliveries action. This runs all configured delivery export connectors for deliveries associated with the purchase order. See Purchase Order Statuses for workflow step configuration.

Complete configuration example

Below is a comprehensive example showing all delivery-related settings configured together:

{
  "PurchaseOrderSettings": {
    "GoodsReceptionCompletedStatus": "Completed",
    "GoodsReceptionShipmentOrderStatusUpdate": "ReadyToShip",
    "GoodsReceptionRunShipmentWorkflow": true,
    "SetEstimatedTimeOfArrivalFromPurchaseOrder": true,
    "CreateInternalTransfersForPickUpWarehouses": true,
    "CreateInternalTransfersForPickUpWarehousesStatus": "New",
    "OrderTypesWithAutomaticLineSplitting": ["Online", "ClickAndCollect"]
  }
}

Delivery numbering is configured separately as a number option:

{
  "NumberOptions": [
    {
      "NumberType": "DeliveryNumberOptions",
      "Key": "DeliveryNumber",
      "StartSequence": 10000,
      "Prefix": "DEL-",
      "Service": "SequentialNumberService",
      "IsReadOnly": true
    }
  ]
}