Create Reseller Authorization

Easily create a reseller authorization (Channel Partner Private Offer / CPPO) using the Fours App within your Salesforce Console.


Overview

A reseller authorization — also called a Channel Partner Private Offer (CPPO) — is how you give a reseller or channel partner permission to sell your product on a cloud marketplace on your behalf.

Here’s how it works in plain terms:

  • You (the ISV) create a reseller authorization that sets the price you’re willing to give the reseller.
  • The reseller then creates their own private offer to the end customer, using your authorization as the basis — at whatever markup they choose.
  • The end customer buys from the reseller through the marketplace, and billing flows through accordingly.

Think of it as a wholesale price you set for your channel partner, who then handles the last mile to the customer. On Azure you can instead grant a standing resale authorization, which carries no price. On AWS you can instead authorize AWS Brazil as a Distributor: there is no channel partner, and AWS Brazil makes the offer to one buyer in Brazil as seller of record, under AWS’s program terms.

For more details on resale, see Channel Partner Private Offers (CPPO).

Prerequisites

  • The Fours App must be installed, connected, and set up with the Fours widget on your opportunity pages. If you haven’t done that yet, work through Install the Fours App first.
  • You need the Fours User, Fours User - Marketplace, or a cloud-specific marketplace permission set assigned to your Salesforce account. If you can’t see the New Offer button on an opportunity, your permission set is likely missing — see Permission Sets.
  • The product you want to authorize must already exist in Fours. If it doesn’t, create it in the Fours Console first. See Products.

Create a Reseller Authorization

  1. Navigate to the opportunity’s detail page (the opportunity associated with your reseller) and click the New Offer dropdown button at the top of the Fours App. If you don’t see the widget, it may not be added to your page layout yet — see Page Components.
New Offer dropdown button on Salesforce opportunity page
  1. Locate and click the “Reseller Authorization” button.
Reseller Authorization option in New Offer menu
  1. Choose the product on which the Reseller Authorization will be based and complete the required fields in the form. Note that the required fields may vary depending on the cloud marketplace and type of product. The product list shows only the products available in your Fours account — if you are assigned a cloud-specific permission set (e.g., Fours Marketplace - AWS), you will only see products for that cloud. Each product is listed with its type after its name — an AWS SaaS product, contract or subscription, reads {product name} · SaaS, and other products show the type stored for them — so you can tell which AWS products offer the Distributor resale type.
Product selection for reseller authorization
Reseller authorization form fields
  1. Once all necessary information is filled in, submit the form to create the offer. Salesforce asks you to confirm: the prompt is headed Create resale authorization and reads Create this resale authorization?; click OK. With the offer approval process on, an approver’s Approve & Create asks instead, under the heading Approve request: Approve this request? The resale authorization will be created as soon as you approve.
Completed reseller authorization form ready to submit
  1. You are all set!

AWS: choose the currency

The AWS reseller authorization form has a Currency section — Choose a transaction currency for this offer. You will receive payment in the selected currency. — with USD, AUD, CAD, GBP, EUR and JPY, USD by default. A currency your AWS Marketplace integration doesn’t support is refused when you submit: the currency code … is invalid for AWS marketplace.

That choice is for a Channel partner authorization. On a Distributor authorization the section shows USD, read-only, and reads You will receive payment in USD.

AWS: commit term length

The AWS reseller authorization form accepts a commit term length of up to 144 months for SaaS products — contract or subscription — and up to 60 months for other AWS product types.

AWS: Distributor (AWS Brazil 2P)

On an AWS SaaS product — contract or subscription — the AWS reseller authorization form starts with a Resale type section, Choose how this authorization is resold., with two choices:

  • Channel partner — the default, and the form the rest of this page describes.
  • Distributor — authorizes AWS Brazil to distribute your product to one buyer in Brazil, under the AWS Brazil 2P program. The program’s prerequisites, and what happens once the authorization is Active, are in AWS Brazil 2P.

Choosing Distributor changes the form to what AWS accepts for an authorization to AWS Brazil (Brazil 2P Authorizations):

