Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Order in Store catalog: These queries provide the availability of products in the Store App catalog. The “immediate pickup” availability is based on the detailed query, and the “ordering” availability is based on the unified query

    • ois_detailed - This query is only used to provide the “immediate pickup” availability, and so can be created at the root to target the current OIS store. It should only contain one aggregate "ois_stores"
      - The “ois_stores” aggregate should use the items_ois items query, and the stores_ois stock locations query which lists stores enabled in Immediate Pickup. Since we want to target ONLY the current store, we'll need to enable the parameter “Force usage of stock location filter requested” for the stock locations query because the store app will add the filter to the query.

    • ois_unified_{saleschannel} - Then, the unified query is used to provide the “ordering” availability on a given sales channel. This query should looks like the export_unified_{saleschannel}_full one, because we will set up the same aggregates (“stores” and “warehouses” enabled for export). The parameter “Force usage of items filter requested” must be enabled for both aggregates.
      However, the export parameter must not be enabled (if a scope key is set, this may affect diff exports).

...

  • E-reservation:

...

  • Delivery promise:

...

Full stock queries tree

This is what our stock queries tree should look like.

...

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

...

    • The unification parameter must be enabled (unification by stock types and stock locations).

➡️ Here's what the OIS queries might look like, with a single detailed query at the root, and two unified queries for the two sales channels/websites FR and UK. The UK inherits from the FR, and only the “stores” aggregate is changed.

...

  • E-reservation:

...

  • Delivery promise:

...