Choose the meat, cut, quantity, and rhythm your household actually uses. Bay reviews the request, cuts it fresh, wraps it by name, and puts it on the right weekly route.
Next delivery runFriday · Aug 7
Standing request preview
Maple & Walnut Route
Request cutoff Wednesday at 2 pm. Bay confirms final weight and price before the Friday route leaves.
2 daysuntil cutoff
$35delivery minimum
1 textto confirm
Build the weekly request
Tell the butcher exactly what works.
A request is not charged immediately. Bay confirms availability, final counter weight, substitutions, and the delivery window first.
1
Choose the rhythm
Pause or change before the weekly cutoff.
2
Choose the delivery day
Sample Lancaster delivery windows.
3
Choose meat, cut & quantity
Quantities below are estimated pounds per delivery.
4
Set the substitution rule
The butcher never guesses without your permission.
Butcher production view · Friday route
Cut once. Pack the whole route.
Recurring requests roll into one weekly cut sheet, grouped by meat, spec, quantity, and route. The counter team sees exceptions before the first knife comes out.
Committed demand178 lbAcross 21 sample requestsCut groups11Consolidated by specRoute packages67Labels staged by stopExceptions3Need customer confirmationReady18%Production completion
Consolidated cut sheet
Friday, Aug 7 production
Driver route view · Friday morning
Seven stops. One clean handoff.
The driver sees only what is needed for today’s delivery: route order, household initials, package count, contact method, payment state, and delivery instruction.
Maple & Walnut route
Depart Bay at 10:00 am.
Sample route order is designed around Lancaster neighborhoods, delivery windows, and cold-chain timing.
Owner / manager view · weekly control
Know next week before it arrives.
Standing demand creates a reliable production baseline. Bay keeps the ability to confirm weights, cap a route, manage pauses, and protect counter inventory.
Recurring households21+3 this monthWeekly committed178 lbBefore counter demandProjected sales$1,486Sample Friday routeRoute utilization72%9 spots remainPaused this week2No manual deletion
Capacity by department
Protect the counter and the route.
Beef cutting
78%
Pork cutting
61%
Smokehouse
88%
Route stops
72%
Recurring request roster
Frequency is the planning engine.
Weekly
11 household codes96 lb average demand
$824
2 weeks
7 household codesAlternating Friday cohorts
$462
Monthly
3 household codesFreezer-fill requests
$200
Weekly operating rhythm
One deadline for every handoff.
Monday
Standing requests openCustomers receive the week’s availability.
8 am
Wednesday
Requests lockChanges move to a staff-assisted exception lane.
2 pm
Thursday
Cut, weigh, and confirmFinal totals and approved substitutions are sent.
All day
Friday
Wrap, stage, and deliverCold route departs in two planned waves.
10 am
Guardrails
Standing order, not autopilot.
Access & login model
Easy for customers. Private for the company.
A production build would connect identity, payment, notifications, and durable order history. This sandbox demonstrates the access boundaries without collecting real information.
Customer secure link
Passwordless text or email link. Household sees only its own recurring request, confirmations, pauses, and delivery history.
Butcher station PIN
Shared shop tablet shows cut codes and specs—not addresses, payment details, or full customer histories.
Driver route sign-in
Time-limited route access with only today’s delivery details. Records clear when the route closes.
Owner / manager account
Magic link or existing business login, role permissions, change audit, capacity controls, and exception approval.
One weekly operating loop
Request → confirm → cut → wrap → route → repeat.
01Customer requestsMeat, cut, quantity, frequency, day, and substitution rule.02Bay confirmsAvailability, expected weight, price range, and route capacity.03Demand combinesRecurring requests become one cut sheet organized by spec.04Butchers executeCut, weigh, label, wrap, and stage by cold route.05Driver completesOnly today’s route details, package count, and delivery instruction.06Next week resetsStanding requests repeat unless paused or edited before cutoff.
One weekly run · four views
Run the Bay Weekly sandbox.
Every view follows the same sample Friday delivery.
Sandbox data resets when the page reloads. A real launch would add private accounts, payments, messages, and a durable order database.