SectionOn a Distributor authorization
Reseller AccountFixed and read-only: Amazon AWS Serviços Brasil Ltda. · 664418980131, AWS Brazil’s own account. There is no reseller list and no Add reseller manually.
AcknowledgmentAdded. Tick both boxes: I acknowledge that any deals created through this authorization will be subject to the 2P Distribution Program Seller Terms. (the last words link to AWS’s seller terms), and I acknowledge that any disbursements I receive will be subject to withholding tax (WHT) as required by applicable law.
BuyerRequired, and takes one buyer: One buyer AWS account. Required on this path.
Maximum buyer net payment termNot shown.
CurrencyUSD, read-only.
DurationSingle use, read-only: One offer can be created per product specified.
EULAUse your own EULA only, with no Attach Standard Contract for AWS Marketplace checkbox and no option to attach the public offer’s EULA.
Reseller AgreementNot shown.

The rest of the form — pricing, renewal, the expiry and maximum service start dates, usage dimensions and your EULA files, plus whatever else the product’s type offers — is still yours to set.

Before it is created. Create, Approve & Create and Submit for Approval check AWS Brazil’s rules first. A form that breaks one stops with The private offer is not valid: followed by the reason:

MessageWhat to do
A Distributor authorization supports SaaS products only. Switch to Channel partner, or choose a SaaS product.Choose a SaaS product, or switch Resale type back to Channel partner.
Buyer is required.Enter the buyer’s AWS account ID.
A Distributor authorization targets exactly one buyer.Leave one buyer on the authorization.
A Distributor authorization needs your own EULA.Set EULA Type to Use your own EULA and attach your EULA. A reopened draft can still hold a standard EULA.
Both acknowledgments are required.Tick both boxes under Acknowledgment.

Save as Draft doesn’t run these checks, so you can save a draft before ticking the acknowledgments.

Switching Resale type. Choosing Distributor keeps only the first buyer, sets Currency to USD, Duration to Single use and EULA Type to Use your own EULA, unticks the attach checkboxes and removes any reseller agreement files. Switching back to Channel partner empties Reseller Account, so pick the reseller again. Either switch unticks both acknowledgments, so tick them again after you choose Distributor. Resale type can’t be changed for a moment when the form opens, while it loads your organization’s settings.

When your admin has locked parts of the form. If you don’t hold the Approve Offer permission and your admin has locked sections of this form, a Distributor authorization leaves the locked sections below Resale type editable — pricing, payment schedule, duration, renewal, dates, usage dimensions and the EULA — because AWS Brazil needs values of its own. Opportunity Name and Description keep their lock. Switching back to Channel partner puts the locked values back: the pricing, payment schedule, duration, renewal, dates and usage dimensions together when any of them is locked, and the EULA when it is. With nothing locked, your Distributor edits stay. A draft or a clone that opens as a Distributor has no locked values to put back, so while any of those sections is locked it can’t switch to Channel partner: the form says This authorization cannot switch to Channel partner. — Some of its fields are locked by your admin. Create a new authorization instead.

Where the resale type shows afterward. Once the authorization exists, its card in the opportunity’s Fours widget shows Resale Type — Channel partner or Distributor — just before Reseller ID, and so does Offer Information on its offer detail page (see Resale Type).

AWS: Percentage discount

On a SaaS contract, AMI or container product, Discount Type offers Percentage discount: apply a single discount rate to all prices. With it selected, the form prices each commit and each usage dimension’s Unit Rate from the product’s list price less your Percentage Discount, rounded to three decimals, and those prices are read-only. A commit you pick with Add commit afterwards is priced the same way, and one with no list price stays at 0. A commit you add with Create new commit keeps the price you enter. The dimension-tag discount panel is hidden while Percentage discount is selected. A draft saved with Percentage discount reopens on it with its percentage, 0% included; choosing Percentage discount before you enter a rate prices everything from the list at 0%.

Dates on a GCP reseller authorization

