Ops & Supply

How to set reorder points and safety stock as Restaurant and Hospitality Founders

Ops & SupplyFor Restaurant and Hospitality Founders2 apps11 steps~22 min to set up

You run out of 86'd items on a Friday night because your par levels were set in January and nobody updated them after you added brunch. Your ordering is based on what you bought last week, not what you actually sold. You're checking your POS (Square or Toast) manually, comparing it against a paper order sheet or a Google Sheet your kitchen manager maintains, and calling your Sysco rep by Tuesday to make sure you're covered for the weekend. Safety stock is whatever's still in the walk-in. When a supplier runs short or lead time stretches from two days to five, you find out when the truck doesn't show — not before.

Build this on Starch → See the apps used

Ops & SupplyFor Restaurant and Hospitality Founders2 apps11 steps~22 min to set up

Outcome

What you'll set up

Reorder points for every key ingredient tied to actual sales velocity from your POS, not last week's gut feel — so your walk-in is stocked going into Friday service without over-ordering for a slow Tuesday

Safety stock buffers that account for your supplier lead times and your busiest covers days, automatically flagging when you're likely to run short before you'd need to place the order

A weekly inventory alert that tells you what to order, how much, and why — pulling from your POS sales data and your current on-hand counts — before you even pick up the phone to your distributor

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

Square is connected from Starch's integration catalog and queried live when your inventory app runs. Starch syncs your Plaid bank feed on a schedule to cross-check cash flow against ordering spend. For suppliers like Sysco or your local produce vendor that don't have a public API, Starch automates the order status and confirmation pages through your browser — no API needed. Slack is connected from Starch's integration catalog to deliver your Monday morning reorder alert.

Prompts to copy

Connect my Square POS sales data and show me the average weekly usage for each ingredient category — proteins, produce, dairy, dry goods — over the last 12 weeks, broken out by day of week

Using my sales velocity from Square and my supplier lead times (Sysco is 2 days, produce vendor is 1 day, specialty items are 4-5 days), set reorder points for my top 20 ingredients so I get an alert when I need to order, not after I've already run out

Build me a weekly reorder report: what I need to order this week, the quantity based on projected covers through next Sunday, the safety stock buffer for each item, and which vendor it comes from

Flag any ingredient where my on-hand quantity is below my safety stock threshold and send me a Slack message Monday morning before I place my Tuesday order

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

Walkthrough

Step-by-step

1 Connect Square from Starch's integration catalog. The agent pulls your item-level sales history — covers by day, menu item quantities sold, and revenue by category — going back 12 weeks.

2 Tell Starch your top 20-30 ingredients by order frequency, along with the vendor name and typical lead time for each. You can type this in plain language: 'Sysco delivers Tuesday and Friday, my produce vendor delivers Monday, my specialty protein takes 4 days.'

3 Starch calculates average daily usage for each ingredient by dividing your total ingredient consumption (back-calculated from sales mix) by the number of service days in the period, then weights it toward recent weeks so a slow January doesn't distort your spring numbers.

4 For each ingredient, Starch sets a reorder point: average daily usage multiplied by lead time in days, plus a safety stock buffer sized to your busiest single day's usage. You review and adjust any item where you know the number is off — a custom tasting menu night, a recurring catering order — and Starch saves those overrides.

5 Starch builds an Inventory Planner app for your specific ingredient list, with current reorder points and safety stock levels visible in one dashboard. You and your kitchen manager both have access.

6 Connect Slack from Starch's integration catalog. Set an automation: every Monday at 7 AM, Starch compares your current on-hand counts (entered by your kitchen manager the night before) against your reorder points and sends a message listing what needs to be ordered, the quantity, and which vendor.

7 For any supplier whose order portal is web-based but has no API — a regional specialty vendor, your linen service, a local bakery — Starch automates status checks through your browser. You get confirmation that orders landed without logging into four portals.

8 Connect Plaid so Starch syncs your bank transactions on a schedule. The app flags weeks where your food purchasing spend is running above your food cost target percentage, so you catch over-ordering before it hits your P&L.

9 After your first 4 weeks of live data, Starch surfaces the ingredients where you consistently had leftover safety stock (over-ordered) and the ones where you got close to the reorder point before the next delivery (under-covered). You adjust those buffers in plain language: 'Tighten the safety stock on salmon by 20%, increase the buffer on butter by half a case.'

10 For weeks with events — a private dining buyout, a holiday weekend, a neighborhood festival — add a note in Starch ('We have a 60-person buyout Saturday the 14th, expecting 30% more protein usage'). The reorder calculation for that week updates automatically.

11 At month-end, Starch generates a summary: total ingredient spend, which items you 86'd (you log these manually or via browser automation if your POS tracks it), and how often your safety stock actually got used. This becomes the input for adjusting your par levels the following month.

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

Week of April 7, 2026 — Busy spring weekend with a private event Saturday

Sample numbers from a real run

