How to test a retail CRM with one partially returned order
A sale is the easy part of any retail CRM demo. Returns are harder. Our test case: one online order, two jumpers, sizes M and L. The customer keeps the M and walks the L back into a branch with the tag cut off. That one visit touches the counter, the stockroom, the refund and whoever is on shift next.

Choose a return that crosses the shop counter
Prepare the order before the call: one web order, same jumper in M and L, real names swapped for invented ones. The M stays with the customer. The L comes back to a branch in its original bag, tag cut off.
Start at the counter. The customer has the order email on their phone, maybe the card they paid with. That should be enough for the assistant to find the order, see which line is coming back and read whatever the customer already sent online. A warehouse login shouldn't be needed for any of it. Make a note every time the customer would have to tell the story twice.
Then change the request halfway. The customer now wants an exchange for the same jumper in navy. A good CRM for retail keeps the first request on record and shows the new one next to it. Watch for demos where the presenter quietly deletes the original ticket to make the screen tidy, because your colleague on the late shift will have no idea what happened.
Find the point where stock becomes sellable
A returned jumper goes through a few physical states. On the counter with no tag. On a rail in the back waiting for someone to check the seams. Folded and back on the shelf. Only the last one is stock you can sell, and the gap between the first and the last can be hours or days.
The vendor should be able to show the single action that makes the jumper sellable again. Meanwhile, a second login into the warehouse management system, say a colleague picking a web order, is useful. CRMiUS only changes stock through documents (receipts, delivery notes, transfers, counts), so any number on screen has a source. Try selling the returned L to that web order before it's inspected. For a while the shelf count and the available count may differ, and staff need to know which one to believe.
- Receive the jumper against its original order line, and leave the M line untouched. Check what the customer sees about the M.
- Move the L to an inspection location. Look at available quantity from the point of view of someone filling an unrelated order.
- Record the inspection result. The demo should show who decided and when.
- Swap the example for something that can't go back on sale, a jumper with a pulled thread for instance. Follow how it is recorded and how it stays off the next pick list.
If this is the step where your shop loses track today, send the CRMiUS team your return scenario in writing. Say which channel the sale came through and where the item physically comes back. A parcel posted to the warehouse makes for a different handover than a bag carried into a branch.
Follow the money separately from the garment
The jumper can be back on sale while the refund still waits for a manager. The opposite happens too: money back for a jumper that's heading for the bin. One green "complete" flag tells the colleague answering the customer's next email nothing useful. The money and the garment each need their own status.
Make it a partial refund, from a basket that was on a two-for promotion. How much goes back for one jumper is a policy question, so bring the policy your manager signed off and see where the system applies it and records who approved the amount. With a payment integration in the middle, the CRM should still show the refund as pending until confirmation comes back.
The finance module in CRMiUS covers invoices and payments, and the customer card keeps invoices, payments and the statement in one place; the financial CRM system page has the details. It comes with the Advanced plan. In a demo, the same example order should be used for the finance part and for the stock part. A polished presentation can easily switch to a different order in each module, and then the link between them is never tested.
Check what survives a handover at closing time
By closing the case is still open. Fine. The evening colleague never saw the customer, so ask them to read the situation off the record: navy L on hold for collection, returned L on the inspection rail, no refund due. Each of those three facts should sit in an entry they can open.
Access matters for the same handover. CRMiUS gives cashiers, store managers and buyers their own permissions, so a store sees its own work. A shop assistant may need to know that finance is handling a refund without seeing payment details that have nothing to do with the return. Where the assistant had enough to go on, and where a supervisor had to step in, shows how much training a rollout needs and how many roles a pilot has to set up.
Customer emails can go through the helpdesk, which is part of Advanced as well. An email to the support address becomes a ticket attached to the customer, with statuses Open, In progress, Answered, On hold and Closed. For a return, that thread sits on the customer card next to the invoices.
Ask for a quote against the work you just watched
Then the list of gaps, and only after that the price. Relabelling a field is trivial. Building a till integration that doesn't exist yet is real work. CRMiUS offers module configuration and team training as services, so ask for the quote to separate setup, anything that depends on another provider, and the test with a sample return before go-live.
Last step: one of your own staff runs the same partial return with the receipt and no help. By the end they know when the navy jumper is ready and where the returned one sits. Any question they had to ask goes on the gap list. Request a written CRMiUS walkthrough and say how you want the return to end, a replacement held for collection or a refund confirmed to the buyer.