Price adjustments for specific regions based on purchasing power parity, market conditions, or competitive landscape.
Regional pricing sets a product's price per market according to local purchasing power, so the same plan costs less where incomes are lower. It is the deliberate decisionDecisionStrategyA recorded decision with context, rationale, and consequencesView reference → to charge a fraction of the headline price in some regions, and the tension is that doing so opens the door to arbitrage.
The economic basis is purchasing power parity, the idea that a unit of currency should buy a comparable basket of goods across countries. Applied to software, PPP pricing multiplies a global price by a country's parity factor: a $100 plan at an Indian PPP factor of roughly 0.3 lands near $30 locally. The practice spread through consumer subscriptionsSubscriptionSales & RevenueA recurring subscriptionView reference → before becoming standard SaaS tooling. Spotify, GitHub, Slack, and Netflix run dozens of adjusted price points; Spotify's premium tier sits near $9.99 in the US and closer to $3.50 in India after adjustment.
The field converged on rough discount bands by region, with reported benchmarks of 40 to 60 percent in India, 30 to 40 percent in Brazil, and single digits in Western Europe. The debate moved from whether to do it to how to defend it, because every gap between regions is an incentive to game the cheaper one.
A SaaS company prices its team plan at $50 per seat globally and sees near-zero conversion in emerging markets. It introduces regional pricing: $20 in India, $30 in Brazil, $45 in Western Europe, each derived from the local parity factor rather than a same-day currency conversion. Conversion in those markets climbs. The riskRiskComplianceA risk to the product or businessView reference → arrives with it. A buyer in a high-price region routes through a VPN to claim the Indian rate. The company closes the loophole by binding the price to the payment method's billing country, so a US card cannot redeem India pricing regardless of stated location, and the parity discount stays with the audience it was built for.
pricing_tier_localised_as_regional_pricingPricing Tierlocalised asRegional Pricingcross-domain, so the tier defines the offer and the regional price sets its number in a market.locale_priced_in_regional_pricingLocalepriced inRegional Pricinghierarchy without that price affecting which language renders.In the Unified Product Graph, regional pricing lives at the meeting point of the business and localisation regions. It connects up to the plan it adjusts through Pricing Tierlocalised asRegional Pricingcross-domain and across to the market it serves through pricing_tier_localised_as_regional_pricingLocalepriced inRegional Pricinghierarchy. Keeping price as its own node, tied to both a tier and a locale, lets the graph answer "what does a locale_priced_in_regional_pricingpt-BR buyer pay for Pro, and why" by following two edges, and it makes the arbitrage surface visible: any locale whose price diverges sharply from a neighbouring region is a queryable risk rather than a buried config value.
Type-specific fields on BaseNode
currencystringLocal currency code
price_overridenumberOverridden price for this region
ppp_factornumberPurchasing power parity adjustment factor
effective_datestringDate the regional pricing takes effect (ISO format)
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
2 edge types connected to this entity.
locale_priced_in_regional_pricingpricing_tier_localised_as_regional_pricing