The Factory Floor That Fits in a Cottage Kitchen
Meet Run Ticket, the software behind The Un-Factory.
Someone picks up a bag at a market, hears it was baked in a cottage kitchen twenty minutes away, and asks the reasonable question:
How do you know the next bag will be the same?
It's the right question. A grocery buyer asks it in colder language — consistency, traceability, recall procedure — but it's the same question. A conventional food brand answers it by pointing at a building: one plant, one line, one set of cameras. We don't have a building. We have a network of local makers producing the same products in their own cottage kitchens, under one brand.
So the answer has to come from somewhere else. It comes from a piece of software called Run Ticket.
One run, one ticket
In older industries, a run ticket is the paper that follows a batch from start to finish — what went in, who touched it, when, and what came out. Ours is a screen instead of a clipboard. A maker opens a ticket when a production run starts and closes it when the last case is sealed. Nothing in between is optional, and nothing in between is remembered rather than recorded.
Every product line runs on the same app. What changes between them is the formula, the sequence of steps, and where the critical control point sits.
The math isn't the maker's job
The maker enters the orders they're filling. Run Ticket works backward: orders to bags, bags to ingredient weights per mix, mixes to mixer loads and oven loads. Formulas live centrally and are versioned, so when one changes it changes for everyone at once — nobody is working off a printout from March.
Ingredient lot numbers get captured here, at the top of the run. That's the step that extends traceability past our own door and back to the supplier's.
Before the run begins, the app shows the maker how long it will actually take, waits included.
Steps unlock in order — and don't unlock without a signature
Production is broken into numbered steps. Each one takes initials and a timestamp before the next one opens. A signature entered out of sequence is flagged, not quietly accepted. The ticket holds its state across interruptions.
The clock is part of the recipe
Some steps are waits, and a wait is where standards usually go soft. A long hold isn't one box to tick at the end — it's a series of spaced checkpoints, each with a description of what the maker should be seeing at that point. The step won't close until every one of them is logged at its real time. Reminders go out by text, because a phone in a flour-dusted kitchen is a phone with notifications turned off.
Photographs, on a standard card
Cameras aren't saved for the finish line. Photo checkpoints sit throughout the run, so the record shows the product at the stages where quality is actually decided — not just how it looked once it was already in the bag.
Every shot is taken against a standard reference card carrying a scale and a grey patch, so a run photographed in a bright August kitchen is comparable to one shot under a January bulb. Each product is presented the same way every time, so runs can be lined up against each other rather than judged one at a time.
The label prints itself
At the end, Run Ticket drives a thermal printer in the maker's cottage kitchen. A variable strip goes onto a pre-printed panel: date, batch ID, maker, and the cottage-law information the state requires. No one hand-types compliance text, which means no one hand-types it wrong.
That code is the thread. Enter it and it resolves to the product, the date it was made, the maker's name, and the region it came from.
What happens when a step gets missed
Kitchens are real places and people are people, so the system expects misses. There are grace windows before a check counts as late, tiers of severity so a five-minute overrun isn't treated like a skipped hold, and strikes that decay over time rather than following someone forever. Self-reported problems are treated more gently than discovered ones — a system that punishes honesty simply buys itself dishonesty.
Makers are certified per product line. Strikes count against that certification. Enough of them and the app stops opening tickets for that product.
What this means if you're stocking it
The distributed model usually raises a buyer's eyebrow, and the concern is legitimate: more hands, more variables, more places for a standard to drift. What Run Ticket offers in exchange is a record that a single plant rarely produces at this resolution — every unit tied to a run, every run tied to a maker, a set of timestamped sign-offs, a photo, and the supplier lots that went into it.
Practically, that means a recall is a database query, not a phone tree. It means "which kitchens touched this lot" has an answer measured in seconds.
The point
We didn't get rid of the factory's discipline. We got rid of its building.
The result is food made close to the people eating it — fresher, in smaller runs, by someone whose name is on the bag — held to a standard that doesn't loosen just because the ovens are further apart.
Dare to Pop · Asheville, NC · Addison Myers Group LLC. Interested in carrying us? Let's talk about your market.