Grocery splitting fails when the system is implied instead of agreed. Here are the three setups that actually survive contact with real roommates, and how to fix the classic disputes before they start.
Marcus Hale
Most grocery resentment isn't math - it's mismatched assumptions. One person thinks the olive oil is communal; another bought it as theirs. So before picking a splitting system, have the ten-minute conversation: which categories are shared (cleaning supplies, paper goods, condiments, staples?) and which are personal (snacks, alcohol, special diets, that cheese?).
The shared/personal line varies wildly between houses and both extremes work fine - what fails is ambiguity. Write the outcome down somewhere visible or in the house chat. A fridge shelf or cupboard zone per person for personal items, plus one communal zone, makes the agreement physical and self-enforcing.
All groceries communal, total cost divided by heads. It's the simplest possible system and genuinely great for households that eat together regularly and have similar appetites and diets - couples-of-friends flats, households that cook shared dinners most nights.
It collapses when consumption is visibly unequal: the vegan subsidizing the carnivore's steaks, the traveler-for-work paying for groceries they never see, someone's partner effectively living in. If any of those describe your house, even-split will breed quiet resentment - pick a hybrid instead. If you do run it, log purchases in a split app as you shop and settle monthly.
The most popular real-world setup: split only the true commons - cleaning products, paper goods, oil, salt and spices, condiments, maybe bread, milk, and eggs - and everyone buys their own actual food. The shared list is small, cheap, and uncontroversial, so the splitting stays frictionless.
It suits houses with different diets, schedules, and budgets - which is most houses. Run it with a shared shopping list (any shared note app): whoever's at the store grabs what's on it, logs the amount, and the app keeps the running balance. The key discipline is keeping the staples list short and explicit; scope creep ('I assumed the nice coffee was communal') is this system's only failure mode.
Everyone contributes a fixed amount monthly - say $40-60 each - into a shared pot (a shared account, a jointly-topped-up prepaid card, or literal envelope cash), and the kitty buys the communal goods. The buyer role can rotate monthly so no one becomes the permanent shopper.
The kitty's superpower is that it removes per-receipt accounting entirely: no logging, no monthly reconciliation, no 'you owe me $3.40.' Its requirement is calibration - if the pot keeps running dry or piling up, adjust the contribution. It's the best fit for stable households who want minimum admin, and the worst fit for high-turnover flats where someone moves out mid-month.
Someone eats more: don't audit portions - either move that category to personal, or accept that shared living rounds roughly even over time. Someone's partner is always over: the standard convention is that frequent guests tip their host's contribution up a notch, raised kindly and early. Someone never shops but always eats: rotate the shopping or use the kitty, which makes contribution automatic rather than behavioral.
Settle balances monthly on a fixed date - small numbers settled often stay friendly; large numbers settled rarely become loaded. And when something isn't working, renegotiate the system rather than enforcing it harder: the goal is a fed household that likes each other, and all three systems are means to that end, not ends themselves.
Splitwise is the default for logging shared expenses and auto-balancing who owes whom; any shared-list app covers the shopping list itself. For kitty systems you barely need software - a group chat message when the pot needs topping up does it.
For a staples-only system, $20-40 per person per month typically covers commons in most areas; full-share food budgets vary too much by city and diet to generalize - track one normal month and set the number from reality rather than guessing.
Settle all logged balances on their last day, and pro-rate any kitty contribution for the partial month. Communal items bought long ago stay with the house - relitigating who paid for the two-year-old pepper grinder is never worth it.
Not if the house agreed on personal zones - labels and shelf assignments are just the agreement made visible. What's rude is the ambiguity that makes labels feel hostile. Set the shared/personal line together and labels become logistics, not accusations.
