Eyeball the Inventory tab
Free
Catches the obvious.
The Inventory tab shows on-hand, not runway. A SKU at 18 units looks safe until it sold 6 a day last week and the supplier needs 10.
Shopify to Slack, every morning
Spot the runway. Send the reorder.
Daily Slack digest of SKUs about to run empty. Runway in days. From $29/mo.
Before the cron
Three ways the reorder gets missed.
Low-stock email alert
Free
Fires too late.
A static threshold trips after the runway is already a few days. The PO that should have shipped yesterday ships tomorrow.
Weekly inventory meeting
One hour, two people
Right cadence, wrong window.
Weekly works for slow movers and breaks on the fast ones. A SKU at 14 days Monday is at 5 by Friday's meeting.
What lands in Slack
A short list, sorted by days of runway.
Header line
Store name, date, horizon. 'Acme Co, 14-day stockout watch, Tue 26 May.'
Top 15 SKUs
Ranked by runway, shortest first. SKU, product, days. The reorder shortlist.
Runway in days
Forecast from the prior 30 days of orders, divided into on-hand. Plain integer. No commentary.
Lead-time flag
An ochre dot when runway is shorter than your supplier's lead time. The PO is already late.
Horizon footer
Two numbers: SKUs at-risk today, change vs. yesterday. The trend line.
Source link
Each line links straight to the Shopify product page. One click to the PO.
How it runs
Connect twice. The cron does the rest.
01
Connect Shopify and Slack
OAuth both, pick the alert channel. Two minutes, one time.
02
Pick the cron time
Default 7am store-local. Override to fit warehouse open. First digest lands tomorrow.
03
Read the digest, send the PO
The names at the top are the POs to send. The ones you didn't expect are the misses caught.
Pricing
One cron. One channel. Monthly.
Starter
$29/mo
Up to 50 SKUs, one Shopify store, one Slack channel.
- Daily 7am digest, top 15 at-risk SKUs
- Runway in days per SKU
- 14-day stockout horizon, 7-day lead-time assumption
- 30-day order window for velocity
Standard
$79/mo
Up to 500 SKUs, one store, multiple channels by warehouse.
- Everything in Starter
- Top 50 at-risk per digest
- Adjustable lead-time + horizon per run
- Per-channel routing by tag, SKU prefix, or location
- Backfill the prior 7 days on first connect
Growth
$199/mo
Up to 5,000 SKUs, multi-store, multi-warehouse.
- Everything in Standard
- Multi-store consolidation in one digest
- Per-warehouse runway split
- Velocity windows up to 90 days
- CSV export of each daily run, retained 90 days
Billed monthly. Cancel any time. SKU counts are upper bounds.
What it is. What it isn't.
A cron, not a forecasting suite.
Right tool when
- You sell physical goods on Shopify.
- Slack is where ops reads alerts.
- Days-of-runway is the unit you think in.
- One digest fits your SKU count.
Wrong tool when
- You need a planning suite with promo modelling.
- You sell services, subs, or digital goods.
- Inventory of record isn't Shopify.
- You need approval flows or auto-PO.
The runway is a forecast off 30 days of orders and your configured lead time. It catches the ordinary misses, not the viral TikTok. Treat it as the shortlist, not the decision.
The five questions every ops manager asks
Answers worth having before the cron starts.
- Why pay for this instead of writing it myself?
- You can. Three Shopify endpoints, one Slack endpoint, a cron, the runway math. About a weekend of work then forever of maintenance. The $29 is for not maintaining it.
- How is this different from Shopify's built-in low-stock alert?
- Shopify's is a static threshold. This is a velocity forecast: days of runway against the prior 30 days, ranked across the catalog, posted where ops already reads.
- What happens if the cron misses a day?
- It logs the miss and runs the next morning. The horizon footer's 'change vs. yesterday' goes blank — your signal. Two misses in a row, we email the account owner.
- Can I change the horizon, lead time, or top-N?
- Starter locks the defaults (14 / 7 / 15). Standard and Growth are per-run configurable.
- What does the data audit look like?
- We read products, inventory levels, and 30 days of orders. We write one Slack message per day. We don't store order data after the digest sends. Full list on the Privacy page.