Checking access…
Validating the plan without sending settlement data.
Food Data Extractor
Choose an authorised Zomato or Swiggy ZIP, JSON or CSV. The analyser maps payouts, fees and deductions on this device, then highlights the cycles that need attention.
Validating the plan without sending settlement data.
Choose the complete exporter ZIP, settlement JSON or a tabular settlement CSV.
Run the same parser on two synthetic payout cycles. No login, subscription or partner account is needed. These figures are not actual platform fees or restaurant results.
Loading the sample replaces the displayed results. Your selected file stays on this device and is not changed; use “Run local settlement scan” to analyse it again.
Synthetic teaching example, not your restaurant data. Payout retained is a settlement ratio, not profit margin. Read the calculations and bank-matching exercise.
| Cycle | Status | Orders | Order value | Additions | Order deductions | Tax deductions | Growth | Hyperpure | Payout | Masked UTR |
|---|
Compares net payout with net order value so you can see the percentage retained after the available settlement adjustments.
Surfaces order deductions, tax deductions, growth investments and Hyperpure spend where the report provides them.
Flags estimated-versus-recorded payout differences, low retention and payout statuses that may still need checking.
The analyser identifies Zomato or Swiggy from the supported file structure and labels the result. This is an operational estimate, not accounting, tax or legal advice. Report labels and availability can change; confirm material amounts against platform invoices and bank statements.
Open a focused explanation without losing your place in the analyser.