What we build

Where ecommerce money goes missing between the sale and the remittance

The order was placed on Monday, dispatched on Tuesday, refused at the door on Thursday and paid for by the courier a fortnight later, minus deductions nobody checked.

The day, from the order list to the courier pickup

AI automation for ecommerce is mostly reconciliation and inbox work rather than anything clever. Orders from the website, Instagram and the marketplaces become one list. The courier remittance is matched line by line against what was dispatched, so deductions and refused parcels stop passing unchecked. Customer messages land in one place, and the owner gets a short daily report that shows what each order actually earned.

Where this has actually run. Wobble runs the full system behind Emraan Rajput in Pakistan, which has carried 2.46 million lifetime impressions and 68,000 clicks at a 2.76 percent click-through rate. See the work, with the numbers.

An online store here runs on a rhythm that has almost nothing to do with the software it was sold. Somebody opens the laptop in the morning and pulls the overnight orders from the website. Then they go through the Instagram DMs and the WhatsApp thread and add the orders that arrived there, which do not have order numbers because nobody generated one. Then the marketplace panel, which has its own rules and its own labels.

That combined list becomes the day. Confirmation messages go out before anything is packed, because cash on delivery means an unconfirmed order is a coin toss with the shipping cost attached. Packing happens against a printed list. Labels get printed, the courier booking is made, and everything has to be sealed and stacked before the pickup rider arrives in the late afternoon. Miss the pickup and the whole day ships tomorrow.

In the evening the owner looks at the ad account, decides what to spend tomorrow, and answers the messages that came in while the packing was happening. The week ends with a remittance file from the courier and a sack of returned parcels that nobody has time to open. That is the operation. Any automation that does not fit inside that shape will be abandoned in a fortnight, whatever it does in a demo.

Nobody knows what an order earned until the courier pays

This is the structural difference between running a store here and running one in a card paying market, and it is the reason so many stores grow while quietly losing money. The advertising is paid for today, upfront, in advance of anything shipping. The goods go out tomorrow. The courier remits the collected cash on its own cycle, which is measured in weeks. The refused parcels come back later still, and only some of them are in a condition to sell again.

So the number on the advertising dashboard is not profit and it is not close to profit. It is revenue on orders placed, before refusals, before the courier's cash handling deduction, before weight discrepancy charges, before return shipping on the parcels that came back, and before the pieces that came back creased. A campaign can look like the best one you have ever run and be the one that cost you the most.

Reconciliation is therefore the highest value thing to automate in a store of any size, and it is almost never the thing that gets asked for. Match every remittance line to a dispatched order.

Flag orders that were dispatched and neither remitted nor returned, because those are parcels that have disappeared and the window to claim them is short. Flag deductions that differ from the agreed rate card. Attribute returns back to the campaign and the product that generated them, so the ad decision on Thursday evening is made with the real number.

The reconciliation nobody runs

Take last month's dispatched orders. Subtract what came back, the return shipping, the cash handling deduction and any weight adjustments. Compare what is left against what the ad dashboard reported for the same month. If those two numbers are strangers to each other, you have been making spending decisions on the wrong one.

Three people, one number

Most stores at this size share one WhatsApp number between two or three people, plus the owner, who answers from her own phone at eleven at night. A customer therefore gets three different answers to the same question about a return, and nobody can find out later who promised the discount that is now being argued about.

The fix is not a bigger bot, it is ownership. Conversations get assigned, replies carry a record, notes attach to the order rather than living in the head of whoever was on shift, and a message that has been open for two hours without a reply becomes visible to a supervisor instead of quietly ageing. The automated layer sits on top of that and handles the questions that repeat.

There is a second reason to get this right that has nothing to do with service quality. The number is an asset of the business. When it lives on a staff member's personal phone, the conversation history, the customer relationships and sometimes the number itself walk out with them. Accounts in the company's own name, with the business holding the administration, is the difference between a system you own and a system you are borrowing from an employee.

A shared inbox with no owner is not a support system. It is four people apologising for each other.

One order record, or four versions of the truth

Orders arriving through a website, a DM, a WhatsApp thread and a marketplace are the same commercial event in four different shapes. If they never become one record with one identifier, everything downstream is manual forever: the packing list is assembled by hand, the stock count is a guess, the customer who ordered on two channels is treated as two people, and the remittance cannot be reconciled because there is nothing consistent to reconcile against.

Consolidation is unglamorous plumbing and it is the prerequisite for everything else on this page. Every order gets an identifier at the moment it is accepted, including the ones that arrive as a voice note. That identifier goes on the label, into the courier booking, into the customer conversation and into the remittance match.

Stock accuracy is the other prerequisite, and it is the one that punishes stores that skip it. A single piece listed on a website, a marketplace and an Instagram post can be sold three times in an afternoon. Automating customer communication on top of unreliable stock means confidently telling three people that their order is on its way, which is worse than telling nobody anything, because an automated wrong answer travels further and faster than a manual one.

