Can Airtable really replace an ERP?

For a brand between $1M and $10M, a custom operations system usually can, and Airtable is one of the foundations it can run on. At that size the gap is rarely accounting or manufacturing depth, it is that product data, stock and purchase orders live in separate places. A tailored system closes that gap. A brand running its own factories or complex financial consolidation is a different case.

Airtable or custom software, which one do you build on?

It depends on the volume and on what your team already uses. Airtable when the team needs to open, filter and edit the data every day and the volume stays reasonable. A database you control, with an application built on top, when the catalog, the order volume or the integrations outgrow a no-code tool. Both give you the same thing: one structured system, documented, that your team runs.

What happens when we outgrow it?

You move up, the same way you would move off any system. The difference is what you take with you: a clean, structured, documented dataset and the logic that runs on it, instead of an export from a vendor. A system that started on Airtable can move to a database you control without redesigning the model. Brands that later move to an ERP arrive with their data already in order.

Does it sync with Shopify?

Yes, in both directions, and across several stores. Product data, inventory and orders stay aligned between the system and each store, so the catalog does not drift. Multi-store brands are the most common case, because that is where a spreadsheet fails first.

Who controls the system once it is built?

You do. Your data, your logic, documented and handed over with the admin rights. On Airtable it lives in your own workspace under your billing; on custom software it lives on a database you control. There is no retainer to keep it running and no dependency on us: you can change it yourself, hand it to another builder, or ask us to keep evolving it.

Is this just a spreadsheet with a nicer interface?

No. A spreadsheet has no relationships, no permissions, no automation and no integrations. A custom operations system has linked records, a real data model, roles, automated flows, live connections to Shopify and your other tools, and AI agents where a task needs reading. The visible surface is simple, what runs underneath is not.

Airtable vs ERP for ecommerce brands

Most brands between $1M and $10M ask this question at the same moment: the spreadsheet has broken, and the first quote for an ERP has landed. Here is what actually separates an ERP from a custom operations system, whether it runs on Airtable or on software built for you, including the cases where the ERP is the right answer.

An ERP is a complete, standardised system you adopt and adapt to. A custom operations system is smaller, tailored, and shaped around how you already work. It can run on Airtable or on a database you control with an application on top. Below roughly $10M in revenue, most ecommerce brands need the second. The ERP becomes the right call when finance, manufacturing or regulatory depth stops being optional.

What each one actually is

An ERP, enterprise resource planning, is a single system covering finance, inventory, purchasing, production and often sales. It arrives with its own model of how a company should run. That model is the product. You configure it, you train your team on it, and where your process differs from the model, you change your process.

A custom operations system starts from the opposite end. It begins with how your brand already works, and builds a structure around it: product data, stock across warehouses, cost per unit, purchase orders, wholesale. It connects to Shopify and to the tools you already pay for. The foundation is a choice, not a religion: Airtable when your team needs to open and edit the data every day and the volume allows it,custom software on a database you control when the volume or the integrations outgrow a no-code tool. Either way the model, the logic and the documentation are yours.

Both replace the spreadsheet. They replace it with very different things.

Side by side

	Spreadsheet	Custom operations system	ERP
Fits your process	Completely, that is why it survived	Built around it	You adapt to the system
Time to something usable	Immediate, then it degrades	Weeks, one block at a time	Months, often longer
Who can change it	Anyone, which is the problem	Your team, with guardrails	A consultant, on a change request
Independence	Yours, until it breaks	Your data and logic, documented, no retainer needed	Licensed, renewed annually
Foundation	Excel or Sheets	Airtable, or a database you control	The vendor's platform
Multi-store Shopify	Manual, drifts within weeks	Synced both ways	Depends on the connector
Accounting depth	None	Feeds your accounting tool	Native and complete
Manufacturing depth	None	BOM and costing, not shop floor	Full, down to work orders
AI agents	An AI pilot on top of the mess	Where a task needs reading, with a human sign-off	Vendor roadmap
What breaks first	Two people editing at once	Undocumented custom logic	Adoption, people work around it

When an ERP is the right call

This section exists because the honest answer is not always the one that suits us. An ERP is the better choice when:

You manufacture at scale and need work orders, shop floor scheduling and production capacity planning, not just a bill of materials.
Your finance function needs statutory consolidation across entities, multi-currency ledgers and an audit trail built into the same system as operations.
You operate in a regulated category where traceability and validated systems are a legal requirement, not a preference.
You have grown past the point where a small team can hold the process, and you would rather buy a proven model than define your own.

If two or more of these describe you, the ERP conversation is the right one to have. A tailored system will feel lighter and cost less, and it will still be the wrong tool.

When a custom system is the right call

Your operations are specific enough that every ERP demo requires you to explain why your case is different.
The real problem is that product data, stock and costs live in separate places, not that you lack accounting features.
You sell across several Shopify stores and the catalog drifts between them.
You need something working this quarter, not a project that lands next year.
You want to keep the ability to change how you work without raising a change request.

Airtable or custom software

The question comes up in every audit call, and the answer is not ideological. Airtable wins when the people who run the operations need to open the data every day, add a field, filter a view, share a slice with a supplier, without calling anyone. It loses when the catalog runs into tens of thousands of records, when the integrations need more than its API allows, or when the interface has to be a real application rather than a grid.

In that second case we build the same model on a database you control, with an application on top and the automations and agents around it. The design does not change, the foundation does. A system that starts on Airtable and outgrows it moves to that setup without a redesign, because the model was clean from day one.

What people get wrong about running Airtable as an ERP

The phrase invites a false comparison. Nobody should try to rebuild SAP in Airtable, and the attempts that fail are usually the ones that tried. What works is narrower and more useful: take the operational core that the spreadsheet was already holding, product data, stock, costs, purchase orders, wholesale, and give it a real structure, real permissions and real connections.

Accounting stays in the accounting tool. Shipping stays with the 3PL. Selling stays in Shopify. What you build is the layer that ties them together, which is precisely the layer the spreadsheet was pretending to be.

The second mistake is building it as one big system. A brand that tries to launch everything at once tends to abandon it. Starting with the single block that hurts most, usually product data or stock, gets something in use within weeks and earns the right to build the next one.

How we approach it

Propicca builds these systems for ecommerce brands scaling from $1M to $10M, in three layers: the structure first, then the automation that follows your rules, then AI agents where a task needs reading. We start with a free audit call, write the scope and the price down, build the block that hurts most, then grow it. The system is documented and handed over, so it keeps running without us. If you want the detail on the product data side, we wrote a separate page on building a PIM on Airtable.