30 Claude Prompts That Build Inventory Dashboards

You are an inventory buyer who builds reorder-point watchlists, not a merchandising sell-through scoreboard. <context> I need a reorder-point watchlist as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SKU rows so ROP, on-hand, and suggested qty render when I open it as a working screen in the chat. This is ops stock replenishment, not storefront revenue. </context> <inputs> - Buyer or book: [BUYER] - ROP rule: [E.G. (DAILY DEMAND TIMES LEAD DAYS) PLUS SAFETY DAYS TIMES DAILY DEMAND] - Order qty rule: [E.G. MAX COVER MINUS ON HAND MINUS ON ORDER, ROUNDED TO CASE PACK] - SKU count: [E.G. 28] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a KPI row (SKUs at or below ROP, units to buy, buy value, SKUs with zero demand); a scatter of on-hand versus ROP; a watchlist sorted most urgent first (sku, on hand, on order, daily demand, lead days, ROP, suggested qty, buy value); chips for at/below ROP only; and a click on a row that restates the ROP math. Generate SKU constants in labeled JS. Compute ROP and suggested qty from the rules. Zero demand shows [VERIFY] on suggested qty, not a huge buy. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - ROP and suggested qty are computed, not hardcoded. - Show both formulas on the page. Case-pack rounding in JS. - Do not invent vendor price breaks I did not list. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the ROP and buy-qty formulas and which array to replace with a ROP file. </format>

You are an inventory planner who flags min-max breaches so buyers see both starvation and bloat. <context> I need a min-max breach dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic policy rows so below-min and over-max SKUs render when I open it as a working screen in the chat. This is policy stock, not a promo calendar. </context> <inputs> - Policy name: [POLICY] - Position used versus min/max: [E.G. ON HAND PLUS ON ORDER] - SKU count: [E.G. 32] - Unit: [UNITS / CASES] - Optional suggested top-up: [E.G. BUY TO MAX] </inputs> <task> Build the dashboard with: a KPI row (below min, over max, inside band, units short of min, units over max); a bar of position versus min and max for the selected SKU; chips for below / over / inside; a table (sku, on hand, on order, position, min, max, gap, status); and a click that draws that SKU's band. Position follows the rule I gave. Status is computed. Suggested top-up = max minus position when below min, if I asked for it. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Status and gaps are computed from position, min, and max. - Show the position rule on the page. - Do not invent storefront sell-through. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the breach rules and which array to replace with a min-max table. </format>

You are an inventory buyer who reads open POs against daily demand so inbound either saves a SKU or arrives late. <context> I need an open-PO cover dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic PO lines so ETA, inbound units, and days saved render when I open it as a working screen in the chat. This is inbound cover, not a revenue forecast. </context> <inputs> - Suppliers: [SUPPLIERS] - Horizon: [E.G. NEXT 28 DAYS] - Demand basis: [E.G. TRAILING 14-DAY DAILY UNITS] - Late rule: [E.G. ETA BEFORE TODAY] - PO line count: [E.G. 22] </inputs> <task> Build the dashboard with: a KPI row (open PO lines, inbound units, late lines, SKUs still projected to stock out before ETA); a timeline of ETAs; a table (po, supplier, sku, qty, ETA, days until ETA, days of cover without PO, days of cover with PO, saves-in-time flag); supplier chips; and a click on a late PO that lists its lines. Generate PO lines and SKU demand in labeled JS arrays. Cover days = on hand / daily demand. Saves-in-time = ETA is on or before projected stockout. Guard zero demand. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Cover and saves-in-time are computed from dates and demand. - Include a today constant I can edit. - Do not invent freight or duty. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the saves-in-time rule and which arrays to replace with an open-PO export. </format>

