Japanese Tax-Inclusive Pricing Display:
The Sōgaku Hyōji Rule That Can Make Your Prices Illegal

TL;DR

Key Takeaways

• 税込 must be the prominent figure for consumers — under 総額表示義務, the tax-inclusive total is what consumers must see clearly, not a small footnote beside a large 税抜 number.
• Translating an English pricing page produces a 税抜 page by default — English headline prices are pre-tax, so a literal port shows the wrong figure as the hero number.
• Consumption tax is 10% standard, 8% reduced — most SaaS falls under the standard 10% rate; the 8% reduced rate covers items such as most food and beverages.
• B2B can use 税抜, B2C must lead with 税込 — pure business audiences accept clearly labeled 税抜; consumer-facing or mixed-audience pages should default to 税込.
• Currency and cadence have conventions too — write 「1,100円（税込）」 with 円 after the number, no decimals, and pair it with 「月額」or 「／月」 so price, tax status, and billing period read in one glance.

Why a Translated Pricing Page Is the Wrong Price

The most consequential difference between an English and Japanese pricing page is not the words around the number — it is the number itself. An English pricing page almost always displays the pre-tax amount as its headline figure, because sales tax in many markets is added at checkout and varies by jurisdiction. When that page is translated into Japanese, the headline figure carries over unchanged, and the result is a Japanese pricing page that prominently shows a 税抜 (tax-excluded) price to consumers who are legally entitled to see the 税込 (tax-included) total.

This is not a stylistic nuance. Japan's 総額表示義務 (sōgaku hyōji gimu — tax-inclusive total display obligation), under the Consumption Tax Act, requires that prices shown to general consumers display the total amount including consumption tax. The obligation has applied to consumer-facing prices since April 1, 2021. A page that shows only a pre-tax figure, without the tax-inclusive total clearly presented, does not satisfy the rule. The risk is therefore twofold: the page reads as un-localized to Japanese eyes, and it can be non-compliant.

The trap is that nothing in the translation process flags this. A translator handed an English pricing page produces fluent Japanese around a number they were never asked to change. The fix is not linguistic — it is a localization decision about which figure is the hero number and how tax status is labeled. That decision has to be made deliberately, because the default behavior of translation is to get it wrong.

For most SaaS and digital products, the relevant rate is the standard 10%. The 8% reduced rate exists, but it covers categories such as most food and beverages and some publications — it rarely applies to software subscriptions. The practical point is that whatever rate applies, the consumer-facing figure must already include it.

税込 vs 税抜: Which Figure the Consumer Must See

The two terms at the center of Japanese price display are 税込 (zeikomi, tax-included) and 税抜 (zeinuki, tax-excluded). 税込 is the amount the customer actually pays. 税抜 is the base amount before consumption tax is added. English pricing pages overwhelmingly present the 税抜-equivalent figure as the headline, because that is how pre-tax pricing is conventionally shown in markets where tax is appended later.

Under 総額表示義務, the figure a consumer sees most prominently must be the 税込 total. You may still show the 税抜 amount — many Japanese pages do, because the pre-tax figure is useful for business buyers and for transparency — but it cannot be the only figure, and it should not be the dominant one. The compliant pattern is to lead with the tax-inclusive total and treat the pre-tax figure as secondary.

When a page shows only one figure, that figure must be the 税込 total, and labeling it explicitly as 税込 removes any ambiguity. The single most common compliance gap on localized SaaS pricing pages is exactly this: a large pre-tax number, no tax-inclusive total, and a small "+ tax" note borrowed from the English original. That structure inverts the Japanese requirement.

B2B vs B2C: When 税抜 Display Is Acceptable

The obligation to display tax-inclusive totals targets prices shown to general consumers — the B2C context. In pure business-to-business transactions, where the audience is companies that handle their own tax accounting, 税抜 display with clear labeling is common and widely accepted. A B2B invoicing tool aimed squarely at finance departments can reasonably lead with 税抜 figures, because that is how those buyers think about cost.

