How Return-to-Vendor Delays Drain Working Capital for Indian Retailers

Return-to-vendor, or RTV, is the process of sending damaged, excess, expired, or wrong stock back to a supplier for a refund, replacement, or credit note. It is the quiet opposite of a customer return, and in most Indian retail chains it is the most neglected workflow in the warehouse. Stock that should have gone back to a vendor weeks ago sits in a corner instead, and the money it represents sits with it.

What Return-to-Vendor Delays Actually Cost Retail Chains

RTV delays cost retailers twice: once in the working capital locked inside unreturned stock, and again in the warehouse space that stock occupies instead of sellable inventory. Neither shows up as a single line item, which is exactly why it goes unnoticed for months.

A damaged shipment that arrives at a store or a central warehouse creates an immediate decision: accept it into sellable stock, write it off, or flag it for return. In chains without a central system, that decision is made store by store, often by whoever is free at the time. The flagged units get set aside "to deal with later," and later rarely comes until a cycle count or a stock audit forces the issue.

• Cash tied up in stock that has already left sellable inventory but has not yet been credited back by the vendor
• Shelf and warehouse space occupied by units generating zero revenue
• Vendor credit notes that arrive months late, or never, because nobody tracked the return against the original purchase order
• Store staff time spent repeatedly sorting through the same pile of returns during every stock check

Why RTV Gets Stuck in Most Indian Retail Operations

RTV stalls because it depends on information that typically lives in three different places: the store that received the damaged stock, the warehouse that is supposed to consolidate it, and the accounts team that has to match it against a purchase order before anyone can raise a debit note. When those three do not share one system, the return waits for someone to manually connect the dots.

A few patterns show up repeatedly across multi-store chains:

• No single list of what is return-eligible across stores, so nobody knows the total value sitting idle until an audit finds it
• Return decisions made per store rather than against a vendor-wide return policy, so similar damage gets written off in one branch and returned in another
• Debit notes raised long after the physical stock has left the store, by which point nobody remembers the original receiving date or batch
• No link between the goods received note from the original delivery and the return, so a vendor can dispute the claim with no paper trail

Most of this traces back to receiving discipline. If damage and shortages are not recorded accurately the moment stock arrives, there is nothing solid to base an RTV claim on later. Chains that have tightened up their warehouse receiving process tend to catch return-eligible stock within days instead of months.

How GST Treats Goods Sent Back to a Vendor

Under GST, a return to a vendor is generally documented through a debit note raised by the buyer or a credit note raised by the supplier, and this document is what allows the input tax credit position on both sides to be corrected. Get the documentation sequence wrong and the return becomes a tax reconciliation problem on top of a stock problem.

The exact rules for debit and credit notes, including timelines and the fields they must carry, are set out by the GST authorities rather than left to individual businesses to interpret. Retail finance teams tracking vendor returns across multiple stores should work from the provisions published on the CBIC GST portal and the invoicing guidance on GSTN's website rather than relying on what one accountant remembers from a previous job. A centralized GST compliance view across locations makes it far easier to confirm that every RTV has a matching debit note before the books close for the month.

How to Set Up an RTV Workflow That Doesn't Lock Up Capital

Fixing RTV is less about new software and more about giving the return a clear, trackable path from the moment damage is spotted to the moment the vendor credits the account. The sequence below works whether a chain has two stores or fifty.

1. Flag return-eligible stock the moment it is identified, whether at receiving, during a cycle count, or when a store manager spots damage on the shelf, and record it against the original purchase order and batch rather than as a generic write-off.
2. Consolidate flagged stock from every store into a single warehouse view so the total value and quantity pending return is visible to one person, not scattered across branch-level notebooks or spreadsheets.
3. Agree a return window and a pickup or dispatch schedule with each vendor in advance, so RTV stock does not sit waiting for an ad hoc pickup that keeps getting postponed.
4. Raise the debit note at the point the stock is dispatched back to the vendor, not weeks later, and attach the original goods received note and batch details so the vendor cannot dispute the claim.
5. Reconcile vendor credit notes against the debit notes raised every month, and escalate anything still open after the agreed return window instead of letting it roll forward indefinitely.

None of this requires a separate system if stock movement is already tracked centrally. A chain that has already brought cycle counting and stock audits onto one platform is most of the way there, because the same stock accuracy data that powers those processes is what flags RTV-eligible units in the first place. Commmerce, built as an Omnichannel Retail Operating System for Indian retailers, keeps this stock movement visible across every store and warehouse from one dashboard, so RTV units get flagged and tracked the same way any other inventory movement is, instead of needing a separate manual process.

RTV vs Customer Returns: Different Problems, Different Systems

Customer returns and vendor returns look similar on paper because both involve stock coming back, but they run on different timelines, different documents, and different people, and treating them as one process is a common reason RTV gets neglected.

Chains that have already built strong processes for centralized supplier management usually extend the same vendor-wise visibility to returns, since the people negotiating purchase terms are the same ones who should be chasing overdue RTV credits.

What This Means as Retail Chains Scale Across Stores

The more stores and vendors a chain adds, the more an informal RTV process breaks down, simply because more people are making independent decisions about stock nobody else can see. Industry bodies like the Retailers Association of India and research from IBEF have both tracked organized retail in India expanding into smaller cities and additional formats, and that expansion multiplies the number of receiving points generating potential RTV stock, not just the number of billing counters.

A chain opening its fifth or fifteenth store cannot rely on one person remembering which vendor owes a credit note for a shipment damaged three months ago. The fix is structural: one view of return-eligible stock, one documented process per vendor, and a monthly reconciliation that treats unreturned stock as unpaid revenue rather than a background chore. Retailers who have already standardized how they manage procurement across stores find RTV is the easier half of that same discipline, not a separate project.