Sales return management should keep one event connected
Sales return management for shops in Bangladesh is more than taking a product back across the counter. Once a return is accepted, the original sale, customer refund or outstanding due, returned quantity, stock condition, and sales records may all need to change together. If staff update only one part, the shop can end up with stock that looks correct while cash is wrong, a customer balance that remains too high, or a refund with no matching return record. The practical control is simple: one accepted return should be traceable from the original invoice to the final money and stock outcome. This matters in clothing shops, electronics and mobile stores, groceries, general stores, wholesalers, and other businesses that allow returns or exchanges. Each business should define its own return policy according to its products and operating requirements. This guide focuses on keeping the records correct after a return has been accepted.
First identify whether it is a return, exchange, adjustment, or warranty case
Before changing stock or money, identify what actually happened. A sales return reduces a completed sale because one or more sold items are being returned. An exchange combines an accepted return with a replacement item or new sale. A price adjustment is different because the customer keeps the product while the accepted selling value changes. A repair or warranty intake may also be different when the original sale is not being reversed. A sale cancelled before completion should not be treated as a return from a completed invoice. This distinction matters because each event can affect stock, sales, customer dues, and money differently. A practical counter check is to ask three questions: Is the original completed sale being reduced? Is money or customer due changing? Is a product physically coming back? If the situation does not fit the normal workflow, send it for manager approval instead of forcing it into the wrong transaction type.
Start every accepted return from the original invoice
The safest starting point is the original invoice or approved sale reference. Record the invoice number and date, customer where applicable, SKU or product, returned quantity, original invoiced value, relevant discount, and payment status. For serialised, warranty-sensitive, batch-controlled, or similar products, retain the references the business normally uses. The accepted return value should be based on the relevant value from the original sale rather than today's shelf price. For example, if an item was sold at a discount, refunding today's full selling price could overstate the return. If the customer cannot provide an invoice, follow the shop's approved no-invoice process and document the evidence or manager approval used. Do not create a false invoice number or estimated selling value merely to complete the transaction. A clear link to the original sale makes it much easier to explain later why sales, refunds, dues, stock, or reports changed.
Inspect returned products before putting them back into sellable stock
Returned quantity and sellable quantity are not always the same. After accepting a return, inspect the product and decide its stock disposition. A sealed or unused item in acceptable condition may be suitable to return to normal sellable stock under the business's policy. A damaged, defective, opened, expired, incomplete, or otherwise unsuitable item may need to remain outside normal available stock while it is reviewed, repaired, written off, or prepared for a supplier claim or return. The exact process depends on the product and the business. Condition is especially important where packaging, expiry, batch, serial number, accessories, or warranty status affects resale. A useful return record therefore keeps at least two separate quantities or statuses: what physically came back and what can actually be sold again. Automatically putting every returned unit into available stock can make the system show inventory that exists physically but cannot realistically be sold.
Handle refunds, customer dues, and exchanges separately
Once the product side is clear, settle the financial side. For a fully paid sale, an accepted return may create a customer refund according to the shop's policy. Record both the refund amount and the actual payment method used. For a credit sale where the customer still owes money, the return may reduce the outstanding due instead of creating an immediate cash refund. For an exchange, use the accepted return value as a credit against the replacement transaction and calculate any difference separately. A simple operational formula is: accepted return value = returned quantity × accepted net unit value from the original sale, where one net unit value applies. For a due-only adjustment with no new payment, new customer due = due before return - accepted return value. For a simple exchange, remaining amount payable = replacement net value - accepted return credit. Bundles, discounts, partial payments, or special pricing may require additional review, so preserve the original invoice details rather than calculating from memory.
Worked example: one item returned from a cash sale
Example only: a Dhaka clothing shop sells three shirts at an invoiced net price of ৳900 each, creating a cash sale of ৳2,700. The next day, the customer returns one shirt. The shop verifies the original invoice, accepts the return under its policy, and confirms that the shirt is suitable for resale. Accepted return value = 1 × ৳900 = ৳900. The shop records one returned unit against the original invoice, records the actual ৳900 refund, and adds one unit back to sellable stock. The remaining net value of the original sale becomes ৳1,800. The important control is that the sale reduction, refund, and stock movement all belong to the same return transaction. If the returned shirt were damaged and unsuitable for resale, the accepted return and refund could still be recorded, but the returned unit should follow the appropriate damaged or exception-stock process instead of automatically becoming available stock.
Worked example: partial return from a due sale
Example only: a small wholesale counter sells ten LED bulbs at an invoiced net price of ৳300 each, creating a ৳3,000 sale. The customer pays ৳1,000 and leaves ৳2,000 due. Later, the customer returns two bulbs and the shop accepts them at the original net value of ৳300 each. Accepted return value = 2 × ৳300 = ৳600. If there is no cash refund and no replacement sale, the customer's due falls from ৳2,000 to ৳1,400. If the customer also pays ৳500 during the same visit, record that payment as a separate due collection. The closing due then becomes ৳900. If both returned bulbs pass inspection, sellable stock can increase by two units. If one is defective, only one should return to normal sellable stock while the defective unit follows the appropriate exception process. Keeping the return, due adjustment, collection, and stock decision separate makes the final balance easier to verify.
Use a consistent daily sales return checklist
A short checklist helps counter staff handle returns consistently. 1) Find the original invoice or approved sale reference. 2) Confirm the product, SKU, quantity, and return reason. 3) Inspect the item before deciding whether it can return to sellable stock. 4) Calculate the accepted return value using the relevant original invoiced value rather than today's shelf price. 5) Decide whether the financial outcome is a refund, due reduction, exchange credit, or another approved treatment. 6) Record the actual refund or collection method and reference where applicable. 7) Record stock disposition separately from the financial outcome. 8) Keep staff and approver details identifiable for exceptions. 9) At day end, compare sales returns with refunds, due adjustments, exchanges, and returned quantities. 10) Investigate any refund without a matching return, or any returned-stock movement without a matching customer transaction.
Watch for return records that no longer tell the same story
Several warning signs deserve review. A refund exists but the related sales return cannot be found. A returned product was entered only as a stock adjustment, leaving sales and customer balances unchanged. A due customer returned goods but the outstanding balance did not decrease. An exchange was recorded only as a new sale, so the return credit disappeared from the trail. Damaged or incomplete products were added directly to sellable stock. Staff used the current selling price instead of the relevant original invoice value. The same product appears to have been returned twice against one invoice. Cash refund totals do not agree with approved cash-return records. Returns have no reason, invoice reference, or identifiable approver. These signs do not automatically prove fraud or a serious accounting problem, but they indicate an incomplete transaction trail. Investigate the source transaction rather than changing a closing total simply to make reports agree.
A manual sales return register can work for a small shop
A small shop can use a dedicated paper or spreadsheet return register instead of mixing returns into the normal sales notebook. Useful fields include return date, original invoice, customer or reference, SKU, returned quantity, original net value, reason, condition, refund amount and method, due reduction, exchange reference, stock disposition, staff member, and approval note. A spreadsheet can make totals easier, but it still depends on consistent entry and becomes harder to control when several people sell, collect dues, approve refunds, or adjust stock. Whatever method is used, test the process with common scenarios: a full cash return, a partial return from a due sale, an exchange with a price difference, and a returned item that cannot go back into normal sellable inventory. If each case can be traced cleanly from invoice to financial outcome and stock status, the process is much easier to review.
Where StockLedger fits in the sales return workflow
Sales returns become harder to control when the invoice is in one system, stock is changed somewhere else, customer dues are kept in a separate khata, and refunds are reviewed from cash or bank records later. StockLedger can keep retail POS and invoicing, inventory, customer dues, cash and bank activity, accounting, reporting, and role-based access within a connected business workflow. The practical benefit is traceability: staff have fewer separate places to update when one accepted return affects several records. Software still depends on a clear return policy, correct invoice selection, accurate item inspection, appropriate approvals, and disciplined transaction entry. A useful evaluation is to test the same practical cases described above and confirm that the original invoice, accepted return value, refund or due adjustment, returned-stock status, and final reports tell the same story before using the process more widely.