Three dates on the GCP form are checked before the authorization is submitted. All three accept today — they are compared as calendar dates in your own timezone, so picking today is never rejected as being in the past:

DateRule
Offer start timeToday or later. “The offer start time should be today or in the future.”
Acceptance Due DateToday or later, and within GCP’s three-month acceptance window. A later date passes the form but is refused when you submit: the Failed to create CPPO_OUT message contains the offer expiration date (…) is too late. Google Cloud Marketplace requires offers to expire within 3 months, so choose a date on or before … — pick that date or an earlier one.
Scheduled start dateToday or later, when the start policy is On a scheduled date and you are setting custom payment installments.

The offer end time must be on or after the start time, and the installment start date on the form is labelled (UTC) because the installment arithmetic runs in UTC.

GCP: reseller discount

Reseller Discount (%) on the GCP reseller authorization and its replacement form accepts any value from 0 to 100 with up to six decimal places. On a payment schedule, each installment’s Discount on Usage or Discount on Commitment accepts 0 to 100 with up to two decimal places, such as 12.5.

A flat fee or commitment of 0. The flat fee on the GCP reseller authorization and its replacement form (for example Monthly Flat Fee, or Monthly Commitment on a usage plan) accepts 0. Only an empty or negative amount is refused, with The commit amount should be greater than or equal to 0. A saved draft with a fee of 0 reopens showing 0 rather than an empty field.

Amending from a Salesforce record. When you amend a GCP entitlement bought through a reseller from New Offer → Amendment Offer, the replacement form applies your private offer field mapping on top of the original authorization. Mapped values fill in what an amendment lets you change, such as the name, expiry date, duration, buyer and seller contacts, notes, discounts, deal type, features, EULA, reseller agreement, SOW, Reseller Discount (%) and Offer Duration. What the amendment locks to the authorization it replaces keeps the original value: Billing Account Information, Scope, Payment Schedule, Proration, and which offer is replaced. A mapped usage pricing model is used only when the replaced offer has none, because GCP refuses a replacement that changes it.

The replacement form also refuses to replace a reseller authorization that GCP already shows as ended — expired, cancelled, lapsed, or failed approval — unless its entitlement is pending cancellation. See GCP replacement offers for the message and what to do instead.

GCP: SOW on a Professional Services authorization

When the product is a Professional Services product, the GCP reseller authorization form adds a required SOW section under Legal Terms, before the EULA. Upload a PDF of up to 3.5 MB, or click Select from Opportunity Attachments to pick one from the opportunity’s files. Without a SOW the form refuses to submit with The SOW agreement document is required for professional service resale authorizations. For these products the first EULA choice reads None in place of Google Cloud Marketplace Standard EULA. When you amend the authorization, the replacement form starts with its SOW and has the same section.

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, and GCP CPPO for the same rule in the Fours Console.

Azure: multiparty private offer or resale authorization

The Azure reseller authorization form opens with a Private Offer Type choice:

TypeWhat it creates
Multiparty private offer (the default)You and an authorized partner sell a personalized offer with custom payouts to a Microsoft customer. The form works as described above.
Resale authorizationA standing grant, not a private offer. A resale partner may sell this product on your behalf in the customer markets you choose, and creates their own private offers for it in Partner Center. It has no pricing, dates or terms of its own, and you can revoke it at any time.

On a Multiparty private offer, Start Date (When offer is accepted or Specify first day of the month) and End Date are picked by month and year, as on an Azure private offer — see Start and end dates (Azure). On a Virtual Machine product, Contract Duration follows the private offer form’s rule too: the plan’s 1-year and 3-year terms, plus its 5-year term when the owning Azure integration has 5-Year VM Reservation Term on — see Contract duration on a Virtual Machine plan (Azure).

Scheduled charges stay inside the pricing term. On a pricing term billed on a Flexible schedule, every Charge date (UTC) must fall within that term’s contract duration, counted in UTC:

