A transfer has left the main warehouse, but the receiving site cannot find all the stock. The system shows the order as shipped. Production sees a planned receipt and assumes the material will be ready. Neither view explains the full position. Which pieces arrived? Which are damaged? Which remain unaccounted for?

In transit inventory reconciliation connects those views. It follows each shipment between named sites. The open quantity stays visible until evidence explains it. A receipt can be partial. A completed transfer can include a documented loss. A damaged item can be physically present without being ready to use.

This guide develops an original apparel example. It follows two shipments, partial receipts and a later return. It explains each quantity and event record. It also shows how to resolve exceptions and close the movement. All numbers are illustrative. The case covers transfers between warehouses within one company. Moves between separate legal entities need their own ownership and tax review.

Choose a transfer process that records the journey

An immediate stock movement and an in transit transfer serve different needs. Moving a tote between adjacent bins may need only a location change. During a trip between sites, neither warehouse has the cartons on its shelves. Their location still needs a record.

Microsoft's inventory journal guidance makes this distinction explicit. Its transfer journal posts an immediate issue and receipt. A transfer order can track stock in transit. Choose a process that reflects the actual journey.

Do not use an instant destination receipt merely because it is easier to post. Staff may then pick or promise stock that is still on the road. A complex transport workflow may add little value to a short bin move. Choose the right level of control for that movement.

Write down the physical boundaries. Specify when the sending warehouse hands over the goods. Define when the receiving site confirms custody too. Add any staging area or cross dock that needs a separate record. The record should follow the chosen boundary consistently.

Separate the request, shipment and receipt

The requested quantity describes an instruction. The shipped quantity describes a confirmed departure. The received quantity describes a confirmed arrival. Keep all three, even when they usually match.

Oracle's transfer order overview links several steps to the transfer document. These include picking, shipping, receiving, putaway and returns. That shared reference helps trace a movement through several steps. It does not make the steps interchangeable.

Add a shipment reference beneath the transfer line. One requested quantity may leave on several trucks. Add receipt event references beneath each shipment. Staff may count or post one truck's goods in parts.

Keep the item variant, stock unit and relevant lot with those references. Ten navy medium shirts cannot close a shortage of ten black large shirts. A style total may balance while the destination still lacks the required sizes.

Use the actual shipped quantity as the transport starting point. A request for 2,400 pieces does not prove that 2,400 left the warehouse. Preserve the unshipped balance as an order issue rather than placing it in transit.

Work through a split apparel transfer

Suppose a factory requests 2,400 pieces of one approved trim from its central warehouse. The example uses pieces throughout. There are no pack conversions, consumption entries or opening transit quantities.

Shipment S1 leaves on day 1 with 1,500 pieces. Shipment S2 leaves on day 3 with 700 pieces. At the end of day 5, the destination has physically received 1,460 from S1 and 640 from S2.

The first receipt includes 40 damaged pieces. The second includes 10 held for inspection. The other received pieces are released for use. The held pieces remain at the destination and are included in its physical stock.

Record at the end of day 5

S1 pieces

S2 pieces

Total pieces

Confirmed shipped

1,500

700

2,200

Physically received

1,460

640

2,100

Received but held

40

10

50

Received and released

1,420

630

2,050

Shipped but not yet reconciled

40

60

100

The requested but unshipped balance is 2,400 minus 2,200, or 200 pieces. The open transport balance is 2,200 minus 2,100, or 100 pieces. Those are different problems.

The request has four parts: 200 unshipped and 100 open in transit. Another 50 are received on hold. The remaining 2,050 are received and released. These groups total 2,400. Each piece belongs to one group at this cutoff.

Do not call the whole 350-piece gap from requested to released stock a transport loss. That figure mixes unshipped demand, an unresolved journey and received stock awaiting disposition.

Reconcile each shipment before adding the total

For an ordinary open shipment, start with confirmed dispatch and subtract confirmed receipts. Keep corrections as linked events with a clear sign.

Open transit = shipped − received − confirmed return − approved loss.

Here, a confirmed return brings goods back to the source from this journey. An approved loss removes a supported quantity from transit. It follows the agreed review process. Both are zero at the first cutoff.

The simple day 5 calculation is therefore 2,200 minus 2,100, or 100 pieces. Yet the operational review should retain S1's 40 and S2's 60 separately. They may have different carriers, arrival dates or explanations.