Chicken thighs (primary protein, Sysco)	48
Salmon portions (weekend feature, specialty vendor)	24
Butter, unsalted (bulk, Sysco)	30
Fingerling potatoes (produce, local vendor)	35
Heavy cream (dairy, Sysco)	18
Heirloom tomatoes (seasonal, farmers market)	20

Coming into the week of April 7th, your Monday morning Slack alert from Starch listed six items below or approaching reorder points. Chicken thighs were the critical one: your average usage is 40 portions per weekend service, you had 48 on hand, and Saturday's private event added an estimated 30 portions. Your reorder point for chicken (lead time: 2 days, safety stock: 1 day's average usage = 20 portions) flagged a shortfall by Thursday if you didn't order Monday. Starch's message said: 'Order 60 portions of chicken thighs from Sysco today — current stock won't cover the weekend event plus normal service through Sunday.' Your kitchen manager placed the order Monday afternoon. Salmon was flagged as a watch item: 24 portions on hand, specialty vendor lead time is 4 days, and your safety stock buffer is 12 portions. Not a crisis yet, but Starch surfaced it so you ordered a top-up Wednesday rather than scrambling Friday. Heirloom tomatoes came from the farmers market with no API — Starch checked the market's website through your browser and confirmed they'd have your usual quantity available Saturday morning. Total food spend for the week came in at $1,840 against a projected food cost of 28% on $6,800 in covers — Starch flagged that you were 1.2 points over on dairy because cream usage on the private event ran higher than the estimate, giving you a data point to build into next month's event buffer.

Measurement

How you'll know it's working

Food cost percentage by week (actual vs. target, typically 28-32% for full-service independent restaurants)

86 incidents per service — number of times you ran out of a menu item mid-shift

Inventory turnover by category — how many days of stock you're carrying in proteins, produce, dairy, and dry goods

Order accuracy rate — percentage of weeks where what you ordered matched what you actually needed, without an emergency add-on order

Waste as a percentage of food purchases — what spoiled or was over-ordered relative to what you sold

Comparison

What this replaces

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

MarginEdge

MarginEdge does invoice scanning and food cost tracking well, but it doesn't set dynamic reorder points based on sales velocity — you still decide manually when to order and how much

Google Sheets par sheet (the current default)

Free and flexible, but someone has to update it every week, it doesn't connect to your POS, and it can't send you an alert when you're approaching a reorder threshold

BlueCart or Orderly

Purpose-built for restaurant ordering workflows, but focused on the ordering interface rather than connecting your POS sales data to your inventory logic — you still set the pars manually

Toast Inventory (if you're on Toast)

Native to your POS so item-level data is cleaner, but the reorder logic is basic and it doesn't cross-reference your bank feed or flag cash flow implications of your ordering decisions

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

I use Square for my POS. Can Starch actually pull item-level sales data, not just totals?

Yes. Starch connects Square from its integration catalog and queries it live — item-level sales, quantities sold, and revenue by category. You'll see which menu items drove which ingredient usage, not just total revenue. For very granular ingredient-level consumption (e.g., grams of butter per dish), you'll give Starch your recipes once and it back-calculates from there.

My produce vendor and one specialty supplier don't have any kind of online system — I call them. Can Starch still help?

For suppliers with no digital presence at all, Starch can't automate phone calls. What it can do is generate your order quantities so you go into that call knowing exactly what to ask for, rather than estimating on the spot. For suppliers with any web presence — an order portal, a product catalog, even just a contact form — Starch can automate through your browser without needing an API.

The Inventory Planner and Demand Planner apps you mentioned — are those available now?

Both are currently in development. You can request beta access to get notified when they launch. In the meantime, you can describe exactly what you need in Starch — 'Build me an inventory tracking app that shows reorder points by ingredient, connected to my Square sales data, and sends me a Slack alert Monday mornings' — and Starch's AI will build that custom app for you today using its live connections.

Is my Square or bank data stored by Starch?

Starch syncs your Plaid bank data on a schedule and stores it in Starch's database to power your dashboards. Square data is queried live from Starch's integration catalog when your app runs — it's not stored in Starch's database between queries. Starch is not SOC 2 Type II certified, which is worth knowing if your accountant or a franchising agreement has specific data compliance requirements.

Can I set different reorder points for different seasons — summer patio versus January slowdown?

Yes. You tell Starch in plain language: 'In May through September, assume 20% higher weekend covers and adjust my produce reorder points accordingly. In January and February, tighten safety stock on proteins by 15%.' Starch applies those rules going forward and you can update them any time the same way — no spreadsheet formula editing required.

My kitchen manager is the one who does ordering, not me. Can she use this too?

Yes. Multiple team members can access Starch. Your kitchen manager can log on-hand counts, review the Monday reorder list, and mark items as ordered. You see the same dashboard and can check in without having to ask her directly — which also means you're not the bottleneck if she's not sure what to order for an event week.