Start DateFirst allowed charge dateLast allowed charge date
Specify first day of the monthThe first day of the start monthThe day before the term’s length has run from that first day: a two-year term starting June 2026 runs to 2028-05-31
When offer is acceptedTomorrowThe day before the term’s length has run from today

The date picker offers only the days in that window. A charge already outside it — because you changed the start month or the term after scheduling it — stays on the schedule, flagged under its date, for example Scheduled charge 2 must be between 2026-06-01 and 2028-05-31 (UTC). Fours doesn’t move or delete it. Until every charge is inside, the form refuses to submit and names the plan, the term and the charge: Plan “{plan}”, term 1: Scheduled charge 2 (2029-06-21) must be between 2026-06-01 and 2028-05-31 (UTC). A flexible term also needs at least one scheduled charge with a date.

Resale authorization is offered only for SaaS products (including the Flat Rate and Per User types) and Virtual Machine products — Microsoft supports resale-enabled offers for no other type. A draft that already holds a resale authorization keeps the option.

Choosing Resale authorization cuts the form down to Offer Name, Private Offer Type, the two fields below, and Internal Notes. Everything else — the partner and buyer fields, description, dates, pricing, EULA, customer renewals and notification contacts — does not apply, so it is not shown.

FieldWhat to enter
Resale partner’s seller IDThe Partner Center seller ID of the partner you are authorizing. The partner finds it in Partner Center under Account settings → Identifiers, in their organizational profile.
Customer marketsThe markets where the partner may sell. Move markets from Available to Authorized, or use Select all / Clear all. At least one is required.

Brazil, Belarus, India, South Korea, Mexico, Russia and Singapore are never offered, because Microsoft does not support resale-enabled offers in those markets. A saved draft that still lists one of them drops it when you reopen it, so the authorization can be submitted.

Pre-fill a resale authorization from Salesforce. Your admin can map both fields from Salesforce in the private offer field mapping for Azure — in the Fours Console, open Offer, select Settings in the page’s section rail, then the CRM sub-tab, and edit the configuration in the Salesforce block. When the record supplies a Resale partner’s seller ID or Customer markets, the form opens with Resale authorization selected and those fields filled in. Customer markets reads two-letter country codes from a multi-select picklist or a semicolon-separated text field, such as us;gb, and an unsupported market is still dropped. Both fields are unmapped by default, so the form otherwise opens on Multiparty private offer. For how mapping works, see Private Offer Field Mapping.

If a required field is missing, the form stops with Please enter the resale partner’s seller ID. or Please select at least one customer market.

For how resale authorizations work on the Azure side, see Azure CPPO.

EULA files merge in the order shown

On the AWS, Azure and GCP forms, the EULA section merges the PDFs you attach in the order shown, with the standard contract (if attached) appended last, and uses the same reorder arrows as a private offer — see Attach your own EULA files. The AWS Reseller Agreement list has no reorder arrows.

On the AWS form, changing EULA Type away from Use your own EULA keeps the PDFs you attached: switch back and they are listed again. They are saved with the authorization only while Use your own EULA is selected.

Clone a resale authorization

To start a new authorization from one you have already created, open it from the opportunity’s Fours Widget, click the arrow-down button next to the Refresh icon, and select Clone. Create Resale Authorization opens with the original’s details filled in; the original is left unchanged. Clone is offered on your own resale authorizations (CPPO_OUT) once they are past draft, but not on an inbound resale authorization (CPPO_IN) or on the resale offer a channel partner makes from your authorization (CPPO) — see Clone a private offer.

  • AWS — the clone keeps the Reseller Account, Description, Discount Type, Percentage Discount, Duration, and Maximum allowed service start date you set. Reseller Account is filled in even when the reseller is known only from AWS’s record of an authorization it has released.
    • A clone of a Distributor authorization opens on Distributor, with AWS Brazil as Reseller Account, Single use and USD, and with both acknowledgments unticked: tick them again for the new authorization. Reopening a Distributor draft restores the same fixed values.
  • GCP — the clone keeps the authorization’s monthly fee (commit amount), rounded to the cent, unless the original has payment installments.
  • EULA and reseller agreement files — a file that can’t be reused, such as the marketplace’s link on an authorization synced from the marketplace, is cleared together with the rest of its list, and the form says The EULA file from the original offer can’t be reused. Upload it again. or, on the AWS and GCP forms, The reseller agreement file from the original offer can’t be reused. Upload it again. The EULA type you chose is kept, so attach the file again before you submit. On GCP, where the reseller agreement is optional, a cleared agreement is removed entirely and you decide whether to upload one.

