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:

  • The orchestration_detailed_sfs - This query can be created at the root , containing two aggregates stores and warehouses which will be 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 “stores” aggregate should contains the items_sfs item 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 “warehouses” aggregate should also use the items_sfs item query, and the warehouses_sfs stock locations query, which lists warehouses with the Ship From Store module enabled.
    All aggregate deductions can be activated (buffers, reservations and unavailabilities) as well as the global reservations parameter.
    

    The

    Finally, the unified query orchestration_unified_sfs can be created by inheriting from

    orchestration_

    the detailed

    _sfs

    one. Only the “Unification” parameter should be changed (unification by sock locations and stock types enabled).

  • orchestration_detailed_sfs_

    fr

    • orchestration_unified_sfs_fr

  • orchestration_detailed_sfs_uk

    • orchestration_unified_sfs_uk

  {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 "warehouse" 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.

Voir si exemple en photo

• Click and Collect express:

...

• detailed

  • unified

• orchestration_detailed_sfs

  • orchestration_unified_sfs

  • orchestration_detailed_sfs_fr

    • orchestration_unified_sfs_fr

  • orchestration_detailed_sfs_uk

    • orchestration_unified_sfs_uk

• orchestration_detailed_ckc_exp

  • orchestration_unified_ckc_exp

  • orchestration_detailed_ckc_exp_fr

    • orchestration_unified_ckc_exp_fr

  • orchestration_detailed_ckc_exp_uk

    • orchestration_unified_ckc_exp_uk

• orchestration_detailed_ckc_std

  • orchestration_unified_ckc_std

  • orchestration_detailed_ckc_std_fr

    • orchestration_unified_ckc_std_fr

  • orchestration_detailed_ckc_std_uk

    • orchestration_unified_ckc_std_uk

• export_detailed_fr_full
  export_unified_fr_full
  export_detailed_fr_diff
  export_unified_fr_diff
  export_detailed_uk_full
  export_unified_uk_full
  export_detailed_uk_diff
  export_unified_uk_diff

• ois_detailed_fr
  ois_unified_fr
  ois_detailed_uk
  ois_unified_uk

• eresa_detailed_fr
  eresa_unified_fr
  eresa_detailed_uk
  eresa_unified_uk

• dp_detailed_fr_method1
  dp_unified_fr_method1
  dp_detailed_fr_method2
  dp_unified_fr_method2
  dp_detailed_uk_method1
  dp_unified_uk_method1
  dp_detailed_uk_method2
  dp_unified_uk_method2

• in_stock

(image KO)

...