Picture a founder who started a pet treat company in her kitchen. A few years in, she has expanded. She works with a co-packer, ships weekly orders to independent pet boutiques, and sells directly to consumers through an online shop.

Her business is healthy, but the back office is running on duct tape. Orders, available inventory, ingredient costs, and batch lot numbers all live across three different spreadsheets. Only she truly understands how the formulas connect. Every time an order comes in or a pallet ships, she spends her evenings typing numbers from one screen to another.When it is time to move beyond spreadsheets, the default instinct seems obvious: Get a familiar starter tool. It is cheap and everyone uses it. You can figure out 'real' operations software later when you are bigger.
It sounds like sensible advice, and most business owners hear the exact same thing.

When I began my career in 1989, small businesses were making a similar transition for the first time. Back then, it was paper ledgers. One of my first clients was an accounting firm manually copying check stubs onto 13-column green columnar paper. If the column totals did not balance across the page, staff spent hours hunting down the math error.

They could have moved from paper to an early spreadsheet like Lotus 1-2-3. That would have been an improvement, but it only would have automated adding up the columns. It would not have solved the underlying business workflow. Another client tracked customer invoices in one physical ledger and payments in a separate book, taking half a month just to calculate who was behind on their bills. Moving to software connected the pieces instead of just calculating rows faster.

Today, spreadsheets are the modern equivalent of that 13-column green paper.

The standard recommendation to buy a starter package makes sense if you run a simple business. If your main goals are seeing who owes you money and pulling a clean report once a year to hand to your accountant at tax time, an entry-level tool does the job.
If you make and sell physical products, taking that intermediate step often sets you up for an unnecessary detour. You do not always need to take the starter system route first.

Why is starting with basic software the default move?

The accountants and advisors giving that advice are not wrong. They are just recommending what works for the vast majority of small companies.
Entry-level accounting software is familiar and affordable. For a consulting firm or a very simple service business, a starter tool might be all the company ever needs. If your business primarily invoices clients for time and writes checks for monthly software subscriptions, the basic tools handle that smoothly.

The advice only breaks down when advisors assume every business grows the same way a service company does.

What changes when you sell a physical product?

Physical products introduce operational friction that service companies never have to worry about.

You need to know what is in stock and where it is sitting. You have to understand what each unit actually costs once you factor in raw ingredients and packaging. If you work with a co-packer or sell across multiple channels, like wholesale accounts alongside an online store, those moving parts multiply fast.

Starter systems were never built to handle that kind of operational detail. When a product business tries to run on an entry-level package, the software cannot keep up. So the business quietly starts running half its operations in spreadsheets right beside the accounting software.

I spoke with one business owner using a popular starter program who could never get an accurate picture of her true inventory. Her software could not reflect the conversion of raw materials into finished goods until the finished products were actually sold. Because she could never see what was truly available to ship, she kept tying up precious cash buying extra raw inventory just to ensure she never ran out.

Another founder told me that their team tracked every single lot number in external spreadsheets. The entry-level accounting software handled billing, but if a quality question or customer recall inquiry ever arose, answering which customer received which batch meant digging through separate spreadsheet tabs. They knew that as they expanded, relying on disconnected spreadsheets and bolt-on tools was an operational risk waiting to happen.

If a customer calls about a specific batch tomorrow morning, can you trace every order that batch went into within two minutes? If the answer involves cross-referencing three separate workbooks, your accounting package is not actually running your business. Your spreadsheets are.

What does skipping a step actually save you?

If you talk to an owner who has already been through multiple software transitions, they will tell you the software license is rarely the hard part. The real friction is changing how your people work and moving your data.

Taking the direct route saves you from paying that operational tax twice:

  1. One data move instead of two. Every time a business switches platforms, it has to migrate master records and clean up historical baggage. Doing that once is far easier on your team than doing it now and repeating the exact same painful exercise when you outgrow the system three years later.
  2. Habits get built once. When staff learn an entry-level tool, they build muscle memory around that tool’s specific screens and shortcuts. Then they discover what the software cannot do and plug the gaps with spreadsheet workarounds that become part of the daily routine. Moving to the right software later means untangling both the old system's habits and all the spreadsheet band-aids. When you start with the right operational tool, your team learns the proper workflow on day one.
  3. Starting from spreadsheets is surprisingly clean. Founders often assume that coming from spreadsheets puts them at a disadvantage compared to a company migrating from existing accounting software. Often the opposite is true.

