Stop / Start / Buffer Inventory Sync #281

New Issue

2026-06-29T08:37:36Z

rob commented

2026-06-29 08:37:36 +00:00

Stop / Start / Buffer Inventory Sync is a feature which allows each sales channel to display the most accurate inventory quantities.

This functionality is already built for local eStack stock levels only. It was working with ebay, Amazon (fulfilled by merchant only), and Walmart. Now we need to update this to factor in FBA stock levels and add Shopify support. Walmart should be ignored until we update Walmart to their latest API.

We need to use the following method to display the stock levels on a per SKU basis:

FBA Stock Level + Local eStack Stock Level - SKU Buffer in eStack = Displayed Inventory pushed to Sales Channels (ebay, Shopify, Walmart)

When combined FBA and local eStack stock quantity hits the Buffer Stock level set at the SKU Info tab on eStack, we need to set the stock levels on ebay, Shopify, and Walmart to zero.

Once inventory is added to FBA or local eStack inventory, the system needs to push out the new combined stock levels to eBay, Shopify, and Walmart.

As mentioned, this functionality for stopping and starting SKUs is already built, but you need to get familiar with it so you can update it.

A few things to consider:

Combo SKUs in its current form are currently supported in eStack. This means that if the SKU 202357 has zero stock available, the combo SKU 202359-202357(x2) will be stopped on ebay, Shopify, and Walmart. Likewise, if it's we add new stock for SKU 202357, eStack will push out the new stock levels for the combo SKU 202359-202357(x2).

For a combo SKU, we always display an available quantity that matches the component SKU with the lowest available stock quantity. For example, on combo SKU 202359-202357(x2). If 202357 has 10 units available, and 202357 has 50 units available, we can only push out a quantity of 5 units 202359-202357(x2) because 202357 is sold as (x2). Thus, we only can ship 5 units of 202359-202357(x2).

Since we are considering to redesign the combo SKU structure in eStack, we can discuss this on a call, but the logic is there already and we will maintain a similar logic when we redesign the new combo SKU support.

We only use the FBA stock levels for the relevant country. For example; Only use USA FBA and USA local eStack stock levels when pushing stock to USA based Shopify, ebay, Walmart accounts. If a user has separate Shopify and ebay accounts in both the USA and Canada, we must not push the US FBA and local stock levels to the Canada Shopify and ebay store.
We are not pushing stock levels to Amazon at the moment, but we will support this later once we get approved for customer sensitive data management. When that happens, we will push only the local eStack Stock levels to Amazon as we do not want to add FBA stock levels for listings that are fulfilled by merchant. We can discuss this later when necessary.

Stop / Start / Buffer Inventory Sync is a feature which allows each sales channel to display the most accurate inventory quantities. **** This functionality is already built for local eStack stock levels only. It was working with ebay, Amazon (fulfilled by merchant only), and Walmart. Now we need to update this to factor in FBA stock levels and add Shopify support. Walmart should be ignored until we update Walmart to their latest API. We need to use the following method to display the stock levels on a per SKU basis: _FBA Stock Level + Local eStack Stock Level - SKU Buffer in eStack = Displayed Inventory pushed to Sales Channels (ebay, Shopify, Walmart)_ When combined FBA and local eStack stock quantity hits the Buffer Stock level set at the SKU Info tab on eStack, we need to set the stock levels on ebay, Shopify, and Walmart to zero. Once inventory is added to FBA or local eStack inventory, the system needs to push out the new combined stock levels to eBay, Shopify, and Walmart. As mentioned, this functionality for stopping and starting SKUs is already built, but you need to get familiar with it so you can update it. **A few things to consider:** 1. Combo SKUs in its current form are currently supported in eStack. This means that if the SKU 202357 has zero stock available, the combo SKU 202359-202357(x2) will be stopped on ebay, Shopify, and Walmart. Likewise, if it's we add new stock for SKU 202357, eStack will push out the new stock levels for the combo SKU 202359-202357(x2). For a combo SKU, we always display an available quantity that matches the component SKU with the lowest available stock quantity. For example, on combo SKU 202359-202357(x2). If 202357 has 10 units available, and 202357 has 50 units available, we can only push out a quantity of 5 units 202359-202357(x2) because 202357 is sold as (x2). Thus, we only can ship 5 units of 202359-202357(x2). Since we are considering to redesign the combo SKU structure in eStack, we can discuss this on a call, but the logic is there already and we will maintain a similar logic when we redesign the new combo SKU support. 2. We only use the FBA stock levels for the relevant country. For example; Only use USA FBA and USA local eStack stock levels when pushing stock to USA based Shopify, ebay, Walmart accounts. If a user has separate Shopify and ebay accounts in both the USA and Canada, we must not push the US FBA and local stock levels to the Canada Shopify and ebay store. 3. We are not pushing stock levels to Amazon at the moment, but we will support this later once we get approved for customer sensitive data management. When that happens, we will push only the local eStack Stock levels to Amazon as we do not want to add FBA stock levels for listings that are fulfilled by merchant. We can discuss this later when necessary. ![Screen_Shot_2022-09-29_at_9.46.15_AM](/uploads/0ac7a84a1b78f145768b033fdf1dea97/Screen_Shot_2022-09-29_at_9.46.15_AM.png)

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#281