PRODUCT DOCUMENTATION · VERSION 1.3.3
Your first reliable restaurant export
An export is useful only when you know which outlet, period and records it contains. Follow this workflow to get files you can check, repeat and hand to an authorised accountant without losing their meaning.
Understand your files
See exact field names, file naming patterns and small synthetic samples. Learn why an item row is not an order.
Read the export format reference →Resolve an export problem
Check the active outlet, sign-in session, module result and file type before repeating a job.
Open safe troubleshooting →Start with one question, not every checkbox
If the question is “Did last week's payout arrive?”, start with settlements. If it is “Which dishes sold?”, use Zomato order-level items where available. A menu snapshot alone does not show quantities sold. If you need Swiggy order money, use its order-level finance module; that is not an item-by-item food report.
| Question | Start with | Add separately |
|---|---|---|
| Which menu items contributed? | Zomato order-level items plus current menu | Recipe and packaging costs, refunds and your chosen cost scope |
| Why was the bank payout smaller? | Settlements and accessible finance/invoice evidence | The corresponding bank credit and signed commercial terms |
| What did Swiggy pay for an order? | Swiggy order-level finance | Its payout cycle and any supporting annexure |
| Did a promotion help? | Available Zomato advertising reports plus order/finance evidence | Incremental sales assumptions and restaurant-funded costs |
Use the same platform, outlet and date definition across comparisons. Order date, settlement cycle and bank-credit date answer different questions; they need not fall in the same week.
A small first export you can verify
- Install the current store package. Use the Chrome Web Store listing. The version documented here requires Chrome 111 or later. Check the installed version in Chrome's extension details; a local source folder is not proof of the version installed on your computer.
- Sign in on the official partner website. Open the restaurant dashboard yourself. Do not give anyone your password, OTP, cookie or session token. Use only an account authorised for the outlet.
- Open the intended outlet before the extension. Select Zomato or Swiggy in the extension to match the active tab. Swiggy's supported partner area is
partner.swiggy.com/food. Platform preferences and outlet identities are separate. - Enter the numeric Restaurant / Partner ID. Confirm it against the currently selected outlet, not a saved ID from another restaurant. A visible-outlet mismatch must be corrected in the dashboard; it is not a protection to bypass.
- Choose a short, valid From–To range. Start with one day or one known payout period and one needed module. Keep From no later than To. Plans and authorised modules are shown in the extension; check current plan limits before a large job.
- Select CSV, JSON or both. Choose both for your first diagnostic export: CSV is easier to inspect in a spreadsheet, while JSON retains nested source context. Selecting dates does not make the current menu historical.
- Confirm outlet authorisation and start. Keep the supported partner tab open until the job finishes. Exact order-item collection can take longer because it checks individual order details and deliberately pauses when necessary.
- Read the result before analysis. “100%” means the selected modules have finished being attempted. It does not mean that every request succeeded or every record was available.
Check the export index and completeness
The local output includes an Export-Index JSON file. Check its platform, outlet ID, From and To dates, selected modules and individual module results. A module can report completed records, warnings or a failed status with an error. Do not treat an unavailable section as zero sales or zero fees.
- Match scope: confirm the intended outlet and period before combining files.
- Read warnings: for exact Zomato items, unavailable order details can mean the recovered item file is incomplete. An accompanying order-detail error CSV may list failed order IDs.
- Check record grain: two item rows can belong to one order. Settlement files can have more than one breakdown row for one payout.
- Compare a known record: trace one accessible order or payout back to its official dashboard evidence. If definitions differ, record the difference; do not edit the raw file to make it agree.
- Preserve provenance: retain the unchanged raw archive, make a working copy and note any filters, mapping rules or corrections you apply.
When multiple locally generated files are present, the exporter can package them into a ZIP. Remote documents requested through Chrome Downloads may be separate downloads; use the export result and index rather than assuming every requested invoice is inside the archive. Downloads normally use a “Partner Data Exporter” folder under Chrome's configured download location.
From file to a decision
For example, suppose a working copy shows 120 portions of one dish sold during a week. Your recipe sheet says each portion uses ₹70 of ingredients and ₹12 of packaging. Those two cost categories total 120 × ₹82 = ₹9,840. That is not the complete cost of selling through a platform: funded discounts, platform charges, advertising, refunds and other variable costs still need the agreed scope and evidence.
Use item profitability to connect quantities and recipe costs, or settlement reconciliation to trace sales-to-cash movements. The settlement analyser accepts supported local settlement files; an order-items CSV is not a settlement file. Read its result as a reconciliation aid, not a statutory account or a verdict that a platform charged incorrectly.
Before sharing a working file, remove customer names, customer IDs, instructions and any other fields the recipient does not need. Order, payout and bank references can also be sensitive. Do not paste full exports into public community posts.
Version 1.3.3: what is and is not supported
| Platform | Implemented areas | Important boundary |
|---|---|---|
| Zomato | Exact order-level items, official-report requests/index, ratings and reviews, advertising, current menu/add-ons, settlements, finance and invoices | Some records and documents may be unavailable to the account or rejected upstream. Read module warnings. |
| Swiggy | Order-level finance, settlements/payout breakups, annexures/tax invoices, current menu categories with best-effort hours, outlet rating snapshot | No claim of exact item/variant/add-on lines from the finance response, individual review text or advertising-campaign reports. |
The extension does not supply your ingredient purchases, complete payroll, rent or full tax position. It does not unlock another outlet, change your partner records or guarantee that upstream fields will remain unchanged. If a platform changes its data format, stop using ambiguous figures and send a privacy-safe support report.
Documentation method: reviewed the version 1.3.3 exporter, popup validation and local settlement parser. Downloadable examples are intentionally synthetic; no private restaurant account was used to create them. See our editorial policy, privacy policy and acceptable-use terms.