Orbit for delivery kitchens
Check the payout against the orders, not against your memory.
Expected net per order, what the platform actually paid, and the difference in a list you can dispute.

Who it is for
Built for how delivery & aggregators actually work.
Who
Kitchens taking orders through Talabat, Toters and their own channels.
The problem today
The aggregator pays a lump sum weeks later and nobody checks whether it matches the orders that were actually delivered.
The screens only this trade gets
The tools of your trade, not a generic form.
On top of the accounting, sales, stock and people every business gets, this is what Orbit adds for your work.
Expected net per order
For every delivery order, Orbit holds what you should be paid after commission, so there is a number to check the payout against.
Payout reconciliation
When the platform pays, compare the lump sum to the orders behind it and see the difference at a glance.
A variance you can dispute
The orders that do not match come out in a list with the shortfall, so a dispute is a document rather than an argument.
Price per channel
Keep a separate price list for each channel, because the menu price on an aggregator is not the price at your own counter.
Straight about this one
Orbit checks the payout against the orders you recorded. It is not connected to the delivery platforms by API.
And the whole company underneath
This is one part of a system that runs the whole business.
The trade screens above sit on the same core every Orbit company gets, so the work and the books are never two systems.
Answers
Questions people in your trade ask.
How do I reconcile a delivery aggregator payout?
How do I account for delivery platform commission?
See Orbit on your own numbers.
Show a payout with a variance and the orders that caused it.