🚀Main features and use cases
- 1 Overview & Key concepts
- 1.1 Main features
- 1.2 Data synchronization
- 1.3 Supported use cases
- 1.4 Proxy app usage
- 1.4.1 Use cases
- 2 Limitations & Out-of-Scope Scenarios
- 2.1 Cart content
- 2.1.1 E-gift cards
- 2.1.2 Multi-carts
- 2.2 Checkout & order creation
- 2.3 Detailed inventory per stock location
- 2.4 Refund
- 2.5 Sales channel
- 2.1 Cart content
Overview & Key concepts
This page provides an overview of the features and use cases of the OneStock connector for Shopify.
Main features
Data Synchronization: Synchronize the necessary data between OneStock and Shopify to operate OneStock OMS.
Checkout improvement through delivery promise: The latest availability, inventory, estimated time, costs and shipping information are retrieved and displayed to buyers through Shopify's shipping checkout process only.
Proxy: The OneStock connector acts as a secure proxy between Shopify and OneStock, simplifying integration and ensuring reliable communication between both platforms. It can be used by integrators to speed-up the integration of new data.
Data synchronization
The OneStock connector manages the data synchronization required to run OneStock OMS.
Each synchronization is managed using Shopify APIs.
The synchronization flows cover the following types of data:
Product synchronization: Import and synchronization of product data from Shopify to OneStock to up and running the OneStock OMS platform. All your products with active status in Shopify can be found in your OneStock OMS.
Inventory synchronization: Import real-time unified inventory view from OneStock to Shopify. All your unified inventory view created in OneStock can be used in Shopify.
Order synchronization: Import orders to be orchestrated by OneStock. The OneStock connector immediately creates an order in OneStock as soon as it is created in Shopify.
Status synchronization: Status updates from OneStock to Shopify. As soon as an order or return changes status in OneStock , the OneStock connector notifies Shopify.
The following diagram presents the end-to-end flows.
Supported use cases
We will use the term “checkout” repeatedly. In the Shopify context, it refers to the stage where buyers go to purchase goods.
There are several delivery methods available with Shopify:
Shipping: This checkout allows you to create home delivery orders.
Local delivery: This checkout allows you to create orders by letting the customer choose the stock point that will deliver. Please note Local delivery is integrated in the Shipping checkout.
Pickup in-store BOPIS: This checkout allows you to create orders by choosing a pickup store.
Pickup points PUDO: This checkout allows you to create orders for delivery to a pickup point.
The OneStock connector works with the following checkouts:
Checkout Shopify | OneStock connector integration order |
|---|---|
Shipping | 100% of the orders are retrieved by the connector and integrated in OneStock OMS OneStock connector does not retrieve local delivery orders. |
Pickup in-store BOPIS | 100% of the orders are retrieved by the connector and integrated in OneStock OMS |
Pickup points PUDO | 100% of the orders are retrieved by the connector and integrated in OneStock OMS* |
*PUDO orders are retrieved by the connector but require modification to indicate the relay point ID to OneStock. This data is mandatory to generate a shipping label.
Checkout and delivery promise behaviour
Before jumping into explanation, please refer to Delivery Promise page to understand what delivery promise means.
With the OneStock connector, you can use the Delivery Promise module to enrich the Shopify checkout with real-time data.
Concretely, the delivery methods configured in OneStock are displayed directly in the Shopify checkout.
The OneStock connector displays delivery promise information in the below checkout:
Shopify checkout | Delivery promise displaying |
|---|---|
Shipping |
|
Pickup in-store |
|
Pickup points |
|
It means that OneStock connector loads data from delivery promise only in the shipping checkout.
Shopify checkout | Delivery promise displaying |
|---|---|
Shipping | The delivery promise can expose multiple delivery methods configured in your OneStock backoffice, for example:
|
ROPIS orders are not available in the shipping checkout in Shopify.
Orders from Shopify shipping checkout
This Shopify checkout allows customers to have their orders delivered to an address.
Shipping checkout location can be with or without delivery promise information from OneStock connector. Regardless of the case, the OneStock connector retrieves all orders coming from this checkout.
Orders from Shopify Pickup in-store checkout
This Shopify checkout allows customers to have their orders picked up in a location configured in Shopify as active to do pickup in-store.
Pickup in-store checkout location is always without delivery promise information. Despite that, OneStock connector retrieves all orders coming from this checkout.
Checkout Pickup in-store example
Orders from Shopify Pickup points checkout
This Shopify checkout allows customers to have their orders picked up in a relay point configured in Shopify.
Pickup points checkout location is always without delivery promise information. Despite that, OneStock connector retrieves all orders coming from this checkout.
Checkout Pickup points example
Orders from Shopify Local delivery
This Shopify checkout allows customers to have their orders delivered to an address.
Local delivery checkout location is always without delivery promise information from OneStock connector. It is a subcategory from Shipping checkout. The OneStock connector does not retrieves orders from this checkout.
Checkout Local delivery example
Focus on the Shipping checkout location
The OneStock connector displays delivery promise response only in the shipping checkout location.
If you want to understand how the OneStock connector retrieves the Shopify cart, please refer to the following section.
The OneStock connector can display the delivery promise for the following cart types:
Carts containing only physical items.
Carts containing both physical items and non-shippable items.
Home delivery orders through delivery promise in Shopify
In this example, the displayed delivery promise allows delivery orders to be created in OneStock.
For home delivery orders, the OneStock connector displays the delivery date and shipping fees.
Checkout with delivery promise for home delivery orders
BOPIS orders through delivery promise in Shopify
In this example, the displayed delivery promise allows BOPIS orders to be created in OneStock.
For BOPIS orders, the OneStock connector displays a list of stores, the delivery date and shipping fees.
Checkout with delivery promise for BOPIS orders
OneStock connector can also display a search field by postal code to retrieve all the stores near to the postal code.
Only available with Google API key.
Checkout with delivery promise and Google search for BOPIS orders
PUDO orders through delivery promise in Shopify
In this example, the displayed delivery promise allows Delivery orders to be created in OneStock.
For PUDO orders, the OneStock connector displays a list of pickup points (through Atlas appplication), the delivery date and shipping fees.
Please note that a subscription to the Atlas application is required for the OneStock connector to operate.
Checkout with delivery promise for PUDO orders
Thanks to these integration of the OneStock connector for Shopify, you can use the full capability of the OneStock OMS.
The following diagram presents the end-to-end flows listed above.
Please note:
There is no Delivery Promise front-end module available on the product page. Please refer to proxy app if you want to learn more.
For Shopify checkouts, the OneStock connector does not display delivery promise information for In-Store Pickup (BOPIS) and Pickup Point (PUDO) locations.
Proxy app usage
We have created a proxy app to enable our customers to customize your front-end website with OneStock data and enhance the customer experience.
You can use this proxy app as soon as your connector is installed on your storefront.
Technically speaking, our app proxies take the content in the payload parameter and enrich it with the authentication parameters, allowing a security abstraction that the system integrators don't need to manage using the connector. Thus, you don’t need to input the site_id nor the token when using the app proxy routes.
Use cases
UC1 → You can call OneStock to retrieve inventory information for a store and display it on your product page.
UC2 → You can call OneStock to retrieve delivery promise information and display it on your product page.
Limitations & Out-of-Scope Scenarios
Cart content
E-gift cards
OneStock connector cannot currently display the delivery promise if an e-gift card configured in Shopify is placed in the basket.
Multi-carts
OneStock connector cannot currently display the delivery promise if multiple baskets are available in the Shopify checkout.
Checkout & order creation
Although the connector retrieves the vast majority of orders coming from Shopify, some scenarios are not covered.
Local delivery shipping checkout
OneStock connector do not retrieve this delivery method provided by Shopify. Please note you can easily set-up the same behaviour in the OneStock orchestration rules feature. More information on local delivery here.
PUDO checkout
Orders are retrieved, but additional configuration is needed to pass the PUDO ID, which is required in most cases for OneStock to generate the appropriate carrier label. Therefore, this ID must be transmitted to OneStock through another mechanism.
More information on PUDO Checkout here.
Express Checkout & delivery promise
Checkout with OneStock delivery promise and BOPIS orders → Understanding the impacts
Native Shopify checkout
Detailed inventory per stock location
The OneStock connector does not support transmitting inventory levels per stock location. The only inventory management supported by the connector is the transmission of a unified stock.