Older systems can carry years of history that nobody has looked at in a long time. I recently ran a test conversion for an owner and uncovered open sales orders lingering from twenty years ago. Because their legacy software had never been configured properly for drop-shipped goods, the system showed over half a million dollars in phantom negative inventory. Years of quick fixes and forgotten transactions had quietly piled up in the background.

When you transition straight from spreadsheets, you do not carry that history with you. You take your current customers, your active vendor list, your real items, and your opening numbers, clean them once, and start fresh.

Doing that cleanup once, straight into a system designed for product workflows, is a clean break. Doing it halfway into a starter tool just means kicking the real cleanup down the road.

Does operational software have to mean six figures and enterprise bloat?

When small business owners hear the words "operational software," they often imagine multi-year implementations and runaway budgets.

The software market does not help here. One of the biggest pitfalls facing growing product companies is the "starter" package that looks deceptively cheap. A vendor advertises a system that is free to start, or fifty dollars a month, specifically targeting the exact inventory or invoicing pain point keeping you awake at night.

To actually run your business, you need the order module. And the purchasing module. And seats for four team members instead of one. Before long, that "free" starter package snowballs into thousands of dollars in surprise monthly fees and paid add-ons.

The right system for a small product business is sized and priced for what you need to run it, without the enterprise bloat. Practical systems are designed to fit teams starting with just a handful of users, giving you the operational backbone you need on day one, including inventory visibility and lot tracking, while scaling naturally as your company grows. You do not have to buy modules you will never touch, and you do not have to shop for another system the moment your team expands.

The goal is a system sized for where you are today that will not require an emergency replacement three years down the road.

When is staying simple the right call?

Taking the leap to dedicated operational software is not the right move for everyone.

If you run a service business with no inventory, or only need clean books once a year to hand your accountant at tax time, a basic entry-level accounting tool is usually plenty.

And if you do not have real friction in your day-to-day operations, do not change your systems just because someone told you that you "should." If your current setup gets orders out the door accurately and gives you the visibility you need without draining your weekends, you do not need new software.

A good advisor will tell you that straight out. Software should solve clear operational pain, not create change for the sake of change.

How do you know which side of the line you are on?

If you are trying to decide whether to begin with a starter program or make the leap straight to operational software, walk through this quick checklist:

  • Do you track lots or expiration dates? If tracking a batch means maintaining a separate spreadsheet tab outside your books, you have already outgrown basic accounting software.
  • Are you selling in more than one place? If you balance wholesale orders alongside an online store, starter tools quickly turn into manual data-entry bottlenecks.
  • Does anyone re-type numbers between screens? If orders or quantities get manually re-entered from an ecommerce platform into your books, errors are only a matter of time.
  • Do you build reports by hand for your accountant or lender? If pulling inventory valuation or gross margin requires exporting data and writing formulas in Excel, your system is not giving you clear visibility.
  • Do you work with a co-packer or multiple component suppliers? The moment raw materials get turned into finished goods across different facilities, basic bookkeeping software loses track of what you actually have.

If you checked off two or three of those points, taking a detour through a starter system will likely mean shopping for new software again in a few years.

Where to go from here

You do not need an accounting background or an alphabet soup of tech jargon to choose the right tools. You got into business to make great products, whether that is pet treats, beverages or specialty food, not to spend your evenings untangling inventory spreadsheets.

We work directly alongside your existing outside accountant or bookkeeper. They continue handling your taxes and year-end work, while we set up the operational engine that tracks your inventory and your daily orders. And when you have questions, you get a direct line to an experienced human who knows your setup, not a generic support ticket queue.

If you are running your product business on spreadsheets and wondering which step makes sense next, let's talk through where things stand today.

The Moment Everything Changes

It's 4:00 PM on a Friday. You're thinking about the weekend. Then your phone rings.

A supplier just flagged a contaminated batch. By Monday morning, you need a list of every customer who received product from Lot #882.

The FDA maintains a running list of pet food recalls and advisories, and the pattern is clear: companies that can't trace fast enough face the worst outcomes.

Your first move? Opening three different Excel files. One's on the shared drive. One's on someone's desktop. And one... you're pretty sure exists, but you'll need to call the warehouse manager to find it. He's already left for the day.

In fact, this is the moment most companies discover their lot tracking is broken.

Recalls aren't just logistical headaches. They create financial, reputational, and regulatory cascades that move fast and leave almost no room for error. Industry estimates put the average direct cost of a food recall at $10 million. And that's just the direct costs — retrieval, disposal, notifications. It doesn't include the lawsuits, the lost accounts, or the brand damage that lingers for years.

