ERP vs MES vs WMS vs MRP

Start with the transaction

ERP coordinates business records such as purchasing, inventory, sales and financial transactions. The scope varies by product. Start the architecture discussion by identifying where an order, stock balance and financial posting become authoritative. A product can cover several roles, so the acronyms alone do not tell you how many systems are required.

Planning and execution answer different questions

MRP calculates material requirements from demand, bills of materials and supply assumptions. MES supports execution and collection of production activity. Ask how a late receipt changes the plan, and how scrap or rework changes material demand. Test the feedback loop, rather than viewing planning and production as separate demonstrations.

Warehouse control needs a location model

WMS supports warehouse execution such as receiving, locating stock, picking and shipping. The required depth depends on the operation. Run a receipt, a location transfer, a partial pick and a stock count. Verify lot or serial tracking across the boundary between warehouse transactions and the inventory ledger.

Inspect every handoff

For each interface, record the identifier, message timing, retry behavior and support owner. Ask what happens when production reports arrive late or a receipt is reversed. Compare native and integrated approaches against the same acceptance tests. Either can work; the evaluation should reveal operational responsibilities and reconciliation effort.

Give each event a single authority

Draw the path of a production completion. The machine may count cycles, MES may accept good units and scrap, WMS may move the pallet, and ERP may value the receipt. Decide which event changes stock and which merely records activity. A cycle is not necessarily a saleable unit. Establish a common production order, operation, item revision and tracking identifier across the systems. Retain both event time and posting time where delayed messages matter. If two applications can correct the same quantity, describe the precedence rule and reconciliation process. This simple ownership exercise exposes double posting risks earlier than a diagram containing only application names and arrows.

Understand what a material plan assumes

A material plan depends on demand, inventory availability, expected receipts, lead times and the structure of the product. Decide whether held stock is available, how substitutes are selected and whether a forecast is consumed by orders. A purchase suggestion does not establish that a supplier can meet it. A planned production date does not establish that a constrained machine or qualified operator is available. Ask whether capacity is merely reported, roughly checked or actually used to constrain the schedule in the offered configuration. Demonstrate a component shared by two urgent orders. The useful question is which commitment changes when supply changes, and who is authorized to choose the response.

Use a lost-message exercise

Illustrative example: MES reports 40 completed units, the network drops, and the message is retried. The expected inventory receipt is 40 units, not 80. Give the message a stable identity and ask the proposed integration team to show how a duplicate is detected. Next deliver a correction before the original message and observe the handling. These are architecture test cases, not claims about any vendor. Require a visible exception queue with an owner and a way to reconcile the accepted event with the receiving transaction. A successful retry indicator alone is insufficient if a person must compare databases to discover an incorrect stock balance.

Examine warehouse detail at the right level

A simple stockroom may manage a few bins adequately inside ERP. A complex warehouse may require directed putaway, wave picking, replenishment tasks and mobile exception handling. Build a path from receipt through inspection, storage, picking, packing and shipment, including who owns the goods at each stage. Test damaged stock in a pick location and a carton containing mixed lots. Ask how a stock count interacts with an active pick. More location detail can improve execution but also increases scanning and master-data work. Evaluate the actual handling unit, label and device used by operators. A desktop transfer screen does not prove a workable forklift workflow.

Keep genealogy intact across subcontracting

Send material to an outside processor while retaining the required ownership and tracking records. Receive a partial quantity, record scrap and return unused material. Inspect whether the supplier's process identifier remains linked to the original component lots and finished output. ERPNext's official subcontracting documentation describes a distinct subcontracting flow; that is a useful example of why outsourced work deserves its own scenario. It does not establish the suitability of every edition or configuration. Ask how late invoices, supplier-held inventory and rejected receipts reach the ledger. The aim is to make execution and financial consequences agree even when physical goods are outside your own plant.

Choose boundaries that the team can operate

A native suite may reduce interface work yet provide more execution depth than a site needs, or less than its specialist process requires. Separate systems may fit each function well while demanding stronger integration operations. Compare the same transaction pack and record recurring reconciliation, upgrade coordination and support ownership. Specify who answers when MES shows completion but ERP has no receipt. Keep an interface register containing message identity, source, destination, ordering assumptions, latency target, retry rules and balancing report. The right architecture is the one whose important boundaries are explicit, testable and supportable by the people who will run it.

Common questions

Continue your research

The following profiles provide a starting point for checking vendor-described scope. Inclusion is not a ranking or a statement that every requirement is supported.