Aein Esk has helped 60+ ISVs list and transact on AWS, Azure, and GCP Marketplace. He founded Automatum to remove the engineering and operational complexity that slows cloud marketplace programs down.

This post is for ISV founders, heads of sales, and GTM leads who want to close larger GCP deals faster by routing them through Google Cloud Marketplace as private offers. It covers exactly what a Marketplace Consumption Partner Offer (MCPO) is, how to create one in the GCP Producer Portal, how buyers consume them against committed spend, and the mistakes that slow or kill deals in the field.

What Is a GCP Marketplace Private Offer (MCPO)?

A GCP Marketplace private offer — formally called a Marketplace Consumption Partner Offer (MCPO) — is a customized, buyer-specific listing that an ISV creates in the GCP Producer Portal and sends to a named customer account. The buyer sees custom pricing, custom contract terms, and a defined subscription period.

Unlike your public listing, an MCPO is visible only to the customer you target. When accepted, the transaction runs through Google Cloud's billing infrastructure and counts against the buyer's committed GCP spend.

Standard GCP Marketplace listings display fixed public pricing available to any buyer. They work well for self-serve, low-ACV products.

But enterprise deals almost never fit a public listing: pricing is negotiated, terms are customized, and the customer's procurement team needs a procurement-channel-native transaction to clear legal and finance quickly. That is exactly what an MCPO enables.

The term MCPO reflects Google's framing around the Marketplace Consumption Partner program — the incentive layer Google operates to reward ISVs who drive net new GCP consumption through their products. A private offer can exist independently of the MCPO incentive program, but the terminology is widely used by Google's partner team to refer to the private offer mechanism in general.

Throughout this post, MCPO means the private offer mechanism unless otherwise specified.

MCPO vs. Standard Marketplace Listing: When to Use Which

A standard public listing and an MCPO serve fundamentally different deal types. The decision is driven by deal size, whether terms need to be negotiated, and whether the buyer has committed GCP spend they want to deploy. Use the table below to orient your deal routing decisions.

The practical decision rule: any deal where you are in active commercial negotiation with an enterprise buyer who runs workloads on GCP belongs in an MCPO. Any deal under $25K with standard terms and no procurement overhead can go through the public listing.

How Buyers Consume MCPOs Against Committed GCP Spend

Enterprise GCP customers often sign Committed Use Discounts (CUDs) or Google Cloud Platform Commit agreements — multi-year spending commitments in exchange for discounted cloud pricing. These commitments are real financial obligations.

A buyer with a $5M annual GCP commit who has only deployed $3.2M so far is actively looking for ways to spend the remaining $1.8M against approved cloud vendors.

When a buyer accepts an MCPO, the purchase value counts against their committed GCP spend balance, just like a Compute Engine or BigQuery invoice does. From the buyer's finance team perspective, the ISV software purchase is not a new line item requiring new budget approval — it draws down an existing commitment.

This eliminates the most common procurement delay ISVs face: the "we need to find budget" conversation.

We have seen GCP MCPO deals close 40% faster than the same deals attempted through direct PO channels, precisely because the committed spend angle removes the budget approval step. For a buyer with $800K in uncommitted CUD balance and a June 30 fiscal year-end, accepting an MCPO before year-end converts stranded committed spend into real software value — and that urgency becomes a natural deal accelerator.

Two important conditions apply. First, your GCP Marketplace listing must be published and transactable — an MCPO is a custom layer built on top of an existing listing, not a standalone creation.

Second, the buyer must have an active Google Cloud billing account with a committed spend agreement. Google Cloud's field team can help you identify which of your prospects hold GCP commitments; this information is often surfaced during co-sell conversations.

Step-by-Step: How to Create an MCPO in the GCP Producer Portal

Creating an MCPO requires an active, transactable listing on Google Cloud Marketplace and access to the GCP Producer Portal (also called the Cloud Commerce Producer Portal). Here is the end-to-end process.

Step 1: Confirm Your Listing Is Transactable

Log into the GCP Producer Portal and verify that your listing has a published, transactable pricing plan. A listing in draft or review state cannot have an MCPO created against it.

If your listing is not yet transactable, the first step is completing the listing review process — which typically takes two to four weeks for SaaS listings.

Step 2: Open the Private Offers Section

In the Producer Portal, navigate to your product listing and select Private Offers from the left navigation panel. Click Create Private Offer.

Step 3: Identify the Buyer Account

Enter the buyer's GCP billing account ID. This is a 16-character identifier in the format XXXXXX-XXXXXX-XXXXXX. Your buyer's finance or cloud ops team can provide this — it appears in their GCP Billing console under Billing Account Settings.

The offer will be visible only to this billing account once created. If the buyer has multiple billing accounts (common in large enterprises), confirm which account holds the committed spend balance before you enter the ID.

Step 4: Configure Pricing and Terms

Select the base pricing plan from your public listing that the MCPO will customize. Then configure the private offer terms:

• Custom price: Enter the negotiated per-unit or flat-rate price. This replaces your public listing price for this buyer only.
• Subscription duration: Set the contract length — monthly, annual, two-year, or three-year.
• Payment schedule: Choose upfront, monthly, or custom milestone billing. For large deals, upfront payment is common because it maximizes the buyer's committed spend drawdown in the current period.
• Offer expiration date: Set a date by which the buyer must accept. A 30-day expiration is standard; 14 days is common when there is urgency around a fiscal year-end committed spend deadline.
• Custom end-user license agreement (EULA): If your legal team has negotiated custom contract language, attach it here as a PDF. Google allows custom EULA attachments on private offers, which replaces the need for a separate side-letter agreement.

