Perspective
Plan Around the Parts You Cannot Replace, and the Rest of the Bill Follows
An ERP plan treats a single-source part as one line among thousands. We record which parts cannot be replaced, so the plan is built around them.
4-minute read5 November 2026
In Brief
- A low-cost part with no qualified alternative can halt a whole product, yet cover is usually set by value. The thinnest cover can sit on the part with the largest consequence.
- We see four actions: classify parts by replaceability, link each part to the products and orders that depend on it, plan cover against time to resolve, and record notices as events.
- Thinqmesh sets up stock and purchasing the way you operate, finds where stock moves without a record, and brings a first module live on your own system in four weeks.
A bill of materials for an electronic product can run to hundreds of lines, and an ERP treats them much alike: a part number, a lead time, a safety stock, a reorder rule. Those lines differ in a way the plan rarely records. A resistor can usually be bought from several makers. A particular microcontroller may be designed into the firmware, certified with the product and available from one source. Our view is that parts of the second kind should be planned as constraints, with the rest of the plan built around them.
The Cheapest Part Can Carry the Largest Consequence
Safety stock is commonly tied to annual spend, so planners watch the expensive items and put the cheap ones on simple rules. A low-cost part with no qualified alternative can then hold the thinnest cover of all. When it runs short, a whole product waits, and the cost is a delayed shipment and a customer commitment missed.
The quoted lead time in the item record compounds this. The plan trusts a static number, and the number stops describing reality exactly when supply tightens. Where alternates live only in an engineer's notes, planners cannot use them. The remedy is mostly master data: each part classified by replaceability, linked to what depends on it, and covered according to how long a resolution would take.
Four Actions That Make a Single Source Visible to the Plan
Most of this is disciplined master data, and it can begin in your current system.
Classify Every Active Part by Replaceability
Drop-in alternate, alternate that needs qualifying, or redesign: three answers that change the plan.
We add a field to the item record that engineering and purchasing both maintain. For the last two groups it holds an estimate of the weeks needed to resolve a shortage, agreed with engineering. The plan can then tell a part with three qualified makers from one with a single source.
Get started
- Print the bill of materials of your highest-margin product.
- Mark each line as replaceable now, after qualification, or only by redesign.
Link Each Part to the Products and Orders That Depend on It
A shortage can be costed in minutes when the where-used view shows revenue and commitments.
We set up the where-used view so that a constrained part shows the products, the customer orders and the delivery dates it supports. A buyer then sees what a shortfall would cost before it happens, and finance sees a named part and a sum of money.
Get started
- Pick the ten parts with the longest time to resolve.
- Write the revenue each one puts at risk.
Plan Cover Against Time to Resolve
A part needing months of qualification deserves a different buffer from one with a drop-in alternate.
We configure cover by the weeks needed to resolve a shortage and by the value at risk, and not by purchase value alone. Cover on parts that can be replaced quickly can fall, which releases cash to hold against the few that cannot.
Get started
- Compare current cover with weeks to resolve for your ten longest parts.
- Agree with finance which ones to cover, requalify or redesign.
Treat Manufacturer Notices as Events With an Owner
An end-of-life or change notice opens a decision, with a date, and does not sit in one inbox.
We record each notice in the system against the part, name an owner, and set a date for the decision between a last-time buy, a second source and a redesign. Engineering change control shows a new part's source position before it is approved, when avoiding a single source costs least.
Get started
- Collect the notices received in the past year and note what happened to each.
- Name who owns the decision on the next one.
How Thinqmesh Solves This
We begin on your floor and in your stock report, and the first module runs beside the systems you already use, so you can judge it on real work.
- Week 1
Your Real Data, in a Working System
We stand up the platform with data representative of your business, and look for the places where stock and cost move without a record.
- Week 2
Your Rules, With a Named Owner for Each
Purchasing, approvals, access and costing are configured the way you operate, and each constraint has an owner who maintains it.
- Week 3
Your Records, Moved Across and Checked
We connect the systems you rely on and migrate your records. If your current system cannot export, we tell you first and give extraction its own date.
- Week 4
Real Work Running on It
Stock accuracy or job costing goes live on your own system. Further modules are agreed one at a time, in writing, on the foundation now in place.
You finish with one job running on your own system, parts classified by replaceability, and a clear view of what comes next. The code and the data are yours.
