Which SKUs am I about to run out of?

The short answer

Astra answers "which SKUs am I about to run out of" by joining your inventory table (in MongoDB, Airtable, or wherever you keep it) with the last 30 days of Stripe order velocity per SKU, then projecting days-of-stock-remaining for every line item. She flags anything that runs out in the next 14 days, ranks by revenue impact (a fast-mover going out costs more than a slow tail item), and suggests a reorder quantity sized to your usual lead time. The output is a Lark message: at-risk SKUs, days until stockout, daily burn rate, suggested reorder qty, and the historical supplier link from your Notion vendor sheet. She also flags the opposite — SKUs sitting on 6+ months of inventory tying up cash. You stop discovering stockouts from a customer support ticket.

How Astra actually does it

1. 1

   Read inventory levels

   Pull current stock per SKU from MongoDB inventory collection or Airtable base.

   MongoDB
2. 2

   Calculate burn rate

   Stripe orders by SKU over last 30 days → daily units sold per SKU, smoothed for weekday seasonality.

   Stripe
3. 3

   Project days-of-stock

   Current stock ÷ daily burn = days remaining. Flag anything <14 days as at-risk.

4. 4

   Suggest reorder quantity

   Lookup vendor lead time from Notion supplier sheet, recommend qty to cover lead time + 30-day safety buffer.

   Notion
5. 5

   Send the digest

   Lark table: at-risk SKUs, days remaining, suggested reorder, supplier link. Plus an overstocked-SKU section.

   Lark

What it looks like in chat