Make Food the parent category and give it children such as Groceries, Eating out and Food delivery. That way one tap on the parent shows total food spending, and one tap on a child shows exactly where it went. Two levels is enough for almost every salaried household; a third level mostly creates arguments about where a row belongs.
Why does one Food category hide the real problem?
Say your monthly food spending is ₹24,300. That number alone does not tell you whether the issue is the weekly vegetable run or the number of late-evening orders after a long day in the office. Split it into ₹14,200 on groceries, ₹6,400 on eating out and ₹3,700 on delivery apps, and the second and third lines become visible. Check: 14,200 plus 6,400 plus 3,700 is 24,300.
A flat list of categories cannot do this without becoming long. A tree keeps the top level short, so your reports stay readable, and hides the detail until you ask for it.
A starter tree for a salaried person in a metro city
| Parent | Children | What goes in |
|---|---|---|
| Food | Groceries, Eating out, Food delivery, Office canteen | Kirana, vegetable vendor, supermarket; restaurants; delivery apps; daily lunch at work |
| Home | Rent, Maintenance, Utilities, Household help | Monthly rent, society charges, electricity, gas, maid or cook |
| Travel | Commute, Cabs, Trips | Metro card top-ups, daily cabs, holidays |
| Health | Doctor, Pharmacy, Gym | Consultations, medicines, membership |
| Money | EMI and loans, Insurance, Savings | Loan debits, premiums, transfers to goals |
Five parents is a good start. You can add Shopping, Subscriptions and Family later, once real rows show you they are needed.
How do you decide where quick-commerce orders go?
Metro life brings a grey area: a ten-minute delivery app that sells both milk and ready-to-eat snacks. A workable rule is to follow what was bought, not who sold it. If the basket is mostly staples, it is Groceries. If it is a late-night meal, it is Food delivery. When you cannot tell, pick Groceries for the first time and let the amount settle it afterwards: a ₹180 order for two items is rarely a weekly shop.
What are the steps to set it up?
- List your last two months of food-related rows and notice which merchants repeat.
- Create the parent Food, then add each child under it.
- Move every existing food row under the right child, starting with the biggest amounts.
- Give each child its own colour, or let the children share the parent's colour family, so charts are readable at a glance.
- Set a monthly limit on the parent, not each child, until you know your pattern.
SpendixAI supports custom categories with sub-categories and a colour for each, so the structure above can be built there directly. Each sub-category can also carry settings such as a GST rate or a tax-deductible flag, which is useful if some of your spending is work-related; those figures are estimates, so check them against invoices and with your CA.
When should you add a child, and when should you stop?
Add a child when you have asked the same question twice and could not answer it from the existing categories. For instance, if you twice wondered how much goes on weekend dining versus weekday lunches, split Eating out into Weekend dining and Office lunch. Stop when a child gets fewer than about three rows a month. Below that, merge it back into its parent; reports with twenty tiny slices are harder to read than ones with six.
Review checklist after a month
- Every row has a child, not just a parent.
- No child is empty or has only one entry.
- The sum of the children equals the parent in the report.
- The biggest child is the one you expected.
- Colours differ enough that two neighbouring slices are easy to tell apart.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

