Key Takeaways
- Multi-site inventory usually breaks at specification first. When each site buys its own version of “the same” coverall, stock cannot be pooled, compared or moved, and every downstream tracking effort inherits that inconsistency.
- Inconsistent item data is a measured problem, not a theory. In a CDC-supported pilot across 78 US hospitals, only 74.2% of the 159 PPE model numbers reported could be verified, and the authors called for PPE data standards to improve communication across hospital systems.
- Diagnose before you buy software. Separate the three failure modes (specification, visibility, distribution), because each has a different fix and software alone addresses only one of them well.
- Days of supply is the common language. The CDC PPE Burn Rate Calculator estimates how long remaining stock will last from average consumption, and the same logic works for comparing sites of very different sizes.
- Rebalance before you reorder. A written threshold that triggers transfer between sites prevents the familiar pattern of one site over-holding while another runs short of the same item.
Managing disposable PPE inventory across multiple facility sites works when three things are true: every site buys the same written specification, every site can see stock levels across the network in days of supply, and there is an agreed rule for moving stock between sites before anyone places an emergency order. Most networks that struggle have a tracking problem on the surface and a specification problem underneath it. A hospital group, a multi-plant pharmaceutical company or a food business with several processing units can be overstocked and short at the same moment, simply at different addresses.
The usual first response is to look for inventory software. Software helps, but it cannot reconcile two sites that call different garments by the same name. If Site A stocks a 45 GSM SMS coverall with elasticated hood and Site B stocks a 40 GSM SBPP coverall without one, a dashboard that shows “coveralls: 4,000” is adding together things that cannot replace each other on the gowning bench. This guide sets out a diagnostic first, then a practical fix for each failure mode, scaled to the size of the network.
Dispowear Protection manufactures over 3 million disposable garments a month from its own GenFab® nonwoven fabric, across two plants in Rajasthan and Gujarat, and supplies multi-site hospital groups, pharmaceutical manufacturers, industrial users and distributors serving customers across India and international markets. Multi-site consistency is a problem visible from the supply side as clearly as from the buyer’s side.
Single-site inventory usually fails because of poor tracking. Multi-site inventory tends to fail earlier, at specification, and poor visibility then compounds it. The difference matters because the two problems need different fixes.
The pattern is predictable. Each site was set up at a different time, often with its own procurement contact and its own supplier relationships. Over the years each site specifies its disposable protective clothing slightly differently: a different fabric, a different GSM, a different sizing chart, a different hood or cuff detail, a different pack size. Every one of those decisions was reasonable locally. Together they produce a network that holds several distinct products under one name.
The consequences surface in three places. Stock cannot be pooled, because a garment from one site may not be acceptable in another site’s validated gowning procedure. Bulk-order economics weaken, because the network buys several smaller volumes instead of one consolidated volume. And reporting becomes unreliable, because the item master holds several codes, descriptions and units of measure for what managers think of as one item.
That last point is well documented. In a CDC-supported proof-of-concept that collected near-daily PPE inventory from 78 hospitals, reporting 159 different model numbers across just three PPE types, researchers could verify 74.2% of the model numbers overall, and only 40.0% for face shields. The study concluded that PPE data standards would enable better communication across hospital systems. The same issue appears inside a single organisation the moment it operates more than one site: if the item is not described consistently, it cannot be counted consistently.
Before choosing a fix, identify which failure mode, or which combination, your network actually has. Most content on multi-site inventory treats these as one problem. They are not.
That last point is well documented. In a CDC-supported proof-of-concept that collected near-daily PPE inventory from 78 hospitals, reporting 159 different model numbers across just three PPE types, researchers could verify 74.2% of the model numbers overall, and only 40.0% for face shields. The study concluded that PPE data standards would enable better communication across hospital systems. The same issue appears inside a single organisation the moment it operates more than one site: if the item is not described consistently, it cannot be counted consistently.
A dashboard cannot reconcile products that were never the same. Fix the specification first, then visibility, then distribution.
Specification failure. Sites are buying inconsistent products. The tell-tale signs are multiple item codes for one garment type, staff at one site refusing stock transferred from another, and sizing complaints that appear only when stock moves between sites.
Visibility failure. The products may be consistent, but nobody has a shared, current view of what each site holds. Central procurement learns about a shortage when a site calls, not when its cover falls below a threshold. Reports exist, but in different units: boxes at one site, cartons at another, pieces at a third.
Distribution failure. The stock exists and is visible, but it does not move. One site holds three months of cover while another places an urgent order, because there is no agreed rule, budget code or transport arrangement for transferring stock internally.
| Failure mode | Typical symptoms | Root cause | First fix | Does software solve it? |
|---|---|---|---|---|
| Specification | Several codes for one garment; transferred stock rejected; uneven sizing across sites | Each site specifies and sources independently | One written network specification for each item, with a single approved product per line | No. It can record the decision, not make it |
| Visibility | Shortages discovered by phone; reports in mixed units; no network-wide days-of-supply figure | No common reporting unit, frequency or owner | A shared weekly report of each site’s cover in days, in one unit of measure | Largely yes, once specification is consistent |
| Distribution | Emergency orders while surplus sits elsewhere; expiry write-offs at one site, stockouts at another | No transfer rule, authority or logistics | A threshold that triggers internal transfer before any new order | Partly. It can flag the trigger; people must act on it |
Diagnostic framework drawn from manufacturing and order-stage experience and indicative rather than measured. Item data inconsistency evidence from Haas et al., Health Security, 2021 (CDC Stacks).
The fastest fix for specification failure is a single written specification for each item, applied across the network and not left to site discretion. It sounds obvious. In practice it requires a short project with a clear owner.
Supply structure matters here. When one manufacturer supplies the network to an approved written specification, the risk of sites drifting onto different products can be reduced. Dispowear Protection manufactures its own GenFab® virgin SBPP nonwoven fabric and offers customisation options such as GSM variations, lamination, anti-static treatment and colours. These capabilities can support specification consistency across repeat orders, provided the approved product details are documented and checked. Colour coding can also help make garments recognisable across sites when the same colour system is applied consistently.
Visibility means anyone responsible for supply can see, within an hour, how many days of cover each site holds for each critical item. It does not have to mean enterprise software on day one.
The most useful single number is days of supply: current stock divided by average daily consumption. It lets a 600-bed hospital and a 60-bed clinic, or a large formulation plant and a small packaging unit, be compared on one screen. The CDC PPE Burn Rate Calculator uses exactly this logic, calculating an average consumption rate and estimating how long remaining supply will last, and it was built to help both healthcare and non-healthcare systems plan and track PPE inventory. For the consumption side of the calculation, see forecasting consumption before you standardise stock.
Scale the tooling to the network.
Whatever the tool, fix three things: the reporting unit (pieces, not boxes or cartons, because pack sizes differ), the reporting frequency, and the owner at each site. A report nobody owns decays within a quarter.
Distribution failure is the most frustrating of the three, because the stock already exists. The fix is a minimum-viable rebalancing rule, written down and agreed in advance.
Rebalancing only works if the item is the same at both ends. This is where the specification work pays off: a transferred garment that matches the receiving site’s approved item can go straight into use.
For the order-stage checks that sit alongside this, see our PPE procurement checklist for bulk buyers, and for how inventory fits into the full process from forecast to inspection, see the full procurement playbook.
These are the fields worth fixing once at network level, so that every site receives the same garment.
| Parameter | Typical specification |
|---|---|
| Fabric | GenFab® virgin-polypropylene SBPP nonwoven, manufactured in-house; SMS and laminated constructions available |
| GSM | Selected according to application requirements and fixed on the order datasheet for the whole network |
| Garment range | Coveralls, isolation gowns, lab coats, aprons, sleeve protectors, hoods, caps, beard covers, shoe and boot covers |
| Sizes | Full size range; sizing chart fixed to the network specification so transferred stock fits the same way |
| Barrier performance | Selected according to application requirements; confirmed through technical documentation where applicable |
| Treatments | Lamination and anti-static treatment selected according to application requirements |
| Colour | White, blue, green and custom shades for consistent colour coding across sites |
| Packaging and labelling | Consistent pack size and unit of measure across deliveries; custom labelling and private label available |
| Documentation | COA, GSM data, fabric test reports and lot traceability with each batch |
Figures are indicative and confirmed on the product datasheet for each order.
Start with a single written specification for each item used across all sites, then build a shared view of each site’s stock in days of supply, then agree a rule for transferring stock between sites before placing new orders. Doing these in that order matters, because visibility and transfers depend on the items being genuinely the same at every site.
Usually because each site was set up separately and specified its disposable protective clothing independently, so small differences in fabric, GSM, sizing or packaging accumulate. Standardisation also fails when there is no owner for the network specification, or when a supplier changes a product without notice and only some sites notice the difference.
Set a lower days-of-supply trigger that requires central procurement to check other sites before raising a purchase order, and an upper trigger that offers surplus to the network. Agree in advance who authorises transfers, which budget absorbs them and how stock physically moves, and keep lot numbers with transferred stock for traceability.
For the same specified item, a single source can reduce the risk of sites drifting onto different products and can consolidate volume. It also concentrates exposure, so it works best with a manufacturer producing across more than one plant, documented buffer stock and a continuity plan. For high-criticality items a qualified second source may still be worth its cost.
Not always. Networks of a few sites can often manage with a shared, disciplined spreadsheet that reports days of supply in one unit of measure. Larger networks usually benefit from an ERP module or dedicated system. In every case software works best after the item master is clean, because it cannot reconcile products that were never the same.
The bottom line. A multi-site network that is overstocked and short at the same time rarely has a software problem first. It has a specification problem, which then makes visibility unreliable and transfers impractical. Fix the three layers in order: one written specification and one item code per item across every site, a shared days-of-supply view with a named owner at each site, and a written rule for rebalancing stock before reordering. Then lock the specification with your supplier, so the consistency you built survives the next delivery.
Running disposable protective clothing across several hospitals, plants or warehouses? Request a bulk quotation, technical specification sheet or product samples for consistent supply across your network.