The first time a health department inspector asked for my production logs, I handed her a spiral notebook with flour stuck to the cover. She flipped through three months of barely legible handwriting, paused at a page where I had clearly written “scones” while holding a toddler, and asked if I had anything more organized. I did not. That was the day I realized that cottage food compliance is not about being perfect. It is about being provable.
Every state that allows home-based bakeries has some form of record-keeping expectation. Some want production logs. Others want sales tracking to enforce revenue caps. A few require temperature documentation if you venture into refrigerated products. And while paper logs are technically legal in most places, they are also fragile, inconsistent, and easy to lose behind a mixer.
If you are scaling beyond the occasional farmers market table, you need software that handles the specific weirdness of home bakery operations. This guide breaks down what each state actually requires, which tools handle those requirements without costing a fortune, and how to build a logging system that survives both a health inspection and a flour explosion.
Why Paper Logs Fail Home Bakeries
Paper feels simple until you try to find a batch record from six months ago. Home kitchens are hostile environments for documentation. Grease splatters, water rings, and the general chaos of residential life destroy notebooks. Worse, paper does not help you calculate anything. It does not warn you when you are approaching your state’s annual sales cap. It does not generate a traceability report when a customer asks which batch of almond flour went into their cookies.
Digital logging solves three problems specific to cottage bakers. First, it creates searchable records. Type “blueberry muffins” and see every batch you have ever made. Second, it automates the math. Revenue caps, ingredient costing, and allergen tracking happen in the background. Third, it produces professional reports that satisfy inspectors and build customer trust. A printed PDF from a proper app looks very different from a coffee-stained notebook.
What States Actually Require: The Real Rules
Cottage food law is a patchwork, and record-keeping rules vary wildly. Here is what you need to know before choosing software.
States That Want Production Logs
Michigan explicitly recommends keeping a production log that tracks the product, ingredient sources, preparation date, amount prepared, who prepared it, packaging method, and where it was sold. The state even provides a template spreadsheet. If you are in Michigan, your software needs batch-level tracking with fields for ingredient sourcing and sales destination.
Mississippi requires detailed production records for acidified foods, including pH testing results, recipe sources, batch quantities, and dates. The state provides a sample log format that covers everything from product specifications to packaging details. If you sell pickles, salsas, or fermented goods in Mississippi, your app needs custom fields for pH values and third-party process authority verification.
South Dakota recently expanded its cottage food law to allow temperature-controlled foods like cheesecakes, cream pies, and fresh salsa. The catch? You must maintain temperature logs proving these items stay at or below 41 degrees Fahrenheit. The state requires completion of food safety training before you can even begin selling these products, and you must keep verification records. For South Dakota bakers moving into refrigerated goods, temperature logging is not optional. It is mandatory.
States That Focus on Sales Tracking
Oregon does not require a production log for basic cottage foods, but it does require you to maintain sales records for three years to prove you have not exceeded the annual cap, which sits around $51,200 and adjusts yearly. You need records showing product, quantity, price, date sold, and purchaser information for online sales. If a retailer sells your goods, you need their agreement documentation on file. Oregon inspectors can request these records within five business days.
Colorado has a unique per-product sales limit of $10,000 per item per year. If you sell cookies, bread, and jam, each product line has its own cap. That means you need software that tracks revenue by individual product, not just total business income.
California runs a two-tier system. Class A operators can sell directly with just registration and training. Class B operators, who sell through retail and restaurants, need annual kitchen inspections and must maintain stricter documentation. If you are aiming for Class B, your logging system needs to be inspection-ready at any moment.
States With Minimal Requirements
Wyoming, Montana, and Utah operate under Food Freedom laws that impose almost no record-keeping requirements. No sales caps, no mandatory logs, no routine inspections. If you live in one of these states, your software choice is driven by business efficiency and customer safety, not regulatory pressure.
Texas requires food handler training and proper labeling, but does not mandate detailed production logs for most baked goods. However, if you sell pickled or acidified foods, you must include a unique batch number on every label. That means your software needs batch numbering capability if you venture beyond cookies and bread.
Idaho has no license, permit, inspection, or sales cap. A risk assessment form is recommended but not required by the state. You could technically run the entire operation on sticky notes, though I would not recommend it.
Software That Actually Works for Home Bakeries
Most food safety software is built for restaurants or commercial manufacturers with dedicated staff and industrial equipment. Home bakers need tools that fit a residential kitchen, a part-time schedule, and a budget under fifty dollars a month.
Craftybase: The All-Rounder for Ingredient Tracking
Craftybase is built specifically for cottage bakers and small-batch food producers. It handles recipe-based inventory, meaning when you log a batch of sourdough, it automatically deducts flour, water, salt, and starter from your stock. It tracks lot numbers on ingredients, which is critical for allergen traceability and recall scenarios. If a supplier issues a flour recall, you can generate a report showing exactly which customers received products made with that lot.
For compliance, Craftybase stores manufacture records with timestamps, ingredient sources, and batch associations. It also calculates cost of goods sold in real time, which helps at tax season. Pricing starts at $20 per month for the Pro plan, which is enough for most home bakeries. The Studio plan at $41 monthly adds more advanced features.
The downside is that Craftybase is primarily an inventory and costing tool, not a temperature or HACCP logging system. If your state requires daily fridge checks or cooling logs, you will need a companion app.
SafetyCulture: The Free Compliance Workhorse
SafetyCulture offers a genuinely free plan for teams up to ten users, which covers most home bakery scenarios. It is a digital checklist and inspection platform that lets you build custom food safety logs. You can create daily opening checklists, temperature monitoring forms, cleaning schedules, and corrective action logs. It supports photo and video evidence, which is useful if you need to prove sanitizer concentration or fridge organization to an inspector.
The platform also integrates with wireless temperature sensors, so if you want automated fridge and freezer monitoring without manually checking a thermometer every morning, this is your tool. The premium plan runs $24 per month and adds analytics and advanced reporting.
For South Dakota bakers who need to prove their cheesecakes stayed cold, or for anyone who wants to professionalize their kitchen habits, SafetyCulture is hard to beat at the free tier.
Food-Safety.app: The Simple HACCP Logger
This UK-based platform offers a refreshingly simple digital HACCP system for £6.99 per month, roughly nine dollars. It records cooking temperatures, cooling logs, cold storage checks, reheat temperatures, and probe calibration records. It works offline, which matters in home kitchens with spotty Wi-Fi, and exports instant PDFs for inspectors or insurance claims.
The app is designed for small food businesses, not corporate chains, so the interface is clean and the setup takes minutes. For home bakers in states that require temperature documentation, this is a low-cost way to stay compliant without learning enterprise software.
CakeBoss: The Order and Recipe Manager
CakeBoss is a desktop and mobile app built for custom cake decorators and home bakers. At $149 for the first year and $20 annually after that, it is one of the cheapest paid options available. It handles order scheduling, recipe costing, shopping lists, and basic expense tracking. It generates branded invoices and quotes, which adds a layer of professionalism.
Where it falls short is food safety-specific logging. There is no built-in temperature tracking, allergen matrix, or batch traceability. Use CakeBoss if your state has minimal requirements and you need help with order management and pricing more than compliance documentation.
Wave Accounting: The Free Financial Backup
While not a food safety tool, Wave is worth mentioning because every state with a sales cap requires accurate financial records. Wave offers genuinely free accounting, expense tracking, receipt scanning, and invoicing. For Oregon bakers tracking toward a $51,200 cap or Colorado bakers watching per-product limits, Wave ensures you know exactly where you stand financially.
QuickBooks Self-Employed: The Tax Integration
At $15 per month, QuickBooks Self-Employed connects to your bank accounts, categorizes expenses, and estimates quarterly taxes. It integrates directly with TurboTax, which saves hours in April. Like Wave, it does not handle batch logs or temperature checks, but it is essential for bakers in states with strict revenue tracking requirements.
Matching Software to Your State
Table
| State | Key Requirement | Best Software | Why |
|---|---|---|---|
| Michigan | Production logs with ingredient sourcing | Craftybase + SafetyCulture | Batch tracking + custom checklists |
| South Dakota | Temperature logs for TCS foods | Food-Safety.app or SafetyCulture | Built-in temperature monitoring |
| Oregon | Sales records for 3 years | Wave + Craftybase | Financial tracking + product logs |
| Colorado | Per-product revenue caps | Wave or QuickBooks | Product-line profitability tracking |
| Mississippi | pH logs for acidified foods | SafetyCulture custom forms | Custom fields for pH values |
| Texas | Batch numbers for pickled goods | Craftybase | Automatic batch numbering |
| Wyoming/Utah/Idaho | Minimal requirements | CakeBoss or Craftybase | Business efficiency, not compliance |
| California (Class B) | Inspection-ready documentation | SafetyCulture + Craftybase | Full audit trail |
| Washington | Complex permit application | FlexiBake or Wherefour | Enterprise-level documentation |
Common Mistakes Home Bakers Make
Using restaurant software. Tools built for commercial kitchens assume you have a staff, a walk-in cooler, and a manager on duty. They are overbuilt and expensive for a home operation. Look for apps that mention cottage food, small batch, or artisan producers in their marketing.
Ignoring the sales cap until December. By the time you realize you are approaching your state’s limit, you have no way to throttle sales without turning away customers. Set monthly revenue targets in your accounting software and review them weekly.
Not backing up paper records. If you insist on paper logs, scan them monthly. A flooded basement destroys three years of compliance documentation in seconds. Cloud storage is not optional for serious businesses.
Mixing personal and business ingredients. That stick of butter from your family fridge does not belong in a batch for sale. Your logs need to show that ingredients for commercial products were purchased and stored separately. Software with lot tracking makes this distinction automatic.
Forgetting to log failures. If a batch of sourdough overproofs and you throw it out, log it. Inspectors and insurance adjusters want to see that you handle mistakes properly. A disposal log with dates and reasons shows you are running a business, not just baking for fun.
Skipping allergen cross-contamination records. Even if your state does not require them, allergen tracking protects you legally. If a customer claims your “nut-free” brownies caused a reaction, your ingredient lot records are your defense. Log every surface sanitization between allergen and allergen-free batches.
Step-by-Step: Setting Up Your Logging System
You can get compliant in about two hours. Here is how.
Hour one: Choose your stack Pick one primary tool based on your state’s strictest requirement. If you need temperature logs, start with Food-Safety.app or SafetyCulture. If you need production batch tracking, start with Craftybase. Add a free accounting tool if your state has a revenue cap.
Hour two: Build your templates Create digital forms for every recurring task. Opening checklist, production batch log, cooling temperature check, packaging log, closing sanitation check. Set the app to require a photo for critical steps like fridge readings or sanitizer tests.
Ongoing: The two-minute rule Log every batch before you start the next one. Log every temperature before you walk away from the fridge. If it takes longer than two minutes, your system is too complicated. Simplify it.
Weekly: Review the data Spend ten minutes every Sunday checking for gaps. Missing a day’s fridge check is fixable. Missing three weeks is a pattern that looks negligent to an inspector.
Monthly: Export backups Download PDFs of your logs and store them in a cloud folder. Most apps make this easy. Do not rely solely on the app’s servers.
Pro Tips for Inspection-Ready Bakeries
Use timestamps, not just dates. An inspector wants to know that your cheesecake cooled from 140 degrees to 70 degrees within two hours, then to 41 degrees within four more hours. Time-stamped logs prove you understand the danger zone.
Take photos of your thermometer calibration. Ice water should read 32 degrees. Boiling water should read 212. Snap a photo monthly and attach it to your logs. It proves your equipment is accurate.
Keep supplier invoices in the same system. If Michigan asks where you bought your flour, you need the receipt. Most logging apps let you attach PDFs to batch records. Do it immediately after ordering.
Create a “mock inspection” folder. Put your most recent three months of logs, your training certificates, and your labeling samples in one place. When an inspector calls, you sound organized instead of panicked.
Label your digital batches to match your physical labels. If your sourdough jar says “Batch 47,” your app should say “Batch 47.” Mismatched numbering creates confusion during traceability checks.
FAQ: Food Safety Logging for Home Bakeries
Do I need software, or can I use spreadsheets? Spreadsheets work for basic tracking, but they lack photo capture, automatic timestamps, and mobile accessibility. If your state requires detailed logs or if you sell at multiple venues, software saves time and reduces errors. For minimal-requirement states, a well-organized spreadsheet is legally sufficient.
What is the cheapest way to stay compliant? SafetyCulture’s free tier covers temperature logs, checklists, and corrective actions for up to ten users. Pair it with Wave for free accounting. Total cost: zero dollars monthly.
Does my state require digital records, or is paper acceptable? No state currently mandates digital records over paper. However, Oregon requires records to be available within five business days, and digital systems make that trivial. Paper is legal but fragile.
Can I use the same app for orders and food safety? Craftybase handles both inventory tracking and basic batch records. For full HACCP temperature logging, you will likely need a second tool like Food-Safety.app or SafetyCulture. Integration between the two is usually manual.
What happens if I exceed my state’s sales cap? In most states, exceeding the cap means you must transition to a licensed commercial kitchen. You cannot simply keep selling under the cottage food exemption. Accurate logging prevents this surprise.
Do I need to log every ingredient lot? If your state requires production logs with ingredient sourcing, yes. Even if not required, lot tracking is your best defense against allergen claims and supplier recalls. It takes ten seconds per batch and could save your business.
How long should I keep records? Oregon requires three years for sales records. Michigan recommends ongoing production logs. South Dakota requires training records for the duration of your operation. A safe rule is to keep everything for three years minimum, and indefinitely for capital equipment purchases.
Can I sell refrigerated items without temperature logs? In South Dakota and Texas, refrigerated cottage foods require specific temperature handling documentation. In most other states, refrigerated items are simply not allowed under cottage food law. Check your state rules before selling cheesecakes or cream pies.
Conclusion
Home bakery compliance is not about buying the most expensive software or maintaining a laboratory-level notebook. It is about matching your documentation to your state’s actual requirements and your business’s real scale. A Wyoming baker selling sourdough needs a very different system than a South Dakota baker selling refrigerated cream pies.
Start with your state’s rules. If you need production logs, Craftybase handles the batch traceability. If you need temperature documentation, SafetyCulture or Food-Safety.app covers the monitoring. If you need sales tracking, Wave or QuickBooks keeps you honest about revenue caps.
The baker who gets into trouble is not the one with imperfect handwriting. It is the one with no records at all. Build your system this week, log your next batch properly, and sleep better knowing that an inspector’s visit is just another Tuesday, not a crisis.