# Inventory Hold Codes > Site directory and reading guidance: [llms.txt](https://wiki.skusavvy.com/llms.txt). Canonical URL: https://wiki.skusavvy.com/article/inventory-hold-codes Published: 2026-11-03T20:08:03.334Z Last updated: 2026-11-03T20:30:37.240Z Category: Warehousing > This article is AI-assisted reference material. Verify important or time-sensitive claims against the cited sources; AI review does not establish independent factual verification. ## Overview An **inventory hold code** is a label or system value that identifies why inventory is restricted from one or more activities, such as allocation, picking, sale, shipment, or use in production. Hold codes help organizations distinguish stock that is physically present from stock that is operationally available. The exact codes and their effects depend on the organization and its software configuration; there is no single universal vocabulary. A hold may apply to an item, lot, serial number, pallet, location, or specified quantity. It can support inspection, investigation, recalls, regulatory compliance, and other controls. For example, [inventory statuses in Microsoft Dynamics 365](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-statuses) can be configured to block inventory from outbound use, while [lot and expiration tracking](https://www.skusavvy.com/docs/guides/lots-and-expiration-dates) provides identifying information useful when restricting affected stock. A hold code is not necessarily the same as a physical quarantine location: a restriction may be recorded electronically, enforced by physical separation, or both. In pharmaceutical manufacturing, [ICH Q7 defines quarantine](https://www.fda.gov/regulatory-information/search-fda-guidance-documents/q7-good-manufacturing-practice-guidance-active-pharmaceutical-ingredients) as isolation by physical or other effective means pending a decision on approval or rejection. A hold also does not automatically mean that the inventory is defective or should be written off. ## Etymology and Origins In this context, **hold** means to retain goods from normal use or movement; **code** is the abbreviated value used to record the reason or associated restriction. Related terms include *blocked stock*, *quarantine status*, *quality hold*, and *inventory status*. Their precise meanings vary between organizations and applications. The first documented use of the exact phrase *inventory hold code* is not established here. The underlying practice is closely related to quality-control segregation. US drug regulations distinguish [quarantined drug products from approved, rejected, and returned products](https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-H/section-211.142). Modern software expresses similar operational distinctions through configurable [inventory status values](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-statuses). The evidence establishes a relationship between the practices, not that the regulatory terminology directly gave rise to the phrase. ## Historical Development The specific date and inventor of inventory hold codes have not been established. The progression from physical controls to electronic status records is best understood as a development in inventory and quality control rather than the invention of a single standardized code system. - **1974:** The first retail product carrying a Universal Product Code was scanned on 26 June 1974. [Barcode standardization](https://www.gs1.org/standards/barcodes/history) later made machine-readable identification increasingly practical, although a barcode alone does not impose a hold. - **1978:** The US Food and Drug Administration published revised current good manufacturing practice regulations for finished pharmaceuticals, now in [21 CFR Parts 210 and 211](https://www.fda.gov/drugs/pharmaceutical-quality-resources/current-good-manufacturing-practice-cgmp-regulations). Those rules include [quarantine and separation requirements](https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-H/section-211.142). Earlier drug CGMP rules existed; the 1978 revision did not invent segregation, and it does not prescribe a universal hold-code vocabulary. - **Computerized controls:** Warehouse and enterprise systems represent restrictions as electronic statuses or reason codes. Configurable [inventory statuses](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-statuses) can support transaction-level controls, while [barcode workflows](https://www.skusavvy.com/docs/guides/barcodes) help operators identify stock during warehouse tasks. Contemporary implementations may integrate warehouse, quality, order, and planning systems, but an electronic status does not by itself guarantee that every connected system respects it. ## Core Concepts A hold normally combines an **identity**, a **reason**, and an **operational restriction**: 1. **Identity and scope:** Identify the affected item and, where applicable, its lot, serial numbers, location, handling units, and quantity. [Lot and expiration records](https://www.skusavvy.com/docs/guides/lots-and-expiration-dates) can help narrow the scope. 2. **Reason:** Record why the restriction exists, such as pending inspection or suspected damage. A reason code explains the decision; it may be separate from the status that enforces it. 3. **Controls:** Define which actions are blocked, allowed, or require approval. For instance, a system may prevent outbound allocation but permit a controlled transfer to quarantine. Actual behavior depends on configuration; [inventory status controls](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-statuses) illustrate one system's approach. 4. **Disposition and release:** An authorized person reviews evidence and records a decision to release, rework, return, destroy, or continue holding the stock. The decision and its execution should be auditable. For US finished drug products, applicable rules require, among other things, [laboratory determination of satisfactory conformance before release](https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-I/section-211.165). That is a product-specific requirement, not a universal rule for all inventory. For example, if 100 units are on hand, 20 are held, and 30 of the remaining units are already committed, a simplified available quantity is **50 units**. Actual availability calculations vary by system: reservations, safety stock, overlapping restrictions, and channel-specific rules must be defined to avoid double-counting. Multiple reasons can apply to the same goods. If a quality issue and a recall both affect one lot, resolving only the quality issue should not make the lot available while the recall restriction remains active. ## Common Types and Applications | Illustrative code | Typical purpose | Possible next step | |---|---|---| | `QC_PENDING` | Awaiting inspection or test results | Release after approval or move to investigation | | `DAMAGE` | Suspected physical damage | Inspect, rework, return, or dispose | | `RECALL` | Stock potentially affected by a recall | Identify the affected scope and follow the recall procedure | | `EXPIRED` | Product has passed its permitted use or sale date | Review disposition under applicable rules | | `COUNT_REVIEW` | Quantity or identity discrepancy | Investigate and reconcile records | | `CUSTOMER_HOLD` | Contractual or customer-directed restriction | Release only on documented authorization | These labels are examples, not an industry-wide standard. A business may use one status with several reason codes or separate statuses for distinct restrictions. [Cycle counting](https://www.skusavvy.com/docs/guides/warehouse/cycle-counting) can identify discrepancies that warrant investigation, while [lot and expiration tracking](https://www.skusavvy.com/docs/guides/lots-and-expiration-dates) helps identify stock for date- or lot-based controls. In food, pharmaceutical, and other regulated supply chains, the applicable restriction and disposition depend on the product and jurisdiction. Organizations should map their internal codes to the controls required by their own quality and compliance procedures rather than assume that a code name alone establishes compliance. For example, US drug rules require certain unexplained discrepancies and failures of a batch or any of its components to meet specifications to be [thoroughly investigated and documented](https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-J/section-211.192). ### Illustrative example: suspected lot defect A warehouse receives a report of a possible defect in lot A. In this hypothetical workflow, it identifies the lot's on-hand units, applies a quality hold to the affected quantity, checks whether any units have already been picked or shipped, and directs staff to segregate remaining stock. A quality reviewer records the investigation and decides which units can be released or require another disposition. If a separate recall hold also applies, the warehouse keeps those units restricted until that hold is resolved. The example illustrates a control design, not a claim about a particular company or software product; [lot identification](https://www.skusavvy.com/docs/guides/lots-and-expiration-dates) and [status configuration](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-statuses) are relevant to implementing it. ## Implementation and Best Practices - **Define a controlled code set.** Give each code an owner, definition, permitted transactions, evidence requirements, and release authority. Avoid overlapping codes whose differences are unclear. - **Capture the right scope.** Record product, quantity, unit of measure, location, lot or serial identifiers, timestamps, reason, and initiating user as appropriate. Verify that a partial-lot hold does not accidentally block—or leave available—the wrong quantity. - **Combine system and physical controls.** Use labels or segregated space where warranted, and test whether scanning, transfers, and picking respect the restriction. [Warehouse barcode practices](https://www.skusavvy.com/docs/guides/barcodes) and [bin-to-bin transfers](https://www.skusavvy.com/docs/guides/warehouse/bin-to-bin-inventory-transfer) are relevant operational processes; their presence alone does not establish hold enforcement. Regulated operations may also need isolation that meets the applicable definition of quarantine, such as the [physical or other effective means described in ICH Q7](https://www.fda.gov/regulatory-information/search-fda-guidance-documents/q7-good-manufacturing-practice-guidance-active-pharmaceutical-ingredients). - **Protect release decisions.** Separate initiation and approval where risk warrants it, require supporting evidence, and retain a history of changes and overrides. Where applicable, align investigation records with requirements such as [21 CFR 211.192](https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-J/section-211.192). - **Test integrations.** Confirm how held quantities flow to the warehouse management system, enterprise resource planning system, order channels, and planning tools. [Inventory synchronization](https://www.skusavvy.com/docs/guides/shopify/inventory-sync) is an example of an integration area to review; the treatment of held stock must be verified for the specific configuration. Test existing reservations, picks already in progress, transfers, returns, overrides, and hold release—not just new orders. - **Monitor aging.** Review held quantity, value, reason, age, and owner regularly. Escalate overdue investigations and reconcile physical stock with system records. Useful measures include the number of holds past their review date and the time from initiation to disposition; define their start and end events consistently. ## Challenges and Limitations Poorly configured holds can create either safety risks or unnecessary shortages. A broad item-level block may stop unaffected lots, while an overly narrow lot or location restriction can leave affected units available elsewhere. Physical moves, relabeling, returns, and inventory adjustments should therefore be checked for their effect on the hold. A second challenge is inconsistent availability across systems. An order channel may show a quantity as sellable before a restriction is received or processed. Integration testing and reconciliation are essential; consult the relevant [inventory-sync documentation](https://www.skusavvy.com/docs/guides/shopify/inventory-sync) and confirm actual behavior with the systems in use. Likewise, a blocked [inventory status](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-statuses) must be tested against the specific transactions and exceptions the operation permits. Finally, a hold is an operational control, not automatically an accounting adjustment. Finance teams must separately determine whether a write-down or other treatment is appropriate under the applicable accounting framework. For example, [IAS 2 generally measures inventories at the lower of cost and net realisable value](https://www.ifrs.org/issued-standards/list-of-standards/ias-2-inventories/); the existence of a hold alone does not determine that measurement. ## Source links - [Inventory Statuses]() - [Lots and Expiration Dates]() - [21 CFR 211.142: Warehousing Procedures]() - [History of the Barcode]() - [Barcodes Guide]() - [Cycle Counting Guide]() - [Bin-to-Bin Inventory Transfer Guide]() - [Shopify Inventory Sync Guide]() - [21 CFR 211.165: Testing and Release for Distribution]() - [21 CFR 211.192: Production Record Review]() - [IAS 2 Inventories]() - [Current Good Manufacturing Practice (CGMP) Regulations]() - [Q7 Good Manufacturing Practice Guidance for Active Pharmaceutical Ingredients]()