External channels

Menu: Setup → Channels · Reporting → Channel settlements · Who: owner

Foodpanda, Bykea, your own website — the food is made in your kitchen, the tax is filed by you, and the dish appears in your food cost. An order that came from somewhere else is still your sale. So it is an ordinary order with one extra fact on it, not a second kind of order.

Two different questions

A Foodpanda order typed on the counter till is source POS, channel Foodpanda. Neither is folded into the other, or whichever question was asked second would be lost.

Setting a channel up

Setup → Channels. Your own list — write a new one the day an aggregator opens in your city, no waiting on us. Writing a name that was deleted brings it back with its orders still on it; a channel orders point at is switched off rather than deleted.

Why the payment method matters more than the dropdown

An aggregator collects from the customer and remits later. Rung as cash, your drawer would be expected to hold money the platform is holding — short by exactly that amount, every single day, with the cashier standing over it.

So Credit — owed to us means money you have earned that somebody other than the customer in front of you owes. The drawer stays honest with no new arithmetic anywhere.

The method picks the tax rate, exactly as it always has. A platform that charges the customer's card is set to Card and files at the card rate; one that hands over cash-on-delivery takings is Cash. Cash + settles later is refused — a drawer cannot both hold the money and not hold it.

What commission is charged on is your contract's business, not ours. Guessing it would make every figure in the settlement report quietly wrong for half the shops.

Ringing a channel order

Pick the channel on the till like any other id. The server fills one payment row for the whole total at the channel's method — nobody types a figure and the cash/card question is never asked.

A dine-in order refuses a channel. Nobody sits down at a Foodpanda table, and the till would settle it as the platform's money while skipping the hold that occupies the table. The POS hides the control and the API refuses it.

A channel order is completed, not left open. The food was made and handed over; the sale is real. What is outstanding is not the order, it is the payout.

What the order remembers

The commission rate and the amount, snapshotted. A rate renegotiated in June must not rewrite what March was owed.

Their order number goes in channel reference, so a dispute is traceable from day one.

Settlements — what the platform actually paid

Reporting → Channel settlements. Pick the channel and the period, and Sellify claims every unsettled order on that channel inside it. You type one figure — Payments received.

Still owed across every channel is on the same page.

An order belongs to at most one settlement. Deleting a settlement releases its orders rather than stranding them — so a wrong period is corrected by doing it again, not by editing history.

The reports

• Channel sales (Sales) — orders with no channel are the Counter row rather than a missing one, so you can read what came through your own door against what came through somebody else's, on one page.
• Channel settlements (Money)

What is not in Sellify yet

• A per-channel price list. Rates are the same as the counter's. It is a real thing aggregators do and it is a job of its own.
• An API integration. Entry is manual today. When we build it, it will write the same rows this screen writes.