Shopping

Quick commerce plus a weekly grocery shop: avoiding double counting

Track grocery spending from quick commerce and a supermarket together: one parent category, two sub-lines, and how to avoid double counting wallet and card entries.

Editorial illustration for Quick commerce plus a weekly grocery shop: avoiding double counting

When groceries come from a weekly shop and from quick-delivery apps, put both under one parent category called Groceries, give each source its own sub-line, and count each rupee only once. Then you can see the whole grocery bill and still compare what each source is used for.

Why track the two together?

If the weekly shop sits in Groceries and the app orders sit in Shopping or Food, your grocery figure looks smaller than it really is. Worse, a rise in app orders can hide behind a flat weekly shop. One parent with two children shows the sum and the split at the same time.

A structure that works

  • Groceries (parent), the total you care about.
  • Weekly shop (child), for the supermarket, kirana or mandi trip.
  • Quick delivery (child), for orders from delivery apps.
  • Optionally, item types under both: staples, fresh, snacks and household.

Keeping the source and the item type as two separate ideas lets you answer two questions: where do I buy, and what do I buy? Many trackers handle sub-categories only one level deep, so if you need both, pick the source as the sub-category and record the item type in a note or tag.

Where does double counting come from?

  1. Wallet top-ups: loading money into an app wallet from your bank is a transfer. If you count the top-up and the orders paid from it, the same money is counted twice.
  2. Credit card payments: the card bill payment from your bank is not a purchase. The purchases are the rows inside the card statement.
  3. Two records of one bill: if you type the receipt into a sheet and also import the statement, the same order exists twice.
  4. Refunds: a refund for a missing item should reduce the total, not be ignored.

The rule is simple: count the purchase once, at the point where you pay for the goods, and treat everything that merely moves money between your own accounts as a transfer.

A made-up month, compared by item type

Say the weekly shop is ₹2,300 a week for four weeks, so ₹9,200, and quick delivery adds twelve orders totalling ₹4,800. The grocery total is ₹14,000, and quick delivery is about 34 per cent of it (4,800 divided by 14,000). Splitting each source by item type gives this.

Item typeWeekly shopQuick deliveryCombined
Staples₹4,400₹600₹5,000
Fresh₹3,000₹1,400₹4,400
Snacks₹600₹1,500₹2,100
Household₹1,200₹1,300₹2,500
Total₹9,200₹4,800₹14,000

The column totals check out (4,400 + 3,000 + 600 + 1,200 is 9,200, and 600 + 1,400 + 1,500 + 1,300 is 4,800). The interesting row is snacks: the apps account for ₹1,500 of ₹2,100. That suggests the snack habit lives in the app, and a rule such as no snacks in app orders would reach most of it.

Setting it up in your tracker

In SpendixAI you can create custom categories and sub-categories, so Groceries with Weekly shop and Quick delivery fits directly. Pick the account, whether bank, card or wallet, before importing each statement so every transaction keeps the account it came from. Possible duplicate imports are flagged, which helps when a statement overlaps one you already uploaded. Add rules for your usual merchants and fix the rest while reviewing the rows.

A monthly routine

  • Import or enter all accounts used for groceries.
  • Check that no wallet top-up or card bill payment is tagged as groceries.
  • Read the parent total first, then the two children.
  • Note one change to try next month, such as moving the snack orders into the weekly list.

After three months you will know whether the apps are a top-up for forgotten items or have become the main shop, and you can budget for that honestly.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports