Newly Created SKU Alias Lookback Period to Assign Orders & Fulfillment Routing #258

New Issue

2026-06-29T08:37:32Z

rob commented

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

Issue: Imprted Orders (or FBA order data) are not being attributed to Alias SKUs once the new Alias SKU is created.

Impact: User will not have valuable historical order data for FBA orders and will fail to ship orders that need to be shipped using local eStack stock (currrently ebay, Shopify)

Solution: Orders that are imported into eStack without an existing SKU Alias get assigned to the alias Linked SKUs once the Alias is created.

Run a lookback report or cron upon creation of a new SKU alias on the previously fetched channel order reports and look for the for newly created SKU Alias in order to assign the fetched order to the Linked SKU -
When the Activities Notification at the top of eStack is saying 'Some orders are unable to be imported.' because the SKU does not exist:
- We create the SKU or SKU Alias
- Send the Order containting the SKU or SKU SKU Alias through Fulfilment Routing
Fetch reports (or use existing reports) for the previous 30 days (lookback period)

FYI:

Amazon FBA - Comes in as Complete status - no allocations will occur
ebay - user ships eStack stock - gets allocated - is working
Shopify - user ships eStack stock - gets allocated - is working

We may want to run this same process for newly created SKUs that are not Aliases, so the previsouly fetched order data can be attributed to the SKU sales history and sent to fulfillement routing

**Issue:** Imprted Orders (or FBA order data) are not being attributed to Alias SKUs once the new Alias SKU is created. **Impact**: User will not have valuable historical order data for FBA orders and will fail to ship orders that need to be shipped using local eStack stock (currrently ebay, Shopify) **Solution**: Orders that are imported into eStack without an existing SKU Alias get assigned to the alias Linked SKUs once the Alias is created. - Run a lookback report or cron upon creation of a new SKU alias on the previously fetched channel order reports and look for the for newly created SKU Alias in order to assign the fetched order to the Linked SKU - - When the Activities Notification at the top of eStack is saying 'Some orders are unable to be imported.' because the SKU does not exist: * We create the SKU or SKU Alias * Send the Order containting the SKU or SKU SKU Alias through Fulfilment Routing - Fetch reports (or use existing reports) for the previous 30 days (lookback period) FYI: - Amazon FBA - Comes in as Complete status - no allocations will occur - ebay - user ships eStack stock - gets allocated - is working - Shopify - user ships eStack stock - gets allocated - is working We may want to run this same process for newly created SKUs that are not Aliases, so the previsouly fetched order data can be attributed to the SKU sales history and sent to fulfillement routing

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#258