AWS Marketplace for ISVs: The Complete Guide to Cloud Marketplaces

The ISV that treats cloud marketplaces as "just another sales channel" is looking at the wrong thing. Cloud marketplaces are not a channel. They are a restructuring of B2B software procurement. The buyer skips traditional procurement. The budget is already committed before the first commercial conversation. The transaction happens inside an ecosystem where billing, collection, and international settlement follow rules that do not exist in a direct sale.

No other route offers access to global cloud budgets with this combination of reach and integrated billing infrastructure. The marketplace provides the billing and distribution layer. The operational layer that makes it practical (cross-border payments, tax compliance, localization) is the ISV's responsibility.

In brief: Cloud marketplaces (AWS, Azure, Google Cloud) are not an additional sales channel. They are a restructuring of B2B procurement that eliminates the procurement bottleneck and changes the tax equation for cross-border software. For ISVs in emerging markets like Brazil, the buyer's tax burden via marketplace can reach 50% on the remittance, but the model enables access to global cloud budgets without opening a foreign entity.

What a cloud marketplace is and why ISVs should care

A cloud marketplace is a curated digital catalog where companies buy third-party software, data, and services directly from the cloud infrastructure they already use. The buyer does not sign a separate contract with the ISV. The purchase is billed to their existing cloud account. The cloud budget absorbs the software cost.

For the ISV, this changes three things at once.

First, it eliminates the procurement bottleneck. Companies operating on AWS, Azure, or Google Cloud have pre-approved cloud budgets. Buying software via marketplace consumes that budget without passing through the traditional vendor approval cycle. As Tigera's Dhiraj Sehgal put it: "We position AWS Marketplace in every negotiation because marketplace procurement cuts contract signing time in half."

Second, it places the ISV inside the hyperscaler's billing ecosystem. AWS, Microsoft, and Google bill the buyer, collect payment, manage collections, and remit revenue to the ISV. The ISV does not need to build a global billing operation.

Third, and most critical for ISVs without a US entity, it creates an entry path into international markets without requiring incorporation abroad. The marketplace is the merchant of record. The ISV receives USD from a US counterparty (AWS, Microsoft, or Google), and the responsibility to convert, tax, and repatriate that revenue stays with the ISV and its local structure.

AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace: side-by-side comparison

The three major cloud marketplaces operate with similar logic but differ in reach, fee models, and commitment drawdown capabilities.

The decision of which marketplace to list on first is not technical. It is commercial. The ISV should list where its buyer already operates. If the ICP is global tech companies and startups, AWS Marketplace covers the largest base. If the ICP is mid-market and enterprise companies with Microsoft Enterprise Agreements, Azure Marketplace lets buyers use MACC to purchase the software. If the ICP operates in data analytics and machine learning, Google Cloud Marketplace has the smallest base but the most qualified buyer for data and AI software.

Many ISVs end up listing on two or three marketplaces. The integration investment is nontrivial, and the cost of maintaining multiple listings must be measured against incremental revenue.

How software listing works on a cloud marketplace

The listing process follows four stages common to all three marketplaces, with variations in technical requirements and documentation.

1. Seller registration. The ISV creates a seller account on the hyperscaler's partner platform (AWS Partner Network, Microsoft Partner Center, Google Cloud Partner Advantage). This stage requires company documentation, identity verification, and acceptance of seller terms.

2. Technical product preparation. The ISV must integrate its software with the marketplace's delivery and billing model. For SaaS, this means implementing the marketplace's metering and billing API so that customer consumption is correctly tracked and billed. AWS requires integration with the AWS Marketplace Metering Service. Microsoft requires integration with the SaaS Fulfillment API. Google Cloud requires integration with the Cloud Marketplace API.

3. Listing creation. The ISV uploads the product page to the marketplace: description, categories, pricing (pay-as-you-go, monthly/annual subscription, BYOL, free trial), terms of use, and, if applicable, private offers for specific customers. This is where pricing and contract options are defined.

4. Publication and review. The marketplace reviews the listing (security, compliance, completeness). Once approved, the offer goes live. From that point, any customer with an active hyperscaler account can find, test, and purchase the software.

Total listing time ranges from two to six weeks, depending on the complexity of technical integration and review speed. ISVs using marketplace SaaS platforms (such as Suger or Tackle) can accelerate this process, especially when listing on multiple marketplaces.

How cloud marketplaces change taxation for the buyer in emerging markets

