Tag: foodpanda

Why restaurant food delivery is more sustainable than grocery delivery

I’ve ranted a fair bit about both grocery and restaurant delivery on this blog. I’ve criticised the former on grounds that it incurs both inventory and retail transportation costs, and the latter because availability of inventory information is a challenge.

In terms of performance, grocery delivery companies seem to be doing just fine while the restaurant delivery business is getting decimated. Delyver was acquired by BigBasket (a grocery delivery company). JustEat.in was eaten by Foodpanda. Foodpanda, as this Mint story shows, is in deep trouble. TinyOwl had to shut some offices leading to scary scenes. Swiggy is in a way last man standing.

Yet, from a fundamentals perspective, I’m more bullish on the restaurant delivery business than the grocery delivery business, and that has to do with cost structure.

There are two fundamental constraints that drive restaurant capacity – the capacity of the kitchen and the capacity of the seating space. The amount of sales a restaurant can do is the lower of these two capacities. If kitchen capacity is the constraints, there is not much the restaurant can do, apart from perhaps expanding the kitchen or getting rid of some seating space. If seating capacity is the constraint, however, there is easy recourse – delivery.

By delivering food to a customer’s location, the restaurant is swapping cost of providing real estate for the customer to consume the food to the cost of delivery. Apart from the high cost of real estate, seating capacity also results in massive overheads for restaurants, in terms of furniture maintenance, wait staff, cleaning, reservations, etc. Cutting seating space (or even eliminating it altogether, like in places like Veena Stores) can thus save significant overheads for the restaurant.

Thus, a restaurant whose seating capacity determines its overall capacity (and hence sales) will not mind offering a discount on takeaways and deliveries – such sales only affect the company kitchen capacity (currently not a constraint) resulting in lower costs compared to in-house sales. Some of these savings in costs can be used for delivery, while still possibly offering the customer a discount. And restaurant delivery companies such as Swiggy can be used by restaurants to avoid fixed costs on delivery.

Grocery retailers again have a similar pair of constraints – inventory capacity of their shops and counter/checkout capacity for serving customers. If the checkout capacity exceeds inventory capacity, there is not much the shop can do. If the inventory capacity exceeds checkout capacity, attempts should be made to sell without involving the checkout counter.

The problem with services such as Grofers or PepperTap, however, is that their “executives” who pick up the order from the stores need to go through the same checkout process as “normal” customers. In other words, in the current process, the capacity of the retailer is not getting enhanced by means of offering third-party delivery. In other words, there is no direct cost saving for the retailer that can be used to cover for delivery costs. Grocery retail being a lower margin business than restaurants doesn’t help.

One way to get around this is by processing delivery orders in lean times when checkout counters are free, but that prevents “on demand” delivery. Another way is for tighter integration between grocer and shipper (which sidesteps use of scarce checkout counters), but that leads to limited partnerships and shrinks the market.

 

It is interesting that the restaurant delivery market is imploding before the grocery delivery one. Based on economic logic, it should be the other way round!

Hyperlocal and inventory intelligence

The number of potential learnings from today’s story in Mint (disclosure: I write regularly for that paper) on Foodpanda are immense. I’ll focus on only one of them in this blog post. This is a quote from the beginning of the piece:

 But just as he placed the order, one of the men realized the restaurant had shut down sometime back. In fact, he knew for sure that it had wound up. Then, how come it was still live on Foodpanda? The order had gone through. Foodpanda had accepted it. He wondered and waited.

After about 10 minutes, he received a call. From the Foodpanda call centre. The guy at the other end was apologetic:

“I am sorry, sir, but your order cannot be processed because of a technical issue.”

“What do you mean technical issue?” the man said. “Let me tell you something, the restaurant has shut down. Okay.”

I had a similar issue three Sundays back with Swiggy, which is a competitor of Foodpanda. Relatives had come home and we decided to order in. Someone was craving Bisibelebath, and I logged on to Swiggy. Sure enough, the nearby Vasudev Adigas was listed, it said they had Bisibelebath. And so I ordered.

Only to get a call from my “concierge” ten minutes later saying he was at the restaurant and they hadn’t made Bisibelebath that day. I ended up cancelling the order (to their credit, Swiggy refunded my money the same day), and we had to make do with pulao from a nearby restaurant, and some disappointment on having not got the Bisibelebath.

The cancelled order not only caused inconvenience to us, but also to Swiggy because they had needlessly sent a concierge to deliver an impossible order. All because they didn’t have intelligence on the inventory situation.

All this buildup is to make a simple point – that inventory intelligence is important for on-demand hyperlocal startups. Inventory intelligence is a core feature of startups such as Uber or Ola, where availability of nearby cabs is communicated before a booking is accepted. It is the key feature for something like AirBnb, too.

If you don’t know whether what you promise can be delivered or not, you are not only spending for a futile delivery, but also losing the customer’s trust, and this can mean lost future sales.

Keeping track of inventory is not an easy business. It is one thing for an Uber or AirBnB where each service provider has only one product which is mostly sold through you. It is the reason why someone like Practo is selling appointment booking systems to software – it also helps them keep track of appointment inventory, and raise barriers to entry for someone else who wants the same doctor’s inventory.

The challenge is for companies such as Grofers or Swiggy, where each of their sellers have several products. Currently it appears that they are proceeding with “shallow integration”, where they simply have a partnership, but don’t keep track of inventory – and it leads to fiascos like mentioned above.

This is one reason so many people are trying to build billing systems for traditional retailers – currently most of them do their books manually and without technology. While it might still be okay for their business to continue doing that (considering they’ve operated that way for a while now), it makes it impossible for them to share information on inventory. I’m told there is intense competition in this sector, and my money is on a third-party provider of infrastructure who might expose the inventory API to Grofers, PepperTap and any other competitor – for it simply makes no sense for a retailer to get locked in to one delivery company’s infrastructure.

Yet, the problem is easier for the grocery store than it is for the restaurant. For the grocery store, incoming inventory is not hard to track. For a restaurant, it is a problem. Most traditional restaurants are not used to keeping precise track of food that they prepare, and the portion sizes also have some variation in them. And while this might seem like a small problem, the difference between one plate of kesari bhath and zero plates of kesari bhaths is real.

Chew on it!