Replenishment agent

Draft the reorder. Show the working.

The agent filters 10 SKUs down to 7 eligible for reorder, sizes base stock from 13 weeks of history at each of 10 stores, and drafts 45 purchase order lines. Every figure traces back to the row it came from.

7 of 10

SKUs eligible to reorder

Store and SKU pairs sized

Draft PO lines awaiting approval

1,265

Units proposed

Where this data comes from

Three connectors feed the agent. Every one is reading seeded files today, which is why the label on each card says synthetic. The interface each connector exposes is the one a live integration would keep.

MMS

Merchandise Management System

Synthetic, read only

10 SKUs, 100 stock positions

Supplies: SKU master, lifecycle status, stock on hand
Reading today: data/seed/mms.skus.json
data/seed/mms.stock.json
In production: MMS article master and stock extract, nightly or on demand

Blue Yonder

E3 replenishment and allocation, formerly JDA

Synthetic, read only

10 stores across 4 regions

Supplies: Store and region hierarchy
Reading today: data/seed/blueyonder.stores.json
In production: Blue Yonder E3 location hierarchy extract

POS + Hybris

Point of sale and omnichannel

Synthetic, read only

5,080 weekly sales rows

Supplies: Weekly net sales units by store and SKU
Reading today: data/seed/pos.weekly-sales.json
In production: POS sales fact table, Hybris order feed for omni demand

The policy in force

These are the numbers the merchandising team would tune. None of them is buried in code: they live in one configuration file and the run above used exactly these values.

13weeks

Historical baseline

Three months of trailing sales, not a single week

13weeks

Minimum weeks before trusting current year

Below this a limited-life SKU falls back to last year's window

364days

Prior-year comparable shift

364 days keeps the weekday, so retail weeks line up

3weeks

Cover for regional top seller

The rank 1 store in a region carries deeper stock

1.5weeks

Cover for other stores

Applied to every store that is not rank 1

2stores

Stores needed to rank a region

A single-store region has no meaningful top seller

Synthetic dataset. Generated deterministically with seed 20260916, running as of 16 Sep 2026, with weekly sales history from 2 Jun 2025 to 14 Sep 2026. Brand names, SKUs, sales and stock figures are all invented. No real Shoppers Stop record is used anywhere in this application, and nothing here is connected to a Shoppers Stop system.