Cha-ChingIntegrations
Five ways an order reaches the queue.
Whatever you sell through, the thing that lands is an ordinary order — same seven stages, same ledger, same rules about who may read the phone number.
Connected
What works today
The official OAuth flow — install from your admin, approve the scopes, done. Historical orders import and new ones arrive by webhook within seconds. Eleven topics are subscribed, including cancellation and fulfilment, so the two systems do not drift. Tokens are the expiring kind and are rotated automatically.
A consumer key and secret from your WordPress admin. Orders pull on connect and then arrive by webhook, each shop signing with its own secret rather than one shared key — so a compromise at one store is one store.
A page you own, at your own slug, with many products and a real basket. Built for traffic that never touches a storefront: an Instagram bio, a WhatsApp broadcast, a comment under a post. No payment step, because in a cash market there is nothing to charge.
The same order form, dropped into a page you already have. It runs in a browser that has never heard of Cha-Ching and has no session, which is exactly the point.
A signed REST endpoint for a storefront we do not have an adapter for. Idempotent on your own order id, so retrying a failed POST cannot create a second order.
Upload a .xlsx or .csv, or paste a published Google Sheets link. Columns are mapped once (the common call-centre layouts are recognised automatically), every row is previewed before anything is written, re-imports skip what is already in, and the sheet’s own status words — Confirmé, Pas de réponse 3, livré — land in the real lifecycle.
One click on any order opens WhatsApp with the message already written — the customer’s name, order number and total merged into templates the seller controls. The send stays human, so nothing here can spam anybody; the Business API is the roadmap for broadcasts, not for this.
Send a confirmed order to Ozon Express from the order screen on the seller’s own contract: parcel created, label returned, status synced back into the lifecycle. Beta until enough real accounts have made the round trip.
The same hand-off through Sendit: create the delivery, print the label, pull the status. Credentials are verified against the courier before anything is stored, and encrypted like shop tokens after.
No checkout required
The order form is a first-class source, not a fallback
A large share of cash-on-delivery volume in these markets never touches a storefront. It arrives as a message. Treating that traffic as a second-class input — a spreadsheet import, a manual entry screen — is how it ends up uncounted in everybody's numbers.
- Many products, one page, with a real basket and quantities
- No payment, no account, no app for the customer
- Idempotent on submission, so a double tap is one order
- Lands in the same queue as everything from your shop
Not yet
What we have not built, named
An integrations page that lists only what exists is a page that has quietly decided you will not ask. These are the gaps.
YouCan
Wanted, and blocked on their API documentation rather than on our effort. If you sell on YouCan and have developer access, tell us — that is the thing that unblocks it.
Lightfunnels, Shopify Plus checkout extensions
On the list, not started.
More couriers — Cathedis, Ameex, Forcelog, Eagle Express…
Ozon Express and Sendit are in beta above; the rest of the national carriers follow the same adapter, roughly one per week of demand. Tell us which one moves your parcels and it jumps the queue.
Payment gateways
Deliberately none. This is a cash-on-delivery product; there is nothing to charge at checkout, and a payment step on a COD form is the fastest way to lose the order.
Selling through something that is not on this page? Tell us what it is. The intake API covers most of them today, and a real adapter follows demand.