MRP Software Explained: The Planning Engine Inside Your Manufacturing ERP Software

If you run a manufacturing business, you know the pattern: a job stalls because one bracket kit is missing four bolts, the back corner holds three skids of steel nobody has touched since spring, and purchasing places a rush order every Friday afternoon at a premium freight rate. It’s tempting to blame the buyer, the supplier, or the schedule, but the cause usually sits upstream, in how your shop decides what to buy, what to make, and when. This decision process has a name, material requirements planning, or MRP. MRP software sits at the center of manufacturing ERP software, and understanding how it works explains why some shops ship on time with less inventory while others carry more stock and still run short.

What MRP Does, in Plain Terms

Think about hosting a holiday dinner for 20 people. You start with the guest count, pull out the recipes, check the pantry and fridge, subtract what you already have, and write a shopping list. Then you work backward from dinner time: the turkey needs two days to thaw, so it goes in the fridge on Tuesday, and the pies go in the oven Thursday morning. MRP software does the same job for your shop across hundreds or thousands of parts, every day.

The Three Inputs Behind Every MRP Plan

MRP software works from three sets of information, and the plan is only as good as each one:

• Demand: customer orders and forecasts telling you what to ship and when
• Bill of materials (BOM): the recipe for each product, listing every raw material, purchased part, and subassembly with quantities
• Inventory and supply: what’s on the shelf, what’s already committed to other jobs, and what’s on order from suppliers

Add lead times and routings, meaning how long suppliers take to deliver and how long each step takes on your floor, and MRP has what it needs to build a plan.

A Worked Example

Say a customer orders 500 steel brackets for delivery on November 20, and each bracket uses four bolts. Here’s how MRP software works through the bolts alone:

• 500 brackets at four bolts each means you need 2,000 bolts
• You have 1,200 bolts on the shelf, but 300 are committed to another job, leaving 900 available
• You’re short 1,100 bolts
• Your supplier needs two weeks to deliver and the brackets need a week in fabrication and coating, so the purchase order goes out by October 30

MRP repeats this math for the steel sheet, the powder, the packaging, and every other component, does it again for every open order, and recalculates whenever an order, a delivery date, or an inventory count changes. Keeping up with this math by hand across a full order book takes more hours than any planner has, so shops without MRP fall back on gut feel, padded orders, and the one person who keeps it all in their head.

Reading an MRP Schedule

Here’s what MRP output looks like in OnRamp’s Review MRP Schedule screen for a purchased trunnion bottom plate, a component used in a larger assembly. Each row on the schedule is either a demand, meaning a date when production needs plates, or a supply, meaning an order MRP suggests to cover it:

• Net Qty On Hand shows 160 plates in stock, and the first demand on October 8 calls for 160, so current stock covers it and the projected balance drops to zero
• The DEP rows are dependent demand, meaning nobody ordered the plate on its own; the need comes from work orders for the parent assembly, and MRP traced it back through the bill of materials
• The SPO rows are suggested purchase orders, each sized to match the next demand and due the day before production needs the plates
• The Projected column is the running balance, so you see at a glance whether the plan ever goes short

This one part carries 81 scheduled lines over the coming months, and your shop has hundreds or thousands of parts like it, which is why planners working from spreadsheets fall behind.

Why MRP Is the Heart of Manufacturing ERP Software

Nearly every department in your business acts on the answers MRP produces:

• Purchasing knows what to order and when
• Production knows which jobs have material and which jobs will stall
• Sales knows whether a promised ship date holds up
• Finance knows how much cash sits in inventory and what’s coming due to suppliers

When MRP works, these departments follow one plan. When it doesn’t, each department builds its own workaround, and you end up with whiteboards, side spreadsheets, and a daily meeting to sort out what to run next.

What Goes Wrong When MRP Works From Bad Numbers

The risk with MRP sits in the inputs rather than the math. If any input is wrong or out of date, MRP produces a confident plan built on bad information, and your team learns to ignore it. Here’s where the numbers usually drift:

• People pull material for jobs without recording it, so MRP thinks you have stock you don’t
• Operators log scrap at the end of the week or not at all, so MRP plans around the parts you meant to make instead of the parts you made
• Engineering changes a part revision, the BOM in the planning tool still shows the old one, and purchasing buys the wrong component
• Material sitting on quality hold still counts as available
• A machine goes down for repairs, and the plan still assumes full capacity

Each of these failures pushes your team toward the same coping habits: planners pad orders to stay safe, buyers expedite, and inventory grows while stockouts continue. You pay for it in freight premiums, overtime, cash tied up in material, and late shipments to customers who notice.

Why Integration Decides Whether MRP Works

Every failure above has the same root cause, which is the information MRP needs living somewhere other than the MRP tool. Many shops run a standalone MRP or scheduling tool connected to accounting software, with inventory in a spreadsheet, quality on paper, and maintenance on a whiteboard. Each handoff between tools adds a delay or a manual entry, and each one becomes a place where your numbers drift.

In integrated ERP software, MRP reads from the same records your floor, warehouse, quality team, and maintenance crew update every day:

• When an operator reports scrap at the work center, MRP sees the shortfall right away
• When receiving logs a delivery, available inventory updates without a second entry
• When quality places a lot on hold, MRP stops counting it as available
• When engineering releases a new revision, the BOM MRP uses changes with it
• When a machine goes down for maintenance, the schedule reflects the lost capacity
• When shipping closes out an order, the demand drops off the plan

The result is a plan your team trusts enough to follow, which is the reason to have MRP in the first place.

How OnRamp Approaches MRP

OnRamp was built inside Mancor Industries, a Tier 1 automotive supplier running fabrication, machining, and finishing across six facilities, where missed deliveries carry real consequences with OEM customers. MRP in OnRamp shares one data model with manufacturing, inventory, quality, maintenance, shipping, and accounting, so every department works from the same numbers by design rather than through sync jobs or imports. Operators record production and scrap on the floor, receiving and shipping update inventory as work happens, and planners see shortages early enough to act on them.

Questions to Ask Before You Choose MRP Software

Before you sign with any vendor, put these questions on the table:

• Does MRP read inventory, scrap, and receiving data directly, or through imports and sync jobs?
• Does material on quality hold drop out of available inventory automatically?
• When engineering changes a BOM revision, how does the change reach purchasing and the floor?
• Does the plan account for machine downtime and maintenance schedules?
• Will your planners need to export to Excel to make the plan usable?

The answers tell you whether you’re buying a planning tool your team will follow or another report they’ll work around. If your shop runs material planning out of spreadsheets or a tool your team has stopped trusting, we’re happy to walk through how OnRamp handles MRP using your own parts and orders.