Release Only the Received Lots Covered by a Decision

“Release eight” is an incomplete receiving instruction if nobody can identify which eight units it means. A partial release needs a defined population, a decision covering that population and a record that the next person can apply. The remainder must retain its own status rather than inheriting the most recent approval on the order.

Build a lot-status map before changing the administrative release state. Its purpose is to answer whether the approved portion can be distinguished from held or unchecked goods. It does not choose an inspection sample, set acceptance thresholds or authorize shipment and installation.

Begin with the received population

Use the existing receipt record to identify the order line, part or model, supplier lot where available, received quantity and unit of measure. Preserve the evidence behind that quantity. A register showing twelve pieces should not originate solely from a supplier’s statement that one sealed pack contains twelve.

Record the level at which the goods are distinguishable. Some receipts have individual serial numbers. Others have supplier lot and package identifiers. A receiver-assigned tracking ID can help locate a subset, but label it as such; it is not a newly discovered manufacturer lot or proof of origin.

Keep the original population stable. If a later parcel arrives against the same purchase order, give it its own receipt connection. An approval of the first arrival should not silently extend to the later units merely because the SKU is unchanged.

Define the administrative status being counted

Choose mutually exclusive buckets for the particular stage you are tracking, such as released for the defined receiving stage, held pending a named decision, and awaiting review. Each received unit belongs in one primary bucket, even if several open issues apply to it. Store those issue flags separately.

Within that fixed population and stage, the bucket quantities must reconcile to the received quantity. A unit that passes one appearance check but lacks required documentation may still belong in the held bucket. Avoid adding its “appearance approved” count to the released count as though they were different units.

EPCIS 2.0 records an object’s post-event business condition, retained until a later event changes it. This is a bounded data-model example; this buyer workflow neither requires GS1 adoption nor claims EPCIS conformance. GS1 EPCIS, section 7.3.6.2.1, printed page 60

For this buyer workflow, define the release stage in ordinary language and record each authorized change. A colored cell without a legend, date or decision reference is insufficient for a handoff.

Give every split a parent and a clear remainder

When a decision covers only part of a lot, create subset rows linked to the original receipt. Record the exact unit, package or other identifiers by which the authorized team can distinguish the subsets. Preserve manufacturer markings and existing traceability; any physical identification work must follow the agreed safe receiving procedure.

The parent row describes the whole population. Mark it as a non-additive summary once subset rows carry the counted quantities. Otherwise a spreadsheet can accidentally count both the original twelve and its two subsets, reporting twenty-four units that never existed.

If the evidence identifies only an indistinguishable group, do not select arbitrary units to make the approved count possible. Ask the authorized owner and provider what additional identification or review is needed. A numerical decision cannot solve a physical identity gap.

The map can be a small table. Its usefulness depends on clear identity and scope, not warehouse software or automatic barcode processing.

A hypothetical twelve-enclosure split

Assume twelve fictional passive, non-safety-critical enclosures have a supported piece count and receiver-assigned IDs U-01 through U-12. Decision D-12 approves the agreed administrative receiving stage for U-01 through U-08. The other four remain held for document review. This is a record example, not an actual inspection result or a sampling rule.

Eight plus four accounts for twelve. No unit is left unassigned, and no unit is counted twice. The eight-unit decision says nothing about any unlisted characteristic or later transport and installation requirements. If a required approval is still a prerequisite to that receiving stage, the affected units cannot legitimately occupy its released bucket.

Now suppose new evidence resolves the document question for U-09 and U-10 only, and the authorized reviewer issues D-13. Split R-12-B into two identifiable subsets or update unit-level rows. The new summary is ten released at this stage and two held. Retain D-12 and D-13 so the reason for the change remains visible.

Reconcile before the next handoff

Compare the proposed handoff list with the latest map. Check identities and quantities in both directions: every listed unit must be covered by the decision, and every unit covered by the requested handoff should appear once. A total of eight can be arithmetically correct while naming the wrong eight units.

Send the instruction with the decision reference and retained hold references. Request acknowledgement of the exact subset. Keep “instruction issued,” “acknowledged” and “action completed” separate until the relevant provider’s evidence establishes each event.

If goods are repacked or combined under another approved workflow, maintain a link from the original subset to the new package record. A new outer package identifier should not erase the holds attached to its contents. Resolve any conflicting instructions before relying on a new packing list.

Change status only when the decision changes

New evidence can justify reopening a previously released subset. Preserve the former decision and record the new reason, scope, owner and instructions. If the goods have already passed to another party, give the authorized coordinator the affected identifiers so the next step can be determined through the appropriate process.

This article provides no battery storage, segregation or handling method. Battery concerns require the applicable qualified response. An administrative release cannot establish internal safety, compliance, authenticity, shipping fitness or installation permission, and exterior photographs cannot supply those approvals.

The finished map should make the remaining work obvious: which goods are covered, which remain held, why they remain held and whose decision is needed. A partial decision is useful when its boundary survives the handoff.