Office Pantry Par Levels: How Much Stock to Keep in Bangalore

The working answer is one refill cycle plus about a day of slack, counted item by item rather than as one number for the whole pantry. If your supplier refills on a fixed day every week, the par level for each item is simply what your office gets through in those seven days, plus a little margin for the week that runs hot. For most Bangalore offices that is a far smaller cupboard than the one they currently keep, because a shortfall no longer costs a week: on a weekly schedule you choose the delivery day, and an emergency top-up can go out the same day if you flag it before noon. Once same-day refills exist, the cupboard stops being the safety net, and over-stocking turns into cash sitting on a shelf going stale.

What is a par level, and why does a weekly refill need one?

A par level is the quantity you want sitting on the shelf at the moment the refill arrives — not the quantity you order. The order is the gap between the par level and whatever is left. Think of it as the line on the wall: the standing weekly order tops every item back up to its line, and the only thing anyone has to decide each week is whether a line is in the right place.

This matters because the alternative is what most admin teams actually do: someone eyeballs the shelves on the way to a meeting and guesses. That produces both failure modes in the same month — the office runs out of coffee on a Thursday, and three unopened cartons of a juice nobody drinks sit behind the microwave until they expire. Par levels replace the guess with arithmetic you do once and revisit quarterly.

How do you work out your own per-head consumption?

Do not go looking for an industry benchmark. Per-head pantry consumption varies so widely between a 40-person product team on Outer Ring Road and a 200-person support floor in Electronic City that any published average will be wrong for you in both directions. Measure instead — it takes two weeks and no tools.

1. Pick a normal fortnight. Avoid a festival week, an appraisal cycle, a big offsite or a month-end crunch, all of which distort tea and snack consumption sharply.
2. Count what is on the shelf on day one, by item and in the unit you actually buy — sachets, packets, cans, kilos. Photograph the shelves so you are not arguing about it later.
3. Do not restock mid-count unless something runs out, and if it does, write down the day it ran out. That date is more useful than the count itself.
4. Count again on day fifteen. Consumption is the opening count plus anything delivered, minus the closing count.
5. Halve it for a weekly figure, then divide by the number of people who were actually in the office — not headcount on the HR system. In a hybrid office those two numbers are nowhere near each other.
6. Set each par level at one week of that consumption, rounded up to the pack size you buy in.

The item that ran out mid-count is the one to pay attention to. It is telling you its old line was too low, and it is usually coffee, milk or the one biscuit everybody likes.

Which items need a bigger buffer, and which need almost none?

Treating every SKU the same is the most common mistake in a pantry list. Split the shelf into three groups and the buffer sorts itself out.

• Keep a real buffer on the things that cause a visible problem when they run out and that keep well: tea, coffee, sugar, long-life milk, water. These are cheap to hold, slow to spoil, and the only items whose absence generates a complaint within the hour. A week and a half rather than a week is a reasonable line here.
• Keep exactly one cycle of the things people like but can live without for an afternoon: biscuits, namkeen, chocolates, instant noodles, soft drinks. Over-stocking this group is where most pantry waste hides, because variety matters more than depth and a half-eaten assortment goes stale faster than a single flavour would.
• Keep almost nothing of the things that spoil: fruit, fresh milk, anything dated in days. For these, order frequency is the buffer. Shortening the cycle beats raising the line.

What do Bangalore delivery realities do to the buffer?

The city changes the arithmetic more than the pantry does, and almost all of it is about the last two kilometres rather than the distance.

• Pick a refill day and a slot that match your corridor. A fixed Monday morning slot behaves very differently on Outer Ring Road near Bellandur than it does in Indiranagar, and a mid-morning window usually beats trying to land anything at 6pm on a weekday.
• Tech parks add a gate. Manyata, Bagmane and ITPL all need a pass and a dock, and the dock has its own hours. Standing instructions with security save more time than a bigger cupboard does.
• Monsoon is a schedule risk, not a supply risk. Through the wet months the risk is a slot slipping by a few hours, which the first group's buffer absorbs. It is not a reason to double the whole shelf.
• Long weekends are the real spike. Bangalore picks up a cluster of them between August and November, and a Monday refill day plus a Monday holiday means an eight or nine day gap. Move the refill rather than raising every line.
• Same-day cover shrinks the buffer. Emergency top-ups run the same day in the inner ring and the major tech parks if you flag them before noon — and a photo of an empty shelf during office hours is usually enough to start one. A buffer sized for a week you can rescue in an afternoon is smaller than one sized for a week you cannot.

What about water, milk and fruit, which cannot be stockpiled?

These three break the weekly model, and trying to force them into it is what produces both stale fruit and an empty water station.

Water is a frequency question, not a par-level one. Twenty-litre cans run on their own daily or alternate-day schedule, with empties picked up on the same trip, so the only number that matters is how many full cans you want standing at the start of a day. Count the dispensers, not the people. Fresh milk and fruit work the same way: raise the delivery frequency and keep the line low, because the cost of a short delivery is one afternoon, while the cost of over-ordering is a bin.

Who owns the list, and when does it change?

One named person, and in practice it should be whoever already receives the delivery. Splitting the count from the receiving is how par levels quietly stop matching the office.

• Revisit the lines quarterly, not monthly. A month of data in a hybrid office is mostly noise about who happened to come in.
• Revisit them immediately on a real change: a floor added, a shift pattern changed, a team moving to three days in the office, a new coffee machine. Each of these moves consumption enough to make the old lines wrong.
• Keep one month of invoices next to the sheet. An itemised monthly invoice is the cross-check on your own counting, and because it is a single GST-compliant bill rather than eight cash bills, the quantities are actually auditable.

What does the finished sheet look like?

One page, one row per item, four columns: the item in the unit you buy it in, the par level, the current count, and the order quantity that closes the gap. Nothing else earns a column. If it fits on a page it gets used; if it becomes a spreadsheet with a tab per category, it gets abandoned inside two months and the pantry goes back to guesswork.

Once the sheet exists, the standing weekly order should match it without anyone retyping anything, and the only weekly decision left is whether any line has drifted. That is the point of the exercise: not a tightly optimised cupboard, but a pantry nobody has to think about on a Thursday afternoon.