What drifting cutoffs look like
A wholesale bakery takes standing orders from cafés, restaurants, and small grocery accounts. Each account has a cutoff: Tuesday 2 p.m. for Wednesday delivery, Thursday 2 p.m. for Friday delivery. On busy mornings the kitchen still gets late adds by text, drivers leave with handwritten lists that do not match the tickets, and a café that ordered cinnamon rolls gets told at the door that the batch ran short.
This article is about locking wholesale orders after each account's cutoff, building delivery manifests by route and day from those locked orders, and logging substitutions or shortages against the same order so the kitchen, the driver, and the customer see one status.
This is an operations article, not a sales pitch for any particular ordering app. Pricing, credit terms, and what your wholesale agreement must say are business and legal questions for you and your advisors. TwoQM has written about catering inquiries and mobile menus on the inquiry side, and about allergen and menu-change notices between the front and the kitchen. This piece covers wholesale cutoffs and delivery manifests—not generic inquiry routing.
Here is an original example, not a TwoQM client and not a measured result. A bakery runs about thirty wholesale accounts on two delivery days. Standing order sheets live in a binder. Same-day changes arrive by text to whoever answers. Drivers build their own lists from memory and from sticky notes on the packing table. When a SKU runs short, the kitchen decides substitutions on the fly, and the customer hears about it when the driver arrives.
When it doesn't work, the symptoms are familiar: an order accepted after cutoff that the baker never saw, a manifest that omits a café on the route, two different counts for the same SKU, and a shortage explained three different ways. Nobody is careless. The cutoff and the manifest simply live in different places than the bake plan.
Give every wholesale account a cutoff that sticks
Start by turning each wholesale account into a record the office and the kitchen both use. Each record holds:
Account and delivery address. Who receives the order, where it goes, and preferred contact for shortages.
Cutoff times. Day-of-week and clock time when orders lock for each delivery day, exactly as you tell the account.
Standing items and quantities. The baseline order, editable until cutoff.
Delivery day and route. Which route and stop sequence this account belongs on.
Status for the current cycle. Open for edits, locked after cutoff, packed, out for delivery, delivered, or shorted, with the time of each change.
After cutoff, the account cannot add or change quantities without a written exception your company defines. Late requests go into a separate queue the owner or lead baker approves, instead of arriving as a text the kitchen may never see.
Build the manifest from locked orders only
A delivery manifest is the day's list by route: stop order, account name, items and quantities, and any notes the driver needs. Build it only from orders that locked at cutoff, plus any approved exceptions.
When the kitchen packs, they check off against the same manifest. When a driver leaves, they take that list—not a second version written on the packing table. If a stop is added or removed, the change is made on the manifest before the van leaves, so every copy matches.
Log substitutions and shortages on the order
Decide, as a written company rule, what happens when a SKU runs short. Some bakeries substitute a listed alternate. Others reduce quantity and credit the account. Either way, the shortage or substitution should land on the same order record the customer placed: what was ordered, what was packed, who approved the change, and what the customer was told.
The kitchen, the driver, and the customer-facing staff should read the same status. Do not leave the explanation only in a driver's head or a text thread.
Keep kitchen, driver, and customer on one status
A short account view—or a morning email or text your staff send—can show what locked after cutoff, what is packed, and any shortage note in the account's preferred language. If you serve accounts in English and Spanish, keep both templates with the same quantities and facts.
AI can help draft those shortage or delivery notes from the order fields for a person to review. A person sends every customer message. AI does not lock orders, approve substitutions, or decide credit.
Connect ordering, bake plan, and delivery
Many bakeries take wholesale orders in email or a form, plan the bake on a whiteboard, and build driver lists by hand. Custom software can hold the account cutoffs, lock orders, and generate manifests for the routes you already run. Connected systems can pass locked order lines into the tool the kitchen uses for the bake plan, and pass packed quantities back to the manifest the driver carries.
Ordinary automation covers most of the reminders: warn accounts as cutoff approaches, freeze edits at cutoff, and flag routes whose packed counts do not match locked quantities before the van leaves.
Where to start this week
Pick one delivery day and ten wholesale accounts. For each, write down the cutoff you actually enforce, what was ordered, what locked, what was packed, and what the driver delivered. Then list every late add and every shortage, and where each was recorded. The gaps show you where the cutoff and the manifest need to live.
TwoQM builds custom software and connected systems for restaurants and food businesses that run wholesale accounts alongside retail. If your cutoffs live in a binder while drivers build lists from sticky notes, TwoQM can scope an order-lock and manifest workflow around the tools you already use. Pricing explains how business apps, systems, and custom software are scoped.
Tell Us About Your Wholesale Cutoff and Manifest Workflow · Explore TwoQM custom software