Japanese Pricing Page Localization:
Yen, Tax-Inclusive Display, and Plan Naming for SaaS

▶ 60-Second Slide Summary Prefer the 10-slide version of this article? Tap to read in 60 seconds. View slides →

Quick Answers

Should a Japanese pricing page show tax-inclusive or tax-exclusive prices?

It depends on the audience. Prices shown to general consumers must include the 10% consumption tax under Japan's tax-inclusive display obligation (総額表示), fully mandatory again since April 1, 2021. B2B pricing may be shown tax-exclusive (税別), since the obligation targets consumer-facing displays — but the 税込 / 税抜 status must be unmistakable either way. Verify the current rule with official National Tax Agency guidance.

Why does a translated pricing page convert poorly in Japan?

Because price points, tax labels, plan names, billing cadence, and payment methods all carry home-market assumptions. A translated page often shows odd yen amounts converted from dollars, omits the tax label Japanese buyers scan for, names tiers in English jargon, assumes credit-card billing, and offers no invoice — each a small reason to hesitate at the exact moment of paying.

TL;DR

A foreign SaaS pricing page is usually built for the home market and then translated string-by-string into Japanese. The words become Japanese; the pricing logic stays foreign. The result shows yen amounts mechanically converted from dollars (¥1,487 instead of a deliberate ¥1,500), no clear 税込 / 税抜 label, plan tiers named in English jargon, an implicit assumption of credit-card billing, and no mention of invoices or the Qualified Invoice System (インボイス制度) that Japanese business buyers now ask about. Localizing the pricing page means re-deciding the numbers, displaying the consumption tax the way Japan requires (税込 for consumers under 総額表示, 税抜 permitted for B2B), naming the plans for Japanese readers, framing annual versus monthly clearly, and offering the payment methods — invoice/bank transfer, sometimes konbini — that Japanese buyers expect. Tax and invoice facts must always be verified against official National Tax Agency sources, never invented.

Key Takeaways

• Don't show converted-from-dollars yen — Japanese buyers expect deliberate round price points (¥1,500, ¥9,800), not ¥1,487 derived from today's exchange rate.
• The 税込 / 税抜 label is not optional cosmetics — consumer-facing prices must be tax-inclusive (総額表示, mandatory since April 1, 2021); B2B may show 税抜 but must label it.
• The Qualified Invoice System changes B2B billing copy — buyers ask whether you are a registered issuer with a registration number; your billing copy should answer it.
• Plan names need localizing, not just translating — English tier jargon and aspirational naming often read as opaque; clarity beats cleverness in Japanese.
• Card-only checkout excludes real buyers — many Japanese companies pay software by invoice/bank transfer (請求書払い); offering it removes a major conversion blocker.

Why the Pricing Page Is a Localization Surface, Not Just a Translation Job

For most foreign SaaS products entering Japan, the pricing page gets translated like any other marketing page. The plan names, feature bullets, and CTA copy go through the same pipeline, the numbers are left in place or swapped to yen at the current exchange rate, and the page ships. It reads as grammatical Japanese. It also reads, to a Japanese buyer, as a page that was clearly built for somewhere else.

The reason this matters more on the pricing page than almost anywhere else is that this is the page where intent converts to action. A visitor who has read your marketing, understood the product, and reached the pricing page is close to deciding. Every small friction here — a price that looks like a rounding accident, a missing tax label, a plan name they cannot parse, a checkout that only takes a card their company will not issue — is a reason to pause and "think about it." In Japan, "think about it" frequently means routing the decision through a longer internal process, and the momentum is lost.

This is the same late-funnel pattern visible on the surfaces that surround it — the approval-ready checkout, the localized invoice and receipt, and the cancellation and refund flow. The pricing page sits at the head of that sequence. Localizing it well is not about smoother Japanese prose; it is about making the decision to pay feel native and frictionless.

Yen Display: Stop Converting From Dollars

The most visible tell of an un-localized pricing page is the yen figure itself. The Japanese yen has no minor unit — there are no "yen cents" — so prices are whole numbers, written with a half-width thousands comma and no decimal places: 1,500円 or ¥1,500, never ¥1,500.00. A page that displays decimal yen has been ported mechanically and signals exactly that.

The deeper problem is the number itself. When a team prices in dollars and converts at the day's exchange rate, the result is an arbitrary figure — ¥1,487, ¥3,261 — that no Japanese company would ever set deliberately. Japanese price points are intentional and round: ¥1,500, ¥2,980, ¥9,800. The trailing-8 price (¥980, ¥1,980, ¥9,800) is a well-established Japanese retail convention, the local equivalent of charm pricing. A converted odd number does not just look untidy; it signals that pricing for Japan was an afterthought, and it makes the buyer wonder whether the price will drift with the exchange rate.