Step 5: Review and Send

Review all terms. Once submitted, Google processes the offer (usually within a few hours, though some offers require a short review period).

The buyer receives an email notification from Google with a link to view and accept the offer in their GCP console. You cannot modify the offer after it is sent — if terms need to change, you must create a new offer and ask the buyer to discard the previous one.

Step 6: Notify the Buyer Directly

Do not rely solely on Google's automated email. Send the buyer a direct message — from your AE to their champion — with a link to the offer, the billing account it was sent to, and a clear deadline.

Enterprise buyers often have Google's automated notifications routed to a generic cloud-ops inbox, not to their decision-maker. Direct outreach ensures the right person sees the offer and acts on it.

Step 7: Monitor Acceptance in the Producer Portal

Track offer status in the Producer Portal under Private Offers. Once the buyer accepts, the subscription activates, you receive a confirmation from Google, and entitlement provisioning should trigger from your backend via the Cloud Commerce Partner Procurement API if you have that integration live.

MCPO vs. AWS Private Offer vs. Azure Private Offer: Key Differences

If you are running a multi-cloud marketplace program — which most ISVs targeting enterprise accounts should be — the private offer mechanisms differ meaningfully across GCP, AWS, and Azure. Understanding these differences prevents operational errors and sets the right buyer expectations.

The most important operational difference: Azure private plans require the buyer to navigate to your marketplace listing themselves — there is no push notification to the buyer. On AWS and GCP, the buyer receives a direct email.

For GCP specifically, always follow up with direct outreach in addition to the Google-generated notification.

Common MCPO Mistakes ISVs Make

We have seen dozens of MCPO deals stall or fail at the operational level — not because the commercial terms were wrong, but because of avoidable errors in how the offer was configured or managed. Here are the most frequent ones.

Mistake 1: Using the Wrong Buyer Billing Account ID

Enterprise buyers often have multiple GCP billing accounts — one per business unit, subsidiary, or project portfolio. The committed spend balance you are targeting lives in a specific billing account.

If you send the MCPO to the wrong account, the buyer cannot accept it from the account they intended to use for the committed spend drawdown. Always confirm the exact billing account ID with your champion before creating the offer, and verify that it is the account that holds the CUD balance.

Mistake 2: Setting the Offer Expiration Too Short

A 7-day expiration on an enterprise offer is almost never enough time. Even when your champion is enthusiastic, enterprise buyers need time to route the offer through their cloud procurement or FinOps team for acceptance approval.

A 30-day expiration is the minimum for most enterprise accounts; extend to 45 or 60 days if the deal is complex or involves custom legal terms. Short expirations create unnecessary pressure that can sour the relationship — or simply cause the offer to lapse.

Mistake 3: Sending the MCPO Before Legal Is Aligned

If you attach a custom EULA to the MCPO, both sides should have signed off on the legal language before the offer is sent. Sending an offer with unreviewed legal terms creates a situation where the buyer's legal team wants changes, the offer expires while negotiations drag on, and you have to create a new offer.

Do the legal negotiation off-platform first; only create the MCPO when the commercial and legal terms are agreed.

Mistake 4: Not Having the Procurement API Integration Live

When a buyer accepts an MCPO, Google sends an entitlement event to your backend via the Cloud Commerce Partner Procurement API. If your integration is not live — or is only partially implemented — you will not receive the entitlement signal, which means you cannot provision the buyer's account automatically.

The result is a manual provisioning scramble after close, which creates a poor first impression at exactly the wrong moment. Complete and test your Procurement API integration before you send your first MCPO.

Mistake 5: Not Tracking MCPOs in Your CRM

A GCP MCPO that closes does not automatically appear in your Salesforce or HubSpot pipeline. Without intentional tracking — tagging the deal as a marketplace-transacted opportunity, linking it to the MCPO offer ID, recording the contract value and committed spend consumed — you have no visibility into marketplace-attributed revenue.

You also cannot build the data set that informs your co-sell prioritization, your marketplace ROI conversations with leadership, or your Google partner renewal discussions. Track every MCPO deal in your CRM from the moment the offer is created.

How Automatum Handles the MCPO Workflow

Creating an MCPO manually through the GCP Producer Portal is straightforward for a single deal. Managing an MCPO program at scale — multiple deals in flight, different billing account IDs, varied expiration dates, custom legal attachments, post-acceptance entitlement provisioning — is operationally intensive without dedicated tooling.

Automatum handles the MCPO workflow without requiring any engineering effort from your team. We manage the Producer Portal configuration, buyer account verification, offer creation, expiration tracking, and post-acceptance entitlement events — all through a single dashboard that also covers your AWS and Azure private offers.

ISVs who have run their first marketplace deals manually consistently report that the operational overhead of managing multiple simultaneous private offers becomes unworkable without a system.

Automatum works with ISVs of all sizes — not just enterprise-stage companies with dedicated marketplace operations headcount. Smaller teams benefit most: instead of hiring a marketplace operations specialist, the entire workflow runs through Automatum's platform.

We have facilitated 60+ listings and private offer programs across all three major cloud marketplaces, which means the edge cases and operational failures described in this post are ones we have already encountered and built solutions for.

If you are already listed on GCP Marketplace and want to activate private offers, or if you are still in the listing process and want the MCPO workflow built in from day one, the GCP Marketplace page at automatum.io covers how we support both paths.