Inventory Planning Without an ERP: How Small Brands Do It Well

The assumption baked into most inventory planning content is that you have an ERP — a central system that connects your orders, your inventory, your purchasing, and your financials into one place. SAP, NetSuite, Sage X3, Microsoft Dynamics. The kind of system that costs $50,000 to implement and requires a dedicated administrator to run.

Most founder-led brands at $5M–$20M don't have one. They have Shopify. A 3PL with its own warehouse management system. QuickBooks or Xero for financials. Maybe Amazon Seller Central. Maybe a separate system for wholesale orders. Each of these systems knows something about the business. None of them know all of it.

The question isn't how to get an ERP. It's how to run a solid inventory planning process with the tools you actually have — and when the lack of an ERP is genuinely costing you versus when it isn't.

What an ERP Does for Inventory Planning (And What It Doesn't)

An ERP centralizes data. When a sales order comes in, it updates inventory. When a purchase order is received, it updates the stock count. When inventory falls below a reorder threshold, it triggers an alert. All of this happens in one system, automatically, with a single source of truth for every function that needs to see it.

That's genuinely valuable at scale. At $50M+ with complex multi-site inventory, manufacturing orders, and a large team making decisions from the same data, a central system prevents the expensive errors that come from people working off different spreadsheets.

What an ERP doesn't do: think. It doesn't decide what your demand forecast should be. It doesn't determine the right safety stock level for a SKU with variable lead times. It doesn't flag that your year-2 forecast is inflated by a pantry loading event from the prior year's promotion. It doesn't tell you whether to cut production if a retailer goes quiet.

The planning intelligence lives in the process, not the system. Brands that buy an ERP hoping it will install a planning process are consistently disappointed. Brands that build a solid planning process with basic tools and then migrate to an ERP when the operational complexity justifies it — those transitions go well.

What You Actually Need for Inventory Planning

Strip it back to the essentials. Inventory planning requires four things:

1. A clean, current picture of what you have

How many units of each SKU are on hand, where they are, and when inbound purchase orders are arriving.

2. A forward-looking demand forecast

A reasonable expectation of how many units of each SKU you'll sell in the next 3–12 months, by channel.

3. Lead time and reorder logic

How long it takes to get product from order to available, and at what inventory level you need to trigger that order.

4. A regular process for updating and acting on the above

Someone reviews the picture monthly, updates the forecast, confirms or places orders, and makes decisions when the plan and reality diverge.

An ERP can automate parts of this. A well-built spreadsheet connected to data exports from your existing systems can do all of it manually. The automation is a speed and accuracy improvement. The process is the requirement.

How to Build the Data Layer Without an ERP

The data challenge without an ERP is that your inventory picture lives in multiple places. Here's how to pull it together.

Inventory on hand: Your 3PL's WMS or warehouse system is the source of truth for physical inventory. Most 3PLs can generate a standard inventory report — units on hand by SKU, by location — on demand or on a scheduled export. If your 3PL can't produce this report cleanly, that's a 3PL problem worth addressing separately.

If you're fulfilling from your own warehouse or a co-location, the source of truth is whatever system you're using for receiving and picking — even if that's a spreadsheet maintained by your warehouse team.

Sales data: Shopify, Amazon Seller Central, and most wholesale order management platforms can export unit-level sales by SKU by date. The key is pulling this at the unit level, not the revenue level, and exporting it consistently — same fields, same date range format — every month. The inconsistency of manual exports is one of the most common data quality problems we see. Standardize the export format once and stick to it.

Inbound purchase orders: This is often the weakest link in a non-ERP setup. POs are in email threads, shared in PDFs with the co-man, tracked in a spreadsheet someone started six months ago. The fix is simple but requires discipline: maintain a single PO tracker — a Google Sheet works fine — with one row per open PO, the SKU, quantity, expected receipt date, and status. Update it whenever a PO is placed, when it ships, and when it's received. This is the inbound inventory visibility layer that most small brands are missing.

Lead times: Document your full supply chain lead time by SKU and by channel once, in writing. Production time plus transit to your 3PL plus 3PL receiving plus any retailer DC lead time if applicable. These numbers don't change often. Write them down and keep them updated.

With these four data sources pulling into a central planning model — even a spreadsheet — you have what an ERP would give you for inventory planning purposes.

Building the Planning Model in a Spreadsheet

A Google Sheet or Excel workbook structured around these components handles inventory planning for most brands under $15M with 40 or fewer SKUs:

Tab 1: SKU Master

One row per SKU. Columns for: lead time (days), safety stock target (units), reorder point (units), MOQ, co-manufacturer, channel. This is reference data — update it when something changes, not monthly.

Tab 2: Demand Forecast

One row per SKU. Monthly unit forecast for the next 12 months. Columns for each month. Updated monthly with the latest demand assumptions. The first column of each update cycle becomes the prior month actuals.

Tab 3: Inventory Position

One row per SKU. Columns for: current on-hand, inbound POs by expected receipt month, projected closing inventory for each of the next 6 months (on-hand + inbound − forecast demand), weeks of stock at each projection point, reorder trigger flag.

The projected closing inventory is the most important output. It tells you, for each SKU, when you're going to hit your safety stock level if no new orders are placed. That's the number that drives your purchasing decisions.

Tab 4: PO Tracker

One row per open purchase order. SKU, quantity, order date, expected ship date, expected receipt date, status. When a PO is received, mark it and move to a historical tab rather than deleting it — the history is useful for measuring actual lead times against estimates.

Tab 5: Forecast Accuracy

One row per SKU per month. Forecast, actual, variance, MAPE. Updated monthly. This tab tells you whether your planning model is getting better or worse over time, and which SKUs are driving the most forecast error.

This isn't a complex build. A competent spreadsheet user can build a working version of this in a day. The maintenance is a monthly update cycle of 45–90 minutes depending on SKU count.

The Tools That Bridge the Gap

If manual data exports are consuming too much time or creating too many errors, several lightweight tools can automate the data layer without requiring a full ERP implementation:

Inventory Planner by Sage connects directly to Shopify and Amazon and generates SKU-level demand forecasts and purchase order recommendations automatically. At $100–$300/month, it eliminates most of the manual data work for DTC-first brands. It doesn't solve for complex retail channel planning or trade promotion modeling, but for straightforward e-commerce inventory it's a clean step up from a spreadsheet.

Cin7 Omni and similar inventory management platforms sit between spreadsheet and full ERP — they centralize inventory across channels, generate reorder alerts, and manage POs without the implementation cost and complexity of enterprise software. Worth evaluating once you're above 40 SKUs or managing three or more sales channels.

Parabola is a workflow automation tool that can connect your data sources — Shopify, your 3PL's reports, your wholesale system — and push them into a central model automatically on a schedule. Not a planning tool itself, but a way to eliminate the manual export-and-paste cycle that makes spreadsheet-based planning error-prone. Particularly useful for brands that have the planning model figured out but are losing time to data wrangling.

Airtable or Notion can replace a PO tracker spreadsheet with something more collaborative and trackable if multiple people need to update and view open orders. Not a planning tool, but a cleaner way to maintain the PO log when more than one person is touching it.

None of these require ERP-level investment or implementation time. They're bridges — ways to get more automation and accuracy from a process you've already built.

When the Lack of an ERP Is Actually Costing You

For most brands under $15M with a clean planning process, the absence of an ERP is not a material problem. The process works. The manual overhead is manageable. The decisions are good.

There are specific situations where the lack of a central system starts to hurt:

You're managing more than 50 SKUs across three or more channels and the monthly update cycle is taking a full day or more. The manual overhead is a real cost, and the error rate in complex spreadsheets starts to become a risk.

Multiple people are making inventory decisions from different data sources. Your ops lead has one inventory number, your sales lead has another, and finance has a third. Decisions get made based on different pictures of reality. This is a data centralization problem that a shared system solves.

Your purchasing decisions require real-time data. If you're operating in an environment where inventory positions change fast enough that a monthly update cycle creates meaningful risk — high velocity, short shelf life, perishable goods — a system that updates continuously matters more than it does for a brand with a 90-day demand cycle.

You're preparing for a significant scale event — a major retail rollout, a Series A, a third-party acquisition. Enterprise buyers and investors expect to see centralized, auditable inventory data. A spreadsheet-based system that works perfectly for operations can be a liability in a due diligence process.

Outside of these scenarios, an ERP is a future investment, not a current requirement. Don't let the absence of one become an excuse for not having a planning process — the process is what matters, and a spreadsheet is sufficient to run it.

The Sequence That Works

Start here, in this order:

1. Build the data layer. Clean inventory report from your 3PL. Consistent unit-level sales export from your channels. A maintained PO tracker. Lead times documented per SKU.
2. Build the planning model. A spreadsheet with the five tabs described above, updated monthly.
3. Run the process. Monthly S&OP cadence — refresh the data, review demand, check inventory, make reorder decisions. Every month, on a schedule.
4. Evaluate tooling when the manual overhead becomes a problem. Not before. Let the process tell you when automation is worth buying.

An ERP won't install this process for you. But once the process exists, an ERP — or any tool that automates parts of it — will make it faster and more reliable.

Build the process first. The tools follow.

Running inventory without an ERP and not sure if your process is holding up?

Book your audit at izba.co