A transfer total of zero can conceal an overreceipt on one shipment and a shortage on another. Match the event to the shipment before netting values. If staff used the wrong reference, correct that reference with evidence.

Use ApparelDiary's cycle counting guide for controlled recounts and movement cutoff. A warehouse count helps locate the goods. It does not automatically establish which shipment or receipt record needs correction.

Count damaged stock as present, with its own status

Physical arrival and release for use answer different questions. In the case, 2,100 pieces arrived and 2,050 are released. Keeping the 50 held pieces in transit would misstate their location.

Oracle Retail's transfer receiving documentation describes separate damaged quantities within the received total. Its workflow places such stock in an unavailable category. The exact names and posting rules vary by system.

At the destination, identify the hold location, quantity and reason. Link the inspection or damage review to the receipt. If a later review releases ten pieces, change their status once; do not record a second arrival.

Microsoft's inventory blocking guidance shows that blocking can be applied through different mechanisms. Test the chosen mechanism with the actual warehouse process. Open work, planning rules and available statuses can affect the result.

The warehouse should be able to explain physical stock and usable stock separately. A production planner needs the released amount and its timing. A transport reviewer needs proof that the goods reached the destination.

Preserve partial receipts without counting them twice

A receiving team may confirm part of a shipment, then finish the count later. Establish whether each message reports an additional event quantity or a cumulative total.

Suppose S1 first reports 1,000 pieces received. A later cumulative report says 1,460. The second report adds 460 to the previous total. Adding 1,000 and 1,460 would invent 1,000 extra pieces.

With S2's 640 included, that mistake would produce 3,100 received against only 2,200 shipped. The apparent transit balance would be negative 900 pieces. This is a data error to investigate, not evidence that transport created stock.

For event messages, each unique receipt can be added once. For cumulative messages, calculate the change from the previous accepted version. Preserve the old value and the correction trail.

A repeated message after a connection failure should not create another receipt. Use a stable event reference and a repeat check. Keep the first successful posting result. Staff can then tell a replay from a new physical arrival.

Test this with a real sample transfer before relying on an interface. Inspect the stock entries and the resulting balance. A successful screen message alone does not prove the quantity.

Investigate the open balance in an evidence sequence

Begin with the identity and count. Check whether the receiving team used the correct transfer, shipment, item and unit. Look for a receipt parked in an error queue or posted under another reference.

Next compare the dispatch evidence with the loading record. A planned carton on a pick list may still be in the source staging area. A carton count may agree even when one carton contains fewer pieces.

Then examine custody evidence. Match the carrier reference, package identifiers, handover times and any condition notes. A signature may confirm that the vehicle was accepted. It may not prove the contents of each carton.

Keep the affected stock separate while resolving the count. Ask the destination to preserve its packaging too. Avoid moving uncertain units into mixed pick faces before their identity is known.

Record a next action and owner for each open shipment. “Waiting for reply” needs a named party and a follow-up date. Set escalation rules for the route and the date the stock is needed. Consider material risk too. One age limit will not suit every transfer.

Close the journey with the event that actually happened

Continue the case after day 5. The missing 40 pieces from S1 arrive and are confirmed. Of S2's remaining 60, the carrier returns 30 to the source, 20 are confirmed lost and ten remain unresolved.

The confirmed loss requires the company's evidence and approval process. It is not inferred merely from the age of the shipment. The example assumes that process supports the stated 20-piece loss.

Remaining transit = 2,200 − 2,140 − 30 − 20 = 10 pieces.

The 2,140 received now includes the original 2,100 plus S1's late 40. The 30 returned pieces go back to the source record. The 20 lost pieces leave the transit balance through a documented adjustment. Ten pieces remain open.

Do not post all 100 as received just to close the order. Do not reduce the original dispatch to 2,100 when records prove that 2,200 left. Those shortcuts erase the evidence needed to understand what happened.

A system may close a document before the review ends. Keep the unresolved quantity in a controlled exception record. The operational issue remains open even if a software status says otherwise.

Check the whole company's quantity bridge

The transfer should also make sense across locations. Assume the source began with 8,000 pieces and the destination with 500. There were no other receipts, issues or transfers during this illustration.

The source ends with 8,000 minus 2,200 shipped plus 30 returned, or 5,830 pieces. The destination ends with 500 plus 2,140 received, or 2,640 pieces. Ten remain in transit.

Together, those positions total 5,830 plus 2,640 plus ten, or 8,480 pieces. Opening stock was 8,500. The difference is the supported loss of 20 pieces.