The five minute report the owner will actually read

Dashboards fail in small ecommerce businesses because they are built for someone with an hour and a question. The owner has neither. What works is a short daily summary that arrives on the channel she already reads, showing yesterday against the day before, and a weekly version that adds the money.

Daily: orders received, orders confirmed, orders dispatched, orders that failed confirmation, messages still unanswered. Weekly: delivered, returned, remitted, deductions, ad spend, and contribution per order after all of it. Nothing else, until somebody asks for something else.

The order of building matters as much as the list itself. Consolidation first, because nothing works without it. Then confirmation before dispatch, which protects margin directly. Then reconciliation, which tells you the truth about what you are selling. Then the shared inbox with ownership. Reporting last, because a report built on unreliable underlying data is a faster way to be wrong.

Prepaid markets, where the number that goes missing is a different number

Everything above assumes cash on delivery, because in Pakistan it usually is. Take the same store to the Gulf, Europe, Australia or North America and the money question changes rather than disappears.

In a prepaid market the payment processor settles on a published schedule, so nobody waits on a courier remittance to find out what an order earned. The number that goes missing sits after the sale instead. Online orders carry a statutory cooling off period in the European Union and the United Kingdom, and generous return windows are normal elsewhere, so the refund, the return shipping and the restock decide whether a month was profitable. Reconciliation moves off the courier statement and onto the returns queue.

Tax has to be in the order record from the first day rather than added later. VAT in the Gulf, the United Kingdom and the European Union, sales tax that varies by state in the United States, GST in Australia and Canada. Bolting a tax field on afterwards means rebuilding every report that has already run.

Order updates go by WhatsApp in Pakistan and the Gulf, and by email with SMS for shipping events in the United Kingdom and North America, where Meta excludes the United States and Canada from business-initiated WhatsApp calling. One order record is still the rule. What changes by market is which systems are allowed to write to it.

When the store is too small for this

A store shipping a handful of orders a day does not need any of this. One person can hold that entire operation in their head and will do it more accurately than a system, and the money is better spent on photography and acquisition. Automation earns its cost on repetition.

If the unit economics are already negative, automating the operation makes the losses arrive more efficiently. Reconciliation will tell you this, which is useful, but it is worth being honest that the first project might be a pricing and product decision rather than a technology one.

If everything is sold through a marketplace that owns the customer relationship, much of this is out of reach. You cannot consolidate a conversation you are not allowed to have, and the more valuable project is usually building a channel the business owns before automating the one it rents.

And if nobody in the business is willing to enforce the discipline of an order identifier and a stock update, the system will drift out of line with reality within a month and everyone will go back to the spreadsheet. That is a management decision made before the first workflow is built, not a feature that can be bought.

Common questions

What should a Pakistani online store automate first?

Consolidating orders from every channel into one record with one identifier, because everything else depends on it. After that, confirming orders before dispatch, which directly reduces the cost of refused cash on delivery parcels, and reconciling courier remittances so the business knows what an order actually earned. Customer messaging automation is valuable but it sits on top of those three.

Why does courier remittance need automating?

Because it is where the money is quietly lost. Remittance arrives weeks after dispatch, with deductions for cash handling, weight adjustments and return shipping, and it has to be matched line by line against what was actually sent. Parcels that were dispatched but neither remitted nor returned only surface if somebody is looking, and the window to claim them is short.

How do we manage one WhatsApp number shared by several staff?

Assign conversations to a named person, attach notes to the order rather than to whoever was on shift, and make an unanswered conversation visible to a supervisor after a set time. Hold the account in the company's name so the history and the number stay with the business when staff change. The automated replies handle repeated questions and sit above that structure rather than replacing it.

Can automation tell us which ads are actually profitable?

It can get you much closer, by attributing returns and remittance deductions back to the campaign and product that generated the order. That turns the advertising decision from revenue on orders placed into contribution after refusals and deductions. It will not be perfect, because attribution never is, and any supplier claiming a precise figure is overselling what the data supports.

Do we need accurate inventory before automating anything?

For anything that tells a customer whether an item is available or where their order is, yes. A single piece listed on a website, a marketplace and a social post can be sold several times in an afternoon, and automated communication built on that will confidently promise the same item to three people. Fixing the stock record is the first project in that situation, not the messaging.

How is this different from setting up a Shopify store properly?

Platform setup covers the storefront, checkout and the flows attached to them. This is about the operation around the storefront: the orders that arrive outside it, the shared inbox, the courier cycle, the returns and the reporting the owner reads in the evening. Both matter, and a well configured store on top of an unreconciled operation still leaves you guessing about profit.

See where this applies to your business

The AI Readiness Call is a short, free conversation about where automation would actually pay back in your business. The call is free. The diagnosis is not.

Book AI Readiness Call