On symbol choice, both ¥ and 円 are correct and widely understood. The 円 character tends to read as more natural and consumer-friendly in Japanese copy, while ¥ is compact and common in tables; many localized pages use 円 in prose and ¥ in dense pricing grids. The non-negotiable is consistency, full-width avoidance in numerals, and a clear tax label, which the next section covers.

The Consumption Tax Display Question (総額表示)

Japan's consumption tax is 10% as a standard rate, with a reduced 8% rate for certain items such as food and some subscriptions — SaaS generally falls under the standard 10%. But the localization decision is not the rate; it is how the price is displayed relative to that tax. This is governed by the tax-inclusive price display obligation, 総額表示.

The rule turns on audience. For price displays aimed at general, unspecified consumers, the displayed price must include consumption tax — the total, tax-inclusive figure (e.g. 1,100円, or 1,100円(税込)). This obligation has a history worth knowing: it originally took effect in 2004, was relaxed by a transitional special-measures law during the period of tax-rate increases, and then became fully mandatory again on April 1, 2021, when that special-measures law ended. For displays aimed at businesses — genuine B2B pricing — tax-exclusive (税別 / 税抜) display is permitted, because the 総額表示 obligation applies specifically to prices shown to unspecified general consumers, not to business-to-business price displays.

For a SaaS company this has a direct, practical consequence. If your product is consumer-facing or could be read as such, your Japanese pricing page should show tax-inclusive totals. If your product is unambiguously B2B, you may show 税抜 prices — and many Japanese B2B SaaS pages do — but you must label them unmistakably, because a Japanese buyer scans for whether a number is 税込 or 税抜 the way a US buyer never has to. The single worst outcome is an unlabeled number: the buyer cannot tell what they will actually be charged, and the uncertainty itself is the conversion-killer.

The Qualified Invoice System and B2B Billing Copy

For any SaaS selling to Japanese businesses, the Qualified Invoice System (適格請求書等保存方式, commonly インボイス制度) has changed what buyers need from your billing. The system began on October 1, 2023. Under it, a Japanese business buyer can generally claim an input consumption-tax credit only when it receives a qualified invoice from a registered qualified invoice issuer (適格請求書発行事業者). The registration is evidenced by a registration number — a "T" followed by a 13-digit number — that must appear on the invoice.

The consequence for a foreign vendor is concrete: a Japanese business customer who pays you and cannot obtain a qualified invoice with a valid registration number may be unable to claim the consumption-tax portion as an input credit, which effectively raises their cost of buying from you. There are transitional measures that have phased down the credit available on invoices from unregistered suppliers over time, but the direction is clear, and procurement teams now routinely ask vendors whether they are registered issuers. This is no longer an accounting back-office detail; it is a question your Japanese buyer may raise before signing.

This does not all belong on the pricing page itself, but the pricing and billing copy should not be silent on it. A short, accurate statement of what kind of invoice you issue — and, if applicable, that it carries a registration number — removes a recurring question from the B2B sales conversation. Where you are not a registered issuer, say so honestly rather than imply otherwise; a clear statement lets the buyer make their own decision, whereas a vague one invites a follow-up that stalls the deal. The exact wording and the current transitional rules should be verified with official National Tax Agency sources before publishing.

Plan and Tier Naming for Japanese Buyers

English SaaS pricing leans on tier names that carry connotation more than meaning — "Starter," "Growth," "Pro," "Business," "Enterprise," and aspirational coinages like "Scale" or "Premium." Some of these survive into Japanese as accepted loanwords (プロ, ビジネス, エンタープライズ are widely understood). Others translate into something opaque or oddly grand. The localization question for each tier is not "what is the Japanese word for this" but "will a Japanese buyer immediately understand who this plan is for and what it costs."

Three patterns recur. First, English-only tier names left untranslated in an otherwise Japanese page can read as a barrier for buyers who are not comfortable parsing English marketing jargon, especially in the SMB and public-sector segments. Second, over-clever names lose their connotation in translation — a name that signals "ambitious but affordable" in English may signal nothing in Japanese. Third, the per-seat versus per-account model and what "user" means should be stated in unambiguous Japanese (ユーザー, アカウント, 席数), because pricing-unit confusion is a common source of pre-purchase questions. Clarity consistently outperforms cleverness here: a Japanese buyer rewards a pricing table they can read at a glance.

English tier (typical)	Common literal handling	Localized approach
Starter / Free	スターター / フリー	無料プラン / 個人・お試し向け framing makes the audience explicit
Pro	プロ	プロ is understood; add who it is for (例: 少人数チーム向け)
Business	ビジネス	ビジネス works; clarify seats/account model in Japanese
Enterprise	エンタープライズ	エンタープライズ + お問い合わせ／お見積り (quote-based) framing
Scale / Growth (coined)	スケール / グロース	Often opaque — prefer a descriptive Japanese label over the coinage