The destination's 50 held pieces are already inside its 2,640. Adding them again would double count stock. Assuming its opening 500 and late 40 are released, its released quantity is 2,640 minus 50, or 2,590.

This bridge is a quantity check under the stated assumptions. It does not prescribe general ledger accounts or prove the value of a claim. Financial treatment needs the relevant company policy and transaction configuration.

in transit inventory reconciliation

Understand what a force close will change

Test a close-short or force-close action before use. Check its effect on both warehouses and transit. A status change may create inventory entries as well as close the document.

Oracle Retail's transfer guide illustrates several force-close settings. One setting adds the shortage back to the sender's stock record. Other settings assign a loss. Such settings describe configured treatment; they do not establish the physical cause.

If goods are truly lost, a setting that adds them to source stock can create phantom availability. If goods never left the source, a loss entry can hide a dispatch error. The action needs to match the evidence.

Document who can close a discrepancy and what support they must retain. Small routine differences may follow an approved policy. That policy must still distinguish missing evidence from proof of receipt.

Use ApparelDiary's ERP factory checklist to test the end-to-end result. Check source stock, destination stock, transit and the exception history after the action.

Keep cancellation, correction and return distinct

Canceling an unshipped request reduces future work. It does not bring goods back from the road. In the case, the remaining request is 200 pieces. Canceling it leaves the 2,200 already dispatched unchanged.

Oracle's transfer order change rules place limits on quantity changes after shipment. The permitted action depends on the order's path and state. Confirm those rules in the installed release.

A correction fixes an incorrect record. A physical return records goods moving back. Goods may have reached the destination before coming back. Erasing their receipt would remove that history.

Oracle's receipt correction guidance sets limits after goods have been put away or returned. Its transfer return guidance also covers two types of return. One moves goods back; the other changes accounting records only.

Those distinctions matter when a user sees a tempting correction button. Verify that the action represents the real event and is allowed at that stage. Never invent a receiving event to unlock a later reversal.

Age the outstanding shipment quantities

An order's creation date is not the same as its dispatch date. Age the open quantity from its departure event. Define the calendar and cutoff.

At the end of day 5, S1's remaining 40 pieces are four days old by simple day-number difference. S2's remaining 60 are two days old. Their quantity-weighted age is calculated below.

Weighted open age = (40 × 4 + 60 × 2) ÷ 100 = 2.8 days.

This average describes only the 100 open pieces. It does not include the 2,100 already received. It does not establish whether either shipment is overdue. Compare its age with the expected arrival time.

Show the oldest open shipment as well as the average. A large recent dispatch can lower the average age. An older shortage may still remain unresolved. Keep route expectations beside age so staff can see which action is due.

If one shipment contains goods with several departure times, split the event record. Do not reset an older portion's clock when the final carton leaves.

Measure completion with named denominators

The first cutoff supports several different measures. Shipment fill against the request is 2,200 divided by 2,400, or 91.67%. Physical receipt against shipment is 2,100 divided by 2,200, or 95.45%.

Released receipt against shipment is 2,050 divided by 2,200, or 93.18%. Round only the displayed percentages. Keep the underlying piece counts available.

These measures describe different stages. They do not measure customer service or on-time delivery. They also do not prove a transport loss. Label the population, cutoff and treatment of holds.

In each review, examine open pieces by shipment and overdue exceptions. Measure the time from finding a difference to closing it with evidence. Review both counts and material importance. Consider tomorrow's production needs too. One missing rare trim may matter more than many common pieces.

Keep changes visible. Valid receipts can reduce the open balance. So can write-offs or a decision to close the record. Keep those causes distinct. A useful report shows which events reduced it.

Design a focused transfer acceptance test

Use a small transfer with known quantities and distinct package references. Post two shipments, receive one in parts and leave a small balance open. Confirm that the source, transit and destination records agree.

Then enter a receipt hold, release part of it and verify that physical stock is not received twice. Replay a receipt message and check that the balance stays unchanged. Try a wrong variant and confirm that it cannot silently close the intended line.

Microsoft's Business Central transfer guidance compares direct and in transit modes. Partial posting and reversal options differ by mode. Test the process chosen for the actual route.

Include a canceled unshipped balance, a supported receipt correction and a physical return. Check the resulting transactions, not only the final header status. Keep the expected quantities and the observed results.

Repeat the test when a material workflow or interface changes. Routine users should know where to find rejected messages and who resolves them. Check errors that receive no alert. The screen may otherwise disagree with the warehouse.

