Excel vs FP&A Software for CPG Brands: When the Spreadsheet Breaks

"We're $1bn + and it's all in excel. It's awful, we're all burnt out, and we should have moved to a budgeting tool three years ago"

— Source: r/FPandA (49 upvotes)

That's a $1 billion company. Not a startup straining under growth. A profitable, established business that waited too long to move off spreadsheets: and now the cost of staying exceeds the cost of moving.

Excel didn't break because of incompetence. It broke because CPG/omnichannel math doesn't fit a 2D spreadsheet.

This guide shows you exactly when Excel stops working, why, and what the real cost is: not in software, but in analyst time and decision-making blindness.

The Formula

SKUs × Channels × Months × Waterfall Lines = Total Cells

Excel's stable limit is ~1M cells. Beyond that:

• File size exceeds 100MB (won't email, backup is slow)
• Recalculation takes 30-60 seconds (users wait for refreshes)
• Formula interdependencies create cascading errors
• Undo history is lost (one mistake, can't roll back)
• The file becomes a liability, not an asset

• You have ≤3 channels (usually DTC only, or DTC + Amazon + one marketplace)
• You have <200 SKUs
• You have <6 months of forecasting (weekly updates, not monthly planning)
• One person owns the model (no version control chaos)
• Your GL is simple (under 50 cost centers, no intercompany)
• Reporting is minimal (1-2 dashboards, not 20+ variations)
• You don't need scenario planning ("What if we launch on TikTok Shop?" = 10 hours of copying sheets)
• Month-end close takes <8 hours

If all of those are true, Excel still works. It's not elegant, but it works.

Most $1-5M DTC brands fit this profile. Most $10M+ omnichannel brands do not.

1. Formula Errors Go Undetected Until Month-End

In a 2M-cell model, there are thousands of formula links. Change one cell, and:

• You break 3 dependent sheets (the tool doesn't warn you)
• The error propagates silently (Excel shows a number, but it's wrong)
• You don't discover it until closing, when actuals don't match the forecast
• You spend 8 hours auditing cell references to find where the break is
• By then, it's 2am, you've missed the reporting deadline, and the CEO is wondering why the board pack is late

2. Version Control Chaos

Multiple people edit the same file:

• Sarah copies FY25_Budget_v3 to FY25_Budget_v3_Sarah_FINAL
• Mark gets FY25_Budget_v3 from shared drive and edits it
• Sarah sends Mark hers. Which is the "current" version?
• Month-end, you realize Mark's version didn't have the latest assumption changes
• There's no audit trail to figure out what happened when

Excel was not designed for collaborative editing. Even with "Track Changes," the process is fragile.

3. No Access Control

Either everyone edits the file, or it gets locked and passed via email.

• CEO opens the file, deletes a formula by accident, saves it
• No one can undo it 10 minutes later
• Finance finds out at board pack time
• Or: file is locked, 5 people email their updates to you, you manually merge 5 versions together at 9pm

4. Onboarding New Analysts Becomes Impossible

A new hire asks: "How do I update the forecast?"

• You spend 3 days documenting the 47-sheet workbook
• Sheet 3, column Q: is that the "current" YTD actual, or the "prior" YTD actual?
• There's a cell named "temp_calc_DO_NOT_TOUCH": what does it do? Even you're not sure anymore
• The new hire makes an innocent change in month 3, breaks three reports
• You rework her work. She leaves after 9 months, defeated
• The company effectively has zero succession plan for FP&A

5. No Audit Trail

Auditors ask: "What changed in the forecast between December and January?"

• You check the file properties. Last modified by "Mark" on Jan 17
• But was it Mark who changed the COGS % assumption, or a different edit?
• The file has no change log. You can't drill into cell-level history
• With an FP&A tool, you can audit: who changed what, when, and why (if they left a comment)

6. Month-End Close Takes 40-60 Hours

Here's what a month-end actually looks like in Excel:

• Day 1 (4 hours): Wait for accounting to close the GL. Export actual GL balances to CSV. Paste into "Actuals" sheet manually.
• Day 2 (3 hours): Check if the GL paste broke any formulas. Fix 5 formulas that got out of sync.
• Day 3 (2 hours): Pull channel actuals from Shopify, Amazon, Stripe. Paste into the forecast. Did the numbers update? Spot-check 10 cells.
• Day 4 (3 hours): Pull YTD metrics from BI tool (Looker, Tableau). Paste into the dashboard. Manually copy 50 metrics from the BI export to Excel (can't link live).
• Day 5 (4 hours): Calculate variance (actual vs forecast). Write variance commentary: "Q4 revenue was down 5% vs forecast due to lower conversion on Amazon." Type it manually for each line item.
• Day 6 (6 hours): Build board pack. Copy charts into PowerPoint. Titles don't match the latest data. Update 20 PowerPoint charts manually (linked Excel ranges don't auto-update in PowerPoint).
• Day 7 (4 hours): Review the board pack. CEO asks "Why is the gross margin down?" You trace the issue to… a wrong paste on Day 1. Fix it. Recalculate everything.
• Day 8 (6 hours): Final review. One more error found. Extend the close another 2 days.
• Total: 40-60 hours.

With an FP&A tool, this becomes:

• Day 1 (1 hour): Tool pulls GL actuals automatically from Xero/NetSuite. Pull Shopify/Amazon data via API.
• Day 2 (2 hours): Review variance reports. Tool calculates variance narrative (AI-assisted commentary).
• Day 3 (1 hour): Approve board pack. Charts update live.
• Total: 8-12 hours (month-end done).

The Analyst Cost

40-60 hours/month on month-end close

The Decision-Making Cost

Staying in Excel doesn't just cost hours; it blinds you.

• Slow insights: "What's my true profit by SKU × channel?" takes 2 weeks of manual analysis in Excel. In a tool, 5 minutes.
• No scenario planning: "What if we bundled these 3 SKUs?" = 4 hours of copying sheets and re-linking formulas. In a tool, 10 minutes.
• Stale reporting: Board pack is always 5 days old (it takes that long to close). Decision-makers work off outdated numbers.
• Risk blindness: "Are we on track to hit Q4 targets?" requires an ad-hoc forecast update that no one has time for. In a tool, the forecast updates weekly.
• Finance team burnout: Your FP&A analyst spends 80% of time on spreadsheet maintenance, 20% on strategy. They leave. You hire a replacement. Repeat cycle.

DTC (Shopify, Amazon, Direct) Scaling

A DTC brand can stay in Excel longer because the data structure is simple:

• Revenue is transactional (orders per day, ARPU)
• COGS is per-unit (easy to aggregate)
• Channels are few (Shopify ≈ DTC, Amazon ≈ marketplace, maybe email)
• The model is: Customers → AOV → Units → COGS → Margin
• You can build a pretty sophisticated model in 10 sheets

DTC brands can scale to $20-50M in Excel. But once you add wholesale/retail:

Wholesale (Distributor/Retail) Complexity

Wholesale breaks Excel because each channel has its own cost structure:

• Wholesale distributor: Discount 35%, payment in 30 days, 80-unit minimum order
• Retail (Target): Discount 40%, payment in 45 days, co-op advertising fund 2%, slotting fees $5K per SKU
• Quick commerce (Gopuff): Commission 35%, payment daily, exclusive SKU restriction
• DTC direct: No discount, payment immediate, single-unit orders OK

Now your model needs:

• Revenue by channel (separate pricing + unit model per channel)
• Cost of goods (same product, but different "cost of sales" per channel after deductions)
• Fulfillment (different payout cycles, inventory holding costs)
• Channel profitability (who actually makes money?)
• Scenario planning (what if we double retail distribution?)

That's a different problem. Your Excel model doesn't scale horizontally; it gets vertically complex.

Step 1: Acknowledge the Problem

Honest questions:

• Does month-end close take 40+ hours?
• Do we have version control chaos (multiple copies of the file)?
• Is it hard to onboard new people to the model?
• Can we run "what-if" scenarios without 4 hours of work?
• Do we have audit trails for who changed what?

If you answered "yes" to 3+, you're ready to move.

Step 2: Pick a Tool Based on Your Data Source

• If your actuals are in QuickBooks/Xero: Abacum, Jirav, or Niblin (all have live GL integration)
• If your data is fragmented (Shopify + Stripe + Inventory tool): Niblin (strong API connectors)
• If you're already in NetSuite: Adaptive Planning (native) or Abacum (via middleware)
• If you want the lowest barrier: Datarails (reads your existing Excel model)

Step 3: Do a 4-Week Pilot

Load your last 12 months of data into the tool. Build one forecast scenario. Run month-end close.

• Measure the time: how many hours to close in the tool vs Excel?
• Check the results: do the numbers reconcile to your books?
• Test a scenario: "What if we grew revenue 20%?" How long does that take?
• If the tool saves 20+ hours/month, commit. If not, try another tool or stay in Excel for now.

Step 4: Plan the Migration

Don't try to migrate everything at once. Parallel run:

• Month 1: Run actuals in both systems (Excel + tool). Check if they match.
• Month 2-3: Build the forecast in the tool. Excel still drives reporting.
• Month 4: Switch reporting to the tool. Excel becomes a backup.
• Month 5+: Excel is offline. Archive it. Tool is now your source of truth.

Excel got you to where you are. It's a remarkable tool. It's also not a database. Not a version-control system. Not a collaboration platform.

The moment your SKU × channel matrix exceeds Excel's 1M-cell stable limit, the tool becomes a liability. Errors hide. Versions multiply. Month-ends stretch to 60 hours.

The question isn't "Should we use Excel?" It's "At what revenue/complexity point do we move?" For omnichannel consumer brands, that point is usually $10-20M in revenue or 500+ SKUs across 8+ channels.

After that, the cost of staying in Excel exceeds the cost of moving.