Returns and Interbranch Transfers Without Phantom Stock

A branch transfer can make stock appear to exist in two places or vanish from both. The source warehouse dispatches a full quantity, the destination counts fewer units, and a returned item is added back to saleable stock before anyone checks its condition. We recommend a transfer ledger that follows physical custody and stock condition, with a separate owner for each handoff. A retailer with a Laguna depot and several Philippine branches can then answer where a disputed unit is, who last counted it, and whether a customer can safely buy it.

Separate dispatch from destination acceptance

Consider a fictional chain sending 100 boxed appliances from its Laguna warehouse: 60 to a Metro Manila branch and 40 to a Cavite branch. At dispatch, the depot records two transfer references, item identifiers, quantities, carrier or driver, time, and proof of handover. The 100 units leave the source's available balance. They should not instantly become sellable at the destinations merely because the source scanned or wrote a dispatch slip.

Metro Manila counts 60 physical units: 58 in acceptable condition and two damaged. Cavite counts 39, leaving one unit short against its transfer document. The destination clerk records the count and condition before signing the receipt, and the manager opens an exception for the missing Cavite unit. A delivery acknowledgment that only says “received” cannot explain these differences later.

The arithmetic is now visible: 97 sellable units at destinations, two physically present but on damage hold, and one unit unresolved in transit or discrepancy review. Those states total the 100 dispatched units. If the system shows 100 sellable across the branches, it has hidden the damage and shortage. If it shows only 97 with no exception record, the business cannot investigate the other three.

These labels describe a recommended control, not a claim about any vendor's built-in status names. The actual stock categories and accounting treatment should follow the organization's approved policy and the demonstrated system configuration.

Give the missing unit an investigation path

For the Cavite shortage, preserve the Laguna pick list, loading count, vehicle handover, seal or package evidence if used, delivery note, branch count, and any photograph taken under company policy. Assign one owner to reconcile them. A recount may find the unit in an unmarked carton; the driver may have a documented return; or the source count may have been wrong. Each result needs a dated correction and a reason.

Do not close the discrepancy by adding one unit to the Cavite branch merely to make the transfer look complete. That creates phantom stock and leaves the physical question unanswered. Likewise, do not remove the unit from the source retrospectively without a traceable adjustment. The investigation can hold an unresolved quantity while operations continue with the 39 actually available units.

Age the exception. An item “in transit” for one day may be normal for a scheduled route; the same status weeks later needs a named follow-up. Set expectations by route and review transfers exceeding them. The useful measure is the number and value of unresolved quantities by owner, not only the count of completed transfers.

Treat customer returns as another condition decision

Now suppose the Metro Manila branch sells three of its 58 usable units. The customers later return all three. Two pass inspection and one is damaged. After the sales, the branch has 55 sellable units from that original group. After inspecting the returns, it has 57 sellable units and one more on damage hold, in addition to the two damaged units from the original transfer. Its physical total is 60 again, but only 57 are ready for sale. A simple “return +3” posted immediately to available stock would overstate sellable quantity by one.

The return record should identify the original sale, item and serial or batch information where the business uses it, reason, receipt time, inspector, and final decision: restock, repair, supplier return, or disposal. Refund or exchange approval is a separate customer-service decision. If an item is sent back to Laguna for repair, begin a new transfer with its own dispatch and acceptance evidence; do not quietly subtract it from the branch.

Review a daily transit and returns worksheet

We would give the depot and branches one compact review view:

Question	Evidence to compare	Owner
What left Laguna?	Pick, dispatch, handover	Depot
What arrived?	Destination count and condition	Branch
What remains disputed?	Shortage note and investigation	Logistics lead
What came back from a customer?	Sale and return references	Branch service
What can be sold now?	Accepted stock less holds	Inventory lead

Reconcile high-risk items daily and slower items on a defined cycle. Watch for transfers with no destination receipt, returns awaiting inspection, negative available balances, and damaged stock that has no disposition. These exceptions are useful because they tell someone exactly what to resolve before a count variance grows into a pricing or customer-service problem.

ERPat's public module directory describes Inventory transfers and Logistic dispatch, returns, and supply movement. Demonstrate the 100-unit example in the proposed setup, including the two damaged units and one Cavite shortage. Ask how it records in-transit ownership, a branch acceptance, an exception correction, and a customer return; verify the exact labels rather than assuming them. For help mapping this flow across stores, explore our retail solutions.