Delivery apps and how their money reaches you

When an order comes through a third-party delivery app, the customer pays the app, not you. The app collects, deducts its commission and any fees, and remits the balance to your bank on its own schedule. Your card processing is not involved, your terminal never sees the transaction, and the money arrives as a lump sum that has to be unpicked against an invoice-style statement.

That structure creates three practical problems: reconciliation, timing, and who owns the customer relationship when something goes wrong.

How do you reconcile it?

Against the app's own statement, line by line, at least monthly. A deposit that arrives as one figure covering dozens of orders minus several deduction types cannot be checked against your register without doing the work.

Most stores discover on the first careful pass that some orders were refunded without their knowledge, some fees were charged that they did not expect, and the commission rate on some orders differs from the headline. None of that is necessarily wrong; all of it needs to be seen.

What about the timing?

Remittance runs on the app's cycle, commonly weekly, which is slower than card settlement and much slower than cash. A store with a meaningful share of delivery volume has moved part of its revenue onto a longer cycle without necessarily noticing.

Plan for it the way you plan for card funding timing generally. The problem is not the delay, it is a delay nobody budgeted for.

Who handles a customer dispute?

The app, usually, and often without asking you. Refunds for missing items, late delivery or quality complaints can be issued by the platform and deducted from your remittance. Your ability to contest varies by platform and is generally weaker than a card chargeback process.

That is the trade for the order volume. Know the refund terms before you sign, and check your statements for deduction patterns rather than assuming the platform's judgment is always right.

Does any of this touch your merchant account?

Not for the platform's own orders, which is why delivery volume does not appear in your processing statements. It matters if you also take direct orders on your own channel, where the payment does run through your processor and behaves like an ordinary card-not-present sale.

A store running both should keep the two separate in its books. Blending platform revenue and processed revenue produces a sales figure that reconciles to nothing.

What should a store watch?

Four numbers, monthly. Gross platform sales, total deductions, net remitted, and refunds issued. The ratio of deductions to gross is the number that drifts, because fee structures change and nobody sends a notice that lands in front of an owner.

The second thing to watch is item-level margin. Platform commission on a low-margin item can exceed the margin entirely, which means the order loses money on purpose. Pricing for the platform separately is normal practice and worth doing deliberately.

Is it worth it?

It depends on whether the orders are incremental. Orders from customers who would otherwise have walked in cost you the commission for nothing. Orders from customers who would not have come at all are new revenue at a lower margin, which is a perfectly good trade.

Nobody can separate those two for you from outside. A quarter of data, with walk-in traffic tracked alongside platform volume, gives you a real answer rather than an assumption.

Watch the direction as well as the level. Platform volume rising while walk-in falls is the signal that matters most, because it means you are paying commission on customers you already had.