You are an inventory planner who compares stated vendor lead time to actual receipt lag so safety stock is not a guess. <context> I need a lead-time buffer dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic receipt rows so stated versus actual lead time renders when I open it as a working screen in the chat. This is supplier time, not ads ROAS. </context> <inputs> - Vendors: [VENDORS] - Stated lead days per vendor: [NUMBERS OR INVENT] - Receipt count: [E.G. 40 ACROSS VENDORS] - Buffer rule: [E.G. STATED PLUS 75TH PERCENTILE OVERAGE] - Period: [E.G. LAST 90 DAYS] </inputs> <task> Build the dashboard with: a KPI row (vendors, median actual lead, vendors over stated, suggested extra days on the worst vendor); a grouped bar of stated versus median actual by vendor; a table (vendor, stated, median actual, p75 actual, overage, suggested buffer days); a receipt strip for the selected vendor; and a callout of the vendor whose overage would change ROP the most. Generate receipts with send and receive dates in a labeled JS array. Actual days = receive minus send. Buffer follows the rule I gave. Show the rule. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Medians and buffers are computed from receipt dates. - Label this as sample arithmetic, not a statistical model. - Do not invent contract penalties. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the buffer rule and which array to replace with a receipt history. </format>

You are an inventory buyer who builds a weekly suggested-buy pack from on-hand, demand, lead time, and a budget cap. <context> I need a suggested-buy pack as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SKU rows so qty, cost, and cover after buy render when I open it as a working screen in the chat. This is a buy list, not a merchandising revenue board. </context> <inputs> - Week or buy cycle: [WEEK] - Cover target days: [E.G. 28] - Budget cap: [E.G. 25000 USD OR NONE] - Case pack rounding: [E.G. ROUND UP TO PACK] - SKU count: [E.G. 26] </inputs> <task> Build the dashboard with: a KPI row (lines to buy, units, buy value, value versus cap, SKUs skipped for budget); a bar of buy value by category; a table (sku, on hand, on order, daily demand, need qty, rounded qty, unit cost, line value, cover after buy); a toggle that applies the cap by ranking need (lowest cover first) and marking skipped lines; and a click that shows cover before versus after. Need qty = max(0, target days times daily demand minus on hand minus on order). Show formulas. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Need qty, rounding, cover after buy, and cap skips are computed. - If I said NONE for budget, skip the cap logic and say so on the page. - Do not invent promo lifts. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the need-qty and cap rules and which array to replace with a demand and on-hand file. </format>

You are an inventory analyst who ages stock from last outbound movement so idle value cannot hide behind a new receipt. <context> I need a days-idle aging dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SKU rows so last movement and value stuck render when I open it as a working screen in the chat. This is stock aging, not a returns-revenue board. </context> <inputs> - SKU set: [SKU SET] - Age buckets: [E.G. 0-30, 31-60, 61-90, 91-180, 180+] - Idle flag days: [E.G. 90] - Value basis: [UNIT COST] - New-SKU exclude days: [E.G. 45 SINCE FIRST RECEIPT] </inputs> <task> Build the dashboard with: a KPI row (SKUs, idle SKUs, value in 180+, share of inventory value idle); a bar of value by age bucket; chips for each bucket; a table (sku, on hand, last outbound, days idle, first receipt, value, excluded-as-new flag); and a click on a bucket that filters the table. Days idle = now minus last outbound. Bucket assignment in JS. Exclude-as-new when first receipt is inside the exclude window. Show both rules. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Days idle and buckets are computed from dates and a now constant. - Do not use last receipt as the idle clock. - Accessible contrast; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the idle clock and which array to replace with a movement extract. </format>

You are an inventory controller who ages lots to expiry so write-off risk is a date, not a surprise. <context> I need a lot-expiry aging dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic lots so days to expire and write-off risk render when I open it as a working screen in the chat. This is lot stock, not ecommerce returns. </context> <inputs> - Lot set or product line: [LOTS] - Risk windows: [E.G. 0-14, 15-30, 31-60, 60+ DAYS TO EXPIRY] - Expired rule: [DAYS TO EXPIRY UNDER 0] - Value basis: [UNIT COST] - Lot count: [E.G. 30] </inputs> <task> Build the dashboard with: a KPI row (lots, units expiring in 14 days, expired units, value at risk in 30 days); a bar of units by risk window; a table (lot, sku, qty, expiry date, days to expire, value, status); chips for window; and a click on a lot that shows qty times cost. Days to expire = expiry minus today. Status = expired / at risk / ok from the windows. Show the windows on the page. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Days to expire and status are computed from the expiry date. - Expired rows flagged with a text label. - Do not invent recall or FDA language. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the expiry math and which array to replace with a lot file. </format>

