Pantry Supply Across Cities: What a Bangalore Vendor Can and Cannot Cover

One supplier can standardise your pantry across four cities on paper — the SKU list, the approval flow, the reporting format, the review cadence — and in most cases it still cannot put the perishable shelf into all four offices itself. The reason is physical rather than commercial: pantry supply is a weekly vehicle on a planned route, not a parcel. OfficeSmart's pantry service is built around Bengaluru delivery; the lines that run pan-India and internationally are corporate gifting and branded merchandise, which are shippable goods. So if your head office is in Bangalore and you have floors in Hyderabad, Pune and Gurgaon, the multi-city pantry question is a procurement-design question before it is a vendor-search question. Here is how the two parts separate.

Why does pantry supply not travel the way corporate gifting does?

Compare what each line actually moves. Gifting and merchandise are produced or assembled in Bangalore — kits at a 30,000 sq ft Hulimavu warehouse — and then go out as one shipment: 2-3 day delivery pan-India, international courier to 30-plus countries, 100-unit MOQs on printed merchandise. One order, one dispatch, one tracking number, and nothing in the box cares how long it sat in transit.

The pantry shelf is the opposite shape. Fresh fruit runs daily or three times a week. Water is 20-litre cans, with empty-can pickup part of the service. Milk is a cold chain measured in hours. The standing weekly order lands on a fixed day because your office sits in a planned Bengaluru route, and buffer stock is held for your office specifically so a spike on your floor is not a two-week wait at a distributor. When something runs out mid-week, a WhatsApp photo of the empty shelf gets a refill within four hours during office hours across the Bangalore metro area, and a WhatsApp before noon gets same-day delivery in the metro inner ring and the major tech parks — Manyata, Bagmane, ITPL.

None of that is a courier promise. It is a depot, a vehicle, a driver who knows your dock, and a buyer who can replace a short-dated carton the same morning. That capability is built city by city, which is why "national pantry supplier" means something very different from "national gifting supplier" even when the same company offers both.

What can one supplier actually standardise across cities?

Quite a lot, and it is the part worth paying for. What centralises cleanly is everything that is a document rather than a delivery:

• The specification — the agreed SKU list, the brands, the pack sizes, and which lines are allowed to vary locally. Tea, coffee, sugar, biscuits, namkeen, chips, chocolates, juice and water are the same categories everywhere; the brands people actually drink are not.
• The sizing method. Size from the attendance pattern, not headcount: a 200-person office in the building three days a week consumes like a 120-person one. Fixing that method once, centrally, prevents the same wrong first order in every city.
• The approval flow — who raises an order, who approves it, and who is allowed to trigger an emergency refill. Name both roles per office, in writing, on day one.
• The reporting format. A consumption dashboard showing real-time usage and month-over-month trends, with maker-checker approval on orders and downloadable itemised bills, comes with pantry supply in Bangalore. Insist the other cities report in the same shape even when a different vendor produces the numbers.
• The review cadence — a monthly look at actuals against the standing order, and a quarterly prune of lines nobody is eating.

What should you ask a national pantry supplier before you sign?

These six questions separate a supplier with real multi-city operations from one that has a sub-contractor list, and the answers are worth getting in writing on the quote rather than in a call:

1. Which cities do you deliver pantry in with your own vehicles and your own buffer stock, and which are served by a local vendor you appoint? Both answers are acceptable; only one of them is what most offices assume they bought.
2. What is the emergency response in each city, stated separately? A four-hour refill is a metro-area promise, not a national one. Ask for the number per city and expect it to differ.
3. Is fresh fruit in scope in every city, or only the packaged shelf? Fruit is the line most packaged-goods vendors cannot do, and the usual reason an office ends up with a second pantry vendor anyway.
4. Who supplies water, and on what cycle — including empty-can pickup? This is the line most likely to stay local no matter who holds the contract.
5. What does "one invoice" mean here: one document covering all cities, or one per city consolidated into a statement? Ask finance which of those they can actually close a month with.
6. What happens when a city vendor changes? You want the specification and the consumption history to survive that, not restart.

How do you run the Bengaluru leg and the other cities together?

Make Bengaluru the reference implementation and port the document, not the vendor. The Bangalore sequence is short enough to finish before you negotiate anything nationally: a free pantry audit at the office that maps what you consume and which vendors you run today, a custom rate card within 48 hours, initial stock inside 72 hours, and the weekly schedule starting the following Monday on a fixed day you choose. The audit is the step worth taking seriously, because it is the only point at which somebody counts your consumption instead of estimating it — and that count is the artefact the other cities need.

Then look at how far the service gradient already runs inside one city. Weekly delivery covers all of Bengaluru, Whitefield and Electronic City included; what changes across the city is the same-day response, not the weekly one. If a gradient that steep exists within Bangalore, plan for a steeper one across four cities: deeper standing orders in the offices furthest from a depot, and the four-hour refill treated as a bonus rather than a control.

What breaks first on a multi-city pantry contract?

• Expecting the Bangalore response time everywhere. The branch office that was promised same-day and gets next-week is where the contract loses its credibility, usually in month two.
• Fruit, milk and water quietly dropping out of scope in the smaller cities, so the local admin starts buying them on petty cash and the consolidated spend number becomes fiction.
• Scope creep in the other direction. Pantry supply is consumables — what gets eaten, drunk and replaced. It is not housekeeping labour, deep cleaning, equipment servicing or fit-out. Those may sit on the same account, but ask for them explicitly rather than assuming them into pantry scope.
• Nobody named as the approver in the branch office, so orders route back to a Bengaluru admin who cannot see the shelf.
• Monsoon and dock reality. Tech-park gate passes, service entrances and a narrow delivery window do more to delay a refill than distance does, and they are different in every building.

When is a single national pantry supplier worth it?

When you have a small number of large offices, standardising is worth real money and real admin hours. When you have many small ones, the honest structure is usually local vendors against a central specification — one document, several routes — with the reporting format mandated rather than the vendor. And if one office holds most of your headcount, run that office properly first: it is the majority of the spend, the majority of the complaints, and the template for everything after it.

One last split worth keeping straight. If what you want is every employee in every city receiving the identical thing, that is a gifting or merchandise order, not a pantry order — those lines are built to be produced in Bangalore and shipped pan-India or internationally. The pantry shelf is built to be local, and the right ambition for it is a common specification with a reliable route under each office, not one truck doing four cities.