What belongs on a bake and pack list when you run bakery subscriptions

A bakery subscription only pays for itself when the bake list and the pack list agree with money already on the books. Recurring revenue means buyers on auto-pilot — standing orders that charge at your cutoff — so next week’s flour order is a number, not a hope. The lists are how that number leaves the oven and reaches the right tote.

Miss the split and you get the classic scramble: you baked the right count, packed the wrong bags, and spent Saturday morning apologizing with a free croissant. Get it right and cutoff night feels boring in the best way.

Bake list vs pack list — different jobs

The bake list answers what comes out of the oven for this bake day. Country loaf × 24. Sesame × 18. Focaccia trays × 6. It rolls up every standing order that locked for that day, plus any one-offs that made it before the mode’s deadline, constrained by the per-day stock you set.

The pack list answers who gets which bag, and how it leaves. Delivery stops in route order. Pickup window sorted by customer name or slot. Market date grouped by stall pickup. Same loaves; different sorting key.

BakeFleet uses that product language on purpose. Production cares about counts. Handoff cares about labels. Mixing them in one spreadsheet is how the third focaccia ends up in the wrong cooler.

The bake list is for the person with flour on their hands. The pack list is for the person with a Sharpie. Sometimes that is the same person on different hours. The document still needs two jobs.

Start from cutoff, not from the mixer

Standing orders do not charge at signup. They do not take a month up front. When a mode’s cutoff hits — delivery round, pickup window, or market date, each with its own days, fee, and deadline — the card on file is charged for that handoff and the order locks.

That is when the bake list becomes real. Before cutoff, customers can still skip, pause, or swap. After cutoff you are baking to paid demand for that mode’s day. Print (or open) the bake list from locked orders, not from last week’s guess plus a sticky note.

If Tuesday delivery closes Monday 9pm and Saturday market closes Thursday noon, you get two bake lists on two clocks in the same kitchen. That is normal. One bakery-wide “order by Sunday” rule is what breaks both.

Charge-at-cutoff is what makes the lists trustworthy. A line on the bake list is not a maybe. It is a paid reservation against that day’s stock. Recurring revenue shows up as oven math, not as a soft promise on a flyer.

Per-day stock is the ceiling on both lists

Set how many of each item you are making for that bake day. The storefront stops when the count is gone — including concurrent checkouts fighting over the last loaf. Standing orders reserve against that day’s stock when the order generates ahead of cutoff. Walk-ups and late one-offs see what is actually left.

So the bake list cannot quietly invent loaves the stock calendar never allowed. If you set sesame at 18 and seventeen standing orders already reserved, the eighteenth walk-up gets turned away online instead of getting an apology text after the fact. The pack list then only contains bags you can fill.

Call stock what you committed to bake for the day, even if dough is still cold when the list locks. Same rule either way: no line on the pack list for bread that was never going to exist.

Raising stock after cutoff to squeeze in a friend who texted late is how the lists lie. The bake list grows, the pack list grows, and the oven does not. Subscribers learn the storefront does not mean what it says. Protect the ceiling you published.

What belongs on the bake list

Keep it production-shaped:

• Item and quantity for this bake day only — not a week rollup that hides which market vs which round
• Notes that change the bake (seeded vs plain, sliced, allergen flags you already track)
• Totals that match locked standing orders plus accepted one-offs against per-day stock
• Batch or tray hints if your kitchen uses them — six focaccia trays, not “a bunch”
• Nothing about addresses, tote numbers, or who picks up when — that is pack-list work

If an item appears because someone skipped after you mentally counted them in, your process is still living in your head. The list should come from the locked orders after cutoff, every time.

A bake list that spans three handoff days in one sheet will hide which oven run feeds which mode. Split by bake day. If Friday’s bake feeds both Thursday-night leftover pickup and Saturday market, still treat Friday as one bake day with one stock ceiling — then pack into two pack lists by mode.

What belongs on the pack list

Keep it handoff-shaped, and split by fulfillment mode:

Delivery round — stop order that matches the route, customer name, items per stop, delivery fee already charged at that round’s cutoff, any gate code or note that saves a callback. Sequence matters. Bag three before bag one and you double back across town.

Pickup window — sorted for the counter rush (name or time slot), items per bag, ready-by time that matches the window you published. People arrive in clusters. A pack list sorted by first name beats a pile of unlabeled bags under the counter.

Market date — bags grouped for the stall, customer name big enough to read when three people arrive at once, market fee if you charge one, nothing that assumes a van sequence. Standing-order markets still need names on bags when two families both claim the sesame.

Same bread can appear on three pack lists in one week if you run all three modes. That is fine. Do not merge them into one “everything Saturday” sheet unless you enjoy sorting in the parking lot.

Pack lists should reflect what actually charged. If a card failed and the order did not lock, that bag should not ride the van. Baking for unpaid hope is accounts receivable theater.

A subscription week that behaves

Monday night: Tuesday delivery cutoff hits. Cards charge. Bake list for Tuesday’s round locks. Pack list sorts by route. Per-day stock for Tuesday already reserved those loaves; nothing else sells into that count.

Tuesday morning: bake from the bake list. Pack in route order. Drive. You are not rewriting counts from texts at 5am. Recurring revenue showed up as paid lines before flour hit the bowl.