What happens next?

After you submit the reseller authorization:

  • Fours creates the reseller authorization record in your Salesforce org, linked to the opportunity.
  • The authorization is sent to the cloud marketplace for processing.
  • Once confirmed by the marketplace, the reseller receives access to the authorization and can create their own private offer to the end customer.
  • You can track the status of the authorization from the offer record in Salesforce or in the Fours Console.

Troubleshooting common issues

IssuePossible causeResolution
No New Offer button visible on the opportunityFours permission set not assigned, or the Fours widget is not on the pageCheck your permission set. If the widget is missing, add it.
Reseller Authorization option is not in the New Offer dropdownThe product type or cloud does not support CPPO, or your permission set restricts accessConfirm your product supports reseller authorization for the target cloud. Check your permission set assignment.
Product list is emptyNo products have been set up in Fours, or your permission set restricts which clouds you can seeConfirm products exist in the Fours Console. Cloud-specific permission sets only show products for that cloud.
Form fields are blank — not pre-filled from the opportunityField mapping has not been configuredField mapping is an optional admin setup. Contact your Salesforce admin to configure it.
A sticky warning Pre-filled product is not available — Product {ID} is not in the list of products you can create offers for. It may be filtered out by your Salesforce permissions or by the Product Status Filter in Fours Settings. Please select a product from the list. — when Create Resale Authorization opensThe product your field mapping names is not one you can pick: your permission set, the Product Status Filter in Fours Settings, or the form’s own product filters leave it outThe product field is left empty: pick a product from the list. If it should be there, ask your admin to check your permission set and the Product Status Filter.
The reseller is not in the reseller account dropdown (AWS)The reseller has not yet been crawled from AWS MarketplaceClick Add reseller manually below the dropdown and enter the reseller’s 12-digit AWS account ID.
Reseller authorization was created but does not appear on the opportunitySync between Fours and Salesforce is delayedRefresh the page after a few minutes. If it still doesn’t appear, confirm the authorization was created in the Fours Console.
Opportunity Name is rejected by the formThe name is under 3 characters, over 100 characters, or contains one of ; " ' < > \Adjust the name to fit. Spaces, forward slashes, periods, and parentheses are allowed, so AWS’s ResellerName_ProductName_MM/YYYY convention is valid as written.

Frequently Asked Questions (FAQs)

Q: What’s the difference between a reseller authorization and a private offer?

A private offer goes directly to an end customer. A reseller authorization goes to a channel partner (reseller), who then creates their own private offer to the end customer. Use a reseller authorization when you’re selling through a partner, not directly to the buyer.

Q: Does the reseller see my cost price when I create a reseller authorization?

Yes — the reseller sees the price you set in the authorization. They can then mark it up when creating their own offer to the end customer, but they cannot go below the price you’ve authorized.

Q: Which cloud marketplaces support reseller authorization (CPPO) from Salesforce?

Check which products appear in the product selector — if products for a specific cloud are missing, that cloud may not yet support CPPO from Salesforce. Contact Fours support to confirm.

Q: Can I track whether the reseller has acted on the authorization?

Yes. You can check the status of the reseller authorization from the offer record in Salesforce or in the Fours Console.

Q: Do I need a separate opportunity for each reseller I authorize?

That depends on your Salesforce setup and sales process. Fours links the reseller authorization to whichever opportunity you create it from. If you have multiple resellers, most teams create a separate opportunity per reseller to keep records clean.

Spotted something wrong or out of date on this page? Tell us and we'll correct it.