Move to an ERP when stock, orders and money no longer agree without manual work. Choose one that fits your entity and site structure, and verify sales tax handling with your own invoices.
The usual starting point
Many growing companies run on a familiar combination: small-business accounting software for the books, spreadsheets for stock, orders and production plans, and a steady stream of email and chat between the office, the warehouse and the sales team. It works well for a long time. It is cheap, the accountant knows it, and everyone understands the spreadsheets because they built them.
The trouble starts gradually. The business adds a second warehouse or a site in another state, the product list grows, and more people need the same information at the same time.
Signs you have outgrown it
- Stock in the books and stock on the floor disagree, and finding out why takes days.
- Salespeople phone the warehouse to check availability before confirming an order.
- The month-end close depends on one person reconciling several spreadsheets.
- You cannot easily tell which customers are over their credit limit before you dispatch.
- Purchase decisions are made from memory rather than from reorder levels and open orders.
- The owner gets a different number for the same question depending on who they ask.
If several of these sound familiar, the problem is not discipline. It is that the information lives in too many places.
What to check before you choose
Fiscal year and currency. The system should run a January to December year by default, support any other fiscal year you keep, and handle multiple currencies natively if you buy or sell abroad.
Multiple companies, sites and states. Many mid-market companies run more than one legal entity. Check that each company keeps its own books and that you can still see consolidated figures. If you collect sales tax in more than one state, check how the system handles addresses, tax rules per location and transfers between sites.
Sales tax handling. Sales tax rules vary by state and change often, and support for them varies between systems. Do not rely on a feature list. Ask the vendor to process a sample of your own real invoices, including multi-state sales, exempt customers and credit notes, and have your accountant check the output. Hold every vendor, including us, to that standard of proof.
Credit and collections. Payment terms and outstanding balances drive working capital. Look for customer credit limits that can block or warn on new orders, and receivables aging you can trust.
Implementation realities
Implementation is where ERP projects succeed or fail. The software is rarely the hardest part; the time of your own people is. Someone senior has to own the project, decide how processes should work and make the team use the new system once it is live.
Keep the first phase small: accounts, sales, purchase and inventory. Add manufacturing, projects, quality or point of sale after the core has run cleanly through a couple of month-end closes. Trying to switch everything on at once is the most common reason implementations stall.
Plan training around jobs, not modules. A warehouse person needs to know how to receive, move and count stock, not a tour of every screen.
Budget realistically for the transition months. Expect the team to be slower for the first few weeks while they learn, and avoid going live in your busiest season. For many businesses that means not switching in the run-up to year-end close in December, or just before a seasonal peak. A quieter month gives people room to learn and gives you time to fix configuration issues before volumes rise.
Where Sundial fits
Sundial is the AI-native ERP for modern mid-market companies. It is built for US companies first and works anywhere: multi-company, multi-currency, any fiscal year. It runs on the open-source ERPNext engine, so there is no lock-in, and covers finance, sales, buying, inventory, manufacturing, projects, assets, quality, support and point of sale in one system, with a redesigned workspace on desktop and phone. Each customer gets a dedicated single-tenant instance with its own database, role-based permissions, a full audit trail and daily backups, plus white-glove onboarding.
If you are weighing a move, try the demo with a handful of your own scenarios, or talk to us about how your business runs today.




