What if my inventory isn't in MongoDB?

Tycoon Agent reads from Airtable, Google Sheets, Shopify, WooCommerce, or any database with a SKU + qty column. She just needs a way to map SKU IDs to current stock. One-time setup, then automatic.

How accurate is the burn rate forecast?

Within ~10% for SKUs with steady demand. For seasonal items she uses last year's same-week velocity if you have ≥1 year of data. New SKUs (under 14 days) get a wider safety buffer because the trend isn't established.

Can she actually place the reorder?

She drafts the PO email or supplier-portal form and asks you to confirm. With Composio you can approve the reorder in one tap and she submits it. Most users prefer the human-in-the-loop step on first orders, then full automation for repeat SKUs.

What about returns or refunds skewing the burn?

She nets refunded units out of the burn calc and flags any SKU with abnormal return rate (>10%) as a separate quality issue worth investigating before reordering.

Ask Tycoon Agent: Which SKUs am I about to run out of?

You'd think this needs a dedicated inventory tool — Tycoon Agent forecasts stockouts from your existing Stripe order data and flags reorders before you sell out.

The short answer

Tycoon Agent 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 Tycoon Agent actually does it

Read inventory levels
Pull current stock per SKU from MongoDB inventory collection or Airtable base.
MongoDB
Calculate burn rate
Stripe orders by SKU over last 30 days → daily units sold per SKU, smoothed for weekday seasonality.
Stripe
Project days-of-stock
Current stock ÷ daily burn = days remaining. Flag anything <14 days as at-risk.
Suggest reorder quantity
Lookup vendor lead time from Notion supplier sheet, recommend qty to cover lead time + 30-day safety buffer.
Notion
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

YouWhich SKUs am I about to run out of?

Tycoon AgentOut of 47 active SKUs, **6 at-risk** in the next 14 days: 1. **SKU-1024 "Forest Green Tee L"** — 23 units, 4.1/day burn → **6 days left**. Reorder 200 (90-day cover). $48 ARR per unit. 2. **SKU-2117 "Cream Mug 12oz"** — 41 units, 3.8/day → **11 days**. Reorder 300. 3. **SKU-1031 "Forest Green Tee M"** — 67 units, 5.2/day → **13 days**. Reorder 250. 4-6. Three slower SKUs all 12-14 days out, lower revenue. **Reorder cost:** $4,840 across 6 SKUs. Vendor (PrintCo) lead time: 9 business days. **Also flagging — overstocked:** "Holiday Box 2025" 320 units, 0.2/day burn → 1,600 days of stock. $2,300 cash tied up. Suggest discount campaign or bundle into Q2 promo. Draft the PrintCo PO?

What you get back

Lark digest with at-risk SKUs ranked by stockout urgency, suggested reorder quantities sized to lead time, supplier links, plus an overstocked-SKU section to free up cash.

Cadence: Daily 8am + immediate alert if any SKU drops to <7 days remaining.

Which SKUs am I about to run out of?