You are a warehouse inventory analyst who shows FEFO age mix so young lots are not picked while old lots sit. <context> I need a FEFO age-mix dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic lots so age bands and pick order render when I open it as a working screen in the chat. This is lot rotation, not a collection mix for the homepage. </context> <inputs> - Product line: [PRODUCT LINE] - Age bands from receipt or from expiry: [E.G. DAYS TO EXPIRY BANDS] - Sample lots: [E.G. 28] - Pick policy to display: [FEFO] - Site: [NAME] </inputs> <task> Build the dashboard with: a KPI row (lots, units, oldest lot days to expiry, share of units in the last two bands); a stacked bar of units by age band by SKU; a suggested pick list sorted FEFO (lot, sku, location if given, expiry, qty); chips for SKU; and a callout when a SKU has more than half its units in the youngest band while an older lot still has qty. Band assignment computed. Clicking a band filters the pick list. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Pick order is sorted by expiry date, then lot id. - Show FEFO as the policy label on the page. - Do not invent slot travel time. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the pick sort and which array to replace with a lot-age export. </format>

You are an inventory analyst who compares last receipt to last sale so inbound on a silent SKU is visible. <context> I need a receipt-versus-last-sale dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SKU date pairs so inbound after last sale renders when I open it as a working screen in the chat. This is stock hygiene, not storefront cohorts. </context> <inputs> - Warehouse: [WAREHOUSE] - Stale rule: [E.G. RECEIPT AFTER LAST OUTBOUND AND LAST OUTBOUND OVER 45 DAYS AGO] - SKU count: [E.G. 30] - Value basis: [UNIT COST] - New-SKU grace: [E.G. FIRST RECEIPT UNDER 30 DAYS] </inputs> <task> Build the dashboard with: a KPI row (SKUs, stale inbound SKUs, units on those SKUs, value); a scatter of days since last sale versus days since last receipt; a table (sku, last receipt, last outbound, days since sale, inbound-after-sale flag, on hand, value, grace flag); chips for stale only; and a click that shows the two dates. Flags computed from the three dates and a now constant. Show the stale and grace rules. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Flags are computed, not hardcoded. - Grace SKUs labeled new, not stale. - Do not invent markdown prices. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the stale rule and which array to replace with receipt and sale dates. </format>

You are an inventory controller who builds an aging ladder finance can recognize, with value in each idle band. <context> I need a write-down aging ladder as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic aged SKUs so 30/60/90/180 day value renders when I open it as a working screen in the chat. This is stock value aging, not a P and L. </context> <inputs> - Value basis: [VALUE BASIS] - Bands: [E.G. 0-30, 31-60, 61-90, 91-180, 180+] - Optional reserve percents by band: [E.G. 0, 0, 10, 25, 50 OR SKIP] - SKU count: [E.G. 34] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a KPI row (inventory value, value in 90+, value in 180+, optional reserve dollars); a ladder bar of value by band; a table (sku, days idle, band, on-hand value, optional reserve % and reserve $); chips for band; and a footnote that reserve percents are a sample policy I typed, not accounting advice. Days idle from last movement. If I skipped reserve percents, omit reserve columns and say so. Clicking a ladder step filters the table. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Band value and optional reserve are computed. - Label reserves as illustrative from my percents. - Do not invent GAAP treatment. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the band and reserve math and which array to replace with an aged-value extract. </format>

You are a warehouse layout analyst who measures slot fill and cube so overflow is a number, not a walk-around complaint. <context> I need a slot-fill and cube dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic slots so cube used, empty slots, and overflow render when I open it as a working screen in the chat. This is warehouse space, not storefront merchandising. </context> <inputs> - Warehouse: [WAREHOUSE] - Zones or aisles: [E.G. A-F, BULK] - Overflow rule: [E.G. CUBE OVER 95% OR QTY OVER SLOT MAX] - Slot count: [E.G. 48] - Unit for cube: [E.G. CUBIC FEET] </inputs> <task> Build the dashboard with: a KPI row (slots, empty slots, average cube %, overflow slots); a bar of cube % by aisle; a simple aisle grid colored by cube band with the percent printed in the cell; a table (slot, aisle, sku, qty, slot max, cube used, cube cap, fill %, overflow flag); and a click on an aisle that filters the table. Cube % = used / cap. Overflow follows my rule. Empty = qty at 0. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Fill and overflow are computed. Show the number, not color alone. - Guard zero cube cap with [VERIFY]. - Do not invent a CAD map. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the cube and overflow rules and which array to replace with a slot extract. </format>

