Page Comparison

...

We recommend that you separate orchestration requests according to delivery type. In our example, we have 3 types of delivery: Ship From Store, Click & Collect standard and Click and Collect express.

For better consistency, we recommend you adopt the following naming convention : orchestration_{detailed/unified}_{delivery type}_{country/sales channel)

• Ship From Store:

  • orchestration_detailed_sfs - This query can be created at the root to target the stocks available for SFS orchestration. It can be used in rulesets that do not make differences between countries or sales channels. It should contain two aggregates "stores" and "warehouses" which are the two order fulfillment paths.
    - The “stores” aggregate should contains the items_sfs item items query, which lists items eligible for order-taking, and the stores_sfs stock locations query, which lists stores with the Ship From Store module enabled.
    - The “warehouses” aggregate should also The parameter “Force usage of stock location filter requested” must be disabled for the stock locations query.
    - The “warehouses” aggregate should also use the items_sfs item items query, and the warehouses_sfs stock locations query, which lists warehouses with the Ship From Store module enabled. The parameter “Force usage of stock location filter requested” must be disabled for the stock locations query.
    All aggregate deductions can be activated (buffers, reservations and unavailabilities) as well as the global reservations parameter.
    FinallyThen, the unified query orchestration_unified_sfs can be created by inheriting from the detailed one. Only the “Unification” parameter should be changed (unification by sock locations and stock types enabled).

  • orchestration_detailed_sfs_{country} - This query can be created by inheriting from the previous one to target a particular country or sales channel. The same two aggregate identifiers, "stores" and "warehouse", can be kept.
    If we consider that the warehouse can deliver to any country, then the "warehousewarehouses" aggregate can remain unchanged. However, we need to modify the "stores" aggregate so that it uses the stores_sfs_{country} stock locations query to target only stores in the chosen country.
    FinallyThen, the unified query orchestration_unified_sfs_{country} can be created by inheriting from the detailed one. Only the “Unification” parameter should be changed (unification by sock locations and stock types enabled).

➡️ Here's what the Ship From Store orchestration requests queries might look like, differentiating between the two countries "FR" and "UK".

...

• Click and Collect express:

  • orchestration_detailed_ckc_exp - This query can be created at the root to target only the pick-up store.

• Click and Collect standard:

  • orchestration_detailed_ckc_std - This query can be created at the root to target the stocks available for standard Click and Collect orders, whether the stock is directly available in the pick up store or sent from another stock location. It can be used in rulesets that do not make differences between countries or sales channels. It should contain 3 aggregates "stores", "warehouses" and “destination_store” which are the three order fulfillment paths.

...

• • As there will be no shipping, it should contain only one aggregate “destination_store” regardless of the country or the sales channel.
    - The “destination_store” aggregate should use the items_ckc items query, and the stores_cfs stock locations query which lists stores enabled in Collect From Store (in-store pick-up). Since we want to target ONLY the destination store, we'll need to enable the parameter “Force usage of stock location filter requested” for the stock locations query.
    Then, the unified query orchestration_unified_ckc_exp can be created by inheriting from the detailed one. Only the “Unification” parameter should be changed (unification by sock locations and stock types enabled).

➡️ The result is a single pair of stock queries for Click & Collect express, regardless of country or sales channel.

(image)

• Click and Collect standard:

  • orchestration_detailed_ckc_std - This query can be created at the root to target the stocks available for standard Click & Collect orders, whether the stock is directly available in the pick up store or sent from another stock location. It can be used in rulesets that do not make differences between countries or sales channels. It should contain 3 aggregates "stores", "warehouses" and “destination_store” which are the three order fulfillment paths.
    - The “stores” aggregate should contains the items_ckc items query, which lists items eligible for Click & Collect, and the stores_sfs stock locations query, which lists stores with the Ship From Store module enabled who will be able to ship the order to the pick-up store. The parameter “Force usage of stock location filter requested” must be disabled for the stock locations query.
    - The “warehouses” aggregate should also use the items_ckc items query, and the warehouses_sfs stock locations query, which lists warehouses with the Ship From Store module enabled who will be able to ship the order to the pick-up store. The parameter “Force usage of stock location filter requested” must be disabled for the stock locations query.
    - The “destination_store” aggregate should also use the items_ckc items query, and the stores_cfs_not_sfs stock locations query which lists stores enabled in Collect From Store (in-store pick-up) but not enabled in Ship From Store otherwise they will be double-counted with the "stores" aggregate. Since we want to target ONLY the destination store, we'll need to enable the parameter “Force usage of stock location filter requested” for the stock locations query.
    All aggregate deductions can be activated (buffers, reservations and unavailabilities) as well as the global reservations parameter.
    Then, the unified query orchestration_unified_ckc_std can be created by inheriting from the detailed one. Only the “Unification” parameter should be changed (unification by sock locations and stock types enabled).

  • orchestration_detailed_ckc_std_{country} - This query can be created by inheriting from the previous one to target a particular country or sales channel. If we consider that the warehouse can deliver to any country, then the "warehouses" and “destination_store” aggregates can remain unchanged. However, we need to modify the "stores" aggregate so that it uses the stores_sfs_{country} stock locations query to target only stores in the chosen country.
    Finally, the unified query orchestration_unified_ckc_std_{country} can be created by inheriting from the detailed one. Only the “Unification” parameter should be changed (unification by sock locations and stock types enabled).

➡️ Here's what the standard Click & Collect queries might look like, differentiating between the two countries "FR" and "UK".

...

For stock export

Stock exports requested from Onestock by websites allow product availability to be updated.

In general, stock exports are separated by sales channels and/or different websites. For example, if both UK and FR websites exist in your project, you will need to configure independent stock export flows between UK and FR.

For each sales channel, you will need to set up unified/detailed and full/diff queries.

• export_detailed_{country}_full - This query can be created at the root to target the details of all stocks available for delivery. As the Ship From Store orchestration query, it should contain two aggregates "stores" and "warehouses" which are the two scopes of stock availability.
  - The “stores” aggregate should contains the items_sfs items query, which lists items eligible for order-taking, and the stores_sfs_export stock locations query, which lists stores eligible for export with the Ship From Store module enabled. The parameter “Force usage of stock location filter requested” can be enabled for the stock locations query, this will allow you to filter on specific stock locations if necessary.
  - The “warehouses” aggregate should also use the items_sfs items query, and the warehouses_sfs_export stock locations query, which lists warehouses eligible for export with the Ship From Store module enabled. The parameter “Force usage of stock location filter requested” can be enabled for the stock locations query, this will allow you to filter on specific stock locations if necessary.
  All aggregate deductions can be activated (buffers, reservations and unavailabilities) as well as the global reservations parameter.Then, the export parameter should be enabled
  
  Finally, the unified query export_unified_{country}_full can be created by inheriting from the detailed one. Only the "Unification" parameter should be changed (unification by sock locations and stock types enabled).
  

• export_detailed_{country}_diff
  export_unified_{country}_diff

For the OIS catalog

For e-reservation

...