How to Automate GoPrep

A meal prep kitchen commits to the week before it cooks

GoPrep is the ordering platform a weekly meal prep or catering business sells through. Customers pick meals from a branded storefront, choose a one-time order or a recurring subscription, and the kitchen finds out on Monday what it is cooking on Tuesday.

That shape is unusual. A restaurant discovers demand as it walks through the door. A meal prep company has to know demand before it buys a single chicken breast, because everything is portioned, labelled and cooked in one run against a cutoff that closes days before anybody eats. Miss the count and you either throw food away or ring twenty customers to apologise.

So GoPrep holds the menu, the order book, the subscriptions, the delivery days, the special instructions and the nutrition panel that ends up on the lid. For a kitchen doing a few hundred meals a week it is the shopfront, the production office and the customer file at the same time.

The counting starts the moment orders close

Almost everything after the cutoff is counting.

Somebody totals the orders by meal and splits them across prep stations. Somebody works the ingredient list back into a shopping order and compares it with what is already in the walk-in. Somebody prints labels, checks the allergy flags against the special instructions, and then checks them again, because a nut flag is not a thing you get wrong twice.

Then there is the money and the people. A subscription card declines and the meal is already cooked. A customer who ordered every week since March quietly stops, and nobody notices for a month. Tuesday's food cost gets compared with what the supplier actually charged, usually in a spreadsheet, usually late.

None of it is difficult. It is the same handful of comparisons every week, each one needing one screen opened next to another.

GoPrep

Ingredient costs before the order This week's shopping list priced against what your suppliers are actually charging today, so an ingredient that jumped can be swapped before the cutoff closes.

Declines caught the same week A subscription card that failed on Monday matched to meals already cooked and bagged, rather than found at month end.

Subscribers who quietly stopped The customers who paused twice in a row, listed with what they used to order every week, ready for a note that mentions it.

Production reports know the orders and nothing else

GoPrep automates more of the prep week than most kitchens switch on.

Production Reports tell the kitchen the exact quantity of each meal to make, and they break down into separate production groups so the hot line and the cold bench get their own sheet. Ingredients Reports roll the same orders back into what has to be bought. Packing Slips go in the bag with heating instructions and expiry dates, and labels with nutrition facts print in a few clicks. Recurring subscriptions bill themselves, menus rotate on a schedule, and automated SMS reaches the whole customer list.

All of that operates on orders, meals and customers held inside GoPrep.

Everything it automates lives on one side of a login. The supplier portal showing this week's chicken price is on the other. So is the bank account where card settlements land, the co-packer's stock sheet, the driver's route for Thursday, and the marketplace that sent you half of last week's one-time orders. GoPrep can tell you what to cook. It cannot go and find out what it will cost.

A prep list that already knows what the food cost

Once an order sheet can be carried out to those other screens, the week stops being a series of recounts.

This week's ingredient list priced against what four suppliers are charging this morning, so a jump on chicken shows up before the order is placed rather than on the invoice afterwards. Card declines matched to meals already cooked and bagged, caught on Wednesday instead of at month end when a customer has eaten six free dinners.

Subscribers who paused twice running, listed with what they used to order, so a win-back note goes out while the habit is still fresh. Delivery windows checked back against the driver's schedule, so a route with nineteen drops and eighteen bagged orders is flagged while it can still be fixed. Allergy flags read off the orders and held against the recipe the kitchen is actually going to make that day.

None of that needs an API, a developer, or an integration somebody else has to build first. The limit is the same in each case: the counting gets handed over, the choosing stays in the kitchen. Anything addressed to a customer about money or an allergy gets prepared, then read by a person.

Counting between screens is not cooking

Pricing a shopping list across four supplier logins is not cooking, and neither is chasing a declined card. Both still decide whether the week made money.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens GoPrep, the supplier site, the bank or the mailing tool, reads each one, and puts the comparison in front of you with the differences named and their source shown.

It runs on your schedule inside your own private environment, and you can watch a run and stop it. Nothing is changed in the menu or the order book, and anything going to a customer waits for somebody to send it.

The workflows below are already built, and each one names the screens it opens.