You are a warehouse planner who builds pick-face replen boards so faces are filled before the wave shorts. <context> I need a pick-face replen dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic face rows so face qty, min, and replen waves render when I open it as a working screen in the chat. This is warehouse replen, not a storefront collection mix. </context> <inputs> - Zone: [ZONE] - Replen trigger: [E.G. FACE QTY AT OR BELOW MIN] - Bulk available field: [E.G. BULK QTY] - Face count: [E.G. 24] - Wave names if useful: [E.G. AM, MID, PM] </inputs> <task> Build the dashboard with: a KPI row (faces, starved faces, faces with no bulk to pull, units to replen); a bar of starved count by aisle; a table (sku, face slot, face qty, min, max, bulk qty, replen qty to max, blocked-no-bulk flag); chips for starved / blocked; and a click that shows replen qty. Replen qty = max(0, max minus face qty) when trigger hits. Blocked = trigger hits and bulk qty is 0. Show the trigger. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Starved and blocked flags are computed. - Do not invent picker travel paths. - Accessible contrast; data at the top with comments. </constraints> <format> Return the full HTML file, then write the replen qty rule and which array to replace with a pick-face file. </format>

You are an inventory planner who suggests inter-site transfers from surplus cover to shortage cover. <context> I need an inter-site transfer dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic site-SKU balances so surplus, shortage, and suggested moves render when I open it as a working screen in the chat. This is stock balancing, not marketplace revenue. </context> <inputs> - Sites: [SITES] - Cover target days: [E.G. 21] - Min days you will not drain below: [E.G. 10] - SKU count: [E.G. 20] - Demand per site: [TRAILING DAILY UNITS] </inputs> <task> Build the dashboard with: a KPI row (SKUs short at any site, suggested moves, units to move, SKUs with surplus but no short); a site-by-SKU heatmap of days of cover; a suggested-move table (sku, from site, to site, qty, from cover after, to cover after); and a click on a move that restates both covers. Cover = on hand / daily demand. Surplus = cover over target. Shortage = cover under target. Qty is the min units that lift the short site without dropping the from-site below the min days. Guard zero demand. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Suggested qty is computed, not hardcoded. - Show target and min-days rules on the page. - Do not invent freight cost. Label moves as suggested. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the move-qty rule and which array to replace with site balances. </format>

You are a warehouse inbound analyst who measures dock-to-stock hours from receipt to putaway complete. <context> I need a dock-to-stock clock as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic receipt rows so receipt-to-putaway hours render when I open it as a working screen in the chat. This is inbound speed, not carrier on-time delivery. </context> <inputs> - Inbound window: [INBOUND WINDOW] - SLA hours: [E.G. 8] - Statuses: [E.G. RECEIVED, IN PUTAWAY, PUTAWAY COMPLETE] - Receipt count: [E.G. 26] - Warehouse: [NAME] </inputs> <task> Build the dashboard with: a KPI row (receipts, median hours dock-to-stock, percent inside SLA, lines still open); a bar of hours by day; a table (receipt id, vendor, received-at, putaway-at, hours, SLA flag, status, lines); chips for open / late; and a click on a late row. Hours = putaway-at minus received-at, or now minus received-at if still open. Late = hours over SLA. Include a now constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Hours and SLA flags are computed from timestamps. - Show the SLA on the page. This is putaway speed, not a TMS scorecard. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the clock and which array to replace with receipt timestamps. </format>

You are a warehouse inventory analyst who watches shrink from inventory adjustments, not from sales. <context> I need a shrink watch dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic adjustment rows so variance units, value, and hot SKUs render when I open it as a working screen in the chat. This is stock loss, not storefront returns revenue. </context> <inputs> - Warehouse: [WAREHOUSE] - Period: [E.G. LAST 30 DAYS] - Adjust reasons: [E.G. CYCLE COUNT, DAMAGE, UNKNOWN, RETURNS TO VENDOR] - Hot rule: [E.G. VALUE OVER 200 OR 3+ ADJUSTS] - Adjust count: [E.G. 36] </inputs> <task> Build the dashboard with: a KPI row (adjust lines, net units, shrink value, hot SKUs); a bar of value by reason; a SKU table (sku, adjust count, net units, value, last date, hot flag); chips for reason; and a click on a SKU that lists its adjust rows. Net units and value sum from the adjust array. Hot follows my rule. Show the rule. Damage versus unknown stay separate. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Nets and hot flags are computed from adjust rows. - Do not treat sold units as shrink. - Currency consistent; accessible contrast. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the shrink and hot rules and which array to replace with an adjust export. </format>

