Retail Return and Exchange Software
HisabLekha connects retail returns and exchanges to the original sale, returned variant, replacement stock, payment difference, customer ledger, and participating branch. It supports the operational record while tax treatment and credit-note decisions remain with the retailer’s accountant.
What does HisabLekha handle for this shop type?
A return is not complete when the cashier takes back a garment or shoe. The original sale, returned variant, replacement variant, stock movement, payment difference, customer balance, and branch need one traceable exchange story. HisabLekha supports that workflow while tax treatment and credit-note decisions remain subject to the retailer’s accountant and current rules.
Find the source invoice and record the returned variant, quantity, reason, and stock movement together.
Select the replacement size, colour, or footwear variant and calculate any payment difference before settlement.
Keep due, advance, refund, and customer ledger effects tied to the return or exchange instead of correcting them later.
Support branch exchange cases where a participating shop accepts the return and another branch supplies the replacement.
Give the accountant the original sale and return context needed to decide the applicable GST or credit-note treatment.
How do fashion shop inventory models differ?
The sellable unit changes by shop type. This table shows which product attributes and workflow matter for each category.
| Shop type | Inventory model | Relevant workflow |
|---|---|---|
| Apparel return | Original size-colour variant | Source invoice, restock decision, and ledger update |
| Footwear size exchange | Returned shoe size + replacement size | Variant stock and payment difference |
| Boutique or fabric case | Piece or roll/metre item | Physical inspection and quantity adjustment |
| Multi-branch exchange | Return shop + replacement shop | Cross-shop settlement and separate GST context |
When should a retailer verify the fit first?
- Returns and exchanges depend on the configured shop policy, source invoice, physical inspection, and participating branch; the page does not promise every retailer’s policy automatically.
- GST refund, credit-note, damaged-stock, and tax-period treatment must be checked by the retailer’s accountant and current law.
Frequently asked questions about retail return and exchange software
Can a customer exchange a shirt, pant, or shoe size?
Yes. Supported variant workflows can record the returned size or colour and the replacement variant separately, with stock and any payment difference connected to the exchange.
Can returns work across branches?
Supported multi-shop workflows can record a return in one participating shop and replacement settlement in another, while preserving shop-wise accounting boundaries. Confirm the participating-branch setup before promising the customer a cross-shop policy.
Does the software decide GST credit-note treatment?
No. The system can preserve the original sale and return context, but the correct GST, refund, and credit-note treatment must be approved by the retailer’s accountant under current rules.
What happens to the returned stock?
The returned item and replacement item remain distinct stock movements. Staff should inspect the physical item and choose the correct restock, damage, or adjustment process.
Can an exchange include a payment difference?
Yes. A supported exchange can keep the replacement value, refund or additional payment, due or advance, and customer ledger effect together for review.
Related fashion-retail workflows
Explore another documented workflow that may fit the next stock, shop, or channel question.
See the connected workflow in action
HisabLekha adds combined checkout, separate shop-wise GST bills, cross-shop exchange, customer balance visibility, and connected storefront stock to the category workflow.