The dhaba is not a restaurant that happens to be beside a road. It is an institution produced by the road, in the way that a lighthouse is produced by a coast. Its hours, its menu, its prices and its architecture all follow from one fact about its customer: he is passing through, he is carrying something heavy, he has a fixed amount of money for the trip, and he does not know when he will stop next.

The word means a hut. The first ones were tarpaulin over wooden poles, on the shoulder of a highway, with charpais outside and one fire inside. The name never caught up with the buildings that replaced them, which is why a place with 150 tables and a car park the size of a football field is still called a hut.

The corridor chose the site

The strip that most people mean when they say dhaba runs along the old Grand Trunk Road — the Delhi–Ambala–Amritsar axis, now numbered NH-44, a road that has been the main artery between the Gangetic plain and the Punjab since Sher Shah Suri rebuilt it in the sixteenth century. That history matters less than the traffic count, which is extreme: national highways are about two per cent of India's road length and carry roughly forty per cent of its road freight.

A dhaba needs three things from a site and they are all about stopping distance. Cheap land, because the operation is low-margin and needs a big footprint for parking. A reason for a truck to be slow, because a vehicle at speed does not decide to eat — the classic locations are the approach to a toll plaza, the exit from a city where the highway is still congested, and, for fifty years, the state border. The border posts were the best site of all: a truck queued for two hours at an octroi checkpoint is a customer with nothing else to do. When the goods and services tax abolished those posts in 2017, it did not only speed up freight. It relocated a whole layer of the food economy.

What the customer cannot do, and what the kitchen does about it THE DRIVER'S CONSTRAINT THE KITCHEN'S ANSWER arrives at any hour the fire never goes out cannot wait for a dish food is held, not cooked to order a fixed trip allowance priced per roti, not per dish park, wash, sleep yard, tap, charpai, no clock comes back the same way a route, not a customer Every feature of the menu is an answer to a constraint, which is why the food is what it is.
The menu is a solution set. Dal held for hours, bread made to order, prices counted in rotis, and a yard with a tap — none of it is a style choice.

The menu is a schedule

A kitchen that never closes cannot cook everything to order, so it cooks a few things once and holds them. That is the origin of the dhaba repertoire: a pulse simmered for hours and improved by it, a vegetable in a thick gravy that survives reheating, a pot of tea on the boil all night. The dal is not slow-cooked because slowness is virtuous. It is slow-cooked because the pot has to be ready at four in the morning and still good at four in the afternoon, and a dish that is designed to be held is a different dish from one that is designed to be served.

The bread is the exception, and it is where the labour goes. Rotis are made to order because they are terrible when held — a cold roti is a piece of leather — and because the customer judges the place by them. This is why a dhaba has a man at a griddle and why the price is quoted per roti rather than per plate: the customer can count what he is buying, and the kitchen can adjust to how hungry he is.

The portions are large for the same reason the prices are low. A driver eating once or twice in a day needs the day's calories in one sitting, and he is spending an allowance that is set by his transporter, not by the restaurant. The economics that follow are unforgiving: low price, high volume, cheap land, family labour, and a margin that comes from turnover rather than from any single plate.

The strip becomes a destination

Then the customer changed. From the 1990s, car ownership turned a truckers' halt into a family outing; by the 2010s a stretch like Murthal was a weekend destination and the busiest dhabas were serving thousands of people a day, most of whom had driven out from Delhi for the parathas. The founding story of the strip — a tarpaulin shack in 1956 feeding drivers between Delhi and the Punjab, renamed for the founder's two sons — is retold on the menus, and it is good marketing precisely because it is true.

But a dhaba that serves nine thousand covers is not a hut with a fire. It is a food factory with a car park, and the constraints that shaped the original menu have stopped binding: the customer now arrives by choice, at a predictable hour, in a car, and he is willing to queue. What survives is the vocabulary — the charpai, the steel tumbler, the white butter, the name — and the food, which turns out to be good in its own right and not only as a solution to a scheduling problem.

What the expressway did

The bigger change is upstream of the customer. Access-controlled expressways do not let you stop. A road with no at-grade junctions has no shoulder to build a shack on, no village lane to turn into, and no reason for a truck to slow down; the state has responded by planning service areas instead — several hundred sites, of which a few hundred have been awarded and only about a hundred are running. Those sites are leased for fifteen to thirty years on a minimum guarantee plus revenue share, which is a completely different capital structure from a family that put up a tarpaulin on land it already owned.

So the dhaba is being sorted into two futures. On the old highways it persists, cheaper and better than the alternatives, serving the traffic that still stops. On the new ones it is replaced by a food court with a lease, a brand and a washroom standard — cleaner, more expensive, and engineered around a dwell time of twenty minutes rather than a night's sleep. The food gets worse and the hygiene gets better, which is roughly what happens whenever an institution is rebuilt around the property rather than around the customer.

The point of the place

It is tempting to end with nostalgia, and it would be wrong. The dhaba is not good because it is old. It is good because it was built to fit a very specific set of facts, and the cooking that resulted — the long-held dal, the bread off the griddle, the sharp pickle cutting through the fat — is a genuinely good answer to the question of how to feed a lot of tired people quickly and cheaply.

The honest lesson is the one the pillar keeps making. A cuisine is not a set of recipes handed down; it is a set of solutions to material problems, and it changes when the problems change. The dhaba is the clearest case in the country, because the problem it solved — a road, a truck, a fixed allowance and no schedule — is written on its face, in the size of the car park and the price of a single roti.

Sources and checks

  1. Ministry of Road Transport and Highways Annual report and highway network statistics; National Highways Authority wayside amenities programme
  2. Economic Survey of India Road transport chapter — network length and share of freight traffic
  3. National Highways Authority of India Wayside amenities: site awards and operational status
  4. Sen, Colleen Taylor Feasts and Fasts: A History of Food in India. Reaktion Books, 2015
  5. Achaya, K. T. A Historical Dictionary of Indian Food. Oxford University Press, 1998
  6. Press reports on the Murthal strip Business and food journalism on highway dhabas, 2015–2026 — figures vary and are treated here as reported, not audited

Last checked 1 November 2026 Yellowsea Huang Corrections