Delivery marketplaces add a second accounting system. Learn a practical 15-minute daily reconciliation workflow, how to handle price parity, refunds, and modifier hygiene, and how to keep your POS as the source of truth.

Third-party delivery didn't just add a channel. It added a second accounting system.

When a restaurant or cafe adds a marketplace delivery app, it usually starts as a growth move: new customers, new orders, new revenue. Then the first payout hits, and reality arrives. The deposit doesn't match the sales total, fees are scattered across categories, refunds look different than in-store refunds, and staff can't always explain why a customer was charged one price on an app and another price at the counter.

None of that means third-party delivery is "bad." It means you need a reconciliation workflow that treats marketplace sales like a separate channel with its own rules.

Our team recommends building a channel map first, then building a simple daily reconciliation habit. And it all starts with the POS data you control. If you're tightening up operations, use M&M POS as your system of record for items, modifiers, and taxes, and download M&M POS to trial a delivery-reconciliation workflow before you change anything live.

The three numbers that should match (and why they never do)

Most operators look at one number: today's sales. With delivery marketplaces, you now have at least three:

• Order total: what the customer paid (including app fees, delivery fees, tips, etc.).
• Merchant sales: what you actually earned for food/drink before marketplace fees.
• Payout: what hits your bank account after fees, refunds, and adjustments.

If you don't separate these, you'll spend hours chasing "missing money" that isn't missing. It's just categorized differently.

A practical reconciliation workflow (15 minutes a day)

This workflow is designed for small teams. It's not "enterprise accounting." It's a clean habit.

Step 1: Create a delivery channel bucket in your reporting

You want delivery marketplace sales to be visible as a channel, not blended into counter sales. That lets you answer questions like:

• Are delivery orders cannibalizing dine-in, or truly incremental?
• Which items perform well on delivery vs in-store?
• What is the effective margin after marketplace fees?

Step 2: Decide your "price parity" stance

There are three honest approaches, and each has consequences:

• Parity pricing: same price everywhere. Simple for customers, harder on margins.
• Channel pricing: slightly higher prices in marketplaces to offset fees. Better margins, but you need staff-ready explanations.
• Delivery-only bundles: keep item prices consistent, but create delivery combos that carry margin.

Pick one stance and be consistent. Inconsistent pricing is what triggers arguments at the counter.

Step 3: Map fees to a small set of categories

Marketplace statements can be overwhelming. Reduce them to a few categories you track every day:

• Marketplace commission/fees
• Promotions/discounts funded by you
• Refunds/charge adjustments
• Tips (if routed through the platform)

Once you have categories, reconciliation becomes repeatable.

Step 4: Handle refunds with a single rule

Delivery refunds are a special kind of messy because the customer relationship is mediated by the platform. Choose one rule and train it:

• If the platform issues a refund, you record it as a channel refund and keep notes (order id, reason, item).
• If the customer comes to your store for a remake, you treat it as a comps/voids workflow (with manager approval).

The mistake is letting staff issue in-store refunds for marketplace orders without a documented rule. That turns one incident into two different books of record.

Menu and modifier hygiene matters more on delivery than in-store

In-store, staff can clarify a question. On delivery, the customer makes assumptions. That means your menu and modifiers need to be explicit:

• Use clear modifier names (no inside jokes).
• Make default choices obvious (spice level, sides, dressings).
• Be careful with "notes" as a substitute for real options.

When delivery orders arrive wrong, the root cause is usually menu ambiguity, not staff effort.

A small-business take on "omnichannel"

You don't need a corporate omnichannel strategy deck. You need one simple principle: one source of truth for products and prices. Everything else is a controlled copy.

That's why we like to keep the POS as the hub. Use M&M POS to keep item data stable, and download M&M POS to test how your delivery channel reconciliation will work. When your hub is clean, every channel downstream gets easier.

Checklist: what to do this week

• Pick your price parity stance and document it.
• Create a daily 15-minute reconciliation habit (order totals, merchant sales, payout).
• Define one refund rule for marketplace orders and train it.
• Clean up modifiers and defaults to reduce delivery mistakes.

Delivery can be a growth engine, but only if the back office stays calm. Calm comes from a repeatable system, not from heroic end-of-night spreadsheet work.