--- title: "Selling Internationally on Cloud Marketplaces" url: https://www.suger.io/resources/blog/selling-internationally-on-cloud-marketplaces/ canonical: https://www.suger.io/resources/blog/selling-internationally-on-cloud-marketplaces/ type: Blog description: "Marketplace multi currency selling across regions: how AWS, Microsoft and Google Cloud handle currency, tax and payout, and what a seller still owns." --- # Selling Internationally on Cloud Marketplaces > Canonical HTML version: https://www.suger.io/resources/blog/selling-internationally-on-cloud-marketplaces/ 1. [Home](/) 2. / 3. [Resources](/resources/) 4. / 5. [Blog](/resources/blog/) 6. / 7. Selling Internationally on Cloud Marketplaces # Selling Internationally on Cloud Marketplaces Selling across borders through a cloud marketplace changes five things at once — currency, tax, the entity that pays you, where a listing is buyable, and how a contract localizes. Here is what each marketplace decides and what you still own. [![Chloe Wu](/authors/chloe-wu.jpg)](/resources/blog/author/chloe-wu/) [Chloe Wu](/resources/blog/author/chloe-wu/) Aug 20, 2026 ![Selling Internationally on Cloud Marketplaces](/images/blog/selling-internationally-on-cloud-marketplaces/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fselling-internationally-on-cloud-marketplaces%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Cloud%20GTM%2C%20Marketplaces. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fselling-internationally-on-cloud-marketplaces%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Cloud%20GTM%2C%20Marketplaces. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fselling-internationally-on-cloud-marketplaces%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Cloud%20GTM%2C%20Marketplaces. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fselling-internationally-on-cloud-marketplaces%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Cloud%20GTM%2C%20Marketplaces. "Summarize with Perplexity") Table of Contents - [What “marketplace multi currency” actually means](#what-marketplace-multi-currency-actually-means) - [Who calculates and remits the tax is the marketplace’s call, not yours](#who-calculates-and-remits-the-tax-is-the-marketplaces-call-not-yours) - [Which entity pays you, and after what deductions](#which-entity-pays-you-and-after-what-deductions) - [Where a listing is buyable is a per-region setting, not a default](#where-a-listing-is-buyable-is-a-per-region-setting-not-a-default) - [Contract localization: the private offer is where terms get region-specific](#contract-localization-the-private-offer-is-where-terms-get-region-specific) - [The five dimensions, side by side](#the-five-dimensions-side-by-side) - [The operational trap: doing all of this per marketplace](#the-operational-trap-doing-all-of-this-per-marketplace) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _Selling internationally on a cloud marketplace is not one decision — it is five that fire at once: the currency the buyer is charged in, who calculates and remits the tax, which legal entity pays you and after what deductions, whether the listing is even buyable in that region, and how the contract localizes. The marketplace decides most of them for you. What you still own is the price, the market list, and keeping all of it reconciled across every marketplace at the same time._ * * * A revenue lead expanding a marketplace listing into a second region usually asks a single question — “can we sell in Europe?” — and expects a single answer. There isn’t one. Behind that question sit five separate mechanics, each governed differently, and each cloud marketplace resolves them in its own way. The good news is that almost none of it is yours to build. The marketplace is the seller of record on most of these transactions, which means it charges the buyer, collects the money, handles the tax where it is the responsible party, and pays you downstream. The work that remains is smaller and more specific than “become a company that sells internationally” — it is deciding a handful of things per market, and then not letting the reconciliation fall apart once you are selling the same product six ways. Here is what actually changes when a marketplace listing crosses a border, dimension by dimension. * * * ## What “marketplace multi currency” actually means Marketplace multi currency is the marketplace charging each buyer in a currency assigned by that buyer’s billing geography — not a grid of prices you set per country, and not a currency the buyer chooses at checkout. You set a base price; the marketplace maps it onto the local currency the buyer’s region transacts in. This is the first place the “one answer” expectation breaks. On Microsoft’s marketplace, per [Microsoft’s own geographic-availability documentation](https://learn.microsoft.com/en-us/partner-center/marketplace-offers/marketplace-geo-availability-currencies), each supported geography is tied to a fixed currency defined by the customer’s billing address, a buyer views the price in that currency, and _“you cannot pick a different currency to view prices.”_ A German buyer sees euros because the market map says Germany transacts in euros — not because you typed a euro figure. The mechanics of that specific conversion, and the fact that a converted local price then freezes, are covered in depth in [per-market pricing on Azure Marketplace](/resources/blog/per-market-pricing-on-azure-marketplace/). The shape is similar on the other marketplaces even where the details differ: you establish a base price, the marketplace determines the currency each region is charged in, and the buyer is not shown a currency picker. So the practical rule for a revenue lead is the same everywhere — a “market” is a billing geography with an assigned currency, not a price band you tune in isolation. What you control is the base number and which geographies you enable. This post states no exchange rates and no target margins on purpose: those move, and they are yours to set. What is fixed is the _shape_ of the control. * * * ## Who calculates and remits the tax is the marketplace’s call, not yours On an international marketplace sale, the party responsible for calculating and remitting transaction tax is decided by the marketplace and varies by country — it is not a property of your company, and it is not consistent across the marketplaces you sell on. In many countries the marketplace is the responsible party and handles the customer-facing tax on your behalf; in others the seller is. Microsoft states this structure explicitly. Its [tax-responsibilities documentation](https://learn.microsoft.com/en-us/partner-center/marketplace-offers/tax-details-marketplace) describes a per-country model where a market is Publisher-Managed, Microsoft-Managed, or Reseller-managed — meaning the answer to “who remits VAT here?” is a lookup by country, set by Microsoft, not a decision you make. The other marketplaces draw their own version of that same line in their own places. The operational consequence, and the reason this matters before your first international payout: you do not build the customer-facing tax into your local price. Set your price as your price, and treat the buyer’s tax line as the marketplace’s mechanism wherever the marketplace is the responsible party. The withholding and payout-side tax that _does_ land on you — deductions between the buyer’s order and your bank account — is a separate, downstream question covered in [tax and withholding on marketplace revenue](/resources/blog/tax-and-withholding-on-marketplace-revenue/). This post is not tax advice; it describes how the marketplaces structure the question so the people in your business who _do_ give tax advice are looking at the right one. * * * ## Which entity pays you, and after what deductions The money that reaches your bank is not the number on the buyer’s order, and the entity that sends it is the marketplace, not the customer. Because the marketplace is the collecting party on most international transactions, expansion adds a settlement layer between the sale and your account — one you should model before you turn a region on. Per [AWS’s disbursement documentation](https://docs.aws.amazon.com/marketplace/latest/userguide/disbursement.html), AWS pays proceeds to your registered bank account on a defined schedule once the buyer has paid and the funds have cleared — the marketplace collects, then disburses to the seller downstream. Each marketplace runs its own version of this: a service fee comes out, tax on that fee may come out, transaction tax that is the marketplace’s to remit is handled at the buyer’s end, and withholding may apply depending on the country pairing between you and the buyer. Finance teams that model international marketplace revenue as “list price minus a percentage” get a surprise on the first cross-border payout and a worse one at year end. The broader map of who invoices, who is liable, and how money reaches you is in [what seller of record means on a cloud marketplace](/resources/blog/marketplace-seller-of-record/). Two things follow for a revenue leader. First, your payout entity and bank details must be set up and validated per the marketplace’s requirements before a region can pay you — a live listing that cannot receive funds is a common and avoidable stall. Second, the _timing_ and _currency_ of what you receive is the marketplace’s mechanism, not the customer’s payment terms, so reconciliation has to match a marketplace disbursement back to the originating order, not to an invoice you sent. * * * ## Where a listing is buyable is a per-region setting, not a default A marketplace listing is not automatically purchasable everywhere the moment it publishes. Region availability is something you enable — and something the marketplace can also constrain — so “we sell in Europe” is a setting you turn on per geography, not a state you reach by default. Enabling a geography does two things at once: it opts that region’s assigned currency into your pricing, and it makes the listing buyable to accounts billing in that region. Some marketplaces exclude certain plan types or government-cloud environments from parts of this, and some regions have their own entity or listing requirements before a buyer there can transact. The point for a revenue lead is to confirm each target region is actually enabled and buyable — with the currency you expected, not USD by accident — rather than assuming the listing’s reach is global. This is also where the marketplaces diverge most by geography. The three hyperscaler marketplaces — AWS, Microsoft, and Google Cloud — cover overlapping but not identical sets of regions, and a genuinely international motion often means a regional marketplace as well: Alibaba Cloud Marketplace is the practical route to buyers in China, a market the others do not reach the same way, and it gates sellers and localizes differently. If China is part of “international” for your product, [selling on Alibaba Cloud Marketplace](/solutions/alibaba-marketplace/) is a separate enablement track, not a region toggle on an existing listing. * * * ## Contract localization: the private offer is where terms get region-specific For negotiated deals, the private offer is the instrument that carries region-specific commercial terms — currency, price, and duration set for one buyer — without touching the public listing every other region sees. Public-listing pricing is converted and largely standardized; a private offer is where a single international buyer’s terms get made specific. This matters because enterprise buyers in different regions rarely want the public number. A private offer lets you set the exact price and term a specific customer pays, in the currency their region transacts in, as a one-to-one agreement — the cross-border analogue of a locally negotiated contract, run through the marketplace so it still bills against the buyer’s committed cloud spend. The mechanics of building those offers, and how they differ across the marketplaces, are in [private offers](/platform/private-offers/). The public listing gives you reach across regions; the private offer gives you a localized contract for the deals that need one. * * * ## The five dimensions, side by side Each row is decided differently, and most of them are the marketplace’s decision to make, not yours. This is the map to settle per target region before you enable it. Dimension Who decides it What you actually control Where it bites **Currency** The marketplace, by the buyer’s billing geography Your base price and which geographies you enable A buyer sees an assigned currency, not one they pick; enable the wrong region and it may transact in USD **Tax (calculate + remit)** The marketplace, per country — varies by market Whether _withholding/payout-side_ tax is modeled correctly Do not price customer-facing tax into your local number where the marketplace is the responsible party **Entity + payout** The marketplace collects and disburses to you Your validated payout entity and bank details per marketplace A region can’t pay you until payout setup clears; deductions sit between order and bank **Region availability** You enable it; the marketplace can constrain it Which geographies (and plan types) are buyable Listings are not global by default; some plan/gov-cloud types and regions are excluded **Contract localization** You, via a private offer Currency, price, and term for a specific buyer Public pricing is standardized; region-specific enterprise terms belong in a private offer The pattern across the table is the point: on four of five dimensions the marketplace is the seller of record making the call, and your job is to configure inputs and model outputs — not to become the international merchant of record yourself. * * * ## The operational trap: doing all of this per marketplace The genuinely expensive part of selling internationally is not any single dimension — it is that a real motion runs these five decisions across several marketplaces at once, and the reconciliation multiplies. Each marketplace has its own currency map, its own tax model, its own disbursement schedule, and its own place to set region availability and localized offers. Run each marketplace as its own project — its own console, its own catalogue, its own reconciliation spreadsheet — and the second region on the second marketplace costs what the first one did, and the numbers stop tying out. That is the failure mode a multi-marketplace operating model exists to prevent: one catalogue, one offer model, and one place where transactions across every marketplace reconcile, so international expansion is configuration rather than a new project each time. The shape of that operating model is in [running one GTM motion across AWS, Azure and Google Cloud](/resources/blog/one-gtm-motion-across-aws-azure-google-cloud/), and the metering and disbursement mechanics that make cross-currency reconciliation tie out sit in [billing and metering](/platform/billing-metering/). * * * ## Frequently asked questions **What currency are international buyers charged in on a cloud marketplace?** The currency assigned to the buyer’s billing geography by the marketplace, not one the buyer picks. You set a base price and the marketplace maps it to the region’s currency. Microsoft, for example, ties each supported geography to a fixed currency and does not let a buyer switch it. **Who handles tax when I sell internationally through a marketplace?** The marketplace decides per country, and it varies. In many markets the marketplace is the responsible party and calculates and remits the buyer’s transaction tax; in others the seller is. It is set by the marketplace, not a property of your company, so do not price customer-facing tax into your local number where the marketplace handles it. **How do I get paid for international marketplace sales?** The marketplace collects from the buyer and disburses to your registered bank account on its schedule, after deductions. AWS, for instance, pays proceeds once the buyer has paid and funds clear. Set up and validate your payout entity per marketplace before enabling a region, or a live listing cannot receive funds. **Is a marketplace listing automatically available in every country?** No. Region availability is a per-geography setting you enable, and the marketplace can constrain it. Enabling a region opts in its assigned currency and makes the listing buyable there. Some plan types and government-cloud environments are excluded, so confirm each target region is enabled with the currency you expected. **How do I set region-specific pricing or contract terms for one international buyer?** Use a private offer. It sets the exact price, currency and term a specific buyer pays without changing the public listing other regions see. Public pricing is standardized and converted; a private offer is where a single international buyer’s localized commercial terms are made specific. **Which marketplace do I use to reach buyers in China?** Alibaba Cloud Marketplace is the practical route to buyers in China, a market the AWS, Microsoft and Google Cloud marketplaces do not reach the same way. It gates sellers and localizes differently, so treat it as a separate enablement track rather than a region toggle on an existing hyperscaler listing. * * * ## Takeaways - Selling internationally on a marketplace is five decisions, not one: currency, tax, payout entity, region availability, and contract localization — each governed differently. - On four of the five, the marketplace is the seller of record making the call. You set the base price and the market list and model the outputs; you do not become the international merchant of record. - Currency is assigned by the buyer’s billing geography, not chosen at checkout. Enable a region and you opt in its currency — confirm it, so nothing transacts in USD by accident. - Who remits tax is a per-country lookup the marketplace controls, and it differs across the marketplaces you sell on. Do not price customer-facing tax into your local number where the marketplace handles it. - The expensive part is doing all of this per marketplace at once. One catalogue, one offer model, and one reconciliation surface turns international expansion into configuration instead of a new project each time. Suger transacts on six marketplaces — AWS, Microsoft, Google Cloud, Snowflake, Alibaba Cloud, and Oracle — so region availability, per-region pricing, private offers, tax handling, and cross-currency disbursement reconcile from one place instead of one console per marketplace. See how [billing and metering](/platform/billing-metering/) ties out cross-currency payouts, how [AWS Marketplace](/solutions/aws-marketplace/) and [Microsoft Marketplace](/solutions/microsoft-marketplace/) selling work end to end, or read the [Suger docs for connecting each marketplace](https://doc.suger.io/get-started/connect-your-marketplace/). ## Sources Primary sources for the platform rules cited above. Last verified August 20, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [Geographic availability and currency support for Microsoft Marketplace](https://learn.microsoft.com/en-us/partner-center/marketplace-offers/marketplace-geo-availability-currencies) — That each supported geography is mapped to a fixed transaction currency defined by the customer's billing address, that a buyer views the price in their own currency and cannot pick another, and that a USD base is converted to a static local price. - [Tax Responsibilities for Microsoft Marketplace publishers](https://learn.microsoft.com/en-us/partner-center/marketplace-offers/tax-details-marketplace) — The Publisher-Managed / Microsoft-Managed / Reseller country model — i.e. that which party calculates and remits transaction tax is set by the marketplace and varies by country, not by the seller. - [AWS Marketplace: Seller disbursement](https://docs.aws.amazon.com/marketplace/latest/userguide/disbursement.html) — That AWS disburses proceeds to the seller's registered bank account on a defined schedule after the buyer pays and the funds clear — i.e. the marketplace is the collecting party and the seller is paid downstream. ### Stay Updated Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.