Annual vs Monthly, and How Japan Frames the Discount

Most SaaS pricing pages offer monthly and annual billing with the annual plan discounted, framed in English as "Save 20%" or "2 months free." Both the framing and the assumption underneath need a localization pass. On framing, Japanese pages commonly express the saving as the effective monthly rate under annual billing (年間契約で月あたり◯◯円) and as the concrete yen amount saved, rather than as a bare percentage — a concrete monthly figure is easier for a Japanese buyer to evaluate against a budget.

The assumption underneath matters more. Annual billing in many foreign SaaS pages presumes an upfront card charge for the full year. A meaningful share of Japanese business buyers cannot or will not put an annual software charge on a corporate card; they expect to receive an invoice and pay by bank transfer, often on monthly or agreed terms even for an annual contract. So "annual plan" in Japan may need to mean "annual commitment, invoiced" rather than "annual charge, upfront on card." Stating the billing mechanics in plain Japanese — what is committed, how it is invoiced, when it is paid — prevents the annual option from quietly excluding the buyers most likely to commit.

Payment Methods Japanese Buyers Expect

This is where many foreign pricing pages lose B2B deals invisibly. A card-only checkout is normal in the home market and silently disqualifies a large share of Japanese business buyers, because many Japanese companies are simply not set up to pay for software with a corporate card. The expected B2B method is invoice-based payment by bank transfer — 請求書払い / 銀行振込 — where the vendor issues an invoice and the buyer's accounting department pays it on terms. A pricing page that offers no invoice option asks the buyer to solve a problem your competitors have already solved for them.

The picture differs by segment. For consumer-facing or prosumer products, convenience-store payment (コンビニ決済) remains a meaningful method for buyers without a card or who prefer not to use one online, and digital wallets and QR-code payments have grown substantially. For B2B, the invoice/bank-transfer path is the one that unblocks procurement. The practical step is not to support every method, but to (1) name the accepted payment methods clearly near the price, and (2) ensure that at least an invoice/bank-transfer route exists for business buyers. Connecting this to a properly localized Japanese checkout is what turns a viewed price into a completed purchase.

Trust Signals and Conversion-Killers on the Japanese Pricing Page

Beyond the numbers and tax, a Japanese pricing page is read for reassurance signals that differ from the home market. Buyers look for a clear statement of what happens at renewal and how to cancel (Japanese buyers are wary of auto-renew traps and read cancellation terms carefully), whether there is a free trial or money-back framing, and whether company and contact information is present and credible. The legally required 特定商取引法に基づく表記 (Specified Commercial Transactions Act disclosure) and clear contact details function as trust signals as much as compliance items — their absence is itself a red flag to a careful Japanese buyer.

The recurring conversion-killers, then, are a short list: an unlabeled or FX-derived yen price; no 税込 / 税抜 clarity; English-only plan names; an annual option that assumes upfront card billing; card-only checkout with no invoice route; silence on the Qualified Invoice System for B2B; and missing renewal, cancellation, and company-information signals. None is individually fatal, and none requires rebuilding the product. Together they are the difference between a page that reads as "priced for Japan" and one that reads as "translated and hoping." The fixes are mostly framing, ordering, and a few honest additions layered onto facts you already have.

A Pre-Launch Japanese Pricing Page Checklist

Before a Japanese pricing page is considered ready, run it through this audit. Most of these checks require comparing the page against how a Japanese buyer actually decides and pays, not against the English source.

Why This Page Is Higher-Leverage Than It Looks

The pricing page is short — a few numbers, a few labels, a handful of plan names. That brevity is exactly why it is under-localized: there is little text to translate, so it gets waved through. But it is also the page closest to revenue. A visitor here has already decided they want the product; the only question left is whether paying feels native and safe. Every friction on this page acts as a tax on conversion at the precise moment intent is highest.

The work concentrates on framing and a few honest additions — deliberate price points, a tax label, plan names a buyer can read, an invoice payment route, a clear word on the Qualified Invoice System — layered onto facts you already have. It does not require new infrastructure (though it may surface a billing gap worth closing). A focused Japanese QA pass over the pricing and checkout pages, read the way a Japanese buyer reads them, typically lifts conversion at the highest-intent point in the funnel — and signals, in the place it matters most, that you have priced and sold in Japan before.

For a localization PM at an overseas SaaS HQ, this is the kind of surface a focused Japanese localization audit is built for: low word count, high stakes, and fixes that are about the buyer's decision rather than the dictionary.

Frequently Asked Questions