Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.stigg.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Price localization allows you to expand to new markets by accommodating your product’s pricing to the local willingness to pay. Stigg’s price localization implementation can also be leveraged to test and gradually roll out pricing changes in specific geographies before applying the change to your main markets. Using Stigg’s price localization functionality, you can:
  1. Offer your products using different price points in different countries, for example: $X USD in the US, $Y USD in Israel.
  2. Offer your product in the local currency per country, decoupled from the current conversion rate, for example: $X USD in the US, ₹Y INR in India.
  3. Display the localized prices to customers on your public pricing page and in-app paywalls.
  4. When Stigg is integrated with a billing solution (such as Stripe) - bill customers in their local currency, including invoicing, payment collection and receipt generation.
Customers in countries for which no localized pricing has been defined will automatically fall back to using the product’s default pricing. Rolling out price localization to your product can be achieved directly from the Stigg app using no-code after the initial integration with Stigg.

​
How billing currency is determined

Stigg provides the infrastructure to define localized prices per country, but does not automatically determine which currency applies to a given customer. Your team is responsible for implementing the logic that resolves the customer’s billing country code and passing it to Stigg. Common approaches used by SaaS vendors include:
  • GeoIP — resolve the customer’s country from their IP address.
  • Billing address — use the country from the customer’s billing address once it’s been collected.
  • Customer preference — let the customer select their preferred currency during onboarding or in account settings.
Whichever approach you choose, it’s important to apply it consistently across both your public pricing page (where visitors don’t yet have a billing address) and your in-app experience. Without consistency, customers may see prices change unexpectedly — for example, if a localized price differs significantly from the default, a customer who saw the default price on your public page could be surprised when a different price appears after entering a billing address.

​
Prerequisites

Model your pricing in Stigg Integrate Stigg into your codebase

​
See it in action

​
Limitations

Customers can have only one billing currency. This means that when customers have a subscription to paid plan, all other subscriptions will be billed in the same currency. The customer’s billing currency is reset once they don’t have any active subscriptions to paid plans.