Procurement Data Cleansing: What to Do When Your Supply Chain Data Is Bad

Most manufacturers know their ERP data isn't perfect. What surprises them is just how widespread the problems are once they start actually looking.

Bad data shows up everywhere: lead times that haven't been updated in years, safety stock levels set for demand that no longer exists, buyer assignments tied to people who left the company long ago. Individually, these errors feel like minor housekeeping issues. Collectively, they drive poor purchasing decisions, excess inventory, unnecessary shortages, and a slow erosion of trust in the systems your team is supposed to rely on.

Procurement data cleansing is the process of systematically finding and fixing those errors before they compound further. LeanDNA has worked with manufacturers across industries and, through that work, identified 13 common data points where problems tend to cluster. This guide walks through each one, explains what to look for, and offers a framework for keeping data clean over time.

What Is Procurement Data Cleansing?

Procurement data cleansing is the process of auditing and correcting the master data and transactional records that drive purchasing, planning, and inventory management decisions. In practice, this means reviewing fields in your ERP system that directly influence what gets ordered, when, and in what quantity.

The scope typically covers order policies, demand signals, supplier parameters, cost data, and the accuracy of on-hand inventory counts. When any of these are wrong or out of date, the downstream effects ripple through procurement planning, supplier relationships, and production schedules.

For manufacturers managing thousands of SKUs across multiple sites, the cost of data silos is significant. Bad data doesn't just produce bad outputs; it undermines confidence in the entire system, leading teams to work around their ERP rather than with it. That's when you know a cleansing effort is overdue.

Procurement data cleansing is distinct from a one-time audit. Done well, it establishes a repeatable process for maintaining data accuracy over time, not just a snapshot fix.

How to Start the Procurement Data Cleansing Process

Working through your data in segments makes the problem manageable. Below are the 13 data points LeanDNA consistently identifies as high-risk areas for errors. For each one, you'll find a definition, an explanation of why it matters for procurement, and the most common failure patterns to watch for.

1. Supplier Lead Time

What it is: The number of days between initiating a procurement action (such as firming a purchase order) and receiving the inventory.

Lead times are foundational to ordering and procurement policies. When they're inaccurate, everything built on top of them is off too: safety stock calculations, reorder points, order intervals, and delivery expectations all depend on this number being current.

The most common failure modes are data that has simply gone stale, and a gap between what suppliers promise and what they actually deliver. Using your own historical receipt data to set lead times is more reliable than relying solely on supplier-provided dates. If your system can automate this calculation on a rolling basis, use that capability.

2. Past-Due Demand Requirements

What it is: Open demand that has passed its due date and has not yet been fulfilled.

Production schedules slip. That's a normal part of manufacturing. The problem is when unfulfilled demand stays open in the system with old due dates still attached. Those stale records can trigger unnecessary purchase orders to cover demand that has already been addressed or rescheduled through other means.

Past-due requirements typically stem from SIOP process gaps, particularly when work orders and sales orders are not updated simultaneously. The volume of impact here can be significant. LeanDNA has helped clients uncover millions of dollars in past-due requirements that had accumulated invisibly over time, giving them the visibility to address root causes quickly.

3. Missing or Inaccurate Demand

What it is: Demand data, typically calculated by MRP, that is either absent from the system or reflects outdated assumptions.

Demand is the starting point for procurement. If it's wrong or missing, every downstream calculation inherits the error: purchase orders, replenishment levels, reorder points, safety stock sizing. The result is procurement that consistently undershoots or overshoots actual needs.

Two root causes account for most cases: bills of materials (BOMs) that haven't been kept current, and forecasts that were never loaded into the system in the first place. Both are worth auditing as part of any data cleansing effort.

4. Reorder Point (ROP)

What it is: The inventory level at which a replenishment action is triggered for a given item.

ROP needs to reflect current demand patterns and lead time variability. When it doesn't, you're either reordering too early (building excess inventory) or too late (risking shortages). The calculation should account for standard deviations in both lead time and demand, not just average values.

Manual updates to ROP are difficult to sustain at scale. Tools like LeanDNA can auto-generate these calculations daily, which is the only realistic way to keep them accurate across a large SKU base.

5. Min/Max Levels

What it is: A replenishment control method that sets a minimum stock level (trigger point) and a maximum level (replenishment ceiling).

Min/Max is a straightforward policy on paper, but maintaining it accurately is harder than it looks. These values depend on demand, lead times, and variability, all of which change over time. Without a regular process to update them, Min/Max levels drift out of alignment with actual operating conditions and start generating orders that either build up stock unnecessarily or leave the system chronically short.

The fix is establishing a recurrence for reviewing and resizing these levels, rather than treating them as a set-it-and-forget-it parameter.

6. Order Interval

What it is: The fixed time period covered by a single order. A longer interval means larger but less frequent orders; a shorter interval means smaller but more frequent ones.

Order intervals are one of the most widely used order policies, so errors here affect a significant portion of your inventory. The most common problem is that intervals are set based on manufacturing practices or demand profiles that have since changed. When an item's ABC classification shifts due to demand changes, the order interval should shift with it, but often it doesn't.

Review order intervals as part of your regular order policy maintenance cycle rather than waiting for a shortage or excess situation to surface the problem.

7. Kanban Bin Sizing

