How often do marketplaces pay restaurants?

Most marketplaces pay weekly or bi-weekly in Europe and Latin America. Exact cadence is in the restaurant's contract with each marketplace.

Does Sinqro talk directly to the marketplace's settlement API?

Where the marketplace exposes a settlement endpoint, yes — the Sinqro connector reads it on its cadence. Where only CSV exports are available, Sinqro ingests the same files the operations team used to download manually.

Can a chain see settlements per venue and per brand?

Yes. Each order carries the venue ID and the brand attribution, so settlement views aggregate at any level: per venue, per brand, per region, per marketplace, per period.

How marketplace settlements work for restaurants

A delivery marketplace charges a restaurant a per-order commission, takes its cut from the price the customer paid, and pays the rest to the restaurant on a periodic settlement — usually weekly or bi-weekly. Restaurants that operate several marketplaces end up reconciling several settlement streams against POS sales, against bank deposits, against refunds and disputes. Sinqro Data Sync replaces that monthly chase with an automated reconciliation against the live POS data.

The pieces of a marketplace settlement

A typical settlement statement has five moving parts: gross sales (the price customers paid), marketplace commission (a percentage plus fixed fees), promotions funded by the restaurant (discount campaigns the marketplace ran on the restaurant's behalf), refunds and disputes (orders refunded to the customer), and net payout (what the marketplace actually transfers to the restaurant's bank). Each marketplace formats this differently and uses different terms, which is part of why reconciliation is painful.

Why manual reconciliation is painful

The standard manual loop goes like this: download the marketplace's CSV for each week; open the POS to find the corresponding sales tickets; match each line to the right order in the POS; spot the refunds; cross-check the bank deposit; argue with the marketplace when an order is missing or a refund is misapplied. The work is linear in the number of orders and quadratic in the number of marketplaces. A chain with five venues and four marketplaces spends days per month on it.

How Sinqro Data Sync changes it

Sinqro Data Sync collects each order at the moment it lands in Order Hub, carries the marketplace order ID and the venue ID, follows the order through POS handoff (where it gets a POS ticket ID), and links it later to the marketplace settlement record when it arrives. Each order ends up with a single audit chain: marketplace order → POS ticket → marketplace settlement → bank deposit. Reconciliation becomes a derived check: 'does this settlement match the sum of POS tickets attributed to this marketplace in this period?'

The common disputes Sinqro flags automatically

Three recurring disputes account for most settlement disagreements. (1) Missing orders — the marketplace's settlement skips an order that the POS clearly fired and the customer received. (2) Misapplied refunds — the marketplace deducted a refund that was the courier's fault, not the restaurant's. (3) Wrong commission tier — the marketplace billed a higher commission rate than the contracted one. Data Sync surfaces each of these automatically by cross-referencing POS, marketplace, and bank data; the operations team only handles the exceptions.