Business management software

ERP for small business: what an online store needs

Written by The StoreChart team6 min read

In short

An ERP system runs finance, purchasing, inventory, manufacturing and payroll on one shared database. A small or mid-sized online store usually does not need one: order, stock and cost management next to accounting software is enough. An ERP starts to pay off with manufacturing, complex purchasing or several legal entities.

Many store owners hear that a growing business needs an ERP system, and start shopping for one. But ERP software was built for organizations with manufacturing, complex purchasing and several companies, and most online stores are not there. Sometimes an ERP really is necessary, and sometimes it is a slow, expensive way to solve a small problem: orders and stock scattered across channels. This guide helps you decide. It explains what an ERP includes, a check based on what a store actually needs, how an ERP differs from store management software, and what to ask a vendor. It is part of the business management software guide.

What an ERP system gives you

An ERP is software that runs an organization's core processes on one database: finance, purchasing, inventory, sales, manufacturing and HR. Its core is a general ledger, so every operational action, such as receiving goods, is also recorded automatically in the books. For the full explanation, see what is ERP.

The advantage is one version of the truth: operations and finance see the same numbers. The price is a heavy implementation, because every product, account and process has to be mapped before the system starts to work.

When a store needs an ERP

A store with two operations people, one warehouse and an accountant who closes the month in her own software usually does not need an ERP. The signs that change the answer:

  • Several companies or currencies: that must be combined into one set of financial reports.
  • Manufacturing or assembly: a product made of components, with a bill of materials and production orders.
  • Complex purchasing: approvals in several steps and budgets per department.
  • Your accountant requires it: stock and cost of goods sold must post to the general ledger automatically.
  • The cost of integration: the work of linking several separate tools costs more than one system.

If none of these applies, the real need is probably operational.

ERP or store management software

Comparing by need shows where each option is strong:

NeedFull ERPStore management softwareAccounting software
Orders from several storesDepends on the linkBuilt inNo
Stock and product costYesYesPartly
Profit per orderSometimesYesNo
General ledgerYesNoYes
Manufacturing and payrollYesNoNo
Implementation timeMonthsShorterShort

The table is general, and capabilities differ between vendors. A typical store gets what it needs from a combination of store management software and accounting software. For a closer look, see management software for small business and bookkeeping for an online store.

Example: three stores and one warehouse

A business runs three WooCommerce stores and one Shopify store from a shared warehouse. Its pain: orders and stock in four places, and nobody knows the real profit. It does not manufacture, does not buy through approval workflows and has no other companies. A system that brings orders, stock and costs together, next to accounting software, solves the problem without an ERP implementation.

The figures in this article's examples are illustrative only and do not reflect actual customer data.

Example: when the need changes

The same business starts assembling kits from components bought from several suppliers. Every purchase needs a manager's approval, and it opens a subsidiary abroad with another currency. Suddenly there is a bill of materials, purchase approvals and a need to consolidate reports. These are exactly the signs that justify looking at an ERP, and tidy data from an earlier system saves a large part of the implementation.

The figures in this article's examples are illustrative only and do not reflect actual customer data.

What a store needs first

Before you choose a system, write down what hurts most today. For most stores the list looks like this:

  1. Orders from every store in one place: without switching between admin panels.
  2. Accurate stock by warehouse: so you do not sell what you do not have.
  3. A real product cost: including freight and customs on imports, not only the supplier price.
  4. Profit per order: so you know what is actually worth selling.
  5. Expenses and supplier invoices: gathered, not scattered across an inbox.
  6. An export for your accountant: tidy data at the end of the month.

All of this is operational. None of it needs a general ledger, so there is no reason to start with a long implementation.

How to compare cost

The right comparison is total cost over two years, not the license price. For an ERP the cost is made of a license, implementation, customization, training and maintenance. For a modular setup it is a monthly subscription to store management software, plus accounting software. Before you decide, also write down the time your team will spend on each option, because an implementation that takes two months of the team's attention is a real cost.

The gradual route

You can start with store management software and move to an ERP only when the need appears. The advantage: when the time comes, your data is already in order. Products, suppliers, stock and costs are defined in one place, and an ERP implementation is easier because nothing has to be cleaned from scratch. A business that starts with an ERP before its data is tidy pays for data cleanup inside an expensive implementation.

Terms worth knowing

A few terms that come up in every conversation with an ERP vendor:

  • General ledger: the place where every financial transaction is recorded, using double entry.
  • Module: a part of the system that handles one area, such as purchasing or inventory.
  • Master data: products, customers and suppliers shared by every module.
  • Customization: changing the system to fit the business, which raises the cost and lengthens the implementation.

Questions for an ERP vendor

When you do evaluate an ERP, insist on clear answers:

  • What the implementation includes: setup, training, data migration and customization.
  • How it connects to the store: a ready link or custom development, and who maintains it.
  • How you get data out: what happens if you move to another vendor.
  • The total cost: licenses, implementation, maintenance and add-ons, for two years at least.
  • Who will use it in practice: whether your small team can work with it without a permanent consultant.

Three questions to decide

If it is still unclear, three questions help:

  1. Is there a process our current tools cannot handle? If the answer is manufacturing or consolidating several companies, an ERP is probably needed. If it is mostly orders and stock, it is not.
  2. What does it cost us to do nothing? Hours of manual work, order mistakes and a late month-end close are real costs you can estimate.
  3. What does the accountant really need? Sometimes only a tidy export, sometimes automatic posting to the general ledger. The answer decides a lot.

Common mistakes

  • Buying an ERP "just in case": software configured for needs you do not have adds cost and training without adding control.
  • Ignoring the store link: an excellent system that does not receive orders automatically doubles the work.
  • Implementing in peak season: implementation takes the team's attention, and in the busy season nobody has it.
  • Postponing the accountant's input: what the accountant needs from the system decides a lot.

What StoreChart includes and what it does not

StoreChart is not an ERP. It covers the operational side: orders from WooCommerce and Shopify stores, inventory with fixed cost, weighted average or FIFO, imports and suppliers with landed cost, expenses and per-order profitability.

Not included: a double-entry general ledger, payroll, manufacturing, tax invoices and receipts. That is why you use it alongside accounting software, and your accountant receives an export of orders and customers plus supplier invoices collected from Gmail. The full overview is on the platform page.

Frequently asked questions

Does an online store need an ERP system?

Usually not at the start. A store with a small team and one warehouse does fine with order and inventory management plus accounting software. An ERP becomes relevant with manufacturing, complex purchasing or several legal entities.

What is the difference between an ERP and store management software?

An ERP includes a general ledger and covers the whole organization, including payroll and manufacturing. Store management software focuses on orders, stock, suppliers and profitability, and connects to accounting software.

How long does an ERP implementation take?

A full implementation usually takes months, because products, accounts and processes have to be mapped. The more customization, the longer it runs. Lighter software is quicker to set up but covers less.

Does an ERP connect to WooCommerce or Shopify?

Some systems offer a connection, and others need a custom link or a go-between tool. Check in advance which data moves, such as orders, stock and customers, and in which direction.

Is StoreChart an ERP system?

No. StoreChart covers the operational side of an online store: orders, inventory, imports and suppliers, expenses and profitability. It has no double-entry general ledger, payroll or manufacturing, so you use it alongside accounting software.

What should I ask an ERP vendor before choosing?

What the implementation price includes, how the store connects, who maintains the customizations, how you get your data out if you switch, and the total cost after two years.

See StoreChart with your own store data

Open an account, connect your store and see your own numbers.