CPPO
Create and manage Google Cloud Marketplace Channel Private Offers (MCPOs) in Fours: the reseller private offer plans you give channel partners, and the private offers they create from them. Fours files these under the CPPO offer types.
Overview
A Marketplace Channel Private Offer lets you, as an Independent Software Vendor (ISV/Seller), give a Channel Partner wholesale pricing for your software through a reseller private offer plan; the partner then creates the customer’s private offer from that plan. This delegates the financial and contractual side of the customer relationship in GCP Marketplace to your Channel Partner, while you retain full visibility over the deal.
In Fours, you manage the full indirect-channel lifecycle in one place:
CPPO_OUT— the reseller private offer plan you create to authorize a partner.CPPO— the final private offer the Channel Partner creates for the buyer from that plan (Google’s Marketplace Channel Private Offer).CPPO Entitlement— the active contract after the buyer accepts. Entitlements support overage usage metering when the relevant usage metering dimensions are available.
Key terms
- Marketplace Channel Private Offer (MCPO) — a private offer where a Channel Partner works with an ISV to sell a product to a buyer through Google Cloud Marketplace.
- Reseller Private Offer Plan — GCP’s term for the configuration an ISV creates to authorize a Channel Partner to resell their product. It defines pricing, terms, and allowed plans. In Fours this is stored as an Offer with type
CPPO_OUT. - ISV (Independent Software Vendor) — the company that owns and publishes the software in GCP Marketplace.
- Channel Partner (Reseller) — the partner who sells the ISV’s product to the buyer and creates the final private offer.
The three-actor lifecycle
A CPPO deal passes through three parties, and each object in Fours belongs to exactly one of them:
You never see the partner’s markup — only your own wholesale plan, the resulting CPPO record, and the entitlement.
Prerequisites
Before you can create a Reseller Private Offer Plan, both the ISV and the Channel Partner must complete a few GCP Marketplace and Fours setup requirements. If any are missing, you won’t be able to proceed.
Google Cloud Marketplace
- Register as a GCP Marketplace vendor (ISV). The ISV must be enrolled in Google Cloud Partner Network and have an active Cloud Marketplace vendor account with a verified payment profile in good standing.
- Turn on reselling (ISV). Turn on reselling for your products in Producer Portal; until you do, resellers can’t buy them for their customers. This can require an amendment to your Google Cloud Marketplace Vendor Agreement.
- Reseller eligibility (Channel Partner). The Channel Partner must be accepted in Google Cloud Partner Network and participate in its Resale Subprogram.
- Publish an eligible product (ISV only). The ISV must have an active, publicly listed product in GCP Marketplace, such as a SaaS application, Kubernetes app, or Virtual Machine product.
Fours
You need Admin access to the Fours Console. If you don’t have access yet, ask your company admin to invite you to the organization. See Manage Users and Roles.
GCP IAM roles
To let Fours manage your GCP reseller discounts and private offer plans, grant the Fours support user (gcpdev@suger.io) the following IAM roles within your GCP organization (not your GCP project):
- Commerce Business Enablement Configuration Admin
- Commerce Business Enablement Reseller Discount Admin
- Commerce Producer Admin
Or run this command (requires Organization Administrator access; find your ORG_ID with gcloud organizations list):
for ROLE in \
roles/commercebusinessenablement.admin \
roles/commercebusinessenablement.resellerDiscountAdmin \
roles/commerceproducer.admin
do
gcloud organizations add-iam-policy-binding ORG_ID \
--member="user:gcpdev@suger.io" \
--role="$ROLE"
done
Step 1: Create the Reseller Private Offer Plan
After completing the setup, create a Reseller Private Offer Plan (CPPO_OUT) in the Fours Console.
Open the Resale Authorization flow
- Open Offer → Resale in the Fours Console: click Offer in the main navigation, then Resale in the page’s section rail. Resale is no longer an entry in the main navigation, and older links to the
/resalepage redirect there. - Click + New Resale Authorization in the upper-right corner.
- Select the GCP product you want to use. This defines what the Channel Partner is allowed to resell.
To fill the form from what you already have, click Fill with AI in the page header and paste your deal notes or the partner’s email into the AI assistant. It shows the values it proposes and writes them only when you choose Fill the form, and each field it filled is marked AI until you change it. Check every marked field before you click Create offer.
Add basic information
-
Opportunity Name: A custom name to identify the resale authorization. It is displayed to the reseller.
-
Salesforce Opportunity (optional): Link the record to a Salesforce Opportunity.
-
HubSpot Deal (optional): Link the record to a HubSpot Deal.
-
Salesforce Opportunity / Quote / Account: When the reseller creates the final private offer from this authorization, the CPPO and its entitlement inherit the Salesforce Opportunity, Quote, and Account you set here — so the resold deal stays linked to the same CRM records without anyone re-entering them.
-
Scope: Required. How the reseller can use the authorization. Pick one:
Single use: The reseller can use this plan to create one private offer for one specific customer.Multi-use: The reseller can use this plan to create one or more private offers, to resell your products to one or more of their customers.
Leaving it unset, or carrying a value GCP does not accept, blocks the submit with “Please select a valid Scope (Single use or Multi-use).” On an amendment the scope is inherited from the base offer and locked — unless the inherited value is one GCP rejects, in which case the control unlocks so you can correct it.
-
Start Time: When the authorization becomes active. GCP starts a plan at 07:00 UTC on the chosen day, so today is accepted only before 07:00 UTC; from then on the earliest start is tomorrow. Fours checks this again when you submit — which catches a cloned or AI-filled draft still carrying an old date — and names the earliest date you can use: “Start time must be … or later. GCP starts offers at 07:00 UTC, so today stops being accepted once that hour has passed.”
-
End Time: When the authorization expires.
-
Acceptance Due Date: The last date the reseller can accept the offer. Today counts — the date is compared as a UTC calendar date, so a same-day deadline is accepted no matter what time you submit the authorization. It must not fall after the End Time. Besides that End Time rule, it can be no later than today plus three months, minus one day, counted on Google’s Pacific calendar — the same 3-month ceiling Fours applies to a GCP private offer. A later date is refused when you submit, with a message that names the last date you can use.
-
Billing Account Information: The customer billing account details.
Account Name: The name of the billing account.Account ID: The billing account ID to which the reseller can apply this plan. Enter a Cloud Billing Account ID — three groups of six hexadecimal characters,XXXXXX-XXXXXX-XXXXXX— not the reseller’s or customer’s display name. Anything else is flagged when you leave the field, and blocks the submit, with “Enter a Cloud Billing Account ID in the format XXXXXX-XXXXXX-XXXXXX.”
Before it publishes the plan, Fours looks the billing account up with Google, as Producer Portal does when you enter one there. When the lookup succeeds, the plan’s Reseller name in Producer Portal is the billing account’s organization; an account Google says can’t buy through a reseller offer stops the authorization (see If the resale authorization is refused). If the lookup itself can’t run, Fours publishes the plan anyway.
-
Contact Information: Your contact info, shared with the reseller. This is not visible to the customer.
-
Notes to Reseller: Instructions or context for the Channel Partner.
Set pricing information
Select a Plan to define the pricing model. See the GCP pricing models. Fill in the fields that match the selected pricing model.
-
Subscription-based plan
-
Monthly flat fee: How much the reseller pays you for the contract private offer created from this opportunity.
-
Reseller discount (off): The reseller discount on the commitment amount, from 0% (no discount) to 100% (full discount).
-
-
Usage-based plan — choose one of the following usage price models:
-
Commitment discount with additional usage at list price
-
Monthly commitment: The monthly commitment fee the reseller pays you.
-
Discount on commitment: The discount on the monthly commitment fee.
-
Reseller discount (off): The reseller discount on the commitment fee.
-
-
Commitment with all usage discounted
-
Monthly commitment: The monthly commitment fee the reseller pays you.
-
Discount on usage: The discount on usage fees.
-
Reseller discount (off): The reseller discount on the commitment fee.
-
-
Usage-based discount only
- Discount on usage: The discount on usage fees.
-
-
Flat fee with usage plan
-
Monthly flat fee: How much the reseller pays you for the contract private offer created from this opportunity.
-
Discount on usage: The discount on usage fees.
-
Reseller discount (off): The reseller discount on the commitment fee.
-
Set offer settings (optional)
Enable features resellers can use when creating private offers:
Allow scheduled start date: Whether the reseller private offer plan can start on a scheduled date.Allow auto renewal: Whether the reseller private offer plan can auto-renew.Number of renewals: The number of renewals allowed.
Define legal terms
- SOW (Professional Services products only): Fours requires a statement of work on a resale authorization for a Professional Services product, so for those products a SOW section appears before the EULA. Optionally enter a file name, then select or upload the PDF. Create offer stays greyed out until a SOW file is attached, and its tooltip names SOW among the fields still to complete. A replacement CPPO starts with the SOW of the resale authorization it replaces; if the field is empty, attach the file again.
- End User License Agreement (EULA): Choose Google Cloud Marketplace Standard EULA or Use your own EULA for your custom contract. For a Professional Services product, the standard option reads None instead.
- Reseller Agreement (PDF) (optional): Select or upload the terms for the Channel Partner.
- Deal Type: The type of commercial agreement used.
Fours’ SOW rule for Professional Services resale authorizations matches what Google requires of a direct Professional Services private offer: a statement of work, and no Standard EULA. See Google’s Create and manage private offers using the API.
Click Create offer to finish. It stays greyed out while a required field — marked with an asterisk (*) — is empty or a value isn’t valid; hover over it, or press Tab until it has focus, to see what’s left.
Amending an existing CPPO: Change Offer Duration
When you build a replacement CPPO, a Change Offer Duration switch appears above the date pickers:
- Off (default) — the new offer coterms to the offer it replaces. End Time is locked to the replaced offer’s end time, so both finish together.
- On — set your own End Time.
Leave it off unless the deal genuinely changes the end date. Coterming is what lets GCP align the new plan’s schedule against the replaced offer; without it, GCP has nothing to align to and rejects the publish.
If Fours cannot determine which offer the replacement CPPO replaces, the form stops with “Could not determine the offer being replaced. Reload the entitlement and try again.” The create API refuses the same request, so an amendment is never created as a new reseller plan by mistake.
If the resale authorization is refused
A start date that has passed. GCP starts a plan at 07:00 UTC on the chosen day, so a date stops being accepted at 07:00 UTC that day. When you click Submit on a saved draft, Fours checks its Start Date and Offer Start Date first. If either has passed, nothing is sent: a toast reads “The Start Date … has passed.” with “Change it to … or later. GCP starts offers at 07:00 UTC.”, and its Edit Draft button opens the draft so you can change the date. The create API refuses the same request with the same message, for a new authorization and a replacement alike.
Google’s refusals. When Google refuses to publish the authorization, two of its terse errors are replaced on the offer with what to check:
- A failed precondition reads “Google refused to publish this resale authorization. Check that the Start Date, Offer Start Date and acceptance due date are all still in the future, then click Edit Draft to change them.”
- When Fours can’t open the Producer Portal’s resale pages for your organization, the offer reads “Fours couldn’t open the Google Cloud Producer Portal for your GCP organization …”, naming the organization, and lists the three roles in GCP IAM roles. Missing roles are the usual cause, but a timeout or a passing Portal failure reads the same, and Fours does not retry it on its own. Check that the Fours support user holds each role on the organization, not only on the project, then submit again.
A billing account Google won’t accept. When Google says the billing account you entered can’t buy through a reseller offer, the authorization fails with a message naming the account and Google’s reason. Check the Account ID against the scope: the customer’s Cloud Billing subaccount for Single use, the reseller’s Cloud Billing account for Multi-use.
For help with any of these, click Troubleshoot with AI in the authorization’s Create Offer Failed alert; when Create offer fails on the form, a Submission failed box shows the error with Fix with AI. Nothing runs until you click, and each run uses your organization’s AI credit.
Step 2: Hand off to the Channel Partner
Once your Reseller Private Offer Plan (CPPO_OUT) is active, the Channel Partner creates the final private offer for the buyer. As the ISV you can’t build the offer for them, but you initiate the handoff and monitor progress.
Notify the Channel Partner
- Open the active Reseller Private Offer Plan in the Fours Console.
- Click More actions in the top-right corner and select Notify Contact.
- Fours emails the reseller a direct link to the plan, letting them know it’s ready to use.
Coordinate deal details
Work with your partner to confirm the correct GCP Cloud Billing account based on the plan’s Scope.
Step 3: Track buyer acceptance and entitlements
After the reseller generates the private offer, you won’t see their final markup, but you can oversee the entire deal lifecycle in the Fours Console for full visibility into your indirect channel sales.
Track your wholesale plan (CPPO_OUT)
Once the reseller successfully generates the private offer, your original Reseller Private Offer Plan status changes to Used.
Monitor the new private offer (CPPO)
A new deal entry automatically appears with type CPPO and a Pending Acceptance status. This confirms the final offer has been delivered to the buyer and is awaiting their approval.
Confirm buyer acceptance and ISV approval
Keep an eye on the CPPO record. For GCP SaaS products, you may need to manually approve the accepted offer before it becomes active, unless you have automatic offer approval enabled.
Manage active entitlements
Once the buyer accepts and the offer is activated, a CPPO Entitlement is generated automatically. This is your authoritative record of the active contract and fully supports overage usage metering when applicable.
The reseller’s offer and its entitlement are linked to the authorization they came from, so they appear on its Entitlement tab, whether or not the integration has Enable PrivateOffer API on (see About Enable PrivateOffer API). Fours makes the link when it syncs the reseller’s offer. It also links the entitlement when the buyer accepted before Fours had synced your authorization, or when a replacement moved the buyer’s existing entitlement onto the offer, and copies the CRM records the offer is linked to — such as its Salesforce opportunity or HubSpot deal — onto that entitlement. With Enable PrivateOffer API on, the hourly sync reads only offers changed in the last 7 days; to link an older offer, run a full sync.
How resellers and buyers appear in your buyer list
Indirect deals introduce two accounts to your buyer list — the reseller and the end customer — and GCP does not always name them consistently. Fours reconciles that for you.
No duplicate row when the reseller got there first. A reseller who transacts on your behalf often appears in Fours before the marketplace account behind them is known. When that account does show up, Fours attaches it to the row already waiting for it rather than creating a second one — but only if that row has no marketplace account of its own yet. A row already linked to a different account is left alone, because one Cloud Billing account can host several GCP accounts and they are genuinely different buyers.
A resolved name is never replaced by a placeholder. GCP sometimes omits a billing account’s organization display name and nickname. When both are missing, Fours falls back to a label built from the billing account ID — but it will not overwrite a real name it already has with that placeholder. So a reseller you know by name keeps that name even across a sync that returned a thinner payload.
If two rows for the same partner do end up in your list, that means they carry different marketplace accounts; contact support@suger.io rather than merging them yourself.
Spotted something wrong or out of date on this page? Tell us and we'll correct it.