How to Choose Inventory Software | Cash Flow Inventory

Start with how your business works

Most software choices go wrong before the first demo. A business picks a product for a feature it saw advertised, and only later finds the product assumes a different way of working: invoices before delivery when you deliver first, one warehouse when you have three, a till when you sell on credit to trade customers.

Before you look at any product, write one page about your own business:

What you sell — stocked goods, goods you make, services, or a mix — and roughly how many items.
Where stock lives: one shop, a warehouse and shops, or several depots.
How a sale runs: quote first or not, order first or not, whether you pick and pack, whether a delivery is recorded, and whether you invoice before or after it leaves.
How you buy: who may ask for goods, who approves, whether goods are received before the supplier’s bill is entered.
Where you sell: a counter, your own web store, marketplaces, sales reps, or all of them.
Which country’s tax and e-invoicing rules apply to you, now and in the next few years.
Who will use it, and what each person should not see — cost prices and margins are the usual ones.

That page is your yardstick. Every criterion below is a question about whether a product fits it.

The stakes are real. Out-of-stocks and overstocks together cost retail about $1.7 trillion a year worldwide (IHL Group, 2024), and holding stock is commonly put at 15–30% of its value a year — an indicative industry range, not a study (Cleverence, 2024). Software does not remove those costs, but the wrong software makes them hard to even see.

The criteria that matter

1. How it keeps stock accurate

Ask what changes the stock figure. In a sound design every change — a sale, a receipt, a transfer, a production run, an adjustment, a count — is a recorded movement with a date, a person and a document behind it, so any figure can be traced back. Be wary of products where stock is a number someone can simply overwrite. Ask what happens when a sale would take stock below zero: is it refused, allowed with a flag, or silently allowed? And look at how counts work: count sheets, differences shown before they are accepted, and a reason on every correction. Store stock records are about 63% accurate with barcodes alone (Auburn University RFID Lab, 2018), so regular counting is not optional.

2. How it values stock

Stock is money on shelves, and the method used to value it changes your cost of goods sold and your profit. The common methods are FIFO and weighted average; LIFO is not allowed under IFRS. Ask which methods the product supports, whether you can see the value of stock on any past date, and whether that value is reconciled to the inventory account in the books. If it cannot show stock at a date, year-end and audits will be painful.

3. Locations, units, lots and serials

If you have more than one site, stock must be held per location, and moving it should be a document — sent from one place, received at the other, with goods on the way visible in between. If you buy in boxes and sell in pieces, you need units with conversions. If your goods expire, you need lots with expiry dates and a way to sell the soonest-dated first. If you sell items with warranties, you need serial numbers. Ask for each of these to be shown, not described.

4. Fit with your sales and purchase process

Compare the product’s steps with your one-page description. Can it run quote → order → pick → pack → delivery → invoice → payment, and also a simple invoice → payment at the counter, without workarounds? Can each step be partial? On the buying side, look for requisition, request for quotation, purchase order, goods received, bill and payment — and the option to skip steps you do not use. Supplier invoices are expensive to handle: one study puts the cost at $2.78 per invoice for the best performers against $12.88 for the rest (Ardent Partners, 2024).

5. Accounting: integrated, or separate books

There are two sound designs. In one, the inventory product has its own double-entry ledger and every document posts as it happens. In the other, it connects to a separate accounting product. The second can work well, but ask exactly what is sent, how often, and what happens to a correction made after it was sent. The design to avoid is one where stock and books are kept apart and reconciled by hand at month end. Also ask whether posted entries can be edited in place — good practice is that they cannot, and corrections are new entries with an audit trail.

6. Approvals, rights and audit trail

As soon as more than one person works in the system, you need control over who can do what. Look for rights per screen and per action, the ability to hide cost, margin and supplier prices from some people, approval limits by amount, and an audit trail that records who changed what, when and from what to what. Ask whether cancelling, closing or writing off a document asks for a reason.

7. Integrations, and how they are proven

Online stores, marketplaces, couriers, payment providers and accounting products are where many projects stall. A logo on a website tells you little. Ask, for each connector you need: has it run against the real service with a live account, or only against the provider’s test system? What syncs — products, stock, orders, cancellations, refunds? In which direction? How fast? What happens when the other side is down, and how would you know? Then connect your own account during the trial.

8. E-invoicing and tax for your country

More countries require structured e-invoices or real-time tax reporting. In the EU, VAT in the Digital Age was adopted on 11 March 2025, with structured e-invoices (EN 16931) and digital reporting for intra-EU trade from 1 July 2030 (European Commission, 2025). Ask whether the product covers your country’s format, whether the profile is certified where certification exists, and what it does today if it does not cover you. Ask also about the tax returns you file.

9. Data ownership and export

Your records belong to you. Ask how your data is separated from other customers’, what you can export (lists, reports, personal data for access requests), whether there is an API, and what happens to your data if you stop paying. Ask how personal data about your customers can be exported or erased when they ask.

10. The pricing model

Prices differ less than pricing models do. Find out what the price is based on — users, locations, orders, items, modules or connectors — and what happens when you grow past a limit. Ask whether features are held back for higher plans, whether there are setup or implementation fees, and what a refund policy covers. Work out the cost for your business in two years, not today.

11. Support and learning

Ask how you get help, in which languages, and how fast. Look at the documentation before you buy: is it specific enough to follow without calling anyone? Check whether the product can teach new staff in the screens they will use, and whether there is someone to tell you when something is not supported rather than suggesting a workaround.