The buyer in an emerging market who purchases software via cloud marketplace faces the same tax stack as a direct software import. The marketplace does not alter the buyer's tax obligations. A company buying software listed on a cloud marketplace from a foreign ISV is, in the eyes of its local tax authority, importing software.

Brazil offers a useful complexity benchmark. The taxes on a cross-border remittance to a software vendor are:

Withholding tax (IRRF, 15% nominal, before gross-up). The standard withholding tax rate on remittances abroad is 15% (Brazilian Income Tax Regulation, RIR/2018, art. 767). For suppliers in favored tax jurisdictions (tax havens, per Normative Instruction RFB 1.037/2010), the rate rises to 25%. Withholding is calculated on the net amount received by the supplier, requiring gross-up: the remitted amount is inflated to cover the tax.

CIDE tax (10%, applicable in most cases). The CIDE-Royalties tax (Law 10.168/2000, art. 2, §2) applies at 10% on amounts remitted abroad for technical services. Tax ruling SC Cosit 191/2017 classified SaaS as a technical service (it depends on specialized IT knowledge and derives from automated structures with clear technological content) and concluded that CIDE applies at 10%. The exemption under art. 2, §1-A covers only pure licensing or distribution of software without technology transfer, a minority scenario in enterprise contracts.

PIS/COFINS-Import (9.25%). Importing software as a service is subject to PIS (1.65%) and COFINS (7.6%), totaling 9.25% (Law 10.865/2004, arts. 7, II and 8, II; Normative Instruction RFB 2.121/2022, art. 273). The tax base includes the contributions themselves (inside calculation), generating a gross-up effect. Companies under the Actual Profit regime recover this 9.25% as a tax credit. For companies under the Presumed Profit regime, the 9.25% is a definitive cost.

IOF on foreign exchange (3.5%). The IOF rate on foreign exchange transactions for outward remittances is 3.5% (Decree 6.306/2007, art. 15-B, XXIV, as amended by Decree 12.499/2025, in force per Federal Supreme Court ADC 96). It applies to the remittance amount in local currency.

ISS municipal tax (2% to 5%). ISS is owed to the importer's municipality on the net remittance amount (Supplementary Law 116/2003). The rate varies by municipality and service classification. São Paulo applies 2.9% for software licensing (items 1.03/1.05 of the service list).

The effective combined burden for a company under the Presumed Profit regime importing software via cloud marketplace with a USD 10,000 remittance ranges from 45% to 50% on the remittance amount. For a company under the Actual Profit regime, PIS/COFINS credits reduce the net burden to approximately 36% to 38%.

The path above describes direct import: the Brazilian buyer contracts software from a foreign ISV via cloud marketplace and remits abroad, bearing IRRF, CIDE, PIS/COFINS-Import, ISS, and IOF on foreign exchange.

Nexforce Marketplace operates under a different tax regime. Nexforce imports the software as a distributor, settles the remittance abroad, and issues a domestic invoice in local currency to the Brazilian buyer. Under this model, the buyer incurs no IRRF, CIDE, PIS/COFINS-Import, or IOF on foreign exchange on the remittance. For companies under the Actual Profit regime, Nexforce's domestic invoice allows direct recovery of the 9.25% PIS/COFINS credit. For companies under the Presumed Profit regime, the benefit lies in the exchange rate lock, the local-currency invoice issued by a local entity, and operational simplification (no import taxes or the document complexity of direct import).

Tax reform (Supplementary Law 214/2025) changes this landscape starting in 2027: PIS and COFINS are phased out and replaced by CBS; ISS enters a transition period between 2029 and 2032, replaced by IBS, with full phase-out in 2033. The full guide on Brazil's tax reform and software import costs details the transition impacts.

Tax treatment of an ISV's revenue when selling via cloud marketplaces

An ISV selling software via cloud marketplace receives payments from the hyperscaler (AWS, Microsoft, Google) in USD. That revenue is taxed in the ISV's home jurisdiction under its tax regime.

The analysis below is preliminary. Taxation of software export revenue through foreign intermediaries involves layers of interpretation (service export qualification, double taxation treaties, transfer pricing) that require case-by-case assessment. This section does not replace specialized tax advice.

Corporate income tax (IRPJ and CSLL). Revenue received from the marketplace is the ISV's operating revenue, taxed under IRPJ (15% + 10% surcharge on monthly profits exceeding BRL 20,000) and CSLL (9%). Under the Actual Profit regime, the base is adjusted accounting profit. Under the Presumed Profit regime, the base is a percentage of gross revenue (32% for services, with an effective combined rate of approximately 10.88% on revenue, factoring in IRPJ at 15%, the 10% surcharge, and CSLL at 9%).

