Page Comparison

...

• 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 contain the items_sfs 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 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 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.

    • Then, the unified query Aggregates deductions: stock locations reservations and unavailability should be enabled, buffers should be disabled.

  • orchestration_unified_sfs - The unified query can be created by inheriting from the detailed one.

    Only the “Unification”

    • Settings : global reservations should be enabled, and 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 detailed previous one to target a particular country or sales channel. If we consider that the warehouse can deliver to any country, then the "warehouses" 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.

  • Then, the unified query

    orchestration_unified_sfs_{country} - The unified query can be created by inheriting from the detailed one.

    Only the “Unification”

    • Settings : global reservations should be enabled, and the unification parameter should be changed (unification by sock locations and stock types enabled).

...

• Click and Collect express:

  • orchestration_detailed_ckc_exp - This query can be created at the root to target only the pick-up store. 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.All aggregate deductions can be activated (buffers, reservations and unavailabilities) as well as the global reservations parameter.

    • Then, the unified query Aggregates deductions: stock locations reservations and unavailability should be enabled, buffers should be disabled.

  • orchestration_unified_ckc_exp - The unified can be created by inheriting from the detailed one.

    Only the “Unification”

    • Settings : global reservations should be enabled, and the unification parameter should be changed (unification by sock locations and stock types enabled).

...

• 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 contain 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 Aggregates deductions: stock locations reservations and unavailability should be enabled, buffers should be disabled.

  • orchestration_unified_ckc_std - The unified query can be created by inheriting from the detailed one.

    Only the “Unification”

    • Settings : global reservations should be enabled, and 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 detailed 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.

  • Then, the unified query

    orchestration_unified_ckc_std_{country} - The unified query can be created by inheriting from the detailed one.

    Only the “Unification”

    • Settings : global reservations should be enabled, and the unification parameter should be changed (unification by sock locations and stock types enabled).

...

• export_detailed_{saleschannel}_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 contain the items_sfs items query, which lists items eligible for order-taking, and the stores_sfs_{saleschannel}_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_{saleschannel}_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.
  Next

  • Aggregates deductions: all deductions should be enabled (stock locations reservations, unavailability, and global and stock locations buffers).

  • Settings: global reservations should be enabled. Then, the export parameter should be enabled with the “Full” option. A scope key must be specified to identify the perimeter of the export and must be identical to the diff export. It could be, for example “detailed_fr”.Then, the unified query

• export_unified_{saleschannel}_full The unified query can be created by inheriting from the detailed one.

  The

  Aggregates must remain unchanged.

  • Settings: the unification parameter should be changed (unification by sock locations and stock types enabled), and also the scope key of the export parameter. It could be, for example “unified_fr”.

• export_detailed_{saleschannel}_diff - This The Diff query can be created by inheriting from the “Full” detailed full one. Aggregates must remain unchanged.However,

  • Settings: the export parameter must be changed to "Diff". Make sure the scope key remains the same as the full query, in my example “detailed_fr”. Then, the "Export stock difference instead of raw value" parameter can be activated or deactivated as needed for your project.Then, the unified query

• export_unified_{saleschannel}_diff The unified Diff query can be created by inheriting from the Diff detailed one.

  The

  • Settings: the unification parameter should be changed (unification by sock locations and stock types enabled), and also the scope key of the export parameter. It could be, for example “unified_fr”.

...

• 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 "pickup_store"
    - The “pickup_store” 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.

    • Aggregates deductions: all deductions should be enabled (stock locations reservations, unavailability, global and stock locations buffers).

  • 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

    • Aggregates deductions: all deductions should be enabled (stock locations reservations, unavailability, global and stock locations buffers).

    • Settings : global reservations should be enabled. The export parameter must not be enabled (if a scope key is set, this may affect diff exports).

    
    

    • 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: These queries provide the availability of products in the Onestock’s e-reservation funnel in the website. The unified query is used to display or not the product as available for e-reservation, and the detailed one displays the list of available stores.

  • eresa_detailed - _{saleschannel} - This query is used to target all available stores, so it should only contain one aggregate "stores".
    - The “stores” aggregate should contain the items_eresa items query, which lists items eligible for Reserve & Collect, and the stores_eresa stock locations query, which lists stores with the e-reservation module enabled.

    • Aggregates deductions: all deductions should be enabled (stock locations reservations, unavailability, global and stock locations buffers).

  • eresa_unified_{saleschannel} - The unified query can be created by inheriting from the detailed one.

    • Settings : only the unification parameter should be changed (unification by sock locations and stock types enabled).

➡️ Here's what the e-reservation queries might look like, with two sales channels/websites FR and UK.

...

• Delivery promise: These queries provide stock availability for different delivery methods.

...