
Guides
Running a specialty food business on software: tools and metrics
Specialty food software and KPIs as one map: the five records a system must hold, the numbers they produce, three approaches compared, and how to keep them safe.
What to take away
- Software in a food business exists to hold five records and produce a handful of numbers from them. Choose it by whether it does that, not by its feature list.
- The five records are the receiving log, the batch record, the finished goods count, the shipment record and the sales ledger. The numbers are yield, unit cost, contribution by channel, stock against shelf life, and the time it takes to trace a lot.
- Three approaches existpaper and a spreadsheet, a general small-business system with food records bolted on, and a purpose-built production system. Each fits a different size and each breaks somewhere predictable.
- The records are the business. Losing them means losing the ability to trace, to cost and to prove. Protect them as you would the product.
- The sub-articles in this cluster take the framework and apply it: an evaluation protocol for any software without naming vendors, the monthly KPI sheet with its formulas, and the bookkeeping that feeds it.
Start from the records, not the software
Before looking at any system, write down the five records the operation keeps and the fields each one holds. Then write the numbers you need from them, monthly. Any software that cannot hold those fields and produce those numbers is the wrong software, whatever else it does. Any software that can is a candidate, whatever it is called.
This article names example vendors and products. Formulas and thresholds live in the sub-articles.
The fields, as a starting list:
Start from the records
- Receiving logdate, supplier, item, lot code, quantity, temperature on arrival, pass or hold.
- Batch recorddate, product, batch number, ingredient lots and quantities, process steps with times and temperatures, operator initials, yield out, corrective action if a step went out of range.
- Finished goods countitem, lot, on-hand units, pack or best-by date.
- Shipment recorddate, customer, item, lot, units, carrier.
- Sales ledgerdate, invoice number, customer, channel, units, price, deductions.
Five Records and Their Numbers
Record
- Receiving log
- Supplier, item, lot, quantity, date, condition
- Batch record
- Date, batch lot, ingredient lots, steps, yield, who
- Finished goods count
- Units by batch lot and date, samples, dumps
- Shipment record
- Batch lot, buyer, units, date
- Sales ledger
- Buyer, channel, product, units, price, deductions, date paid
Fields it must hold
- Receiving log
- Lead time; stock by lot
- Batch record
- Yield; unit cost; backward trace
- Finished goods count
- Stock against shelf life; variance
- Shipment record
- Forward trace; on-time delivery
- Sales ledger
- Contribution by channel; days to payment
Number it feeds
- Receiving log
- Batch record
- Finished goods count
- Shipment record
- Sales ledger
If the federal preventive-controls rule covers your facility, the U.S. Food and Drug Administration: Preventive Controls for Human Food page says a written food safety plan with monitoring and records applies. The batch record is where that monitoring is written.
Ask FDA whether you are covered. Either way, hold the five records: a buyer's audit, an insurer, and a recall all read the same five.
Three approaches compared
What it is
- Paper and a spreadsheet (Microsoft Excel or Google Sheets)
- Printed batch records and count sheets, a spreadsheet for the ledger and the KPIs
- General small-business system plus food records (QuickBooks Online or Xero for accounting, with a spreadsheet or add-on for batch and lot records)
- Accounting and invoicing in a general system; batch and lot records in a spreadsheet or a simple add-on
- Purpose-built production system (BatchMaster ERP, JustFoodERP or Vicinity Software)
- Lot-tracked inventory, batch records and costing in one system, feeding accounting
Fits
- Paper and a spreadsheet (Microsoft Excel or Google Sheets)
- One product line, one kitchen, one person
- General small-business system plus food records (QuickBooks Online or Xero for accounting, with a spreadsheet or add-on for batch and lot records)
- Several products, wholesale accounts, a bookkeeper
- Purpose-built production system (BatchMaster ERP, JustFoodERP or Vicinity Software)
- Multiple channels, a co-packer or private label, a buyer who audits
Where it breaks
- Paper and a spreadsheet (Microsoft Excel or Google Sheets)
- The trace takes an afternoon; a spreadsheet formula nobody remembers
- General small-business system plus food records (QuickBooks Online or Xero for accounting, with a spreadsheet or add-on for batch and lot records)
- Two systems that do not agree on stock; lot data that lives nowhere the accountant can see
- Purpose-built production system (BatchMaster ERP, JustFoodERP or Vicinity Software)
- Cost and setup time; a system that demands more discipline than the operation has
Typical cost and setup
- Paper and a spreadsheet (Microsoft Excel or Google Sheets)
- No license fee. The setup is the hours to build the sheets, typically a day or two.
- General small-business system plus food records (QuickBooks Online or Xero for accounting, with a spreadsheet or add-on for batch and lot records)
- Typically tens of dollars a month for a small plan, per user or per company, plus a few days of setup.
- Purpose-built production system (BatchMaster ERP, JustFoodERP or Vicinity Software)
- Priced per user or per site per month, often with an implementation fee. Typical range: hundreds to thousands of dollars per month, depending on users and modules. Setup typically takes weeks, and the figure turns on lot structure, co-packer data and the accounting link.
The first approach is right longer than most makers think, and the third is right sooner than most makers can afford. The second is where most operations live.
Three Software Approaches Compared
Approach
- Paper and spreadsheet
- Printed batch records, count sheets, spreadsheet ledger
- General system plus food records
- Accounting and invoicing general; batch and lot in spreadsheet or add-on
- Purpose-built production system
- Lot-tracked inventory, batch records, costing, accounting in one
What it is
- Paper and spreadsheet
- One product line, one kitchen, one person
- General system plus food records
- Several products, wholesale accounts, a bookkeeper
- Purpose-built production system
- Multiple channels, co-packer, private label, auditing buyer
Fits
- Paper and spreadsheet
- Trace takes an afternoon; forgotten formula
- General system plus food records
- Two systems disagree on stock; lot data hidden
- Purpose-built production system
- Cost and setup time; demands more discipline
Where it breaks
- Paper and spreadsheet
- General system plus food records
- Purpose-built production system
The break is always the same: the stock count in the accounting system and the stock count in the lot records disagree, and nobody knows which is true. The fix is a monthly reconciliation with one owner, not a fourth system.
Choosing, in order
- Write the five records and their fields.
- Write the monthly numbers and which record feeds each.
- Decide which of the three approaches fits the operation's size for the next two years.
- Evaluate candidates by whether they hold the fields and produce the numbers, using a scripted trial that includes a mock trace.
- Set up the backup and the reconciliation before the first live batch is entered.
The numbers, and what each one fails to show
- Yield per batch.The earliest sign of change. It does not tell you why.
- Unit cost.From the batch record and the invoices. It does not include the founder's unpaid hours unless you put them in.
- Contribution by channel.Price received minus deductions minus unit cost. It does not show that one account is most of a channel.
- Stock against shelf life.Finished units by date against the sales rate. It does not show that a buyer will refuse units inside their remaining-life margin unless you record that margin.
- Days to payment.By buyer. It does not show that a slow payer is also your largest account until you look.
- Time to trace a lot.From the drill. It does not run itself.
The full monthly sheet with the formulas, and the threshold at which each number should change what you do, is one of the sub-articles.
Monthly Numbers and Their Blind Spots
- Yield per batchearliest sign of change; does not tell why
- Unit costfrom batch record and invoices; excludes unpaid founder hours
- Contribution by channelprice minus deductions minus unit cost; hides account concentration
- Stock against shelf lifeunits by date against sales rate; misses buyer remaining-life margin
- Days to paymentby buyer; hides that slow payer is largest account
- Time to trace a lotfrom the drill; does not run itself
Protecting the records
A maker who loses the batch records loses the ability to trace a lot, to cost a product and to answer a buyer. Two sources, both aimed at small operations, set out where to start.
The National Institute of Standards and Technology: NIST Small Business Quick-Start Guides give practical starting points for managing cybersecurity and privacy risk, including the Cybersecurity Framework 2.0 in a form a small business can use. The Cybersecurity and Infrastructure Security Agency: Cyber Guidance for Small Businesses page collects current resources for small and midsize organizations to reduce common risks.
The practical minimum for a maker: a backup of the records that is tested by restoring it, separate logins for separate people, and a way to keep working for a day if the system is down. For the batch record that means a printed blank on the shelf.
Records that satisfy the IRS and a buyer
The Internal Revenue Service: What kind of records should I keep? guidance leaves the recordkeeping system to you provided it clearly shows income and expenses and keeps the documents behind purchases, sales, payroll and assets. The five records, with their invoices attached, are that system.
One set of records, kept once, serves the bookkeeper, the inspector, the buyer, the insurer and the recall. That is the strongest argument for choosing software that holds all five rather than one that holds the ledger and leaves the rest on a clipboard.
What the software depends on
Batch record fields come from stations in the equipment and setup guide. A new machine with data output is a field the record can hold.
Stock numbers are the three stocks and their clocks from the inventory and sourcing guide. What records must contain, and how long they are kept, is a question for the licensing and compliance guide.
Contribution by channel is the arithmetic of the pricing and profit guide run monthly. The batch record is filled during the day described in the operations and workflow guide. And the sales ledger's channel column is the routes compared in the marketing and growth guide.
Common questions
Do I need production software to start?
No. Paper batch records and a spreadsheet ledger, kept every time, are a working system. Software earns its place when the trace takes longer than an afternoon or the count and the ledger stop agreeing.
What is the one feature that matters most?
Lot tracking that connects an ingredient lot to a batch lot to a shipment. Without it the software is a ledger with a stock column.
Should my bookkeeper choose the system?
They should choose the accounting side. The batch and lot side has to work on a kitchen floor with wet hands, and that is your call.
How do I keep records safe without an IT person?
Tested backups, separate logins, and the two small-business guides linked above, which were written for exactly that situation.
How often should I review the numbers?
Monthly, in one sitting, with the batch records open. Yield weekly if a product is new or a machine has changed.







