Ops & Supply

How to set reorder points and safety stock as DTC Brand Founders

Ops & SupplyFor DTC Brand Founders2 apps11 steps~22 min to set up

Your reorder math lives in a Google Sheet that one person built eighteen months ago and nobody fully trusts anymore. You're eyeballing velocity from Shopify, guessing lead times from memory, and carrying 60 days of your slowest SKU while your bestseller goes out of stock two weeks before a Meta campaign peaks. You find out you needed to reorder three weeks ago when your 3PL emails you a low-stock alert. Safety stock is whatever number felt conservative at the time. When you run a promotion, nobody updated the sheet. When your co-packer adds a week to lead times, nobody updated the sheet. The stockout costs you more than the overstock, but both are quietly killing margin.

Build this on Starch → See the apps used

Ops & SupplyFor DTC Brand Founders2 apps11 steps~22 min to set up

Outcome

What you'll set up

Automated reorder points per SKU, calculated from real Shopify velocity, your co-packer's actual lead times, and a safety stock buffer sized to your demand variability — not a gut number

A live inventory view that shows days-of-stock-remaining by SKU across your 3PL and warehouse locations, with a reorder alert that fires before you're already out

A single natural-language prompt layer so when your lead times change, your promotional calendar shifts, or a new SKU launches, you update the logic in plain English instead of re-engineering a spreadsheet

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Inventory Planner Demand Planner

Data sources & config

Shopify connects from Starch's integration catalog — the agent queries your orders and inventory live when the reorder logic runs. Starch syncs your Plaid-connected bank transactions on a schedule so cash context is available alongside stock levels. Slack connects from Starch's integration catalog so reorder alerts and daily stock summaries push to your ops channel automatically. If your 3PL or co-packer exposes a portal but no API, Starch automates it through your browser — no API needed.

Prompts to copy

Connect my Shopify store and show me daily units sold per SKU over the last 90 days, then calculate reorder points assuming a 21-day supplier lead time and 7 days of safety stock based on demand variability

Set up an alert that fires to Slack when any SKU drops below its reorder point, and show me a dashboard of days-of-stock-remaining sorted by fastest-moving SKUs first

When I run a promotion in Meta Ads, automatically adjust the demand forecast for the promoted SKUs by the average lift we've seen on past campaigns and flag if current inventory won't cover the projected uplift

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Shopify from Starch's integration catalog. The agent pulls your last 90 days of order history per SKU — units sold per day, channel, and variant — without you exporting a CSV.

2 Tell Starch your supplier lead times per SKU in plain English ('Supplier A takes 18 days for the whey protein SKU, 14 days for the electrolyte packet'). Starch stores this as editable logic, not a locked formula.

3 Starch calculates average daily demand and demand variability per SKU from your Shopify data, then sets a safety stock buffer sized to cover variability during the lead-time window — typically 1–2 standard deviations depending on how stockout-averse you tell it to be.

4 Reorder points are set automatically: (average daily demand × lead time in days) + safety stock. You see the formula and the output for every SKU so you can sanity-check the math.

5 Connect Slack from Starch's integration catalog. Set up an automation: 'Every morning at 7am, check current inventory levels against reorder points and send a Slack message listing any SKUs at or below their reorder point, with days-of-stock-remaining and suggested order quantity.'

6 Wire in your promotional calendar. Tell Starch: 'When a Meta Ads campaign starts for a specific SKU, add 30% to the demand forecast for that SKU for the campaign duration.' Connect Meta Ads from Starch's integration catalog so campaign start and end dates pull automatically.

7 If your 3PL has a web portal, Starch checks stock levels through your browser — no API needed — and reconciles them against Shopify's reported inventory. Discrepancies surface in your daily stock dashboard.

8 Starch syncs your Plaid bank data on a schedule so your inventory dashboard can show you the cash cost of a suggested reorder alongside the stock alert. You see 'reorder 2,000 units of SKU-014 — estimated $18,400 COGS' in the same view.

9 When lead times change — your co-packer adds a week — you tell Starch in plain English. The reorder points recalculate across every affected SKU immediately. No spreadsheet to find, no formulas to audit.

10 At the end of each week, an automated summary goes to Slack: SKUs that triggered a reorder alert, SKUs with more than 90 days of stock on hand (overstock flag), and the single SKU with the highest stockout risk in the next 30 days.

11 As Inventory Planner and Demand Planner move from beta into full release, these surfaces become starter templates you can install and customize — reorder logic, safety stock methodology, and alert thresholds adjustable in natural language without rebuilding from scratch.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 reorder cycle — 3-SKU DTC supplement brand

Sample numbers from a real run

SKU-001 Whey Protein 2lb — current stock	340
SKU-001 average daily units sold (90-day avg)	38
SKU-001 supplier lead time (days)	18
SKU-001 safety stock (7-day buffer)	266
SKU-001 reorder point (units)	950
SKU-001 days of stock remaining	9
SKU-007 Electrolyte Packets — current stock	4,200
SKU-007 average daily units sold	28
SKU-007 days of stock remaining	150
Suggested reorder — SKU-001, 2000 units — estimated COGS	21,400