Wednesday: Thursday pickup still open on its own clock. Saturday market still open on its own. Different deadlines, different lists later. Tuesday’s lists are done; do not reuse them as a template without rebuilding from the next cutoff.

Thursday noon: Saturday market closes. Standing orders for the stall charge. Bake list for Friday’s market bake prints. Pack list groups by customer for the canopy. Friday pickup, if you run one, may still be taking orders until its own deadline.

Friday: market bake from Thursday’s locked list. Pack for the stall. If Thursday pickup also locked earlier, its pack list is a separate stack — counter bags, not canopy bags.

Saturday: load market. Hand out by name. Walk-ups get what stock allowed. Rain optional. The floor of paid bags already left the oven.

Sunday: glance at next week’s standing orders. Adjust a stock number if Wednesday sesame sold out by Tuesday afternoon. Do not rebuild the customer list from scratch. That is the auto-pilot you wanted when you stopped scrambling for new sales every week.

Mistakes that blow up subscription weeks

Baking to last week’s standing-order total after three people skipped — always rebuild from this cutoff’s locked orders.

Packing from the bake list alone — counts without names is how the wrong bag leaves first.

One shared deadline across delivery, pickup, and market — someone always gets a bad clock; usually you.

Raising per-day stock after cutoff to “make room” for a friend who texted late — that is how concurrent inventory lies, and how subscribers learn the storefront does not mean what it says.

Treating the market pack list as optional because “everyone just grabs their loaf” — standing-order markets still need names on bags when two families both claim the sesame.

Merging three modes into one Saturday spreadsheet — you will sort in the parking lot, and the delivery fee line will confuse the pickup customers.

Printing the bake list before cutoff “to get ahead” — then three people skip and you have already mixed. Wait for the lock. Ahead is not ahead if it is wrong.

Ignoring failed charges — a bag for an order that never locked is a gift you did not mean to give. Fix billing; do not bake through it.

Edge cases the lists have to survive

Holiday weeks: extra one-offs on the market date, skips on Tuesday delivery. Bake lists must rebuild from this cutoff’s locks, not from a saved “usual week” template. Pack lists must keep modes separate so the dinner-party brioche does not ride a delivery route by accident.

Allergen or sliced notes: belong on the bake list if they change the bake, and on the pack list if they change the label. Duplicate the flag on purpose. Production and handoff both need it; neither should hunt the other’s sheet.

Partial shortages after the bake: if something comes up short, the pack list is where you see who is affected. Charge-at-cutoff already happened; making it right is a refund or replacement conversation — not a silent missing loaf. Keep the pack list as the source of truth for who was promised what.

Shared bake day feeding two modes: Friday oven run feeds Saturday market and a Friday evening pickup window. One bake list for Friday’s stock ceiling. Two pack lists after each mode’s cutoff. Do not invent two stock ceilings for one oven run.

Staff handoff: opener reads bake list; packer reads pack list; driver reads only the delivery pack list. One mega-sheet gets “helpfully” resorted and breaks the route.

Checklist: get the lists without flipping the shop

1. Run the modes you already use — delivery, pickup, market — each with its own days, fee, and deadline.
2. Set tight per-day counts for the next few bake days; loosen once cutoffs teach real demand.
3. Point regulars at standing orders on the handoff they already use — charged at that mode’s cutoff, not at signup.
4. After each cutoff, open bake list from locked orders only.
5. Open pack list split by mode — route, window, or stall — never a merged “everything” sheet.
6. Confirm pack list bags match what stock allowed and what charged.
7. Bake. Pack. Hand off. Do not edit stock upward mid-scramble.
8. Next boring week, migrate another text-thread regular onto a standing order. Leave the rest until you are ready.

You do not owe the internet a big-bang switchover. One mode with clean lists beats three modes with a notebook under the flour bin.

FAQ

Why two lists instead of one? Oven math and handoff labels are different jobs. One sheet usually fails one of them under time pressure.

When do I print the bake list? After that mode’s cutoff, when standing orders have charged and locked. Before cutoff, skips and swaps can still change the count.

What if dough is still cold at cutoff? Fine. Per-day stock is what you set for that bake day. The bake list commits to paid demand against that ceiling — not a warehouse photo of finished loaves.

Do markets need a pack list? Yes, if standing orders collect at the stall. Names on bags beat arguments at the table. Markets do not go away when subscriptions run; they still need handoff discipline.

Can the same loaf show on multiple pack lists in one week? Yes — different modes, different days. Split lists by mode and bake day. Do not merge.

Where do fees show? On the mode, and on the pack/handoff side as already charged at that mode’s cutoff. Delivery fee on the round. Market fee on the market date if you use one.

Customers pay how? Through your own Stripe account. Lists reflect paid, locked demand — not platform-wallet theater.

Lists are how recurring revenue leaves the building

More mechanics in how bakery subscriptions work. One-offs vs standing orders: subscriptions vs one-off orders. Mode clocks: pickup windows and cutoffs. Product map: /features. Pricing: /pricing. FAQ: /faq.

The bake list and pack list are not paperwork for its own sake. They are how recurring revenue becomes loaves in the right hands without you inventing next week’s sales every Sunday. Buyers on auto-pilot. Cutoff that locks paid demand. Stock that stops when the day is full.

Start a 14-day free trial — no card to start. Customers pay you through your own Stripe account.