PIS and COFINS on export revenue. Revenue received from a foreign marketplace qualifies as service export revenue and is exempt from PIS/COFINS (Law 10.865/2004, art. 6, I; Law 10.637/2002, art. 5, I). The exemption requires complete documentation: service export invoice, marketplace contract, international payment records (inflow of foreign currency), and Siscoserv registration (RPS). Missing any of these documents exposes the ISV to loss of the exemption and retroactive collection with penalties.

ISS. Service export is exempt from ISS (Supplementary Law 116/2003, art. 2, I), provided the service result does not materialize locally. When the ISV develops software locally but the end customer is abroad and the service is consumed outside the country, the exemption applies. Proof requires a contract and evidence that the final customer is abroad.

Double taxation risk. ISVs receiving payments from a US hyperscaler may be subject to US withholding tax of 30% on royalties (or reduced treaty rate, if applicable). Brazil and the US have no ratified double taxation treaty. Mitigation depends on specific contractual structuring and, in many cases, establishing a US entity. Each marketplace has its own contractual regime.

Note: The taxation of ISV revenue via cloud marketplaces has no consolidated case law in Brazil. The recommendation is to structure the operation with specialized tax advisory covering service exports and international treaties. Nexforce Marketplace provides advisory support for ISVs selling via cloud marketplaces, covering cross-border payments and tax documentation.

How much it costs to list and sell on cloud marketplaces

Listing software on a cloud marketplace carries no publication cost. The three major marketplaces charge only on completed transactions.

Transaction fees (revenue share):

AWS Marketplace charges a listing fee on SaaS subscriptions that varies by transaction type and product. For standard marketplace contracts, the typical fee ranges from 3% to 5% on transacted volume. Private offers and renewals may carry reduced fees, negotiated case by case with AWS. AWS also offers the List & Sell Incentive program, which subsidizes listing costs for new sellers.

Azure Marketplace charges a flat 3% fee (standard store service fee) on all transactions. Microsoft manages tax collection in dozens of countries. There is no listing cost.

Google Cloud Marketplace operates on a variable revenue share model, defined by the Vendor Net Revenue Schedule in effect since April 2025. The percentage depends on product type and transaction volume. Listing is free and Google Cloud may offer promotional credits to buyers acquiring eligible solutions for the first time, which can accelerate initial adoption.

Hidden costs:

The visible cost is the revenue share. The hidden cost lies in technical integration and cross-border operations.

Technical integration (billing and metering APIs) consumes 80 to 200 development hours, depending on product complexity. ISVs listing on multiple marketplaces must multiply this effort or use aggregation platforms like Suger or Tackle, which charge an additional 1% to 3% on revenue.

Foreign exchange conversion and repatriation is the largest hidden cost. An ISV receiving USD 100,000 per year via marketplace loses 3% to 5% on traditional bank spreads when converting to local currency. Add IOF at 3.5% on foreign exchange (Decree 12.499/2025), and the conversion and repatriation bill consumes 7% to 9% of revenue before any domestic taxes.

Tax compliance costs (ancillary filings, Siscoserv, tax calculation) consume time and carry risk. A classification error or a missing ancillary filing generates penalties that can exceed years of revenue share.

Cross-border payments: how to receive in USD and convert to local currency

An ISV listed on a cloud marketplace receives payments from the hyperscaler in USD, into a US bank account. The US bank account is a mandatory requirement across all three marketplaces.

Opening a US account can be done through traditional financial institutions (which require physical presence and an EIN) or through digital banking platforms that open accounts for non-residents. The next step is converting USD to the ISV's local currency and repatriating the funds.

This is where most of the money is lost.

Traditional bank spreads for USD-to-local-currency conversion run between 3% and 5% above the commercial rate. For an ISV receiving USD 100,000 per year, that represents USD 3,000 to USD 5,000 lost on spread alone, before any tax.

Add IOF on foreign exchange at 3.5% (Decree 12.499/2025), and total conversion cost reaches 7% to 9% of revenue. On USD 100,000, that is USD 7,000 to USD 9,000.

Nexforce Marketplace operates at this layer: it executes currency conversion at a spread significantly below the banking average and integrates conversion, tax documentation, and invoicing into a single workflow. For the ISV, the result is higher net revenue and simplified tax compliance, particularly for service export documentation (Siscoserv, contracts, payment records).

Common mistakes ISVs make when entering cloud marketplaces

