Principle

For an order to be properly handled for orchestration, it is necessary to fill the field original_ruleset_id or original_ruleset_chaining_id during the POST /order call.

If the original_ruleset_id is provided, the ruleset inquired will be run at the next orchestration. If the original_ruleset_chaining_id is provided, the next orchestration will be run with the ruleset chaining using the delivery promise information coming with the order.

If neither of those ruleset are provided, the the default ruleset set up in the orchestration configuration will be run.

This operation forces the system in charge of importing orders to deliver the right ruleset for every cases.

In case the ruleset is unknown by the importing system during the posting, the orchestration service provides a mechanism to let OneStock assign the right ruleset depending on the use case.

The attribution can be done using the order fields allowing to assign the ruleset depending on properties embedded by the order (Delivery type, Sales Channel, Destination etc…).

As soon as the orchestrator detects that no ruleset is provided, the attribution mechanism is run.

Configuration

Before setting up an assignation for the orchestration of orders, the following configurations must already be set up :

• Ruleset

• Ruleset chaining

• Lifecycle of orders

• Sales Channel

• Stock locations

  • Tags

  • Calendars

A tab dedicated to assignation of rulesets is available in the Orchestration page.

The Assignation tab display a search bar, an assignation add button, and the ruleset assignations available.

Assignations are displayed in the same order they are run to define the right ruleset for an orchestration.

The sequence of the assignations has an impact on the behaviour of the service. It is then possible to re-order the assignations by drag and droping an attribution.

The orchestration runs each assignation depending on the conditions set up, and assign the ruleset as soon as a matching condition is detected. The last attribution is conditionless and let an order being orchestrated with a default ruleset if no match is encounter.

Adding an attribution is done by clicking on the dedicated button.

An attribution can be named, and a Ruleset or a Ruleset Chaining must be chosen.

When created, the assignation can be modified with two type of parameters :

• Conditions

• Options

When a condition is modified, it can either being modified on the same line which add a condition to verify on the same level (logical AND), or on a new line which add a condition to verify in parallel (logical OR).

The available conditions to compare are the following :

• Order type

• Sales channel

• Delivery type

• Order price

• Item quantity

• Item price

• Carrier name and option

• Destination (Country, zipcode, region)

• Origin (Country, zipcode, region)

• Has a delivery promise

The option allow to define a period date for the assignation to be active.

If not defined, the assignation will always be running.