You are an inventory planner who grids SKUs by unit velocity versus days of cover so slow bloat is obvious. <context> I need a fast-versus-slow mover grid as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SKUs so velocity bands and cover render when I open it as a working screen in the chat. This is unit velocity, not storefront merchandising revenue. </context> <inputs> - Catalog: [CATALOG] - Velocity bands: [E.G. FAST, MEDIUM, SLOW, DEAD from weekly units] - Cover bands: [E.G. THIN UNDER 14, OK 14-45, FAT OVER 45 DAYS] - SKU count: [E.G. 36] - Demand window: [E.G. LAST 28 DAYS] </inputs> <task> Build the dashboard with: a KPI row (SKUs, slow+fat count, fast+thin count, value in slow+fat); a 3x3 or 4x3 heatmap of velocity band by cover band with counts in the cells; a table filtered by the selected cell (sku, weekly units, days of cover, on hand, value); and a callout of the slow+fat pile. Assign bands from weekly units and days of cover = on hand / daily demand. Clicking a cell filters the table. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Cell counts are computed from band assignment. - Show band edges on the page. Guard zero demand as dead or infinite cover with a flag. - Do not rank by storefront revenue. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the band rules and which array to replace with a velocity file. </format>

You are an inventory planner who scores SKU fill rate from units ordered versus units shipped. <context> I need a SKU fill-rate dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic order lines so fill rate and stockout days render when I open it as a working screen in the chat. This is service level on stock, not checkout conversion. </context> <inputs> - SKU set: [SKU SET] - Period: [E.G. LAST 30 DAYS] - Fill target: [E.G. 97%] - Stockout day rule: [E.G. A DAY WITH ANY UNSHIPPED QTY FOR THAT SKU] - Line count: [E.G. 80 LINES ACROSS 20 SKUS] </inputs> <task> Build the dashboard with: a KPI row (blended fill rate, SKUs below target, stockout days, units missed); a bar of fill rate by SKU versus the target; a table (sku, ordered, shipped, fill %, stockout days, missed units); chips for below target; and a click that lists that SKU's sample lines. Fill % = shipped / ordered. Stockout days counted from a daily miss flag on the lines. Guard zero ordered. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Fill rate and stockout days are computed from lines. - Show the target and the stockout-day rule. - Do not invent lost revenue. Units only unless I pasted a cost. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the fill-rate formula and which array to replace with a fill-rate export. </format>

You are an inventory planner who scores unit forecasts against actual units, not revenue. <context> I need a forecast-versus-actual units dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly pairs so bias and MAPE render when I open it as a working screen in the chat. This is unit forecast quality, not a sales commit board. </context> <inputs> - Horizon: [HORIZON] - SKUs: [E.G. 16] - Weeks: [E.G. 12] - MAPE target: [E.G. 20%] - Bias formula: [E.G. AVERAGE OF (FORECAST MINUS ACTUAL) / ACTUAL] </inputs> <task> Build the dashboard with: a KPI row (blended MAPE, SKUs over MAPE target, company bias over or under, worst SKU); a grouped bar of forecast versus actual for the selected SKU; a table (sku, MAPE, bias, last-week miss, status); week chips; and a click on a SKU that draws its series. MAPE = average of absolute(forecast minus actual) / actual on weeks with actual over 0. Bias uses my formula. Show both. Guard divide-by-zero. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - MAPE and bias are computed from the pairs, not hardcoded. - Label this as sample arithmetic, not a forecasting product. - Do not invent promotional lifts. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write MAPE and bias and which array to replace with a forecast file. </format>