When traceability is weak, those costs climb even higher. Why? Because you end up recalling more product than necessary. You can't isolate the problem, so you pull everything that might be affected. That's expensive. And it's avoidable.

If your first instinct during a recall is to start hunting through spreadsheets, you've already lost the critical early window of control.

What Regulators Actually Expect (And How Fast)

The rules have changed.

FSMA 204  (the FDA's Food Traceability Final Rule ) requires companies to provide electronic, sortable traceability data within 24 hours of a request. That's not a soft deadline. That's not "get back to us when you can." That's 24 hours. Including weekends. If FDA calls at 5:00 PM Friday, you have until 5:00 PM Saturday.

Now, FSMA 204 specifically targets high-risk foods. But the expectation it sets ripples outward. Auditors, insurers, and major retailers are already using it as a benchmark for evaluating all food distributors. If you're distributing pet food, you're tracking ingredients from multiple suppliers, batches produced on different dates, and products shipped to retailers, vets, and direct-to-consumer channels. The complexity adds up fast.

The burden of proof is on you. When someone asks for traceability data, they expect verifiable, timestamped records that are immediately retrievable. Not "give us a few days to pull it together." Not "we know where it is, we just need to find it."

Good intentions don't satisfy an auditor. Only verifiable, timestamped data does.

Why Spreadsheets Fail Under Recall Pressure

Spreadsheets are familiar. They're flexible. Everyone knows how to use them.

They're also fragile under stress.

Studies of operational spreadsheets consistently find that over 90% contain errors. Not complicated spreadsheets built by amateurs. Regular, everyday business spreadsheets. The kind your team uses right now.

In normal operations, a small error might not matter much. But during a recall, a single incorrect lot reference can mean over-recalling safe product or missing affected customers entirely. Both are expensive. One is dangerous.

Manual data entry. Someone types "Lot 882" instead of "Lot 822." Nobody catches it. Six months later, that typo determines whether a customer gets notified or not.

Multiple versions. The warehouse has one file. Accounting has another. Sales exported their own copy three weeks ago and added some columns. Which one is the truth? Nobody's entirely sure.

The linking problem. Connecting supplier lots to internal batches to outbound shipments requires hopping between files, cross-referencing dates, and hoping someone kept good notes. Under time pressure, this falls apart fast.

Spreadsheets are fine for storing data. They're catastrophic for retrieving the right data under pressure.

 

The Hidden Risk of "We Can Figure It Out If It Happens"

I get it. Recalls feel rare. Theoretical. Something that happens to other companies.

So the plan becomes: "If it happens, we'll figure it out."

What matters isn't likelihood. It's impact.

A recall doesn't just test your systems. It tests your leadership, your brand trust, and your operational maturity, all at once, under a deadline, with regulators and customers watching.

And if your traceability depends on one person who knows where the files are and how the process works? You don't have a system. You have a single point of failure.

I've seen this pattern over and over. The warehouse manager who's been there 15 years and "just knows" where everything is; the office manager who built the spreadsheet system and is the only one who understands the formulas; the IT person who retired two years ago and took all the workarounds with them.

These aren't bad employees. They're good employees in a bad structure. And when they're on vacation, or sick, or gone, the whole thing stops.

For food distributors, this risk compounds quickly. You're not just tracking finished goods. You're tracking ingredients from multiple suppliers, production batches across different dates, and shipments going to retailers, foodservice, and maybe direct-to-consumer. Every handoff is a place where traceability can break. The question isn't whether you'll ever face a recall. It's whether you'll be ready when you do.

What Proper Lot Tracking Actually Looks Like

Effective lot tracking isn't about better spreadsheets. It's not about more reports or extra columns or color-coded tabs.

It's about how work happens every day.

When lot tracking is built into your system properly, traceability isn't a separate task. It's just how things work.

Every receive is tied to a lot. When product comes in, you capture the lot number as part of receiving. Not written on a sticky note. Not added to a spreadsheet later. It's in the system before the product hits the shelf.

Every pick is tied to a lot. When an order ships, the system knows exactly which lots went out the door. Not "probably from that pallet we got last week." Exactly which lots.

Every transaction is linked.  Supplier lot → internal batch → customer shipment. You can query the unbroken chain. When someone asks "who got Lot 882?" the answer takes minutes, not days.

The difference shows up during a mock recall. Industry best practice is completing a traceability exercise, identifying all affected customers and products, in 2-4 hours. Major retailers like Chewy expect even faster. If your mock recall takes three days of digging through files and calling the warehouse, that's not a drill. That's a warning.

The goal isn't recording information after the fact. It's systems that enforce traceability as work gets done.

Why This Is a System Decision, Not a Process Fix

You can't train your way out of structural gaps.

I've seen companies try. They create checklists. They add steps. They tell the warehouse team to "be more careful" about writing down lot numbers. They hold meetings about the importance of data accuracy.

And for a few weeks, it works. Then someone gets busy. A step gets skipped. The checklist gets ignored because there's a truck waiting. And you're right back where you started.

The problem is rarely the software itself. It's the workflows built around it. I dig into this more in Stop Blaming the System: The Messy Truth About Bad Workflows.

It's not the people either. It's that manual systems depend on perfect human behavior, every time, under pressure. That's not realistic. Well-designed systems act as gatekeepers. If the lot number is missing, the receive can't be completed. If the pick isn't tied to a lot, the shipment can't go out. The system doesn't allow the gap to exist in the first place.

This is the difference between "we have a process" and "we have a system."

Processes depend on people remembering. Systems enforce the rules automatically.

The manual approach scales by adding people: more checkers, more oversight, more meetings about why things fell through the cracks.

Automation scales by adding consistency. The hundredth transaction is tracked exactly like the first.

When a recall hits, you don't want to be hoping everyone followed the process. You want to know the system made it impossible not to.

The Cost of Waiting Is Usually Invisible Until It Isn't

Of course, delaying traceability improvements often feels reasonable. The system works. Nobody's complained lately. There are bigger fires to fight.

But then something shifts, and suddenly the cost becomes very visible.

Retailer audits.  Major retailers and chains like Chewy, Petco, and large grocery buyers increasingly audit supplier traceability before signing or renewing contracts. Excel-based processes raise red flags. That doesn't mean an automatic rejection, but it does mean harder conversations, more scrutiny, and sometimes lost opportunities you never even hear about.

Insurance Scrutiny.  Product recall and liability insurers factor traceability controls into their assessments. Weak documentation can mean higher premiums or, in some cases, difficulty getting coverage at all.

The question you can't answer fast enough. There are few harder moments than telling a regulator or a major customer that the data exists, you just need more time to find it. That's not a confidence-building statement.

The costs of waiting don't show up on a balance sheet. They show up in the account you didn't win, the audit that went sideways, and the scramble that could have been avoided.

A Better Time to Learn This Lesson

The best time to evaluate your traceability readiness is when:

  • No recall is active.
  • No deadline is ticking.
  • No one is watching.

Run a mock recall. Pick a random ingredient lot from three to six months ago. See how long it takes to trace it forward to finished products and outward to customers. Document where you got stuck, what took longest, and what required a phone call instead of a report.

If you can do it in under four hours with confidence in the data, then you're in good shape. If it takes days, or depends on one person who "knows where everything is," that's your answer.

The worst time to learn your lot tracking is broken is during your first real recall.

But What About the Cost of Upgrading?

Fair question.

Implementing proper lot tracking typically costs $15,000 to $30,000 in year one, depending on the complexity of your operation and how much cleanup is needed.

That feels substantial until you compare it to the alternatives:

The average food recall costs $10 million or more in direct expenses alone.

Over-recalling even one week's worth of product because you couldn't isolate the affected lots can exceed your entire implementation cost.

Retailer and insurance requirements increasingly treat traceability as table stakes, not a nice-to-have.

The real question isn't whether you can afford to upgrade. It's whether you can afford the risk of not upgrading.

Let's Talk About Your Recall Readiness

Are you compliant on paper, or actually ready to respond within 24 hours?

If you're not sure, let's walk through your current workflows and see where manual processes might be creating hidden risk. No pressure, no pitch. Just an honest look at where you stand.

 

Schedule a 30-Minute Traceability Review

~Audrey Quick, Founder of AGS Enterprises Consulting LLC

Audrey has spent 35+ years helping businesses manage ERP implementations and accounting software transitions.  If you're evaluating your options, we can book a free 15-minute call 

Book A Call to see wether a starter tool fits your stage or if going straight to the right system will save you a second move.

~Audrey Quick, Founder of AGS Enterprises Consulting LLC

Audrey has spent 35+ years helping businesses manage ERP implementations and accounting software transitions.  If you're evaluating your options, we can book a free 15-minute call