What it is: The fixed quantity of inventory maintained at a workstation or location that is replenished when consumed.

Improperly sized Kanban bins cause two categories of problems: excess inventory when bins are too large, and production disruptions when they're too small. The latter is especially damaging at bottleneck stations where a material shortage can halt an entire line.

Bin sizes require revisiting when demand shifts, when items become obsolete, or when order policies change upstream. A Kanban system that was sized accurately two years ago may not reflect current production realities.

8. Minimum Order Quantity (MOQ)

What it is: The smallest quantity a supplier will sell per order for a given item.

MOQ is used as an input to multiple procurement calculations, so outdated values produce cascading errors. If your system is calculating order quantities based on MOQs that no longer reflect what your suppliers actually require, you're either ordering too little (creating compliance issues or forcing expedites) or building in unnecessary excess.

Like lead times, MOQs require regular updates from your suppliers. Building a recurring check into your supplier review process is the most reliable way to keep this data current.

9. Standard Cost

What it is: The expected per-unit cost for a purchased item, typically set by the finance team and used as the baseline for purchase price variance (PPV) reporting.

PPV compares actual spending against forecasted spend across your parts. When standard costs are stale, PPV figures become misleading. Large variances in either direction are a signal that the underlying standard costs need revisiting.

LeanDNA flags items where PPV patterns suggest standard costs may be wrong, which gives your team a targeted list rather than requiring a full manual review.

10. Safety Stock

What it is: Extra inventory held beyond expected demand to buffer against variability in supply and demand.

Safety stock needs to be sized to the actual volatility of the items it covers. Too much, and you're carrying unnecessary holding costs. Too little, and a demand spike or supplier delay leads to a stockout. The right level requires calculating standard deviations across both lead time and demand, not just setting a flat buffer based on intuition.

This is another field that deteriorates quickly without regular attention. As demand patterns evolve or supplier reliability changes, safety stock levels need to follow. Building this into a monthly or quarterly review cadence is the most practical approach.

11. Purchase Order Dates

What it is: The suite of key dates tied to a PO: the Order Date (when placed), the Requested Date (when you need it), and the Promise Date or Supplier Commit Date (when the supplier says it will arrive).

Inaccurate PO dates create misalignment between what the system shows and when materials will actually be available for production. This has direct consequences for scheduling, and it also undermines supplier performance tracking if the data being evaluated doesn't reflect reality.

Date errors typically originate when schedules shift and no one updates the corresponding PO records. This is fundamentally a process problem as much as a data problem. The root cause fix usually involves tightening SIOP workflows so that PO dates get updated as part of standard schedule revision activities.

12. Inventory Accuracy

What it is: The degree to which the inventory quantities recorded in your ERP match what is physically on hand.

If your on-hand counts can't be trusted, the entire system becomes suspect. Buyers and planners will start making decisions based on physical observation rather than system data, which defeats the purpose of having an ERP in the first place. Inventory accuracy is the foundation that everything else rests on.

Accuracy tends to slip when operators are under pressure to move fast and skip the process steps for recording usage. Cycle counting programs and user accountability measures address the symptom, but the underlying cause is usually a combination of process complexity and time pressure. Simplifying the recording steps and building compliance into daily routines helps more than audits alone.

13. Buyer Alias

What it is: The name or identifier that links specific item codes to the buyer or planner responsible for managing their inventory.

As supply chain analytics tools become more capable of prescribing specific actions to individual team members, getting buyer assignments right has become increasingly important. Items assigned to the wrong person, to someone who has left the company, or to no one at all will either be ignored or create confusion about who is accountable for them.

People and parts both turn over regularly. A review of buyer alias data should be part of onboarding and offboarding processes, not something that gets addressed only when a problem surfaces.

Maintaining Data Quality After Cleansing

Cleansing your data is the starting point. Keeping it clean is the ongoing work.

LeanDNA's data cleansing process helps surface where problems exist and gives teams a clear starting point for remediation. But regardless of the tools you're using, every data point covered above needs a defined review cadence. A simple maintenance framework looks like this:

Daily: PO management and date updates

Weekly: Demand plan updates, PO date reconciliation

Monthly: Item order policy review, cycle counting, safety stock sizing, Min/Max resizing

Quarterly: B-item order policy and cycle counting, BOM maintenance

One important thing to understand: an ERP system on its own is not built to maintain this level of data health automatically. ERP solutions provide the data infrastructure, but they lack the prioritization and analytics layer needed to flag what's wrong, surface it to the right people, and track whether it gets fixed. That's the gap that a dedicated analytics and optimization platform fills.

For teams looking to build sustainable data practices, ERP data cleansing best practices offer a useful framework for structuring ongoing governance beyond the initial cleanup effort.

Ready to Get Your Data in Order?

The 13 data points above represent the most common places where procurement data goes wrong. Working through them systematically, rather than trying to fix everything at once, is the most effective approach. Start with the areas most directly tied to your current pain points, whether that's shortages, excess inventory, or supplier reliability issues, and build from there.

LeanDNA helps manufacturers achieve reliable inventory data by flagging errors, automating calculations that would otherwise require constant manual upkeep, and giving teams the visibility to act on what matters most.

Contact LeanDNA to learn how our data cleansing process can help your organization build a stronger foundation for supply chain performance.