# ERP for warehouse management: what it does, where it stops > An ERP can run a warehouse until the warehouse gets busy. What the warehouse module in an ERP covers, how it differs from a WMS, and how to pick one. - **Page** - https://iotready.com/insights/erps-for-warehouse-management - **Author** - Tej Pochiraju - **Published** - 2022-12-15 - **Topics** - Inventory Management, Operations ERP warehouse management means using the inventory module of your ERP to run the warehouse. Stock locations, receipts, issues, pick lists, reorder alerts. All of it lives next to your accounts, your sales orders and your purchasing, in one database. That's the whole appeal. One system, one set of numbers, no reconciling a warehouse tool against the books at month end. It works. For a while. ## What a warehouse ERP actually does Set it up and you get a record of what you own and where it sits. Each receipt adds stock. Each dispatch removes it. You can set a minimum level per item and get an alert before you run out, which is most of what a small warehouse needs from software. Because the ERP also holds your purchase prices, sales orders and returns, it can tell you what an item costs you to hold. Storage, days on hand, special shipping, the returns that come back. A standalone warehouse tool can't see most of that. It starts with a lot of data entry. Your current stock, your locations, your open orders, all of it typed or imported before the first report means anything. ## ERP or WMS? An ERP is wide. It does accounting, sales, manufacturing, HR, payroll and inventory, and it does the warehouse as one of those jobs. A warehouse management system (WMS) does one thing, and does it deeply. A WMS decides where a pallet should go, in what order your pickers should walk, and which bin is closest to the dock for a fast mover. It works from live data and from history. An ERP mostly records what happened after someone tells it. So which one do you need? Two questions get you most of the way. What do you want the warehouse to be doing in three years, in numbers you can check? And what does each option cost to implement and wire into everything else you run? Put those side by side and the answer is usually obvious. If it isn't, you probably don't have the first number yet. Small operation, one site, steady SKUs: the ERP's own module is enough. Several sites, thousands of locations, or pick paths that matter: you'll end up adding a WMS, and it'll sit beside the ERP, not replace it. We've written about that side in [the basics of warehouse management systems](https://iotready.com/insights/the-basics-of-warehouse-management-systems.md) and [how a WMS helps with inventory control](https://iotready.com/insights/how-a-wms-can-help-with-inventory-control.md). ## The part nobody puts in the brochure Both of them share one weakness. They only know what they've been told. A pallet moves and nobody scans it. A picker takes eleven when the slip says twelve. A weight gets typed from memory. The ERP records all of it faithfully and then reports it back to you with two decimal places. I wrote about that gap in [ERPs repeat the lies we tell](https://iotready.com/insights/erps-repeat-the-lies.md). Picking a better ERP doesn't close it. Capturing the event at the moment it happens does, with a scan, a scale or a reader, so the ERP gets something true to store. That's the job our [inventory management](https://iotready.com/solutions/warehouse-management.md) work does, whichever ERP is behind it. ## How to choose an ERP for the warehouse Six things decide it. In roughly the order they bite. - **Price.** What you pay has to match what you'll use. A big suite for a ten-person warehouse is money you'll watch leave. - **Size.** Some ERPs are built for enterprises and some for companies just taking off. Both work badly when you use them for the other. - **Setup.** If you want something running in a few weeks, a simple ERP beats a deep one. The deep ones pay back, but only after you've learned them. - **Platform.** Check that it runs on the machines your people actually have. - **Integration.** No ERP covers everything. Often it's cheaper to connect a small tool for the one thing it misses than to switch. - **Customisation.** Nothing fits to the millimetre. How much you can bend it is the difference between a system your team uses and one they work around. ## The ones people ask about **[SAP S/4HANA](https://iotready.com/integrations/sap.md).** Fast, with real-time analysis, and a lot of add-ons for IoT and analytics. It can catch a stock shortage or a machine fault earlier than slower systems. The catch is cost and constraints: it runs only on certified hardware, licensing is expensive, and a hybrid of cloud and on-premise setups gives people trouble. Teams that bring their old database habits to it rarely get the most out of it. **[ERPNext](https://iotready.com/integrations/erpnext.md).** Simple, and you can set it up yourself. It has a free tier and a growing community that answers questions. It's thinner on complex, high-level functions and it's newer, so some buyers hesitate. For a small or mid-sized warehouse, it's a good deal. **[Odoo](https://iotready.com/integrations/odoo.md).** Flexible. More than 35 modules, accounting through logistics, and pricing you can build up one module at a time, with a free community edition. The downside is setup. It's intricate, customising it takes a dedicated team, and an implementation can run for months. **NetSuite.** Bends to your workflows, integrates well, and gives you real-time visibility over customers and orders. It also needs steady maintenance, and being cloud-only makes it expensive for small companies. ## Where to start Count your locations and your daily movements. If you can hold both in your head, start with the module your ERP already has and put your effort into capturing events accurately. If you can't, price a WMS now. Then walk the floor on a busy day and watch where the data gets typed in. That's where your ERP is lying to you.