The problem
In markets where the customer pays at the door, the order is a statement of intent, not a transaction. Nothing has been collected. Nothing is committed. The person who tapped buy at midnight may be unreachable, may have ordered twice, may have typed the address of a street that does not exist, or may simply have changed their mind — and you find out when the courier calls you from outside their building.
You pay the outbound leg, the return leg, and the handling in between, on an order that was never going to land. Every seller who has run cash on delivery at volume has the same answer: ring them first. The hard part is doing that consistently, at three in the afternoon on the four hundredth order, with somebody you can hold to a number.
How it works
No new tooling for your warehouse, no retraining your staff, and nothing moves until somebody has actually spoken to the customer.
A customer taps buy on your Shopify store, or fills in a Cha-Ching form you put in an Instagram bio. No payment is taken — there is nothing to take. Within seconds it is in the queue, deduplicated against the platform order id by a database constraint rather than a hopeful if-statement, because concurrent webhooks for one order are not a hypothetical.
An agent at the centre you hired, cleared for your shop specifically. They see the basket, your script, your standing instruction, and how many attempts they have left under the rules you set. The stopwatch starts when they dial, so the duration on the record is the duration that happened.
Confirmed, no answer, busy, callback, wrong number, duplicate, or cancelled with one of eight specific reasons. The commission for that call is written at the rate agreed with you, carrying that rate forever. A database trigger refuses to let anybody edit it afterwards — including us.
Data entry, courier, door. Cash collected and reconciled against what the courier actually remitted. Delivered, refused and returned are counted as three different things, because refusal is usually a confirmation problem and return is usually a logistics one — and a single number hides which of the two you have.
Three sides
A seller, the centre they hired, and the platform that referees between them. Each gets a portal built for the job, and the wall between them is enforced on every read rather than drawn on a diagram.
For the seller
Connect a shop, hire a centre, and see the work as it happens. Take an order back and handle it yourself whenever you want to.
For the call centre
A queue ordered by what is going cold, a workspace built for the fortieth call of the day, and the arithmetic to price the next client properly.
For the marketplace
Sellers and centres both work here, so somebody has to referee. The console reaches every record, and every edit is written down.
On the call
Who to ring, what they ordered, what to say, what they bought last time, and the buttons that end the call. An agent on their fortieth call of the day should not be navigating.
The money
Every earning event writes one row carrying the rate that applied at that instant. Nothing is recomputed from orders later, because published prices change and recomputation silently rewrites history. A database trigger refuses any update to a ledger row — not an application check that a future migration can bypass.
It is the difference between a platform a call centre will accept payment from and a spreadsheet with a login screen.
Read the guaranteesOrders without a checkout
A lot of cash-on-delivery volume never touches a storefront. It arrives as a direct message. The hosted order form handles that traffic properly: many products, a real basket, one page, no payment step and no third-party app between you and the customer.
What lands is a normal order. Same queue, same seven stages, same ledger, same rules about who may read the phone number.
See the seller portalQuestions
No. Most sellers arrive with none. You browse the directory, read each centre’s real numbers — confirm rate, delivery rate, how fast they pick up the phone — agree a rate, and both sides sign a contract you can download. You can hire more than one, and you can take an order back and handle it yourself at any point.
No. Your Shopify or WooCommerce store stays exactly where it is. Cha-Ching sits behind it and takes the orders as they are placed. If you also sell through Instagram or WhatsApp, there is a hosted order form with no payment step for that traffic.
Within seconds of the customer clicking buy. Shopify pushes a webhook, we write the order, and the call centre’s screen rings. Delay is the single biggest predictor of a confirm that never happens, which is why the queue sorts by how long something has been waiting rather than by order number.
The call centre you hired, and only the agents inside it that you have been cleared for your shops. Not other centres, not other sellers, and not agents at your own centre who work a different client. That rule is enforced in the query layer on every single read, and it is tested on every deploy as all four kinds of user.
It is recorded as Refused, which is not the same thing as Returned, and it counts against the refusal rate rather than the return rate. The difference matters: refusal is usually a confirmation problem and return is usually a logistics one, and collapsing them hides which of the two you have.
No. The product was built Morocco-first and now runs in 27 countries across 7 regions. Cash at the door is how a large share of e-commerce settles from Casablanca to Karachi to Bogotá, and the confirmation call is the same job in all of them.
Apply in about four minutes. A person reads every application, and you will hear back within one working day.
Cha-Ching