Manufacturing ERP software for growing manufacturers

Both, in the sense most manufacturers mean it. The MRP part is built in: working out what to make and what to buy from your BOMs, your orders and your current stock. It runs on the same database as sales, purchasing, inventory and the general ledger, so material issued on the floor moves your stock and your accounts without anyone re-keying it. If all you need is the planning maths, a standalone MRP tool is cheaper. The reason to buy an ERP is to stop reconciling between systems.

Yes. You define a subcontracting BOM that maps the finished item to the service you’re buying, raise a subcontracting order, and transfer material to the supplier’s warehouse. The stock stays on your books while it’s out. Required against supplied quantity is tracked per material, and the receipt posts the stock and ledger entries when the goods come back.

Yes. Cost accumulates as material is issued and job cards are logged, so you can compare cost-to-date against the BOM estimate while the work order is still open. Job card cost comes from the time actually logged at each workstation, not a standard rate applied afterwards.

That’s the common case. A production plan pulls items straight from sales orders, nets them against stock on hand, and creates the work orders and purchase requests for whatever is short. Make-to-stock works the same way, except you add the items to the plan yourself instead of pulling them from orders. Most factories run a mix and don’t have to pick one.

There is no fixed limit. A BOM can contain sub-assemblies that have BOMs of their own, and cost rolls up through every level. When you create work orders from a production plan, the sub-assembly orders are created alongside the parent, so you are not raising them one at a time.

That’s where most ERPX manufacturing users are. Multi-level BOMs, heavy subcontracting for dyeing, stitching and printing, batch tracking on finished goods, and export paperwork downstream are all part of the same system. There’s a fuller write-up on the textile and apparel export page.

We quote after a demo rather than publishing a price list. Scope moves the number a lot: how many modules you switch on, how many people need logins, and how much history has to be migrated. A demo is the quickest route to a real figure.

It depends almost entirely on the state of your data. If your item master and BOMs are already accurate and somebody on your side owns the project, it moves quickly. If the BOMs have to be rebuilt from scratch, that is the long pole and no honest answer can skip it. We would rather tell you which of the two you are looking at during the demo than quote a timeline now.

Usually a stack of spreadsheets plus a separate accounting package. Because production, inventory and the ledger share one database, the monthly reconciliation between them stops being a job.