How to Manage IST (Inter-Store Transfer) in a Garment Chain — The Right Way

Ask any garment chain owner what causes the most stock discrepancies in their business. The answer, almost universally, is inter-store transfers — ISTs. Stock leaves Store A's books, floats somewhere in transit, arrives at Store B, gets received informally, and by month-end nobody agrees on how much stock any location actually has.

The problem isn't the transfer itself. It's doing it without software that creates a formal, traceable chain of custody from source to destination.

Why ISTs Go Wrong in Garment Retail

• Transfers are initiated verbally or on WhatsApp — no formal request, no reference number
• Dispatched quantities are noted on paper that gets lost in transit
• Receiving stores confirm by thumb rule, not by actual barcode scan
• Head office discovers discrepancies only at month-end stock audit
• Returns from stores back to warehouse follow no standard process

In garment retail, the compounding effect is severe because one IST can involve 40+ SKU-variant combinations — you're not moving 5 boxes, you're moving 200 individual size-colour combinations, each of which needs to be tracked.

What a Proper IST Workflow Looks Like

Step 1 — IST Request

Either the destination store raises a replenishment request ("Store B needs 20 units of Style XY in sizes M, L, XL") or head office proactively initiates based on stock analysis. The request is logged in the system with a unique IST reference number.

Step 2 — Warehouse Picking

The warehouse receives the IST request as a pick list. Staff scan each item's barcode as they pick — the system confirms they're picking the right style, size, and colour. Any shortfall is flagged before dispatch, not after arrival.

Step 3 — Dispatch with E-way Bill

For inter-state transfers or high-value dispatches, E-way Bill generation should be automatic from the IST document. The dispatch records the exact quantities shipped, driver details, and expected delivery date.

Step 4 — GRN at Destination Store

When stock arrives at Store B, the store manager scans each item against the incoming IST document. The system matches received quantities against dispatched quantities. Any discrepancy — missing items, wrong variants — is flagged immediately and captured as a discrepancy report, not silently adjusted.

Step 5 — Auto Stock Update

Once GRN is confirmed, Store B's inventory updates automatically. The stock deduction from Store A (or warehouse) was already done at dispatch. Head office can see both sides of the transfer in real time.

Common IST Mistakes That Create Phantom Stock

• Deducting from source and crediting destination simultaneously on dispatch (ignores in-transit loss)
• Allowing partial GRNs without documenting what was received vs. what was sent
• No barcode confirmation at receiving end — staff manually enter quantities
• No discrepancy escalation process — shortfalls are quietly adjusted
• No tracking of return ISTs when stores send unsold stock back to warehouse

IST in SigmaPOS — How It Works in Practice

In SigmaPOS, an IST moves through four formal stages: Request → Approved → Dispatched → GRN Received. Stock is tracked at every stage. Head office can see exactly which ISTs are in-transit at any moment. Store managers scan barcodes at receiving — no manual entry. Discrepancies are automatically escalated to the head office dashboard.

For garment chains with 5+ stores, a proper IST module typically reduces stock write-offs by 15–25% in the first season. The root cause elimination is significant: when every transfer has a paper trail with barcodes, theft and shrinkage in transit become visible and accountable.