Resolve cutoff and identity problems without losing the trail

A truck may arrive before the warehouse posts its receipt. Keep both the physical event time and the system posting time. At a reporting cutoff, explain the delay instead of silently moving dates to make a report agree.

If the destination is wrong, first locate the goods. Then plan any further move. A new transfer may be needed under the approved workflow. Do not show stock at the intended warehouse while another site holds it.

For fabric rolls, preserve the roll identity and actual measurement basis. A length difference can arise from measurement or unit rules as well as missing material. For trims, verify the pack contents before treating carton counts as pieces.

Use ApparelDiary's material issue and return controls for movements into production after receipt. Keep that later consumption separate from the journey between warehouses.

Keep intermediate stops visible without duplicating receipts

A cross dock may handle a shipment without becoming its final stock destination. Decide whether that stop changes the location record or only records custody. The chosen treatment should match the physical process and the system design.

Suppose a sealed carton is scanned at a hub and later at the factory. The scans describe two events. They may not represent two stock receipts. If the hub is an inventory location, the next leg needs its own linked dispatch. The hub may serve only as a transport checkpoint. In that case, the factory receipt remains the stock event.

Preserve the package reference across the legs. If the hub splits or repacks a load, record which new packages contain the original contents. Otherwise, a receiver may be unable to distinguish a late carton from a duplicate label.

A route change also needs a visible link. Keep the original instruction, the authorized new destination and the actual handover evidence. The history should explain the route change and the actual arrival site.

Give each handoff a clear decision owner

The sending warehouse owns the evidence of what left. The receiving warehouse owns the evidence of what arrived and its condition. Transport staff supply journey and handover records. An authorized reviewer decides how a supported difference should be closed.

These roles can sit within a small team, but the decisions still need to be clear. The person who finds a shortage needs a clear route for review. They should not have to guess which stock entry to change. Give that person a route for preserving the count and escalating the difference.

Agree a response time that reflects the operation. An urgent trim may need attention before the next shift. Another route may allow a longer review. Preserve the original due date when a follow-up is extended so that delays remain visible.

Review recurring causes with the relevant owner. Wrong pack conversions call for a master-data fix. Repeated cartons left in staging call for a dispatch control. Late interface messages need an integration fix. A general reminder to count more carefully will not address all three problems.

Frequently asked questions

Does a delivered carrier status close the transfer?

It supports arrival evidence, but it may not confirm each item and quantity. Match the delivery to the warehouse receipt and resolve remaining differences. Keep goods on hold visible at the destination.

Should damaged units stay in transit until inspection ends?

Record arrived goods at the destination with the correct hold status. Inspection decides release or disposition. It should not conceal where the units are located.

Can a negative transit balance be accepted as an overdelivery?

Investigate it first. Several errors can cause the same sign. Check duplicate receipts, cumulative totals added as events, wrong units and incorrect shipment references. Record genuine excess only when identity and physical evidence support it.

Can the last unshipped quantity be canceled after partial delivery?

Often a system provides a permitted way to reduce the remaining request. The exact rule depends on its state and configuration. Cancel only the unshipped scope; retain the history of quantities already dispatched.

Is a zero transit balance enough to prove a clean transfer?

No. Check each item and shipment. Its receipts, returns and adjustments should explain the balance. Two errors can cancel each other out. A wrong force-close rule can also produce zero without a sound physical record.

Close each transfer with an explainable destination

The worked case begins with a 2,400-piece request and ends with several distinct facts. Only 2,200 pieces shipped. Later evidence places 2,140 at the destination, 30 back at the source and 20 in a supported loss record. Ten remain unresolved.

That final ten-piece balance should remain visible until evidence supports its next step. Preserve the shipment identities, condition states and correction history throughout the review. A transfer is useful to the business when staff can explain where its stock went and which part can now be used.

Transfers end in stock counts, so see material issue and return controls and cycle counting.

Shipping documents and stock classes matter here, so see the export packing list reconciliation and ABC-XYZ inventory segmentation.

References

Microsoft Learn — Inventory journals.

Oracle Cloud SCM — Transfer orders.

Oracle Retail — Transfers.

Microsoft Learn — Inventory blocking.

Oracle Cloud SCM — Transfer order change management.

Oracle Cloud SCM — Receipt corrections.

Oracle Cloud SCM — Transfer order returns.

Microsoft Learn — Transfer items between locations.