FIRST-MONTH CONTROL ROOM

Your first 30 days on Zomato or Swiggy

The first month should answer more than “how many orders did we get?” Track demand, payout retention, promotion spend and item contribution together. That makes it easier to tell a launch problem from a pricing, menu, advertising or operating problem.

Interactive first-month snapshot

Enter figures for exactly the same date range. For a platform comparison, run each platform separately. Payout minus food and packaging is used here as a deliberately simple contribution view; it is not an accounting profit statement.

Average order value₹0
Payout retained0%
Sales-to-payout gap₹0
Deduction rate0%
Promotion load0%
Contribution per order₹0

Privacy: calculations run only in this browser tab. No value is saved or uploaded.

How the six outputs help

OutputUse it to askDo not assume
Average order valueAre customers buying a meal or only one low-value item?A higher basket is automatically profitable.
Payout retainedHow much of reported sales reached this settlement?The missing share is one universal commission.
Sales-to-payout gapWhich discounts, services, ads, refunds and tax movements explain it?Every rupee is an expense; timing and withholding may be present.
Deduction rateWhat share of reported sales did not reach this payout?It measures profit loss; it is the complement of payout retained and can include timing or tax movements.
Promotion loadHow much of sales is associated with restaurant-funded discount and ads?Attributed sales or ROAS equals profit.
Contribution per orderDoes an order help pay fixed expenses after the simplified costs entered?This is final net profit.

A four-week learning plan

WEEK 1

Verify the listing and order flow

Check menu accuracy, opening hours, notification reliability, preparation steps and the first order-to-bank trail. Write down any closure or operational interruption.

WEEK 2

Find demand patterns

Compare day and meal period. Separate new and repeat customers where authorised aggregate reporting is available. Do not copy or store personal customer information.

WEEK 3

Test menu economics

Cost the most ordered items and the items with the highest sales value. Compare contribution per order and total contribution—not food-cost percentage alone.

WEEK 4

Choose one controlled change

Improve availability, description, photo, combo, price or promotion based on the strongest evidence. Set a review date and success measure before making the change.

Diagnose the pattern before acting

Orders low, conversion weak

Check category, availability, item names, descriptions, images, price clarity and customer experience. Menu quality tools can identify catalogue gaps, but an improvement still needs measurement.

Sales healthy, payout weak

Reconcile identical order and settlement periods. Classify funded discounts, services, advertising, refunds, tax and adjustments before blaming one fee.

Payout acceptable, profit weak

Look beyond the platform statement: recipe yield, ingredient purchase price, packaging, waste, labour, rent and capacity can absorb the remaining contribution.

ROAS strong, contribution weak

Attributed revenue is not incremental profit. Compare the promoted orders with a baseline, then subtract funded discounts, advertising and other variable costs.

Example: why weekly context matters

Suppose the month shows 400 orders, but the outlet was closed for four dinner services in week two. A simple monthly average makes demand look uniformly weak. A day-and-meal-period table shows that dinner demand remained strong when the kitchen was open. The immediate action is to fix availability and staffing before spending more on acquisition.

Now suppose ads produced 120 attributed orders and ₹72,000 attributed sales from ₹12,000 spend, a reported 6× ROAS. That sounds positive, but it is not yet profit. If many of those customers would have ordered anyway, or if discount, platform charges, ingredients and packaging consume the basket, the incremental contribution may be small. Compare with a similar non-campaign period and keep the assumptions visible.

Where to get help

Listing, account or order issue

Use the authenticated Restaurant Partner or Owner app first, keeping outlet ID, order ID and the exact date ready. This is safer and more traceable than an unverified contact.

Zomato onboarding overview

Menu quality question

Swiggy’s Menu Score guidance explains how category, images and combos can support discoverability. Review the current tool inside the Owner app.

Swiggy Menu Score guide

Settlement does not match

Start with included order IDs and settlement dates, then use the platform support route for a specific unexplained entry.

Use the settlement analyser

Tax or licence question

Use official FSSAI and GST sources, then consult the restaurant’s accountant or adviser for outlet-specific treatment.

FSSAI business information

Sources and further checks

Campaign features and terms can vary over time and by outlet. Use the current authenticated dashboard and signed campaign terms as the controlling evidence.

Frequently asked questions

What is a good payout-retained percentage?

There is no universal good percentage. The result depends on the revenue basis, outlet contract, funded promotions, ads, refunds and tax movements. Use it as a trend and reconciliation prompt, not a score.

Should I combine Zomato and Swiggy figures?

Review each platform separately first because report fields, dates and commercial arrangements can differ. Combine them only after standardising definitions and retaining the original source.

Does this dashboard calculate net profit?

No. It omits fixed payroll, rent, utilities, licences and other overhead, and it assumes the payout belongs to the same included orders. Use it to locate the next question, not prepare statutory accounts.

How often should a new partner review performance?

Check operational exceptions daily, settlement inclusion when each payout arrives, and the connected dashboard weekly. A monthly review is useful after the weekly records are complete.

Next: menu and item profitBack to launch checklist