The complication for SaaS is that the audience is rarely cleanly one or the other. A pricing page is a public web page; it is read by procurement managers, by freelancers, by individual professionals signing up on a personal card, and by curious consumers. If a page can reasonably be read as consumer-facing — and most public SaaS pricing pages can — the safe default is to show the 税込 total prominently and label any 税抜 figures clearly.

A practical heuristic: if you are unsure whether a given page or plan is consumer-facing, treat it as if it is. Defaulting to tax-inclusive display costs nothing in clarity for business buyers — who can still see the 税抜 figure — and protects you on the consumer side. The reverse default does not.

Currency Formatting: 円, Separators, and No Decimals

Once the right figure is chosen, the way that figure is written carries its own set of conventions. Japanese prices are written with the character 円 placed after the number — 「1,100円」 — or, less commonly in body copy, with the ¥ symbol before it. The trailing 円 is the everyday consumer-facing form, and it is what reads as native on a Japanese pricing page.

The yen has no minor unit in ordinary pricing, so prices are whole numbers. Writing 「¥1,100.00」 with two decimal places — the literal output of a currency formatter configured for dollars — is an immediate tell that the page was not localized, only converted. Thousands are separated with commas, and digits are half-width. 「1,100円」 is correct; 「1100円」 (no separator), 「¥1,100.00」 (decimals), and 「1,100 yen」 (roman unit) all read as foreign on a Japanese page.

For ranges and "starting from" pricing, the Japanese convention appends 〜 (the wave dash) to the figure: 「1,100円〜」 means "from 1,100 yen." This is cleaner than translating "starting at" into a prefix, and it matches how Japanese pricing tables present entry points.

Billing Period: 月額, 年額, and the ／月 Form

SaaS pricing is recurring, so the billing period is part of the price, and Japanese has settled conventions for expressing it. The two cleanest forms are 月額 (getsugaku — monthly fee) and 年額 (nengaku — annual fee), used as a prefix: 「月額1,100円（税込）」. The shorthand 「／月」 and 「／年」 (per month / per year) also appear, typically in compact pricing tables: 「1,100円／月（税込）」.

What does not work is a literal translation of the English cadence. "$10/mo" becomes neither 「10ドル／月」 (wrong currency) nor an awkward 「1,100円 毎月」 (grammatically loose). The natural forms are 月額 as a prefix or ／月 as a suffix, paired with the tax label so the consumer reads amount, tax status, and cadence together. Ambiguity about whether a figure is monthly or annual is one of the most common sources of consumer confusion on localized pricing pages — and it compounds badly when the annual plan is shown as a per-month equivalent without saying so.

For annual plans presented at a monthly-equivalent rate, label the framing explicitly: 「年額13,200円（税込／月あたり1,100円）」 makes clear that the headline is annual while showing the per-month equivalent. Hiding the annual commitment behind a per-month number is both a trust problem and, for consumer-facing plans, a display-clarity risk.

Tax Display at Checkout, Not Just the Pricing Page

Compliance and clarity do not stop at the pricing page. The 税込 total has to remain visible — and correct — through the entire purchase flow: the plan selector, the cart or order summary, the checkout confirmation, and the receipt. A common failure is a pricing page that has been carefully localized to lead with 税込, feeding into a checkout that reverts to the English template and shows the 税抜 subtotal with tax added as a line item at the end.

Japanese consumers expect the order summary to show the tax-inclusive total clearly, with the consumption tax amount itemized as 消費税 if line items are broken out. The final amount payable should be labeled unambiguously — 「お支払い合計（税込）」 (total payment, tax included) — so there is no surprise at the last step. A checkout that surfaces a different, higher number than the pricing page implied is the fastest way to lose a Japanese buyer at the moment of conversion.

The localization audit therefore has to follow the price all the way to the receipt. It is entirely possible to have a compliant pricing page and a non-compliant checkout, because the two are often built from different templates and localized at different times. Treat tax display as a property of the whole funnel, not a single page.

Tax-Display Localization Checklist

Four Before/After Price-Display Examples

Example 1: Headline Plan Price

Example 2: Currency Formatting

Example 3: Billing Cadence

Example 4: Checkout Total

Frequently Asked Questions