1. Listing on three marketplaces at once without validating any. Technical integration consumes time and returns are not linear. The ISV that enters three marketplaces simultaneously spreads development effort across three different APIs, three review processes, and three support channels. The correct path: list on the marketplace where your ICP already operates, generate recurring revenue, and expand to the second one once the operation is running.

2. Not integrating marketplace billing with the ERP. The ISV receives monthly payments from the hyperscaler, but local accounting requires reconciliation between the US bank statement and declared revenue. Without integration, reconciliation is manual and the risk of tax errors is high. The ISV should automate the recording of each payment received and its conversion to local currency at the time of exchange.

3. Underestimating the cost of currency conversion. The ISV focuses on the revenue share (3% to 5%) and ignores that bank spreads and foreign exchange taxes consume another 7% to 9% on conversion to local currency. The real cost of operating via cloud marketplace is not the revenue share: it is the revenue share plus the cost of converting and repatriating revenue.

4. Ignoring service export documentation. Revenue received from a foreign marketplace qualifies as service export and is therefore exempt from certain domestic taxes. The exemption, however, depends on documentation: marketplace contract, service export filings, international payment records. Without this documentation, the ISV risks audit and loss of the tax benefit.

5. Not treating the product page as a conversion asset. The marketplace is a catalog, not a salesperson. The product page (description, use cases, pricing, screenshots, reviews) is the only touchpoint between buyer and ISV before the purchase decision. ISVs frequently publish listings with generic descriptions and confusing pricing. The result is low conversion even with high traffic.

6. Not planning revenue taxation before the first sale. The ISV that receives USD 100,000 from a US marketplace without having structured the tax treatment of service exports will discover the error on the first tax return. Tax structuring must happen before the first listing, not after the first sale.

Frequently asked questions

Do I need to open a US company to sell on AWS Marketplace?

No. All three cloud marketplaces accept sellers incorporated outside the US, provided the ISV has a US bank account to receive payments. Opening a US entity is a tax optimization and commercial presence decision, not a listing requirement.

Which cloud marketplace should I choose first?

List where your ICP already operates. If your buyers use AWS, start with AWS Marketplace. If they use Azure with Enterprise Agreements (and can use MACC to buy your software), Azure Marketplace. If you sell data and analytics software, Google Cloud Marketplace has the smallest base but the most qualified buyer.

How much does it cost to list my software?

The listing itself is free on all three marketplaces. The real cost is in technical integration (80 to 200 development hours) and revenue share on sales (3% to 5%, depending on the marketplace and transaction type). Currency conversion and repatriation costs (bank spread plus foreign exchange tax) add 7% to 9% on revenue.

Does a buyer in an emerging market pay more tax buying via cloud marketplace?

No. The buyer purchasing software via cloud marketplace faces the same taxes as a direct import. The marketplace does not alter the buyer's tax obligations on cross-border procurement.

An alternative is operating through Nexforce Marketplace: Nexforce imports the software as a distributor and issues a domestic invoice in local currency to the buyer. In Brazil, under this model, the buyer avoids import taxes (IRRF, CIDE, PIS/COFINS-Import, IOF), and companies under the Actual Profit regime recover the 9.25% PIS/COFINS credit via the domestic invoice.

Can I sell to customers in my home country via cloud marketplace?

Yes, but the buyer needs an active account on the hyperscaler (AWS, Azure, or GCP). The transaction is a standard software import: the buyer bears import taxes and the ISV receives USD from the marketplace.

How is revenue taxed for ISVs selling via marketplace?

Revenue received from a foreign marketplace qualifies as service export and is exempt from certain domestic taxes, provided it is properly documented (contracts, export filings, payment records). Corporate income tax applies according to the ISV's tax regime. A complete analysis depends on the marketplace's contractual structure and requires specialized tax advisory.

References and Further Reading

• AWS Marketplace Seller Guide
• Microsoft Marketplace FAQ for Publishers
• Google Cloud Marketplace
• AWS Marketplace Management Portal (seller registration)
• Forrester: The Partner Opportunity for AWS Marketplace
• Brazilian Law 10.168/2000, CIDE on outward remittances
• Brazilian Law 10.865/2004, PIS/COFINS-Import
• Brazilian Decree 6.306/2007, IOF Regulation
• Brazilian Supplementary Law 214/2025, Tax Reform (IBS/CBS transition)
• How to Nationalize Imported Software in Brazil (Nexforce)
• Tax Reform and Software Import Cost (Nexforce)
• Nexforce Marketplace