FBA Restock Page #279

New Issue

2026-06-29T08:37:36Z

rob commented

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

Let’s take the following columns from the GET_FBA_INVENTORY_PLANNING_DATA report and put it onto a page in eStack called ‘FBA Restock’ under ‘Inventory’:

sku, asin, product-name, available, units-shipped-t7, units-shipped-t30, units-shipped-t60, units-shipped-t90, recommended-action, sell-through, marketplace, days-of-supply, estimated-excess-quantity, inbound-quantity, recommended-order-date, recommended-order-quantity

We only want to display (filter) the value called 'GoToRestock' on the 'recommended-action' column.

After the 'recommended-order-quantity' column; display the eStack 'local inventory' quantity we have for the SKU(s). On the right side after the 'Local Inventory' column, leave an empty box field for users to type type the quantity they want to send to FBA (like Burn Rate Report). At the bottom of the page, the user can click a button called 'Create FBA Plan', which will create a DO in the system for now. Later we can make this button create an FBA plan via API to Amazon directly, along with a DO in eStack to match it.

Some ASIN's SKUs may need parsing, like 200122a or 202518(x2)-202517ca, so we should discuss how to handle this. My best guess is to make multiple rows for SKUS like 200122, 200122s, etc. Then for ASINs that have multiple SKUs or quantities, like and put a like 202518(x2)-202517ca, we can display the 202518(x2)-202517ca SKU, then underneathe it show the component SKUs on separate lines. This way the user can see how many units they actually can ship to FBA based on the component SKUs local inventory availability.

Let's discuss more on the call.

Let’s take the following columns from the GET_FBA_INVENTORY_PLANNING_DATA report and put it onto a page in eStack called ‘FBA Restock’ under ‘Inventory’: sku, asin, product-name, available, units-shipped-t7, units-shipped-t30, units-shipped-t60, units-shipped-t90, **recommended-action**, sell-through, marketplace, days-of-supply, estimated-excess-quantity, inbound-quantity, **recommended-order-date, recommended-order-quantity** We only want to display (filter) the value called **'GoToRestock**' on the '**recommended-action**' column. After the '**recommended-order-quantity'** column; display the eStack 'local inventory' quantity we have for the SKU(s). On the right side after the 'Local Inventory' column, leave an empty box field for users to type type the quantity they want to send to FBA (like Burn Rate Report). At the bottom of the page, **the user can click a button called 'Create FBA Plan', which will create a DO in the system for now.** Later we can make this button create an FBA plan via API to Amazon directly, along with a DO in eStack to match it. Some ASIN's SKUs may need parsing, like 200122a or 202518(x2)-202517ca, so we should discuss how to handle this. My best guess is to make multiple rows for SKUS like 200122, 200122s, etc. Then for ASINs that have multiple SKUs or quantities, like and put a like 202518(x2)-202517ca, we can display the 202518(x2)-202517ca SKU, then underneathe it show the component SKUs on separate lines. This way the user can see how many units they actually can ship to FBA based on the component SKUs local inventory availability. Let's discuss more on the call.

rob added the To-Fix label 2026-06-29 08:37:36 +00:00

Sign in to join this conversation.

No Label To-Fix

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#279