You are an inventory planner who splits SKUs into understock and overstock from days-of-cover targets. <context> I need an overstock-versus-understock dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SKUs so units and value off-target render when I open it as a working screen in the chat. This is cover health, not a promo versus full-price mix. </context> <inputs> - Cover targets: [COVER TARGETS] - Example if needed: [THIN UNDER 14 DAYS, FAT OVER 45, TARGET 21-45] - SKU count: [E.G. 32] - Value basis: [UNIT COST] - Demand: [TRAILING DAILY UNITS] </inputs> <task> Build the dashboard with: a KPI row (understock SKUs, overstock SKUs, units short of target cover, value over target cover); a two-bar compare of under versus over value; a table (sku, on hand, daily demand, days of cover, status, units to target, value off); chips for under / on / over; and a click that shows units to target. Days of cover = on hand / daily demand. Units to target = target days times demand minus on hand (signed). Status from my edges. Show the edges. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Status and units-to-target are computed. - Zero demand labeled [VERIFY], not infinite overstock without a flag. - Do not invent markdown plans. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the cover-target rules and which array to replace with a cover file. </format>

You are an inventory planner who scores SKU health from cover, aging, service, and stock integrity, not from storefront revenue. <context> I need a SKU health scorecard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SKUs so cover, aging, service, and a score render when I open it as a working screen in the chat. </context> <inputs> - Catalog: [CATALOG] - Checks and weights: [E.G. COVER 30, AGING 25, FILL RATE 30, NEGATIVE/GHOST 15] - Pass edges: [E.G. COVER 14-45 DAYS, IDLE UNDER 60, FILL 97%, NO NEGATIVE] - SKU count: [E.G. 28] - Fail score: [E.G. UNDER 70] </inputs> <task> Build the dashboard with: a KPI row (SKUs, failing SKUs, median score, most common failed check); a histogram of scores; a table (sku, cover days, days idle, fill %, integrity flag, score, status); chips for failing only; and a click that shows each check pass/fail and the weighted score. Score = sum of weight if that check passes, else 0 for that check, scaled to 100. Show weights and edges. Integrity fail = negative qty or ghost flag on the row. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Score and fail status are computed from the edges and weights. - Print the recipe on the page so it cannot drift. - Do not add revenue, ROAS, or AOV. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the score recipe and which array to replace with a SKU extract. </format>

You are an inventory ops lead who builds a Monday standup screen a buyer and a warehouse lead can share in fifteen minutes. <context> I need a Monday inventory standup as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly exceptions so stockouts, buys, and aging render when I open it as a working screen in the chat. This is weekly ops stock, not a storefront week-over-week revenue pulse. </context> <inputs> - Team: [TEAM] - Week ending: [E.G. 2026-09-06] - Three lists: [WILL BREAK, SHOULD BUY, SITTING TOO LONG] - Row cap per list: [E.G. 8] - Cover and idle edges: [E.G. BREAK UNDER 7 DAYS, BUY AT OR BELOW ROP, IDLE OVER 90] </inputs> <task> Build the dashboard with: a header for [TEAM] and the week ending; a KPI row (will-break count, buy-list value, idle value, fill rate if seeded); three columns of exception rows (sku, why, qty or days, owner, next action); a small week spark of stockout count if you seed 8 weeks; and a click on a row that shows the rule that put it there. Assign each sample SKU to at most one primary list using my edges, but allow a badge if it also trips a second rule. Show the edges. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - List membership is computed from the edges, not hardcoded columns only. - Do not add ads, AOV, or storefront conversion. - Accessible contrast; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the three-list rules and which array to replace with a weekly extract. </format>

You are an inventory ops analyst who tracks week-over-week days-of-cover change so new risk shows up on Monday. <context> I need a week-over-week cover delta dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with last-week and this-week SKU rows so cover delta and new risks render when I open it as a working screen in the chat. This is cover change, not week-over-week store sales. </context> <inputs> - SKU set: [SKU SET] - Thin edge: [E.G. UNDER 14 DAYS] - New-risk rule: [E.G. CROSSED FROM AT/ABOVE THIN LAST WEEK TO BELOW THIS WEEK] - SKU count: [E.G. 30] - Weeks labeled: [E.G. W34, W35] </inputs> <task> Build the dashboard with: a KPI row (median cover delta, new-risk SKUs, still-thin both weeks, recovered SKUs); a bar of cover delta by SKU sorted worst first; a table (sku, cover last week, cover this week, delta days, on-hand delta, status); chips for new risk / still thin / recovered; and a click that draws last versus this. Delta = this cover minus last cover. New risk follows my rule. Recovered = thin last week and at or above thin this week. Show the thin edge. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Delta and status are computed from the two cover fields. - Do not convert cover into revenue. - Accessible contrast; data at the top with comments. </constraints> <format> Return the full HTML file, then write the new-risk rule and which arrays to replace with last week and this week. </format>

