SAFE TROUBLESHOOTING · VERSION 1.3.3
Fix the specific problem, then verify the result
An empty file, a missing dish line and a failed bank match are different problems. Start with the exact message and the export index instead of repeating a large job or assuming the platform lost money.
The export will not start
“Open your signed-in partner dashboard”
Open the supported restaurant partner area in the active tab, not a consumer ordering page or the public website. Sign in through the official platform and select the authorised outlet. Reopen the extension and choose the platform matching that tab. Swiggy support is scoped to its partner food area, partner.swiggy.com/food.
“This page is showing restaurant …, not …”
The ID entered in the extension does not match outlet IDs visible on the page. Open the intended outlet first, then confirm its numeric ID and retry a small job. Do not change or hide the page to suppress the check. For Zomato advertising, the requested restaurant must also be available in the authorised advertising filters.
The button or module is disabled
Check the selected platform, active partner tab, licence state and available modules in the popup. A module can be unavailable for that platform or locked by the authorised plan. An export that is already running also locks platform switching. Use current plans and the entitlement shown in the extension, not a plan description saved from an older release. If a purchased plan is not recognised, use the official activation/account workflow; do not post an activation code publicly.
Invalid date or outlet ID
Use a numeric Restaurant / Partner ID, valid From and To dates, and a From date no later than To. Check any plan range limits. Start with a known day containing accessible records so you can distinguish a validation failure from an actually empty period.
The export finished, but data is empty or incomplete
“No records returned”
That marker is not a sales row and does not prove that sales were zero. Check the outlet, dates and date definition; verify whether the official dashboard shows the expected records to the same account. Read the Export-Index module result. If the upstream report is inaccessible, the exporter cannot create it. Retry one relevant module for a smaller known period after confirming scope.
Progress reaches 100%, but there is a warning
The progress count tracks attempted modules. Some modules can complete with warnings, while others fail. Open the index JSON, inspect each results entry, and check status, record/file counts, warnings and any error. Do not merge a partially recovered dataset into a monthly total without flagging its coverage.
Exact Zomato order items are missing
Order summaries and detailed dish responses are separate requests. A detail can remain unavailable even if the order summary was discovered. Check the item JSON's recovered/failed counts and any Order-Detail-Errors CSV. Those errors show the gaps; they are not dishes to include in item totals. A smaller rerun may help with a transient failure, but repeated rejection needs a privacy-safe support report or official platform access resolution.
Swiggy has finance amounts but no dish names
That is an implemented support boundary, not a hidden checkbox. The verified finance response used by this version does not contain item, variant or add-on lines. Do not infer item sales from order payout amounts. The Swiggy menu-category snapshot is also not a record of quantities sold. See the field reference.
The menu ignores my historical date range
Menu export is a current snapshot. The date range in the job does not reconstruct historical menus. To study price changes, keep dated snapshots you collected legitimately over time and record when each was taken.
The job is slow or pauses at a rate limit
Exact order-item collection checks orders individually and includes pacing. The exporter may pause and retry rate limits and temporary server errors. Keep the supported tab open and avoid starting overlapping jobs or repeatedly refreshing. If it cannot finish, record the exact message, stop the job through its controls if needed, and use a smaller authorised range later. Do not disable the request pacing or access checks.
Files downloaded, but I cannot find or use them
- Missing folder: open Chrome's Downloads list and check its configured location. Local outputs normally use the “Partner Data Exporter” folder. Check whether a download was blocked or awaiting a normal save-location choice.
- ZIP but separate invoice files: locally generated files can be archived, while remotely downloaded documents may arrive separately. Read the job's index/results rather than expecting every remote request inside the ZIP.
- Rupee sign or text looks wrong: import CSV as UTF-8 through the spreadsheet's import tool. Keep IDs, timestamps and free-text columns as text until you know their formats.
- More rows than orders: item exports can contain several dishes per order; payout exports can contain several components per payout. Use distinct IDs for counts and understand the grain before summing.
- Cancelled job: a partial archive may contain only files already queued. Treat it as partial, inspect its contents and do not replace your last complete raw archive.
Retain raw files unchanged and troubleshoot a copy. Do not edit identifiers, delete unknown rows or rename headers merely to make a total look plausible.
The settlement analyser rejects a file
| Message or symptom | Likely reason | Safe next step |
|---|---|---|
| Diagnostic CSV has no reliable payout breakup | A flattened source/path/value dataset is not the recognised settlement table. | Use the matching settlement JSON or original exporter ZIP. Do not invent a payout column. |
| No settlement payout JSON in ZIP | The archive contains other modules, or its expected settlement dataset is absent. | Confirm the settlements module completed and that the archive has the relevant payout JSON. |
| Unsupported file / invalid JSON | A PDF, XLSX, renamed file, modified JSON or unrelated report was selected. | Use an unchanged supported JSON, CSV or ZIP from the appropriate module. |
| Free analysis accepts one file | Several files were selected without an activated batch entitlement. | Select one supported settlement file or check your activated subscription state. |
| Selected files exceed the limit | The selection exceeds 15 MB free or 100 MB activated batch limits; ZIP expansion is also bounded. | Export a smaller settlement period; do not split or modify JSON structures blindly. |
| A cycle or amount looks incomplete | Upstream labels/structures changed, required detail was unavailable, or the wrong scope was used. | Compare with the official payout evidence and report the unrecognised structure. Do not treat missing fields as proven zero. |
If a displayed settlement amount differs from the bank, first compare the payout ID, cycle, bank-credit date and UTR context. Multiple credits, pending status, prior adjustments and time differences need evidence. A discrepancy is a question to investigate, not automatically an overcharge. The tool is educational and does not determine a restaurant's complete accounting or tax position.
Send a useful, privacy-safe support report
Email anuragpandey5957@gmail.com or use Support. Include the minimum facts needed to reproduce the problem:
- Installed extension version and Chrome version.
- Platform, module and approximate range length, such as “Swiggy settlements, one week.”
- The exact error message and whether the official dashboard shows the expected records.
- Whether the export index reports completed, warning, failed or partial output.
- File extension, approximate size and the header names if an import was rejected.
- A redacted screenshot or a tiny synthetic example of the structure, not an unedited export.
Remove passwords, OTPs, cookies, tokens, activation codes, customer names/IDs, restaurant identifiers, invoice numbers and full bank/UTR references. A support request does not need your whole restaurant dataset. If extra evidence is genuinely required, agree the limited fields and sharing method first.
These steps were checked against the version 1.3.3 validation/error paths and the current local settlement parser. They are not a claim that every upstream partner endpoint was live-tested on your account. For the workflow and exact field names, use Documentation and Export formats.