On April 3rd, Starch's morning Slack alert flags SKU-001 (Whey Protein 2lb) as below its reorder point. Current stock is 340 units. Average daily demand is 38 units over the last 90 days, and the supplier lead time is 18 days — meaning you need at least 684 units just to cover lead time, plus 266 units of safety stock (7 days × 38 units/day), for a reorder point of 950 units. You're already 610 units below that threshold, with 9 days of stock left. A Meta campaign for the same SKU started April 1st, which Starch detected from your connected Meta Ads account and used to bump the demand forecast by 30% — so actual days-of-stock-remaining is closer to 7. The same alert shows SKU-007 (Electrolyte Packets) at 150 days of stock on hand, automatically flagged as overstock risk. You approve the SKU-001 reorder of 2,000 units ($21,400 COGS, visible from your Plaid-synced bank balance in the same dashboard) and tell Starch to add a note to next quarter's SKU-007 purchase order to cut quantity by 40%. None of this came from a spreadsheet.

Measurement

How you'll know it's working

Days of stock remaining by SKU (target: never below lead time + safety stock buffer)

Stockout rate — percentage of SKUs that hit zero stock in a rolling 90-day window

Overstock carrying cost — value of inventory held beyond 90 days of forward demand

Reorder accuracy — how often actual restocking quantity matched the Starch-suggested quantity

Cash tied up in inventory vs. runway (cross-referenced from Plaid bank sync)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Google Sheets reorder tracker

Free and infinitely flexible, but someone has to update lead times, pull Shopify exports, and maintain the formulas — and that someone is usually you at 11pm before a campaign goes live.

Shopify's native inventory alerts

Sends a low-stock email, but doesn't know your lead times, doesn't calculate safety stock, and can't adjust thresholds when you're running a promotion.

Cin7 or Brightpearl

Purpose-built inventory systems with solid reorder logic, but require dedicated implementation time, charge per-location or per-user, and don't pull in your ad spend or bank balance — so you're still context-switching to understand the full picture.

Inventory Planner (the standalone SaaS tool)

Strong Shopify integration and reorder point math, but it's a separate subscription, doesn't talk to your financial data or ad platforms, and still requires you to manually configure SKU-level settings without a natural-language interface.

On Starch RECOMMENDED

One platform — inventory planner, demand planner all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Inventory Planner and Demand Planner are listed as 'currently in development.' Can I use Starch for reorder points today?

Yes. Both apps are in development and you can request beta access to get notified at launch. In the meantime, you can describe exactly what you want in Starch and the agent builds a custom surface for you — reorder point calculator, days-of-stock-remaining dashboard, Slack alert automation — using your live Shopify data and Plaid-synced financials. The starter templates accelerate setup once they launch; they're not a prerequisite.

My 3PL doesn't have an API. Can Starch still pull stock levels from their portal?

Yes. If your 3PL has a web-based portal you can log into, Starch automates it through your browser — no API needed. It navigates the portal, reads the stock data, and reconciles it against your Shopify inventory. This is a standard Starch pattern, not a workaround.

Will Starch automatically place purchase orders with my supplier, or just flag the reorder?

Starch can flag the reorder and calculate the suggested quantity automatically. For actually placing the PO, it depends on your supplier: if they have a web portal, Starch can automate the order submission through your browser. If they work via email, Starch can draft the PO and send it from your connected Gmail or Outlook account. It won't place orders without your confirmation unless you explicitly set it up to do so.

My demand isn't stable — we run promos every 6 weeks and Q4 is completely different from Q2. Can the reorder logic account for that?

Yes, and this is exactly where the natural-language approach helps. Tell Starch: 'When a Meta campaign is running for a SKU, increase the demand forecast by 30% for that SKU.' Or: 'In October and November, multiply all demand forecasts by 1.4 for seasonal lift.' The Demand Planner (in development) is built specifically to handle promotional lifts and seasonal patterns — it's one of the core reasons it exists. Until it launches, you configure this logic conversationally in Starch and it builds the adjusted forecast rules for you.

Is Starch SOC 2 certified? I'm cautious about connecting my Shopify and bank data.

Starch is not SOC 2 Type II certified yet. That's an honest answer. If SOC 2 is a hard requirement for your business, it's worth knowing upfront. For most DTC founders at the stage where reorder math still lives in a spreadsheet, the practical risk of the data connection is lower than the business risk of another stockout — but you should make that call with full information.

How is this different from just setting low-stock alerts in Shopify?

Shopify's low-stock alert fires at a fixed unit threshold you set manually per SKU. It doesn't know your lead times, so it can't tell you whether 200 units is 3 days of stock or 30 days of stock. It doesn't know you have a campaign running next week that will double velocity. And it doesn't tell you the cash cost of the reorder alongside the alert. Starch calculates the reorder point from your actual velocity, your stated lead times, and your promotional calendar — and surfaces the cash context from your bank data in the same place.