Honey ShelfUsing the pipeline
Stage 1 — Stock & Demand
How velocity, days remaining, and suggested order quantities are calculated, and how to read the list.
Stage 1 is the read-only heart of the pipeline: one row per product showing how fast it sells, how long current stock lasts, and how much to make next. All three roles can see it.
Velocity
Daily velocity = units sold in your window ÷ the days the product was actually in stock during that window. The window is 30, 60, 90, or 120 days (or a custom value): your admin sets the org default in the velocity defaults panel, and each user can pick their own window on this screen. Days where the product was sold out are excluded from the denominator — a stockout means zero sales because there was nothing to sell, not zero demand, and counting those days would drag velocity down and cause under-production.
Products with fewer than 7 days of sales history show "insufficient data" instead of a number. A misleading velocity is worse than none; the row fills in as sales accumulate.
Days remaining and stock status
Days remaining = (available stock + virtual stock) ÷ daily velocity. The status chip (Critical / Low / Stockout / Adequate) compares stock and days remaining against the product's reorder point: daily velocity × (lead time + safety buffer). The safety buffer defaults to 7 days and is configurable; the reorder point can also be manually overridden per product in the Catalogue.
The suggested order
Suggested quantity = velocity × (lead time + a fixed 14-day buffer) − available stock − quantity already in production − virtual stock. Lead time is the longest lead among the product's BOM materials, with a 14-day minimum. Two details worth knowing: this fixed 14-day buffer is separate from the configurable safety buffer (which affects only reorder points), and suggestions always use the ORG default window — changing your personal window changes what you see here, not what the system proposes on Stage 2.
Virtual inventory (planning-only)
Finished goods you hold OUTSIDE Honey Shelf — work in progress at a job worker, a second warehouse, goods in transit — can be recorded as virtual stock per product, so planning stops over-ordering. Virtual stock counts toward availability in the planning math only: days remaining and the suggested order treat effective stock as available + virtual, and the same effective numbers flow through to reports, the stock digest, and the Copilot. It is never pushed to Shopify, never consumed by shipments, and never part of your physical available quantity — it is a number you maintain by hand.
Set it inline from the pencil in the Available column (admins and production leads), or in bulk via Settings → Import with the "Virtual inventory" type: a CSV of sku,virtualQty. Import values are SET absolutely — the value replaces the current virtual stock, and 0 clears it. Archived products are rejected per row.
Setting virtual stock does not dismiss production suggestions that already exist — dismiss outdated ones on Stage 2. New suggestion runs (nightly, or Refresh) respect virtual stock.
Finding products
Search by SKU or name, filter by category and stock status, sort by criticality or velocity, and set rows per page. Products flagged do-not-order are excluded from suggestions and alerts but still appear in the list.
Planning batches — ordering from this screen
Admins and production leads can plan a whole production run without leaving this screen. Pick a batch in the batch bar (or create one inline — "Week 34", "Diwali restock"): every row's suggested-order cell becomes a quantity input prefilled with the suggestion, plus an Add button. Add places a REAL production order into the batch — the same material reservation, shortfall tracking, and automatic draft POs as Stage 2. Products already in the batch show an "in batch" chip, and their open orders count as in-production so the suggestion self-corrects.
A batch is identity and filtering, never a gate — it follows its orders through Production Orders, Produce, and Release to Store, but completing or archiving a batch blocks nothing downstream. Manage batches (progress, status, notes, per-batch OMS CSV) from the Batches page linked in the pipeline header.