Marketplace Onboarding: What Actually Breaks Between the Listing and the Money
Listing is the easy part. The fees, the taxes, the collection cycle and the commitment drawdown are where ISVs get surprised — across AWS, Microsoft, Google, OpenAI and Anthropic.
Every quarter I talk to ISVs who have just been listed on a marketplace, and the first two questions are always the same: "Are we live?" and "When does the money arrive?"
The first one has a date. The second one has a contract, a fee schedule, a tax rule, a payout calendar, and — depending on which marketplace you chose — a very different answer from the one your finance team is expecting.
Here is the thing nobody tells you in the partner meeting: "we are on the marketplaces" is not one thing. AWS Marketplace, Microsoft Marketplace, Google Cloud Marketplace, OpenAI Marketplace and Claude Marketplace look similar from the outside. They are not. Each one decides for you who invoices the customer, who collects the money, who remits the tax, how much they keep, and when you get paid. Getting that wrong is not a detail. It is the whole difference between revenue you can forecast and revenue you cannot explain.
Let me walk the five.
AWS Marketplace: the marketplace is the seller
This is the model most ISVs meet first, and it is the one that feels easiest — until you read the fee table.
AWS charges a listing fee on the pre-tax Total Contract Value, and it deducts it from your disbursement. The rates are not one number:
- SaaS and Data Exchange public offers: 3%
- Server products — AMI, container, and machine learning listings: 20%
- Private offers under $1M TCV: 3%; $1M to under $10M: 2%; $10M and above: 1.5%
- All renewals: 1.5%, regardless of size
- Channel Partner Private Offers: +0.5% on top, charged on the discounted price you gave the partner
- Professional services: 0.5%, and 0% when the professional services offer sits inside a qualifying multi-product solution offer set
- Buyers in South Korea: +1% regional fee, additive
Two things get people. First, that 20% on a server product — the same listing that costs 3% as SaaS. Second, the private-offer bands: they are set by contract value, not annual value, so a three-year commitment worth $1.5M lands in the 2% band even though each year is $500K. And renewals are always 1.5%, which is why a $20M renewal costs the same as a $200K one.
On the money side, AWS is the merchant of record. It invoices the customer, collects, and disburses to you monthly. You never send the invoice. You never chase the payment. That is the appeal.
It is also the trap. AWS collects tax in some jurisdictions and not others. If you are a seller in India, GST applies and is deducted automatically from disbursements. And your direct-sales obligations do not disappear because your cloud channel is on someone else's invoice. If your finance team assumed "the marketplace handles tax," they are wrong on the direct leg and possibly on the marketplace leg too.
Microsoft Marketplace: closer, with one checkbox that costs you 1.5%
Microsoft's model is similar — Microsoft is the seller of record for transactable offers, and when you use transact it acts as the agent of the publisher for billing, payment and collection.
The fee is a 3% store service fee on transactable offers. There is no listing fee to publish. Note the shape of it: publishing is free, and you pay on the transaction.
The detail that costs real money is the renewal discount. Microsoft will apply a 50% discount to the transaction fee for private offer customer renewals — 1.5% instead of 3% — but only if the publisher ticks "this is a renewal" when creating the private offer in Partner Center. Miss the box and you pay the standard 3%. There is no retroactive correction.
Then there is the one nobody budgets for: Microsoft bills you directly for the Azure infrastructure your own SaaS consumes. The customer never sees that line. You have to account for it in your licence pricing as a single cost item, and it changes what a "flat rate" offer actually earns you.
Payout timing follows the customer's payment terms, not yours. Transactions against an Enterprise Agreement pay out in the cycle 30 days after the customer invoice. Credit-card transactions carry an additional 30-day escrow period after Microsoft receives payment. Payouts are monthly, and only release once sales reach a minimum combined value of $50.
If your customer has not paid, you are not paid. That is not a marketplace failure — that is a collections risk you have imported into your margin model.
Google Cloud Marketplace: two models, two tax answers, three invoices
Google is the one that breaks spreadsheets, because Google Cloud Marketplace runs two transaction models at once.
Under the agency model, Google is your payment agent. You remain the merchant of record. Your customer receives a "Request for Payment" document for your product, and you are responsible for invoicing the customer directly for applicable taxes — in Australia, for example, a domestic vendor must invoice GST itself, and a vendor outside Australia receives a standard Cloud Marketplace Invoice with Google-assessed taxes instead. Google will collect transaction taxes where it is appointed to do so, but you have to notify Google when the law puts the obligation on you, and then invoice Google for it.
Under the merchant of record model, Google is the reseller: Google sets the price, Google takes the refund risk, and the transaction-tax clause does not apply.
And since charges incurred in June 2026, customers receive three separate billing documents each month: the Google Cloud Invoice, a Cloud Marketplace "Request for Payment" for agency-model purchases (no VAT in the total), and a Cloud Marketplace Invoice for reseller-model purchases.
Payouts land typically on the 21st of each month. Google will not pay out if the Vendor Net Revenue due is under $100 — it carries over. And for US customers, taxes are not included in the net revenue Google pays you; for non-US customers they are included.
Same product, same customer, two tax treatments, two invoice documents, two payout rules. An ISV that runs three marketplaces without a per-route tax map is reconciling three different stories.
OpenAI Marketplace: a commitment, not a channel
This is the one I would put in front of an ISV right now, because it is new and because the mechanics are genuinely different.
OpenAI Marketplace launched at DevDay on 29 September 2026 with 32 launch partners — Adobe, Figma, Salesforce, ServiceNow, HubSpot, Sierra, Zendesk, CrowdStrike, Palo Alto Networks, Harvey, Baseten, Vercel and the rest. It is not an app store. Think of it as a procurement route built on committed AI spend.
The mechanism, in four steps:
- OpenAI and the partner confirm whether the customer and the proposed purchase qualify.
- The customer contracts directly with the partner.
- The partner invoices the customer.
- OpenAI records the eligible amount against the customer's OpenAI commitment.
Step three is the one that changes your finance team's week. On AWS and Microsoft, the marketplace invoices and collects for you. On OpenAI Marketplace, you invoice the customer. You own the invoice, the collection, and the tax: the customer is responsible for applicable taxes on partner products, which the partner — or OpenAI, as applicable — charges when required by law.
The commitment mechanics have hard edges, and they are all in the published program terms (effective 6 November 2026):
- The customer needs an OpenAI Order Form with a commitment of at least US$1,000,000 to participate.
- The Marketplace Allowance equals 25% of the Commitment Amount for the commitment period, applied collectively across all partners. Unused allowance expires at the end of the period and cannot be transferred.
- OpenAI will apply charges for no more than twelve months of a partner subscription at a time. For a multi-year subscription, each subscription year is invoiced separately, and you re-submit the invoice for that year — even if the customer prepaid.
- Eligibility is decided per customer, per product and per purchase. Being a partner does not make your whole catalogue eligible.
- Taxes, bank and financing charges, and professional services charges do not qualify as eligible spend.
- The terms also allow for the day OpenAI begins collecting payments on your behalf — the transition is possible, and it is negotiated, and it is not automatic.
One more thing about joining: it is a waitlist, not a sign-up. Participation is subject to eligibility and approval, and the initial experience supports discovery and expressions of interest — there is no self-service checkout. If your enterprise customers buy through procurement, this is a procurement conversation you have to be in the room for.
Claude Marketplace: same promise, different hand
Anthropic's Claude Marketplace runs the same logic: eligible enterprise customers apply part of their existing Anthropic commitment toward Claude-powered partner products, with Anthropic managing the invoicing for partner spend. It launched in limited preview and expanded on 4 November 2026 to more than 25 partner agents and products across security, developer infrastructure, creative work and productivity. Partners join through a waitlist.
So: two AI marketplaces, both funded from a commitment, both approval-gated, and — critically — not the same hand on the invoice. Anthropic manages the invoicing for Claude Marketplace. On OpenAI Marketplace, the partner invoices the customer.
The order-to-cash map nobody builds
Put the five side by side and the shape of the problem becomes clear.
On AWS and Microsoft, the marketplace is the seller: you never invoice, never collect, and pay a fee out of what you are disbursed. On Google, it depends on the transaction model, and the tax obligation can land back on you. On OpenAI Marketplace, you are the seller of record — you invoice, you collect, you chase, you remit — and the marketplace's role is to let your buyer's committed AI budget pay for it.
That is a different business. It is closer to your existing direct-sales motion than to a channel, and it should be run that way: with an invoice you control, a collection cycle you own, and a reconciliation against the buyer's commitment rather than against a payout report.
Which brings me to the actual work. The order-to-cash map for one ISV, across five routes, answers:
- What does each offer type actually cost on each route, and at what contract value?
- Which route puts the invoice in your name, and which puts it in the platform's?
- Who collects, and how long between invoice and cash?
- Which taxes are yours to charge, and which are already collected by the platform?
- How much of the buyer's commitment is actually available to you — and what is the allowance?
- When the month closes, does the payout report reconcile to the invoice, line by line?
Most ISVs have fragments of this. Almost nobody has the map.
That is the engagement: we take you from not-listed to transacting, and then we fix the money side — the fee your offer type actually pays, how much of the buyer's cloud or AI commitment you can draw, who collects the tax on each route, and how your invoice becomes cash.
If you want to see whether this is your problem before you book anything: you are listed, but you cannot tell me what you actually made. That sentence is the whole diagnostic. And if it is not your problem, we will tell you on the call — that is faster for both of us than a proposal neither of us needs.
Book 25 minutes if you want to walk your own numbers.