Selling
Returns that can't be sold again by mistake
The return reason decides where the unit goes. Refunds are capped at what the customer actually overpaid.
In short
LaptopERP records warranty on every sale line and handles returns as refund or replacement. Units returned as defective, not as described, or under warranty are held for the supplier and can't be sold; refunds are limited to what was overpaid after the credit, and returns count in the month they happen.
How it works
Open a return on the sale line
Pick the reason.
[SCREENSHOT: return reason]Refund or replacement
[SCREENSHOT: refund or replacement]Complete it
The refund is sized automatically.
[SCREENSHOT: refund sized]Faulty unit to the supplier
Send it back, then receive the replacement.
[SCREENSHOT: supplier return]
What's included
One return per line; nothing moves until it's completed
The reason decides where the unit goes
Refund cap
Return fee
Locked refund records
Repeat warranty replacements
Returns count in their own month
Credits follow invoice edits
Supplier returns
Receive replacement (new serial linked, supplier balance unchanged)
Back to stock
Website order cancellation asks why
Worked example
A refund can't exceed what was overpaid
An invoice of ৳50,000, with ৳20,000 paid. The customer returns a ৳15,000 item.
Refund allowed: ৳0. The cashier can't refund cash the customer never overpaid.
- Invoice৳50,000
- Returned item−৳15,000
- Already paid−৳20,000
It's held for the supplier and can't be sold. Units returned as defective, not as described or under warranty all go there.
See how it fits your shop
Tell us how you run stock, sales and branches. We'll show the workflows that match, and be straight about what isn't built yet.