12. A trial on your own data

A demo shows the product at its best on the vendor’s data. A trial shows it on yours. Use a free plan or trial to run a real cycle: create a few real products with opening stock, buy and receive, sell and deliver, invoice and take payment, process a return, run a stock count, then read the stock value and the profit and loss. If those agree with what you expect, you have learned more than any comparison table can tell you.

Questions to ask any vendor

Show me every way the stock figure can change. Can anyone overwrite it directly?
What happens when a sale would take stock below zero — and who decides?
Which valuation methods do you support, and can I see stock value on any past date, reconciled to the books?
Can your sales steps match ours exactly, including partial picks, deliveries and invoices?
Does every document post to a double-entry ledger as it happens, or is it sent to another product? What happens to a correction?
Can I hide cost and margin from some staff, and set approval limits by amount?
For each integration I need: has it run against the real service with a live account, or only in a test system?
Do you cover e-invoicing and tax returns for my country? Is the profile certified?
How is my data kept apart from other customers’? What can I export, and is there an API?
What exactly does my price depend on, and what will I pay when I double in size?
Where is your documentation, and how do I reach a person when I need one?
Can I run my own business on it for a few weeks before paying?

A checklist for your trial

Products imported from a sheet, with units, prices and opening stock per location.
A purchase order approved, goods received in part, and the supplier’s bill made from the receipt.
A sale run through your own steps, with one partial delivery.
A customer payment, a return and a credit note.
A transfer between two locations, with stock in transit visible.
A stock count with differences, approved into an adjustment with a reason.
Stock value at a date that matches the inventory account.
A staff member who cannot see cost prices, and an approval that stops at a limit.
Your own online store or courier connected, with one real order and one cancellation.
An export of your lists and reports, and a look at the API documentation.
An e-invoice or tax return for your country, if one is required.
One question sent to support, and how long the answer took.

How Cash Flow Inventory answers each criterion

The guide above applies to any product. This section is about ours, stated as facts about what the software does today.

Stock accuracy: every stock change is a movement in one log, with who made it and the document behind it. Stock never goes below zero unless the business allows it. Counts compare counted with system quantities and approve into an adjustment.
Valuation: weighted average or FIFO per business; LIFO is valued as weighted average. Stock at a date is valued by that method and reconciled to the Inventory account.
Locations, units, lots, serials: stock per location, transfer orders with stock in transit, units with conversions, lots with expiry dates, serial numbers and bins.
Process fit: 20 sales processes chosen by five questions, each step partial where needed; purchasing as order → receive → bill → payment, or bill → payment, with requisitions and requests for quotation as options.
Accounting: its own double-entry ledger — every document posts as it happens, with banks and reconciliation, fixed assets, budgets, multi-currency, period locks and tax returns. QuickBooks Online and Xero connections are tested against each provider’s sandbox.
Approvals and rights: approval workflows for 10 document types, rights per page, field and amount, and an audit trail on every change; closing, cancelling and writing off ask why.
Integrations: WooCommerce and the Steadfast courier run live; the other stores, marketplaces and couriers are tested against each provider’s sandbox, and the app says which is which.
E-invoicing and tax: localisation packs for national e-invoicing and tax, including Peppol / EN 16931, India GST e-invoice, Saudi ZATCA, Mexico CFDI 4.0 and Poland KSeF. The national profiles are built to the published specification and are not certified — every file says so.
Data: each business works in its own isolated database. Reports can be printed, exported or scheduled; a REST API, webhooks and the Model Context Protocol give access to your records; personal data can be exported or erased on request.
Pricing model: a free plan with no time limit and no card; paid plans differ only in how many locations, users, items and orders they hold. See pricing.
Support and learning: step-by-step documentation, support by e-mail, and an assistant inside the app that can teach a task step by step in the real screens.
Where it does not fit: restaurants and cafés; a country that needs a certified fiscal device or e-invoice profile it does not cover; a business that depends on a connector not yet proven live; very large enterprises needing on-premise multi-company ERP; and a business with no stock and no invoicing.

Questions and answers

How do I choose inventory software for a small business?

Start from how your business actually works: what you sell, how many locations you have, whether you pick and deliver, and how you invoice. Then test the shortlisted products on your own data — a few real products, a purchase, a sale, a return and a stock count — and check that the stock value and the books agree at the end.

Should inventory and accounting be in one system?

Not always, but separate systems need a reliable link between them. If stock movements do not post to the accounts as they happen, someone has to re-key or reconcile them, and stock value and the balance sheet drift apart. One ledger behind both avoids that work.

What is the difference between FIFO and weighted average cost?

FIFO values the stock that goes out at the cost of the oldest stock still on hand; weighted average spreads cost evenly over all units. Both are accepted under IFRS; LIFO is not. Check which methods a product supports and what happens when you switch.

How can I tell whether an integration really works?

Ask how each connector has been proven: against the real service with a live account, or only against the provider’s test system. Then connect your own store or courier during the trial and watch a real order, a stock change and a cancellation go through.

How long should I test inventory software before deciding?

Long enough to run one full cycle of your business: buy, receive, sell, deliver, invoice, get paid, return and count. For most small businesses that is a few weeks of real work on a free plan or trial, not a demo.

Product

Solutions

Resources

How to choose inventory software — and the accounting behind it