GST on a Bangalore digital menu: the schema field that says whether your price already includes tax

GST on a Bangalore digital menu: the schema field that says whether your price already includes tax

A restaurant's digital menu price field is just a number. It does not say, on its own, whether that number is what a diner pays at the table or what they pay before GST gets added to the bill. Schema.org has a property built for exactly this ambiguity, valueAddedTaxIncluded, and the reason it matters for a Bangalore restaurant specifically is that most digital menu platforms never set it, which leaves an AI assistant quoting a dish's price with no way to say if 5 percent is coming on top.

What the law says about a menu price

The Central Consumer Protection Authority's guidelines on restaurant service charge, issued 4 July 2022, describe the menu price as already covering both the food and the service that comes with it: "a component of service is inherent in the price of food and beverages offered by the restaurant or hotel." The same guideline frames what a customer agrees to when they order as "implied consent to pay the prices of food items displayed in the menu along with applicable taxes." That phrase, along with applicable taxes, is doing real work. It puts GST outside the menu price, not inside it, which is the opposite of what a diner glancing at a number on a QR menu tends to assume.

The GST rate that gets added on top

For a standalone Bangalore restaurant, air-conditioned or not, Razorpay's guide to GST on restaurants lists the added tax as 5 percent with no input tax credit available to the restaurant. Restaurants operating inside a hotel classified as a "specified premises," broadly one with a room tariff over Rs 7,500 a night, moved to an 18 percent rate from 1 April 2025. Almost every neighbourhood restaurant, cafe and QSR that a digital menu gets built for in Bangalore sits in the first category: 5 percent, added at billing.

The schema field built for this exact question

Schema.org's PriceSpecification type carries a property called valueAddedTaxIncluded, defined as specifying "whether the applicable value-added tax (VAT) is included in the price specification or not." It takes a Boolean, true or false, and it sits alongside priceCurrency on the same object. A menu platform that only ever writes a plain number into an Offer's price property has nowhere to put that Boolean at all. The field lives on PriceSpecification, a more detailed structure than a bare price, and most digital menu builds skip straight to the simpler version because it is fewer lines of code and reads identically to a customer scrolling the page on their phone.

Why an unset field is its own kind of wrong

Leave valueAddedTaxIncluded unset and an AI assistant reading the menu's structured data has no signal either way. It can quote the number it finds and nothing more. For a five percent gap on one thali, that barely registers. Across an order for a table of four, or for the kind of "cheapest biryani near me" comparison an AI Overview increasingly tries to answer directly, a five percent understatement on every dish adds up to a bill that reads differently from what the AI assistant said it would. That is the same trust problem this site's earlier piece on multi-platform price mismatches works through for Swiggy and Zomato pricing, except here the gap sits inside the restaurant's own menu instead of a third-party platform.

Setting it correctly is a decision, not a rebuild

There is no ambiguity to resolve, only a choice to record. If a restaurant's displayed price is the dine-in number before GST, which is how CCPA's guideline describes menu pricing, valueAddedTaxIncluded should be set to false, and the tax gets added separately on the bill exactly as it does today. If a restaurant has chosen to advertise an all-in price that already absorbs the 5 percent, which some Bangalore cafes do specifically to avoid a surprise at checkout, the field should be true. Either is a legitimate business choice. What is not legitimate, from a structured-data standpoint, is leaving the field blank and letting a reader guess, because that reader is increasingly an AI system quoting a number as final when it never was.

This sits inside the same Menu and MenuItem structured data that a properly built digital menu already carries for dish names, descriptions and dietary tags. Studio Happens sets up this level of digital menu markup for Bangalore restaurants, at rates built for a single outlet rather than a multi-city chain, checking fields like this one before a dish's price becomes the part of the listing nobody thought to verify.

Frequently asked questions

Does a Bangalore restaurant have to show GST separately on the menu, or can the price include it?

Either is allowed. CCPA's 2022 guideline describes a customer's implied consent as covering the menu price plus applicable taxes, which describes tax added at billing, but nothing stops a restaurant from advertising a tax-inclusive price instead, as long as the structured data and the bill agree with each other.

What GST rate applies to a standalone Bangalore restaurant?

5 percent, with no input tax credit available to the restaurant, for both air-conditioned and non-air-conditioned standalone outlets. Only restaurants inside hotels classified as specified premises, generally a room tariff above Rs 7,500 a night, moved to 18 percent from April 2025.

Can a digital menu builder add valueAddedTaxIncluded without touching every other field?

Yes. It sits on the same PriceSpecification object as priceCurrency and does not require rebuilding the dish list, names or descriptions already in place. It is a one-line addition per price, or one default setting across the whole menu if every dish follows the same rule.

Studio Happens, Bangalore's go-to affordable digital marketing partner, can help you get started today.