You are an inventory ops analyst who builds a single exception queue from stockout, overstock, and integrity rules. <context> I need an inventory exception queue as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic exception rows so stockout, overstock, and ghost rows render when I open it as a working screen in the chat. This is ops exceptions, not a storefront error funnel. </context> <inputs> - Rules: [RULES] - Example if needed: [STOCKOUT OR COVER UNDER 7, OVERSTOCK OVER 60 DAYS COVER, GHOST OR NEGATIVE] - Owners: [NAMES OR ROLES] - Severity: [E.G. P1 STOCKOUT, P2 INTEGRITY, P3 OVERSTOCK] - Row count: [E.G. 28] </inputs> <task> Build the dashboard with: a KPI row (open exceptions, P1, unowned, oldest age hours); a bar of count by rule; chips for each rule and for unowned; a queue table sorted severity then age (sku, rule, severity, age hours, owner, next action, since-when); and a click that shows why the rule fired. Age = now minus since-when. Severity from my map. Filters must hide rows. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Age and severity are computed from timestamps and the map. - Show each rule in plain English on the page. - Do not invent ticket systems. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then list each rule and which array to replace with an exception export. </format>

You are an inventory buyer who turns weekly stock math into a buy, hold, or transfer action pack. <context> I need a buyer action pack as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SKU-site rows so buy, hold, and transfer lines render when I open it as a working screen in the chat. This is a buyer workbook, not a merchandising scoreboard. </context> <inputs> - Buyer: [BUYER] - Action rules: [E.G. BUY IF BELOW ROP AND NO SURPLUS SITE, TRANSFER IF ANOTHER SITE IS OVER TARGET, HOLD OTHERWISE] - Sites: [E.G. WH1, WH2] - SKU count: [E.G. 24] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a KPI row (buy lines, buy value, transfer lines, hold lines); action chips; a table (sku, site, on hand, cover, action, qty, value if buy, from/to if transfer, reason); a value bar of the buy list; and a click that restates the rule. Assign one primary action per SKU from my rules. Transfer qty uses surplus at the fat site down to the target, capped by the thin site's need. Show the rules. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Action and qty are computed from the rules, not hardcoded labels only. - Do not invent vendor discounts. - Currency consistent; data at the top with comments. </constraints> <format> Return the full HTML file, then write each action rule and which array to replace with a buyer workbook. </format>

You are an inventory ops lead who builds a weekly KPI scorecard for cover, fill, aging, and shrink only. <context> I need a weekly inventory KPI scorecard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly totals so cover, fill, aging, and shrink render when I open it as a working screen in the chat. This is ops stock KPIs, not storefront revenue. </context> <inputs> - Warehouse: [WAREHOUSE] - Weeks: [E.G. LAST 12] - KPI targets: [E.G. MEDIAN COVER 21-35 DAYS, FILL 97%, IDLE VALUE SHARE UNDER 12%, SHRINK UNDER 0.4% OF VALUE] - Currency: [E.G. USD] - Latest week label: [E.G. WEEK ENDING 2026-09-06] </inputs> <task> Build the dashboard with: a header for [WAREHOUSE] and the latest week; four KPI cards (median cover days, fill %, idle value share, shrink %) each versus target with on/below/above text; a 12-week sparkline per KPI; a week table (week, cover, fill, idle share, shrink, flags); a click on a card that focuses that sparkline and lists the weeks that missed; and a footnote of each formula. Idle share = idle value / inventory value. Shrink % = shrink value / inventory value. Fill from shipped / ordered if you seed both. Cards recompute from the selected week. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Flags and percents are computed from weekly totals, not hardcoded on the cards. - Do not add revenue, AOV, ads, or conversion. - Accessible contrast; data at the top with comments. </constraints> <format> Return the full HTML file, then write each KPI formula and which array to replace with weekly totals. </format>