What Is a Procured Item in Manufacturing?

A procured item is a product your plant buys rather than makes, flagged as such on its master record so planners treat it as a purchased input to other products' routings instead of a job of its own. The distinction matters because a manufacturing system holds one catalog for everything it knows about: finished goods you sell, sub-assemblies you build, and raw materials you order in. Marking an item procured is how you say "this one arrives on a truck." In EDGEBIC by User Solutions the flag sits on the product form and shows as a column in the product list, so nobody spends an afternoon looking for a routing that was never meant to exist.

How it works

A product record is the master entry for anything the system needs to name: an end item, a sub-assembly, a component, a consumable. What a product record does not carry is a rigid type. There is no raw material versus work-in-process versus finished good switch on the form. A product's role emerges from how it is used, and three signals tell you which role a given record is playing.

Those signals overlap on purpose. A bought casting is usually both procured and referenced as a material, and its category is usually something like Raw Materials. A sub-assembly you make in house is neither procured nor without a routing, yet it is still referenced as a component inside the end item's routing. The catalog stays flat and the meaning comes from context.

The practical consequence of the procured flag is what it removes. A purchased part has no operations, so it needs no routing, so the scheduler never books an hour against it. Its row in the product list shows the circle marker and the text No BOR, and that is the correct resting state rather than a data-quality problem. See what are bill of routing status buckets for how to read that column, because it distinguishes a healthy No BOR from the genuinely broken condition of one product resolving to several routings.

Where a procured item does carry weight is cost. Its per-unit cost is the number that prices it when it appears as a material input, and keeping that number current is the difference between an honest estimate and a flattering one. The identifier planners read on every grid and routing is the product id, defined in what is a product id.

A concrete example

Take the sample plant's catalog as it is built up. Widget-A is a finished good: sale price 120.00, rollup cost 48.50, a two-day delivery-ready tail, category Finished Goods. Frame-S is a sub-assembly with its own routing but no sale price, because it is never sold on its own. Bracket-B is another finished good at sale price 14.00 and rollup cost 10.00.

Then comes Steel-Plate-4mm: unit of measure Each, rollup cost 6.20, category Raw Materials. No routing will ever be created for it, because there is nothing to schedule. It will appear inside routings as a material, and the procured flag on its row is what tells the next planner that the missing routing is deliberate.

Follow the money through one quote and the role becomes obvious. Quoting 200 units of a product whose routing has no explicit material step falls back to the end product's own unit cost times the quantity: 6.50 multiplied by 200 gives 1,300 of material cost sitting alongside the labor. Model the plate as an actual material step in the routing instead, and the estimate prices the plate you really buy rather than a single blended number on the end item. That is exactly why material steps are the preferred way to express purchased content in a multi-component product.

How EDGEBIC uses it

The product list carries a Procured column right beside unit of measure, lead time, sale price and cost, and the grid is grouped by category by default. Between the category bands and that one column, a planner can see at a glance which half of the catalog is bought and which half is built. The routing status column then confirms the pattern: bought items read No BOR, built items read Active BOR.

Procured items load through the same bulk path as everything else in the catalog. The product import mask maps your file's columns onto the product fields once, and every later run is two clicks, which is how a shop keeps a few hundred purchased-part costs current without opening a few hundred dialogs. Matching is by product id and is not case sensitive, so a file row spelled in capitals still finds the existing record.

Three habits keep the flag useful:

• Keep the cost current on anything that reaches a quote. A material fallback priced from a stale unit cost produces a margin that looks better than the job will be. The related roll-up mechanics are covered in what is a cost rollup in manufacturing.
• Give purchased items a category from day one. Raw Materials as a band in the grid does more for navigation than any amount of naming convention.
• Do not build a routing to make a bought part look complete. An invented operation consumes real capacity in every schedule and every quote that touches it.

One thing the flag deliberately does not do is plan the purchase. It records that the item is bought; it does not reserve, order, or promise supply. Treat it as catalog hygiene that keeps the scheduling side honest, not as a procurement module.

The takeaway

A procured item is the simplest and most useful distinction in a product catalog: bought, not made, therefore no routing, therefore no capacity. Set the flag, give the item a category and a current unit cost, and the rest of the system behaves correctly without further intervention. To see the catalog and its routing status column in a working plan, explore EDGEBIC, and if you are coming from the older Resource Manager lineage, the move from RMDB to EDGEBIC maps the equivalents. For the neighboring vocabulary, read what is a unit of measure in manufacturing and what is a bill of routing.