A packaging transfer needs separate source, in-transit and destination counts. Reduce source availability when the agreed transfer event occurs, then recognise destination readiness only when the receiving decision supports it. The same batch must not appear as free stock at both ends.
Name what the transfer moves
Identify the component, revision and usable quantity. A carton label needs the component-version manifest behind it so the receiving site knows which boxes or inserts arrived.
Use physical availability states for this planning record. The transfer does not determine legal ownership or assign a software status universally. Those questions depend on the actual arrangement and system.
Follow 120 boxes between two sites
Assume site A begins with 500 approved boxes and site B has none. A transfers 120. The hypothetical receiving check finds 110 arrived and ten still unresolved.
Scroll horizontally if columns extend beyond the view.
| Event | A available | Transfer or unresolved quantity | B received usable | Total accounted quantity |
|---|---|---|---|---|
| Before transfer | 500 | 0 | 0 | 500 |
| Dispatched | 380 | 120 in transit | 0 | 500 |
| Partial receipt | 380 | 10 unresolved | 110 | 500 |
The ten unresolved boxes remain a quantity question. They are not automatically lost, damaged or released. Keep the next owner and evidence attached to them.
If B counted all 120 as available before receipt while A retained 500, the apparent total would become 620. That error could create promises for boxes that do not exist.
Keep planned movement outside received stock
A transfer request for 120 doesn’t prove it was dispatched. Preserve requested, prepared, dispatched and received events in the actual method. A cancelled request may return its reservation without any physical receipt at B.
If B receives boxes but holds them for version clarification, record the received quantity separately from available quantity. A location total can be correct while the packing availability is still zero.
Completed gifts or subsequent issues also affect the count. Link actual consumption at B to its received batch rather than leaving the transfer row as an everlasting balance.
Return an exception that can be resolved
For the ten-unit discrepancy, retain the dispatch reference, actual receipt and component identity. Ask the responsible parties to locate the remaining goods or correct the evidence. Update the state when that question closes, preserving the original event rather than rewriting a partial receipt as if it had always been complete.
Sources and scope
Australian Government supports the stated general concepts within this scope: General inventory categories, reorder points and stocktake. Access checked 14 October 2026.
Shopify Help Center supports the stated general concepts within this scope: Shopify state definitions only. Access checked 14 October 2026.
The worked scenario is original editorial analysis with assumed inputs, not a supplier offer, customer record or measured Packrivo result. Commercial feasibility and physical suitability remain project-specific.
Received units can be held without vanishing from the reconciliation
Retain the original partial-receipt snapshot: the source has 380 boxes, the destination has 110 usable boxes and 10 remain unresolved, totalling 500. Now add a later hypothetical event: 30 of those already received 110 usable boxes are placed on hold for version clarification. HOLD32 names this subsequent hold snapshot, not a reinterpretation of the original partial receipt. Destination usable quantity is now 80, held quantity 30 and unresolved quantity 10; source stock remains 380. The check is 380+80+30+10=500. The original 110 usable figure belongs to the earlier snapshot, before this assumed hold; no actual receiving or hold record has been obtained.
The hold is a different state of already received units, not another incoming shipment. Counting 110 received and then adding 30 held again would duplicate the same boxes. Nor does an identified physical receipt establish that all 110 are available for packing. The hold does not decide whether the units are damaged, legally owned by a particular party or accepted for use.
A second invented event resolves the remaining 10 as usable receipt: source 380+usable 90+held 30=500. If 40 usable boxes are then issued, remaining accounted stock is 460 and the separate issued quantity 40 reconciles to the original 500. Keep these events and the earlier partial receipt, rather than rewriting history as complete from the start. Actual receiving findings and release decisions remain blank.
| Hypothetical scope | Object and relationship | Input, formula or open question |
|---|---|---|
| HOLD32_SOURCE | SOURCE — ASSUMED_EVENT_STATE | 380 box |
| HOLD32_USABLE | USABLE — ASSUMED_EVENT_STATE | 80 box |
| HOLD32_HELD | HELD — ASSUMED_EVENT_STATE | 30 box |
| HOLD32_UNRESOLVED | UNRESOLVED — ASSUMED_EVENT_STATE | 10 box |
| HOLD32_ISSUED | ISSUED — ASSUMED_EVENT_STATE | 0 box |
| HOLD32_REMAIN | REMAINING_ACCOUNTED_STOCK — CALCULATED_FROM | HOLD32_SOURCE+HOLD32_USABLE+HOLD32_HELD+HOLD32_UNRESOLVED; 500 box |
| HOLD32_TOTAL | RECONCILED_ORIGINAL_QUANTITY — CALCULATED_FROM | HOLD32_REMAIN+HOLD32_ISSUED; 500 box |
| RESOLVE32_SOURCE | SOURCE — ASSUMED_EVENT_STATE | 380 box |
| RESOLVE32_USABLE | USABLE — ASSUMED_EVENT_STATE | 90 box |
| RESOLVE32_HELD | HELD — ASSUMED_EVENT_STATE | 30 box |
| RESOLVE32_UNRESOLVED | UNRESOLVED — ASSUMED_EVENT_STATE | 0 box |
| RESOLVE32_ISSUED | ISSUED — ASSUMED_EVENT_STATE | 0 box |
| RESOLVE32_REMAIN | REMAINING_ACCOUNTED_STOCK — CALCULATED_FROM | RESOLVE32_SOURCE+RESOLVE32_USABLE+RESOLVE32_HELD+RESOLVE32_UNRESOLVED; 500 box |
| RESOLVE32_TOTAL | RECONCILED_ORIGINAL_QUANTITY — CALCULATED_FROM | RESOLVE32_REMAIN+RESOLVE32_ISSUED; 500 box |
| ISSUE32_SOURCE | SOURCE — ASSUMED_EVENT_STATE | 380 box |
| ISSUE32_USABLE | USABLE — ASSUMED_EVENT_STATE | 50 box |
| ISSUE32_HELD | HELD — ASSUMED_EVENT_STATE | 30 box |
| ISSUE32_UNRESOLVED | UNRESOLVED — ASSUMED_EVENT_STATE | 0 box |
| ISSUE32_ISSUED | ISSUED — ASSUMED_EVENT_STATE | 40 box |
| ISSUE32_REMAIN | REMAINING_ACCOUNTED_STOCK — CALCULATED_FROM | ISSUE32_SOURCE+ISSUE32_USABLE+ISSUE32_HELD+ISSUE32_UNRESOLVED; 460 box |
| ISSUE32_TOTAL | RECONCILED_ORIGINAL_QUANTITY — CALCULATED_FROM | ISSUE32_REMAIN+ISSUE32_ISSUED; 500 box |
Download the comparison and project record (.csv). It preserves the original passages, model branches and table fields alongside the added hypothetical scopes. Relationship rows are not business cases, tests or completed records. Every actual identity, quantity, material, process, specification, observation, owner, decision, evidence and date field is blank. ACTUAL_BLANK is an empty starting row; unknown fields require permitted project evidence.
For the separate question, read Complete Gift-Pack Availability Is Limited by Its Scarcest Required Component.
For the separate question, read Consolidating Packaging Print Runs Trades Fewer Setups for Earlier Inventory.
Source scope checked 17 October 2026: General inventory records and Shopify-specific transfer/stock definitions support separate state questions, not legal ownership. Physical receipt, available quantity, hold release and actual title remain distinct; no real movement or received lot is verified.
What this changes in a packaging enquiry
Check stock already committed to a transfer before raising a replacement packaging purchase. The same boxes must not appear as available at both sites. If the transfer cannot supply the destination in time, compare a new order using the actual component version, delivery destination and date at which received stock can be used.
Discuss this packaging specification with Packrivo. We coordinate independent suppliers. MOQ: 500 pieces per product/design; illustrative quantities are not production offers. Confirm materials, samples, price and timing for your project.