While the dining room is full, three online orders arrive on the tablet, and the kitchen gets stuck in two rhythms at once. The evening register revenue looks high, but after deducting commissions and delivery costs, the net profit shrinks.
The dining room, takeout, and platform orders sell the same product, but their prices, delivery times, and costs differ. Pooling all channels together masks profitability.
In this article, we covered channel differences, price and commission management, kitchen prioritization, inventory impact, and profitability reporting.
Table of Contents
Why are channel differences important?
Each channel has different customer expectations, packaging needs, and time pressure. Processing the same menu in the same way reduces service quality.
Dine-in orders depend on the table experience, whereas delivery orders depend on warmth at the door and packaging. Operational rules must be separated accordingly.
Reading revenue without channel breakdown conceals which line is truly profitable. Growth decisions might shift toward the wrong channel.
We covered the table and flow logic of the dining room side in the dining room and table management article.
The channel definition must be clear at the very first moment of the order; correcting it later ruins reports. The source field should be mandatory.
Channel-based pricing
Takeout and platform prices must cover commissions and packaging costs. Directly copying the dine-in price erodes the net margin.
Price lists must be kept by channel and versioned with dates. We covered this topic in the price list management article.
Promotions and discounts must specify which channel they apply to. A blanket discount reduces the profit of a profitable channel by the same margin.
Recipe cost is the lower limit of the channel price; the margin after commissions must also be checked. We broke down the math in the recipe cost article.
Menu item visibility should be adjustable by channel; not every product needs to be offered on every channel. Operationally difficult products can be restricted.
Commission tracking
Platform commissions inflate revenue and squeeze profit; if this difference is not reported, management is misled. Gross revenue and net proceeds should be on separate lines.
Commission rates can vary by platform and campaign. If rate definitions are not kept up to date, profitability calculations will drift.
Payment reconciliations must be periodically compared against order lists. Short or excess deductions accumulate silently.
Product margins after commissions drive decisions on menu removal or price updates. If a high-volume product leaves a low net margin, it is an alarm.
Channel net revenue should be added to the executive KPI set. We discussed this in the daily KPI set article.
Kitchen prioritization
If dine-in and delivery orders get mixed on the same screen, time targets will clash. Channel tags must be visible on the kitchen display screen.
Preparation and packaging steps are added for delivery orders, extending the time calculation accordingly. The delivery line must be managed without disrupting the dine-in pace.
During peak minutes, prioritization rules must be in writing; it should not be left to each chef's preference. Rule clarity shortens debates.
Kitchen Display Systems (KDS) make this distinction practical and visualize the order rhythm. We explained the details in the KDS article.
Readiness time must be reported by channel. A channel with chronic delays calls for a menu or capacity decision.
Inventory and packaging materials
Takeaway service consumes boxes, bags, and sauce packets along with product inventory. These materials must be included in cost and inventory counts.
Channel-based sales clarify how much of which product is consumed. The inventory plan should not rely solely on dine-in forecasts.
Packaging waste and incorrect packaging records must be kept. These invisible items quietly eat away at the takeaway margin.
The foundation of inventory discipline is discussed in the inventory control article.
When a critical product runs out, the relevant channel should be able to close automatically. Taking orders without stock generates returns and loss of rating.
Profitability analysis
Channel profitability is established with selling price, recipe cost, packaging, commission, and return items. A single turnover column is not enough.
Channel distribution by time slot also affects staffing plans. Lunchtime takeaway density and evening dine-in density require different resources.
Return rates should be tracked specifically per channel; takeaway returns may stem from products or logistics. Solutions cannot be produced without isolating the root cause.
You can also see the logic of waste and spoilage with a retail example in this article.
Before scaling a low-profit channel, a price or menu reduction should be considered. Volume growth should not amplify losses.
Personnel and authorization
Order acceptance, cancellation, and return permissions should be separated by role. Allowing everyone to perform every transaction generates loss and disputes.
We explained permission setup in the user permissions article.
Delivery confirmation must be clear in courier or platform deliveries. Unclear delivery records inflate customer complaints.
Channel summaries must be checked at shift closing. We covered this topic in the X/Z report article.
Channel procedures must be explained separately in training; dine-in habits mask takeaway errors. A short checklist is enough for new staff.
Reporting
Daily channel turnover, net revenue, average basket size, and duration metrics must stand side by side. Relying on a single metric leads to misoptimization.
Product × channel breakdown shows which dish performs well on which line. Menu layout is streamlined accordingly.
Weekly trends separate seasonal campaign effects from anomalies. A single day's peak should not be considered a strategy.
We summarized the restaurant management framework in this guide.
The kitchen, cashier, and management should review the report together. When channel decisions are made at a single table, execution succeeds in the field.
Together with your existing system
EQLEM is a solution platform; it does not replace your existing ERP or accounting system. Channel operations remain in the field, while financial records stay in the current system.
Sales documents can be summarized and transferred to Mikro or Logo, ending dual data entry. We covered this topic in this article.
Connection to the existing system on the local network is established with an on-prem component. We explained the architecture in the on-prem agent article.
The web experience is mature for restaurant scenarios, while the mobile side may remain partial in certain flows. Cash register software and firmware are out of scope.
Scope must be validated based on the platform integrations you use and your current system version. Instead of general promises, your specific setup is evaluated.
Points to consider
Opening all channels at once overwhelms the kitchen; expand gradually according to capacity. The line with the highest net margin should be grown first.
Saying "turnover has increased" while ignoring commissions is misleading. Net revenue and product margin must be the basis.
Do not sacrifice the dine-in experience for delivery speed; loyal table guests generate long-term value. Establish the balance consciously.
Do not exclude packaging and waste costs from the menu; delivery profitability is hidden there. Check out the waste tracking article.
The scope must be confirmed according to your business. Every platform and every cash register scenario is not the same.
Frequently asked questions
Should dine-in and delivery be at the same price?
Generally no. Commission and packaging costs should be reflected in the delivery price.
How should commissions be reported?
Gross turnover and net revenue must be kept separate. Product and channel breakdowns should also be visible.
Do I need to change my current accounting system?
No, it is not necessary. EQLEM works alongside your existing ERP system.
How should the kitchen prioritize orders?
Channel tags and time targets should be visible on the screen. Written prioritization rules must be applied.
Delivery and online channels increase turnover; if not managed properly, they thin out net profit. Channel segregation makes this balance visible.
Adjust prices according to commission and packaging; do not blindly copy the dine-in menu. Margins must be tracked on a per-channel basis.
Without channel tags and priority rules in the kitchen, delivery time targets will conflict. Set up your screens and procedures accordingly.
Look at net revenue rather than gross turnover in reports; otherwise, you will grow the wrong line. The product × channel breakdown drives decisions.
It is possible to accelerate channel operations while protecting your current financial setup. Clarify the scope according to your own platform and kitchen capacity.
By consulting with the EQLEM team, you can clarify your delivery service and channel management scope.