...
➡️ 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.
...
| Note |
|---|
Once the stock requests have been created, they need to be set up in the Store App configuration in “order_in_store_options”. Please get in touch with your Onestock contact. |
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 theitems_eresaitems query, which lists items eligible for Reserve & Collect, and thestores_eresastock 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.
...
| Note |
|---|
Once the stock requests have been created, they need to be set up in the e-reservation funnel configuration. Please get in touch with your Onestock contact. |
Delivery promise: These queries provide stock availability for different delivery methods.
...