Private Offers

View, share, and manage your private offers across AWS, Azure, and GCP from the Offers page in Fours Console.


Overview

The Offers page in Fours Console is your central place for tracking and managing every private offer you send. From here you can monitor pipeline health, find specific deals, take actions on an offer (cancel, clone, extend, share, notify contacts, download EULA, export its terms as a PDF), link many offers to Salesforce records or HubSpot deals at once, and track offer statuses across all three cloud marketplaces.

In Fours, you don’t edit a private offer in place once it is sent. Instead, you manage it through the actions on this page: cancel it, clone it into a corrected version, extend its expiry date, notify additional contacts, download the EULA, or export its terms as a PDF. To manage any offer, open the Offers section in the Fours Console and select the offer you want to work with. Most actions live in the More actions menu on the offer detail page. Each of these actions is also available from the Salesforce App — see Manage Offers in the Salesforce App.

Quick pipeline view

At the top of the Offers page, a set of summary cards shows the current state of your deal pipeline. These cards update automatically based on the latest status from AWS, Azure, and GCP, giving you a quick snapshot of both pipeline health and revenue performance in one place.

Quick pipeline view in the Offers page

  • Newly accepted offers — offers recently accepted by the buyer. Use this to confirm which deals have just closed and are ready for handoff to implementation or customer success.
  • Total revenue — the total revenue value from your deals in the system (in USD). For deeper breakdowns like invoiced, collectible, or disbursed amounts, use the Revenue or Home dashboards.
  • Pending acceptance — offers that have been sent but are still waiting for buyer action. Use this to quickly identify deals that may need follow-up before they expire.
  • Recently expired — offers that were not accepted before their expiration date. Use this to spot stalled deals that may need to be reissued or extended.

Sections of the Offers page

The Offers page lists its sections in a rail on the left: Offer, Offer Set, Resale, Log, and Settings. Offer and Offer Set are two ways to view your pipeline, depending on how your deals are structured. Resale holds your resale authorizations. Log shows the background operations behind your offers. Settings holds your private offer settings; it appears only for seller, reseller, and partner organizations, set apart at the bottom of the rail.

  • Collapse the rail: click the chevron at the top of the rail to shrink it to icons, and click it again to expand it. The console remembers your choice for this page.
  • In a narrow window: the rail stays on screen, as it does in a wide one; collapse it to icons to give the page more room.
  • Saved views: Offer, Offer Set, Resale, and Log each keep saved views of their own, listed in the rail below the sections under Saved views · and the section’s name. Settings has none. See Save and share a filtered list.

Offer section

This is your main view for managing offers. It shows each individual private offer across AWS, Azure, and GCP.

From here, you can:

  • Track standard, single-offer deals
  • Check offer status and progress
  • Search or filter across all cloud providers

Offer Set section (AWS only)

This view groups multiple AWS offers into a single bundle (up to 15 offers). It’s used only for AWS Marketplace deals that involve multiple products being sold together.

Use this view when:

  • You are selling a multi-product solution in AWS
  • You want to bundle multiple offers into one buyer flow
  • You need to manage AWS offer sets instead of individual offers

Besides the search box, the list has a Filters panel for Name, Status (Draft, Pending Create, Create Success, Create Failed, or Active), Creation date, and Expiration date; a Columns picker; and Export CSV.

See Create an AWS Marketplace offer set below.

Resale section

Resale lists resale authorizations, which let a channel partner resell a seller’s product. It used to be the Resale page in the console’s main navigation; links to that page now open this section.

A Sent / Received picker sits after the search box:

  • Sent — the resale authorizations you’ve created for your channel partners. Click New Resale Authorization to create one.
  • Received — the resale authorizations other sellers have sent your organization, for products you resell. It’s available only when your organization has Enable Reseller turned on; otherwise the picker shows it greyed out and marked Reseller off.

Sent and Received each keep their own search while you switch between them, and each has a Columns picker and Export CSV. A saved Resale view remembers which of the two it shows.

For the steps on each marketplace, see AWS Marketplace CPPO, Azure Marketplace CPPO, and Google Cloud Marketplace CPPO.

Log section

The Log section lists the operations Fours runs in the background on your offers. These include creating, canceling, and extending offers, syncing them, creating offer sets, and bulk linking.

  • Row contents: each row shows the operation’s ID, Status, Workflow Type, offer Type, Provider, and Timestamp. Use Columns to hide or reorder them.
  • Narrow the list: use the Provider, Workflow Type, Status, and Offer Type filters, the search box, or the time period (Last 7 days, Last 30 days, Last quarter, Last year, or Custom range).
  • Download: click Export CSV to download every entry that matches your filters and period, from all pages, not only the rows on screen.

Settings section

Seller, reseller, and partner organizations also have a Settings section, last in the rail and set apart from the others. It holds the private offer settings that used to be under Settings › Private Offer; an old link to that location now opens this section. The settings are split into three tabs:

  • CRM — the Salesforce, HubSpot, and Dynamics 365 settings that fill in offers created from your CRM.
  • Products — the list products filter, dimension tagging, and dimension sync. Product tagging moved to the Products page’s Settings section; see Tag products by product line.
  • Defaults — the default values for new offers.

For what each setting does, see Private Offer Field Mapping.

Find the right offer

When you have a large number of offers, use search and filters to quickly locate specific deals without scrolling through the full list.

Use the search bar to quickly find a specific offer by name, buyer, or Offer ID. This is the fastest way to jump directly to a single deal when you already know what you’re looking for.

The Buyer column links each offer to its company in Fours. When an offer names a buyer account that no company in Fours matches, the column shows the account itself, prefixed with its cloud — aws--123456789012, for example — instead of -.

Search in the Offers page

Filters

Use filters when you want to narrow down your pipeline instead of finding one specific deal. For example, view all offers in Pending_Acceptance, or filter by AWS vs. Azure vs. GCP.

Filters in the Offers page

Columns

Customize the table columns to control what information you see in the Offers list, so you can tailor the view to what matters most without cluttering the table.

Columns in the Offers page

Click the Columns button to add fields you want to see or remove fields you don’t need. While no saved view is open, your changes affect only your view, not other users. The console keeps them in this browser for this page alone: an offer set’s page, a product’s Offer tab, and a company’s page each keep columns of their own. While a saved view is open, the columns belong to the view, and saving it shares them with your organization.

The Tags column, after Expiry, shows by default; see Tag offers and entitlements. Columns marks seven columns as New: Created By, Pricing Model, Partner ID, Channel, Created Via, Accepted On, and Approval. They start hidden; tick one to add it. On this list you can also drag a column header to move the column, and Export CSV downloads every matching offer — see Reorder columns and add new ones and Export a list to CSV.

Save and share a filtered list

A saved view is a named set of filters, search, and columns on one console list, which Fours keeps for everyone in your organization. Set up the list you check every week once, and anyone on your team opens it from the rail or from a link you send them.

These lists have saved views, and each keeps views of its own:

PageLists with saved views
OffersOffer, Offer Set, Resale, and Log. Settings has none.
ProductsThe product list. Settings has none.
CompaniesThe company list.
ContactsAll, Cloud Contacts, and Buyers. Partner Contacts has none.
EntitlementsThe entitlement list.

A list’s views appear in the page’s rail, below its sections, under a heading that names the list — Saved views · Offer, for example — sorted by name. Companies and Entitlements have no rail until someone in your organization saves the first view there; from then on the rail shows All companies or All entitlements, which opens the full list, with the saved views below it. With the rail collapsed, a number in place of the section counts the list’s views; click it to expand the rail.

Save a view

  1. Set the filters, search, and columns you want on the list.
  2. Click Save view as, in the toolbar after the filters. It appears once you change something on the list; filters the console remembered from an earlier visit don’t count as a change.
  3. Type a Name and click Save view. The dialog reminds you: Everyone in your org can see and use this view.

The new view opens straight away. A name is up to 60 characters and unique on that list, ignoring case; a name already in use gives A view with this name already exists here. Try another. Each list holds up to 10 views for your organization. At the limit, Save view as says so instead of saving: delete a view on that list, then save again. Your filters stay on the page.

Clear filters, beside Save view as, resets the list’s filters and search, and keeps your columns.

Work with an open view

Click a view in the rail to open it; its row turns bold. While it’s unchanged, the toolbar adds nothing. Once you change its filters, search, or columns, a green dot appears on its row and the toolbar offers:

  • Save view — opens Save your changes. Click Save view to update the view for everyone, or Save as new view to leave it as it is and save your changes under a new name. If someone else created the view, the dialog names them.
  • Save as new view — in place of Save view when your role can save views but can’t change this one.
  • Revert changes (the ↺ icon) — puts the view back the way it was saved.

To return to the full list, click the list’s own item in the rail, such as Offer. If a filter saved in a view no longer exists, the view opens without it and the toolbar says Some filters in this view no longer exist and were skipped.

Manage a view

Point to a view in the rail and click its ⋯ button (View actions):

  • Copy link — copies a link to the view. Anyone in your organization who opens it sees that view.
  • Rename view — gives it a new name, under the same rules as saving.
  • Delete view — removes it for everyone in your organization, after you confirm. The confirmation names the view (Delete “Expiring this month”?, for a view of that name) and warns that this can’t be undone.

The menu ends with who created the view, and who last edited it and when.

Who can change saved views

Everyone in your organization sees and opens every saved view on a list. What else they can do depends on their role:

Fours roleOpen a view, copy its linkSave a new viewSave over or rename a viewDelete a view
AdminYesYesYesYes
EditorYesYesYes, unless an Admin created itYes
ViewerYesNoNoNo

On a view an Admin created, an Editor’s View actions menu says Only Admins can change this view. Use Save as new view to make your own copy.; a Viewer’s says Your role can apply saved views, but can’t change them. A Viewer who changes an open view sees Changed in the toolbar and can revert the change, but can’t save it. A custom role grants these actions through its saved-view read, create, edit, and delete permissions; only the standard Admin role counts as an Admin here. See Account for roles.

What a view keeps

A view keeps the list’s filters, including the rows in its Filters panel; its search; which columns show, and in what order; and the switches in its toolbar — Show Resale on Products, Sent or Received on Resale, the time period on Log, and Cloud Partner on Contacts, with Currency and Show My Contacts on Cloud Contacts and Source on Buyers. It doesn’t keep the sort order, column widths, whether the rail is collapsed, or filters inside a dialog. On Products, a view always opens as the list, and the switch to tile view is hidden while it’s open.

While a view is open, column changes belong to the view until you save or revert them. With no view open, the console keeps your columns in this browser, as before.

Come back to a list

The console remembers, for you and in this browser, the last view you opened on each list, and opens it again when you come back, with a notice such as Showing “Expiring this month”, the last view you used here. A copied link opens its view with Opened “Expiring this month” from a shared link. A link that brings its own filter or search, such as one from a summary card, opens that instead of your last view. Returning to the full list from the rail forgets your last view. If someone deletes the view you have open, it closes with That saved view was deleted.

Leave with unsaved changes

If you move to another list, page, or view while the list has changes you haven’t saved — the browser’s Back and Forward buttons included — the console asks first: Save your changes to “Expiring this month”? when a view of that name is open, or Save these filters as a view? when none is. Click Discard to drop the changes and go on, Save as new view or Save view as to save them under a name, or Save view to update the open view, if your role can. Reloading or closing the tab doesn’t ask, and the console never asks a role that can’t save views.

Export a list to CSV

Export CSV, at the right of the toolbar, is on each of these lists: Offer, Offer Set, Resale (Sent and Received), Log, the product list, Companies, Entitlements, and Contacts’ All, Cloud Contacts, and Buyers. Where a list had a download of its own before, such as Download CSV on Contacts, this replaces it.

  1. Click Export CSV. The console counts every row that matches the list’s search and filters, from all pages, not only the rows on screen. Click Cancel to stop.
  2. The dialog, titled with the count (Export 52 offers, for example), lists the open view, the filters, how many columns, and the file name, which is the list’s name and today’s date (offer_2026-11-11.csv).
  3. Click Download CSV.

The file holds the columns the table shows, in the table’s order. When nothing matches, the console says Nothing matches the current filters. To export fewer rows, add a filter or open a saved view first.

Reorder columns and add new ones

On these lists, every column header except the first has a grip. Drag it left or right to move the column, or focus the grip and use the arrow keys; the first column stays first. The order is saved with the list’s columns, in your browser or in the open view. The tables inside a page — a product’s Offer tab, and the Offer, Entitlement, and Reseller tables on a company’s Overview — can’t be dragged.

Columns marks the columns a list newly offers with a green New tag. They start hidden; tick one to add it.

ListNew columns
Offers › OfferCreated By, Pricing Model, Partner ID, Channel, Created Via, Accepted On, Approval
ProductsListing ID, Partner Account, Currency, Fulfillment URL, Last Updated
EntitlementsContract Value, External ID, AWS Account ID, Marketplace Status, Created, Accepted On, Scheduled Cancellation

Tag offers and entitlements

Tags are labels you put on offers and entitlements, such as Overage or True-up, so you can group them and find them again. Offers and entitlements share one set of tag names: a tag you’ve used on an offer can be picked for an entitlement, and each record keeps its own tags.

Tag an offer

  • In the list. The Tags column, after Expiry, shows each offer’s tags; chips that don’t fit fold into a +N count. Click anywhere in a row’s Tags cell to open the tag picker, Search or create a tag…: pick a tag your organization already uses, or type a new name and press Enter. The picker says No more tags to add when the offer already has every tag in use. A chip’s × removes that tag.
  • On the offer’s page. A Tags: row under the offer’s name shows its tags. Click + to add one, or a chip’s × to remove it.

Each change is saved as you make it. Export CSV writes an offer’s tags in its Tags column, separated by semicolons.

Find offers by tag

  • The Tags dropdown. Tags, in the toolbar, shows only the offers that carry the tag you pick, or those with No tags. Type in Search tags… to narrow the list of tags. The button then shows the tag’s name; pick the same tag again to clear it.
  • Filters. The Tags field in the Filters panel takes Is or Is Not, each matching Any of or All of the tags you pick, or Is Null for offers with no tags and Is Not Null for offers with any.

Both are list filters, so a saved view keeps them.

Tag many offers at once

Bulk tagging, at the top of the Tags dropdown, opens Offer Tagging. It lists every offer, newest first, and loads more as you scroll; the list’s own filters and search don’t narrow it.

  1. Find the offers. Search by name or ID in Search offers…, tick Untagged only, or click a tag in the Tag library at the top to list the offers that carry it. No offers match these filters means nothing does.

  2. Select them: tick their rows, or use Select all visible (N) or Select all (N). Deselect clears the selection.

  3. Change their tags:

    • Add tag to selection adds a tag you pick or type.
    • Remove tag from selection lists the tags on the selected offers, each with how many of them carry it (2 of 5); pick one to remove it.
    • Clear tags removes every tag from the selected offers, after you confirm.

    Each row also has its own + button and chips.

  4. Click Save (N), where N is the number of offers you changed. Until then your changes are a draft (Changes stay as a draft until you save); Cancel, or closing the dialog, discards them.

If a save stops part-way, the dialog says Saved n of N. Try again to save the rest. Check the offers and save again.

Delete a tag everywhere. In the Tag library, each tag’s × deletes it from your organization. The confirmation, Delete “Overage”?, says how many offers and entitlements carry it and that this can’t be undone; Delete tag removes it from all of them straight away, without waiting for Save.

Tag entitlements

The Entitlements list works the same way. Its Tags column comes after Status, an entitlement’s page has the same Tags: row, and Bulk tagging opens Entitlement Tagging, which searches entitlements by name or ID, or by their offer’s name. On a company’s Overview, the Offer and Entitlement tables show the Tags column and take the same tag filters.

Tag names and who can tag

  • A tag name is up to 100 characters and needs at least one letter or number. It can’t contain quotes, backslashes, or semicolons. Spaces at either end are dropped, and a run of spaces becomes one.
  • Names ignore case: if your organization uses Overage, typing overage picks it.
Fours roleSee tags and filter by themAdd tagsRemove tags, clear them, delete from the library
AdminYesYesYes
EditorYesYesYes
ViewerYesNoNo

A custom role grants these through the entity_tag.read, entity_tag.edit, and entity_tag.delete permissions. Without entity_tag.read, the Tags column, dropdown, filter, and Tags: row don’t show. With entity_tag.edit but not entity_tag.delete, you can add tags but not remove them. See Account for roles.

Cancel an offer

Canceling an offer withdraws it before the buyer accepts it. Use this when an offer has incorrect details or is no longer needed. A sent offer isn’t edited in place in Fours, so canceling lets you remove the incorrect offer and start fresh.

  1. Go to the Offers page in Fours Console.

  2. Open the offer you want to cancel, then click Cancel in the top-right corner. Cancel an offer in the Fours Console

  3. In the Cancel this offer? dialog, click Cancel offer. Keep offer closes the dialog and leaves the offer as it is.

Once cancelled, the buyer can no longer see the offer in their AWS portal. The status moves to Pending_Cancel while Fours processes the request, then becomes Canceled once AWS confirms it. No charges or entitlements are activated.

When to cancel

  • The buyer requested changes after the offer was sent.
  • The offer contains incorrect information (for example, wrong AWS Account ID, pricing, or term).
  • The offer was misconfigured (for example, wrong pricing or the wrong product was selected).

After canceling, you can clone the canceled offer to quickly recreate a corrected version using the same structure.

Clone an offer

Cloning copies an existing offer into a new draft so you don’t have to rebuild it from scratch. This works for both active and canceled offers.

  1. Go to the Offers page in Fours Console.

  2. Open the offer you want to clone.

  3. Click More actions, then select Clone Offer. Clone an offer in the Fours Console

  4. Make your updates to the pre-filled offer draft. Fields marked with an asterisk (*) are required.

  5. Click Create offer to submit the new offer.

Create offer stays greyed out while a required field is empty or a value isn’t valid. To see what’s left, hover over the button, or press Tab until it has focus. Its tooltip, headed Please complete:, lists each step that still needs work and the fields in it — for example, Step 2 Offer terms — Expiry Date — with the reason beside any value that isn’t valid.

The draft opens as one page, with a guide on the right. Its What to fill in card lists the required fields still left; click a blue link to jump to that field. Fill with AI, at the top of the form, opens the console’s AI assistant to fill fields from deal notes you paste. It lists what it would fill and changes nothing until you click Fill the form. It leaves alone any field you’ve typed in, even when your notes say something else; a field still showing the form’s default can be filled. Each field it fills is marked AI until you change it, so check them before you create the offer. At the bottom, Back sits on the left and Save as draft beside Create offer. If you leave with changes you haven’t saved, the console asks Save a draft before you leave?: Keep editing, Leave, or Save as draft.

When to clone

  • You’re sending a similar offer to a different buyer.
  • You canceled an offer and want to reuse its structure.
  • You need to make small adjustments, such as pricing or term changes.

What gets copied

  • Product
  • SKUs and pricing
  • Term dates
  • EULA, except a file Fours can’t reuse (see below)
  • Internal notes

A clone reuses only EULA files stored in Fours. When the original offer’s custom EULA is a document Fours read from the marketplace rather than a file uploaded in Fours — as on an offer synced from AWS or Azure Marketplace — the clone keeps the custom EULA choice but leaves out the file, and the form shows The EULA file from the original offer can’t be reused. Upload it again. Upload the file before you create the offer. Cloning a resale authorization works the same way for its reseller agreement: The reseller agreement file from the original offer can’t be reused. Upload it again.

What to update before resubmitting

  • Buyer ID(s)
  • Offer name
  • Any updated pricing or expiration dates

Extend the expiry date of an offer

Extending an offer pushes back the expiration date so the buyer has more time to review and accept it. This saves you from recreating the offer if the deadline passes before the buyer responds.

You can extend offers in the Pending_Acceptance, Expired, and Update_Failed statuses. Extending an expired offer reactivates it so the buyer can access and accept it again. Update_Failed is included so that a failed extend can be retried — if an extend request fails, the offer is left in Update_Failed and the Extend Expiry Date action reappears so you can try again.

You can’t extend a CPPO offer — the private offer a channel partner created on AWS from your resale authorization. The channel partner owns it, so only they can extend it: Extend Expiry Date doesn’t appear on it in your console, and the Fours API refuses the request.

When the marketplace rejects an update such as an extension, the offer page shows an Update Offer Failed alert with the marketplace’s reason. Azure offers don’t show this alert. When Google refuses a deadline because an installment starts first, the alert says so in plain words, with the dates and the installment’s number — for example, The offer’s acceptance deadline (Dec 20, 2026) must be on or before Dec 14, 2026, the day before installment 2 of the offer it replaces starts (Dec 15, 2026). — instead of Google’s raw error.

For AWS offers, More actions → History shows a Why AWS rejected this panel under the failed entry, with AWS’s error code and message and the latest attempts (up to three) with their change set IDs. The same panel appears in the Log section of the Offers page. When part of AWS’s reason was shortened — a long link or value AWS quotes back, or a very long message — Show full reason under it shows the whole text.

  1. Go to the Offers page in Fours Console.

  2. Open the offer you want to extend.

  3. Click More actions, then select Extend Expiry Date. Extend Expiry Date action in the Fours Console

  4. Enter the New Expiry Date, then Save your changes. The new date must be in the future and later than the offer’s current expiry date — the same date or an earlier one isn’t an extension. Set a new expiry date

    Two more limits can apply, and the date picker offers only the days that meet all of them:

    • The offer has a start date. The new expiry date must also be earlier than the offer’s start date. Google Cloud requires a scheduled start date to be later than the offer’s acceptance deadline (Set up your offer’s pricing), and AWS rejects an agreement start date that isn’t after the offer’s availability end date (INVALID_AGREEMENT_START_DATE in Work with private offers using the AWS Marketplace APIs).
    • Google Cloud offers. The new expiry date can be at most three months from today, because Google requires an extended deadline to fall within three months (Modify a published offer). The latest date allowed is shown under the date picker.
    • Google Cloud offers with installments. The new expiry date must also come before the next installment starts. For a replacement offer, that is the next installment of the offer it replaces, which Google requires the acceptance deadline to precede (Set up your offer’s pricing); Fours applies the same limit to the offer’s own next installment. For a replacement the buyer has accepted, the limit is the original offer’s installment that follows the ones the replacement carried over, even after that installment has started. If Fours can’t find the offer it replaces, it refuses the extension with The acceptance deadline cannot be verified because the offer it replaces is unavailable. Please sync the original offer and try again. The date picker doesn’t enforce this one. When you save a date past it, Fours refuses the extension before anything reaches Google, and the error names the latest date allowed and the installment that sets it — or says the offer can’t be extended, when no date after the current expiry date is left.

    If the start date leaves no such day, the dialog says the offer can’t be extended, names its current expiry date and its start date, and suggests cloning the offer with a new start date instead. Save stays disabled.

When to extend

  • The buyer hasn’t accepted the offer and the expiry date is approaching.
  • You’re in ongoing negotiations but need more time.

Share the offer with your buyer

Once your offer is ready, you have two ways to get it to your buyer: copy the link yourself or trigger an email directly from Fours. Use whichever fits your workflow.

Share the offer URL

Manually copy the offer link and send it to your buyer through your own email or messaging tool.

  1. Go to the Offers page in Fours Console.

  2. Open the offer and wait for the status to show Pending Acceptance.

  3. Click Copy Offer URL in the top-right corner. Copy Offer URL button in the Fours Console

  4. Send the link to your buyer.

Notify contacts

The Notify Contacts feature sends an email with the offer link and current status directly to people linked to the offer. Use this to keep buyers and internal stakeholders informed without sending emails manually outside of Fours.

  1. Go to the Offers page in Fours Console.

  2. Open the relevant offer.

  3. Click More actions, then select Notify Contacts. Notify Contacts action in the Fours Console

  4. If the person you need to notify isn’t listed yet, add them first using Add Existing Contacts or Create New Contact. Add a contact to notify

  5. Click Notify next to a specific contact, or click Notify All Contacts to send to everyone on the list at once. Notify a contact or all contacts

  6. Check the Notification Events section at the bottom. Notification Events section

    • It lists every Notify Contacts request and the contacts it was addressed to, including requests your email settings then stopped from sending.
    • Contacts notified together share one email, so an open shows against the first contact listed.
    • Emails Fours sends automatically, such as the ready-to-accept email, aren’t listed here.

When to use Notify Contacts

  • To remind a buyer that a private offer is pending acceptance.
  • To alert internal stakeholders that an offer has been created, extended, or canceled.
  • To follow up during negotiations or renewal discussions.

Download EULA

The EULA action downloads a PDF copy of the End User License Agreement (EULA) attached to a private offer. Depending on the offer setup, Fours downloads either the custom EULA (the exact file uploaded for that offer) or the standard marketplace contract (the default agreement provided by the marketplace).

The EULA action appears only when Fours has a EULA recorded for the offer. An offer with none shows no EULA action — for example, a Google Cloud Professional Services offer that carries only a statement of work.

  1. Go to the Offers page in Fours Console.

  2. Open the relevant offer.

  3. Click More actions, then select EULA. This opens the EULA in a new browser tab. EULA action in the More actions menu of an offer in the Fours Console

  4. Click the Download icon on the page.

Fours looks up the document each time you click EULA. If it no longer has a working copy of an AWS offer’s document, it tries to recover one first — from AWS Marketplace or, for a CPPO, from the resale authorization the CPPO is linked to.

  • If your browser blocks the new tab, the console shows Allow popups, then try downloading the EULA again. Allow pop-ups for the Fours Console and click EULA again.
  • If the document can’t be retrieved, the new tab closes and the console shows the reason Fours returned, or Unable to download EULA. Please try again. when there is no reason to show.

Google Cloud offers. This applies when the GCP integration’s Enable PrivateOffer API setting is on, so that Fours syncs offers through Google’s API — including offers created in Producer Portal.

  • What Fours records: the documents attached to the offer there — its EULA (the standard one or a custom PDF) and, for a Professional Services offer, its statement of work.
  • Recorded once: a document you later replace in Producer Portal isn’t picked up.
  • Older offers: the regular sync reads only offers Google changed in the last 7 days, so an older offer gets its documents on the next full import — see About Enable PrivateOffer API.
  • After that: EULA downloads the document, and an offer you clone or amend in Fours carries the documents over.

When you might need it

  • To review the terms included in the offer.
  • To share the EULA with the buyer outside of AWS.
  • To keep a copy for internal record-keeping or legal review.

Export the offer’s terms as a PDF

Export PDF turns an offer’s current terms into a PDF you can pass to the people who review the deal on the buyer’s side but have no marketplace account, such as a procurement or legal team. It is available at every offer status, so you can share a draft or a pending offer as well as an accepted one.

  1. Go to the Offers page in Fours Console.
  2. Open the offer.
  3. Click More actions, then select Export PDF. The PDF opens in a new browser tab.

The PDF follows the offer’s overview page in the console, with the same cards, labels and order, and shows the offer as Fours holds it when you click:

  • A header with your organization’s name, the offer’s name and status, its marketplace, and its Offer ID.
  • Basic Information: the offer’s delivery method, whether it is a renewal, and its marketplace-specific terms and dates. An AWS offer with renewal terms adds a Renewal terms table.
  • Buyer Information and Product Information, when the offer has a buyer and a product. The buyer card shows only the IDs from the offer’s own marketplace.
  • The pricing cards the offer has, in the console’s order: Pricing Info (an Azure offer’s plans), Recurring commits, Usage Dimensions, Usage metering, Installments, and Installment Schedule (Snowflake).

Dates follow the console: most are in UTC, while a Google Cloud offer’s expire, accept, start and end dates are in US Pacific time. A row the console hides when it is empty is left out of the PDF too.

A footer gives the time the PDF was generated and says the summary is not the agreement itself. The PDF leaves out the EULA (download that with EULA), contacts and email addresses, notes for your team, and seller-internal fields such as the CRM opportunity ID or the AWS offer set. Read the Buyer Information card before you send the file on.

  • The new tab opens a link that stops working after an hour, so share the downloaded file rather than the link. Exporting an unchanged offer again within a few minutes returns the same PDF; after you change the offer, the next export reflects the change.
  • If your browser blocks the new tab, the console shows Allow popups, then try exporting the PDF again. Allow pop-ups for the Fours Console and click Export PDF again.
  • If the PDF can’t be created, the new tab closes and the console asks you to try again in a minute, and to contact support if it keeps failing.

Review an offer’s history

The Offer History panel lists the events Fours has recorded about an offer, newest first — up to the latest 1,000.

  1. Go to the Offers page in Fours Console.
  2. Open the offer.
  3. Click More actions, then select History.

Each entry shows when it happened and what happened, followed — where Fours recorded them — by:

  • By: — who made the change. It is left off an offer acceptance, because the buyer who accepted isn’t a member of your organization.
  • Source: — where the change came from: User, Salesforce, HubSpot, API client, Fours AI, or Fours backend. See what each one means under Products → History. Entries recorded before Fours began tracking the source have no Source: line.

When you submit, cancel, or extend an AWS, Azure, Oracle, or Snowflake offer from the console, the status changes Fours records while it carries that out — starting with Pending_Create for a new offer — name you on the By: line, with Source: User. Google Cloud offers work the same way when the GCP integration’s Enable PrivateOffer API setting is on: creating, cancelling or extending an offer through that API names you on the entries Fours records. Offers that take the browser-driven path instead — reseller authorizations included — still record these changes without a name, and entries recorded before Fours began naming the user are not backfilled. Entries nobody on your team caused, such as the offer expiring, show Source: Fours backend and no By: line. For an AWS example, see See who made each change.

A failed AWS change also carries the Why AWS rejected this panel described under Extend the expiry date of an offer.

A failed Google Cloud create, update, or cancel entry shows the reason for that attempt, so a later failure never replaces an earlier entry’s reason. Where Fours has guidance for the error, the entry shows that guidance alone; otherwise it shows the error, shortened. The panel is headed Why Google Cloud rejected this when the error is Google Cloud’s own answer, and Why this failed for anything else, such as a check in Fours or a timeout.

Bulk link connects many private offers to records in your CRM in one pass: Salesforce records, or HubSpot deals. Pick a record for each offer in the dialog, or upload a CSV that gives one per offer. It is a one-time import, separate from the Custom Backfill Line setting, which links offers created in the Salesforce app to the record they came from.

CRMEach row links an offer toWhere the link is written
SalesforceA record of the object that a lookup on the Salesforce Offer object (Suger__Offer__c) points at, such as an Opportunity. You pick the lookup.Into that lookup on the offer’s Salesforce Offer record, right away or on the scheduled sync.
HubSpotA deal.On the offer in Fours. Nothing is written to HubSpot; the offer appears in the Offers tab of the Fours app card on that deal.

Before you start

  • A verified CRM integration. Bulk link appears in the More actions menu of the Offer section only when your organization’s Salesforce or HubSpot integration is connected and verified. With both verified, the dialog opens on Salesforce. See Salesforce and HubSpot.
  • The offer.edit permission. The Admin and Editor roles include it, and a custom role can grant it — see Account. The menu item shows whatever your role. Without the permission, Preview changes is refused with You don’t have the required permission to call this API.
  • Salesforce: check what reacts to Offer record changes. Linking changes each offer’s Salesforce Offer record. That can trigger Salesforce flows or Fours workflows that react to it, such as email notifications, so confirm none depend on it before you run it.
  1. On the Offers page, stay in the Offer section and click More actions, at the right of the section’s title (it shrinks to a ⋯ button when the row runs out of room), then Bulk link. The dialog opens on its first step, Choose, and its title names the CRM: Bulk link offers to Salesforce or Bulk link offers to HubSpot.
  2. If both CRMs are verified, pick Salesforce or HubSpot in the switch at the top of the dialog. Everything below the switch belongs to that CRM, so switching starts the dialog over. The switch is locked once you preview; go back to Choose to change it.
  3. Salesforce only: under Backfill into lookup, pick the lookup on Suger__Offer__c that the record IDs belong in. That one choice decides which offers are listed, which Salesforce object every ID is checked against, and where each link is written.
    • Suger__Opportunity__c is selected by default.
    • Only lookup fields are listed.
    • Suger__Buyer__c and Suger__Product__c can’t be picked, because they point at Fours records rather than CRM records.
    • Suger__Created_By__c can’t be picked, because it is rewritten on every sync.
    • You also can’t pick a lookup that the Salesforce user Fours connects as isn’t allowed to edit.
    • Suger__Account__c can be picked, but the Fours Salesforce app derives it from the Opportunity and may overwrite what you write.
    • Just created a lookup in Salesforce? Click Refresh schema to reload the list.

Step 2: Pick a record for each offer, or upload a CSV

Two tabs set how you say which record each offer links to: Pick offers, where the dialog opens, and Upload CSV. The picker and the downloaded template list the offers that aren’t linked yet:

  • Salesforce: offers whose chosen lookup is still empty in Salesforce.
  • HubSpot: private offers not linked to a HubSpot deal yet.

An uploaded CSV can also name offers that are already linked. A row that points at the record the offer is already linked to changes nothing; a row that points at a different record is skipped unless you turn on Overwrite existing linkage in the preview.

Public and free-trial offers are never listed, because they belong to no one customer. To narrow the offers, use the filter row under the tabs: the same Cloud Partner, Type, Status, and Filters controls as the Offer section.

Pick offers in the dialog

  1. Set Load to how many offers to list at a time: 50, 100, or 200. The list loads again whenever you change the CRM, the lookup, the filter, or Load, and the reload button beside the counts reads it again on demand. When more unlinked offers remain than the list shows, the counts say so: raise Load, narrow the filter, or upload a CSV instead.

  2. Click Pick CRM record on an offer’s row. A dialog opens for that offer, titled Select Deal for HubSpot, or Select and the Salesforce object the lookup points at, such as Select Opportunity; a lookup that points at several objects names them all. Type a name or paste a record ID:

    • HubSpot: a deal name, or a deal ID.
    • Salesforce: the name of a record of the object the lookup points at, or a 15- or 18-character record ID.

    The search runs a second after you stop typing, or when you click Search. Matches are listed in a table of names and IDs: click Select on a match’s row to pick it. The ID is a link, when Fours can build one, that opens the record in Salesforce, or the deal in HubSpot, in a new tab, so you can check it before you pick.

  3. Repeat for each offer you want to link. On a picked row, the pencil icon (Change record) replaces the pick, and the red ✕ (Clear record) clears it.

Your picks survive a trip to the preview and back. Changing the CRM, the lookup, the filter, or Load, or reloading the list, clears them.

Upload a CSV

  1. Click Download template. Fours downloads a CSV of every unlinked offer; for Salesforce, it reads Salesforce to find them. If more than 10,000 offers are unlinked, the template holds the first 10,000 — import those, then download it again.
  2. Fill in crmRecordId for each offer you want to link and save the file as CSV, keeping the sugerOfferId and crmRecordId columns. A file can hold up to 10,000 rows — split a larger one.
  3. Drop the file on the dialog, or click Choose file….

The template has five columns. You fill in only crmRecordId:

ColumnFilled byWhat it holds
offerNameTemplateThe offer’s name, to help you find it. For reference only; the upload ignores it.
marketplaceOfferIdTemplateThe offer’s ID in the cloud marketplace. For reference only; the upload ignores it.
marketplaceTemplateThe cloud marketplace the offer is on, such as AWS. For reference only; the upload ignores it.
sugerOfferIdTemplateThe Fours offer ID — the column that decides which offer a row links. Don’t edit it.
crmRecordIdYouSalesforce: the record ID to link, 15 or 18 characters, from the object the lookup points at. HubSpot: the deal ID, the number in the deal’s URL. Leave it blank to skip the offer.

A file made with the earlier template, which also had a crmType column, still uploads; a row whose crmType names the other CRM is reported as an error.

  1. Salesforce only: under Options, decide on Backfill to CRM right away. It is on by default: each linked offer is written to its Salesforce Offer record as soon as the import finishes. Turn it off to save the links in Fours only; they then wait for the scheduled sync, which carries only recently created offers.
  2. Click Preview changes. The preview checks every row against Fours and your CRM and writes nothing.

Step 3: Review the preview

The preview gives each row one of six outcomes. The table lists rows that will write first, then errors, then rows that change nothing. It shows the first 200 rows; the tiles and the error report cover every row. Each row names the record it points at — the Salesforce record’s name or the HubSpot deal name, linked to the record in your CRM — above the ID from your picks or your file.

OutcomeWhat it means
Will linkThe row will link the offer to the record.
Will overwriteThe offer is linked to a different record, and Overwrite existing linkage is on. The row replaces that link.
Already linkedThe offer is already linked to this record — for Salesforce, the lookup already holds it. The row is skipped.
Skipped · has a different linkThe offer is already linked to a different record. It keeps that link.
Skipped · blankThe row has no record ID.
ErrorThe row can’t be linked. The Detail column says why and how to fix it.

Four tiles above the table count the rows:

  • Will link and Will overwrite count the rows with those outcomes.
  • Skipped counts the Already linked, Skipped · has a different link, and Skipped · blank rows together.
  • Errors counts the rows that can’t be linked.

Below the tiles:

  • Overwrite existing linkage appears when some rows are skipped for having a different link. Turn it on to re-link those offers to the records you chose, and the preview runs again.
  • Download error report saves a CSV with one line per error row: the row number, sugerOfferId, crmRecordId, the error, and how to fix it.
  • Salesforce: record IDs are checked against Salesforce and stored in the 18-character form, so a 15-character ID copied from a spreadsheet matches the 18-character form of the same ID.
  • HubSpot: each deal ID is checked against HubSpot and matched exactly. Nothing is written to HubSpot.

An Error row has one of these reasons:

ReasonHow to fix it
The sugerOfferId column is empty.Use the sugerOfferId values from the template.
The offer appears on another row too.Keep one row per offer.
Salesforce: the value isn’t a Salesforce record ID.Use the 15- or 18-character ID, not the record name or number.
Salesforce: the ID belongs to a record of a different object than the lookup points at.Copy the ID from a record of the right object.
HubSpot: the value isn’t a HubSpot deal ID.Use the number in the deal’s URL in HubSpot, not the deal name.
HubSpot: the spreadsheet saved the deal ID in scientific notation, such as 6.37288E+11.Format the crmRecordId column as Text, paste the deal IDs again, and save the CSV.
The row’s crmType names the other CRM.Change it to the CRM you chose, or upload the file with that CRM selected.
No offer with that ID exists in your organization.Use the sugerOfferId values from the template, unedited.
The offer is a public offer.Remove the row. Only private offers can be linked to one customer’s record.
The record isn’t found in Salesforce, or the deal isn’t found in HubSpot.Confirm the ID in your CRM. Deleted or merged records can’t be linked.

Rows with errors are left out when you link. Fix them and upload the file again, or link the valid rows now.

  1. Click Link N offers, where N counts the Will link and Will overwrite rows. The button is disabled when no row would write.
  2. Fours checks every row against your CRM again and starts the job. The dialog moves to Commit and shows Linked, Skipped, and Failed tiles, plus a result for each row being linked. A Salesforce job with Backfill to CRM right away on adds a Salesforce sync queued tile. A HubSpot link takes effect when the job finishes: the offer then appears in the Offers tab of the Fours app card on its deal — see Manage an offer after it is created.
  3. Click Done. The job carries on if you close the dialog.
  • One job at a time. Your organization can run one bulk link job at a time. Starting another while one is running is refused until the first finishes.
  • A job that stops part-way. The dialog says how many rows weren’t processed. Run the import again to finish them.

Follow the job in Log

Each bulk link job appears in the Log section. Set Workflow Type to Bulk link and leave Provider at All. A bulk link job isn’t tied to one cloud, so it doesn’t show under a single provider.

Create an AWS Marketplace offer set

An offer set groups multiple AWS private offers (up to 15) into a single bundle that the buyer accepts in one checkout flow. Use it when you’re selling a multi-product solution in AWS Marketplace.

Prerequisites

Make sure the following are in place before creating an offer set.

AWS Marketplace

  • Active AWS Marketplace seller account with a published seller profile. See Register and create your seller profile.
  • At least one active public listing. You must have a published product before you can create private offers to include in an offer set.

Fours

  • 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.

Offer alignment

AWS enforces the following rules across all offers in a set. Mismatches block you from publishing. Before you start building, confirm that every offer you plan to include will share:

  • The same currency
  • The same buyer AWS account ID
  • The same expiration date

Supported offer types

Only the following offer types can be included in an offer set:

Offer typeSupported in offer sets?Description
Marketplace Private Offer (MPPO)✅ YesDirect private offers created by the product owner (ISV) for the buyer
Channel Partner Private Offer (CPPO)✅ YesPrivate offers extended by an authorized channel partner using a resale authorization
Standard Private Offer features✅ YesIncludes flexible payment schedules and local currency support
Public & Trial offers❌ NoStandard public listings and promotional free trials can’t be bundled
Replacement offers (amendments)❌ NoAgreement-based offers meant to renew or upsell an existing active entitlement

Step 1: Set up offer set details (container)

Start by filling out the container details in order:

  1. Go to the Fours Console, then Offer.
  2. Select Offer Set in the section rail on the left, then click + New Offer Set. The Create Offer Set page opens, marked AWS Only, with two sections: Offer set details and Private offer.
  3. Enter the Offer set name. Use something that helps you and the buyer identify the deal easily.
  4. Add a Customer note — context for the buyer or internal team. It’s required.
  5. Select or enter the Buyer(s) AWS account ID.
  6. Set the Expiry Date for when the buyer can accept the offer set. Every individual offer you add later must share this exact same expiration date.
  7. (Optional) Use the Solution association field if you already have a related AWS solution listing and want to connect them. A solution is a Marketplace page that explains how multiple products work together; linking it gives buyers additional context and documentation during the purchase flow.

The guide on the right of the page shows an Offer set summary that fills in as you go, and What to fill in, which lists what’s still missing, including the offers: it counts 2 private offers until you add the first, then One more private offer. Click a blue link in it to jump to that field.

To leave the page without creating the set, click Back at the bottom left. Once the set has offers, the console asks Cancel this offer set? first: Keep offer set returns you to it, and Cancel offer set discards it.

Step 2: Add private offers to the offer set

Attach the actual private offers inside the offer set container. You must add at least 2 offers and up to 15 offers per offer set.

  1. Click + Create private offer to add your first offer.
  2. Choose the Product you want to include. Each offer in the set must target a different product ID — you can’t include the same product twice in one offer set.
  3. Fill in the Basic information section.
  4. Set up the Offer terms.
  5. Add the Pricing information.
  6. Attach the End User License Agreement (EULA) for this product.
  7. Once everything is correct, click Add.

To drop the offer you’re building instead, click Cancel at the bottom of the form, and confirm if the console asks. You return to the offer set: the offer you were building is discarded, and the set’s details and the offers you’ve already added are kept.

The offer’s Buyer(s) and Expiry Date come from the offer set, so they are locked and read Set by the offer set.

Fields marked with an asterisk (*) are required. Add stays greyed out until every required field is filled in and every value is valid. It has no tooltip listing what’s missing, so check What to fill in in the guide on the right of the form: it lists each required field still missing, and reads Everything required is filled in once none is. Click a blue link in it to jump to that field.

Repeat until you have added all required offers. The guide’s Offer set summary counts them as you go, for example 3 of 2–15. Once the set holds 15 offers, + Create private offer is disabled and the page shows Maximum 15 offers allowed per offer set.

Step 3: Review and publish the offer set

  1. Check everything you configured. Make sure:
    • All offers are included correctly.
    • Every offer targets the same buyer AWS account.
    • All offers use the same currency.
    • All offers share the same expiration date.
    • Each offer has a different product ID.
    • Pricing, terms, and EULAs are correct.
  2. Click Create offer set, then Create offer set again in the Create this offer set? dialog to publish. Go back returns you to the offer set without creating it.

Step 4: What happens after you publish

  • Buyer notification (automatic). After you click Create offer set, AWS Marketplace automatically sends the buyer a single email — this replaces individual private offer emails. The email includes the Offer Set ID, expiry date, the list of included products, and one link to review and accept the full offer set.
  • Separate agreements (after acceptance). Once the buyer accepts the offer set, each product becomes its own separate agreement, so you can manage renewals, changes, or cancellations per product independently.
  • Invoicing and payments. Even though the buyer completes one checkout flow, billing is split per product. The buyer receives separate invoices for each product based on its own terms and agreement.

Track offer statuses

Status labels in Fours may differ slightly from what you see in the native AWS, Azure, or GCP consoles. Where this applies, the difference is called out below.

Fours Console / CRM status reference

Use the table below to interpret the offer statuses shown in the Fours Console or your CRM.

StatusMeaning
Pending_CreateThe offer is being submitted to AWS.
Create_SuccessAWS has accepted the offer, but it hasn’t been made visible to the buyer yet.
Pending_AcceptanceThe offer has been successfully pushed to AWS and is waiting for the buyer to accept it.
AcceptedThe buyer has accepted the offer. An entitlement is created automatically.
Pending_CancelThe offer cancellation request has been submitted but not yet confirmed by AWS.
CanceledThe offer has been successfully canceled. It is no longer visible to the buyer.
ExpiredThe buyer did not accept the offer before the expiry date. The offer is no longer valid.
ActiveThe offer originated from a public purchase via the Marketplace.

Three statuses mean the offer never reached the marketplace, and all three stay editable — open the offer, correct it, and resubmit rather than starting again:

StatusMeaning
DraftSaved in Fours and never submitted.
Create_FailedFours couldn’t create the offer — for example, the marketplace refused it, or, for a Google Cloud offer, Fours’ own pre-flight checks refused it before anything was sent.
InvalidFours’ own pre-flight checks refused it, so nothing was sent to the marketplace. Fours no longer sets this status, so you’ll only see it on older offers; a Google Cloud offer that the pre-flight checks refuse now lands in Create_Failed.

The offer page explains the failure in a Create Offer Failed alert. It shows the latest reason — in plain language where Fours can rewrite the marketplace’s error, word for word otherwise — and, when the offer has failed before, a Show n earlier attempts link that lists the previous reasons.

Troubleshoot a failed offer with AI

The console’s AI assistant can explain a failed create and propose a fix, but it looks at the offer only when you click one of these buttons:

  • On the offer’s page. When an offer’s status is Create Failed (Create_Failed in the table above), its Create Offer Failed alert has Troubleshoot with AI. Click it to open the AI chat, which reads the error and explains what to change.
  • On its edit form. Open the failed offer’s form, with Edit Draft for example, and a Last submission failed banner at the top shows the latest error, with Fix with AI. The assistant proposes changes to the form’s fields.
  • After a failed create. When creating or submitting an offer from its form fails, a Submission failed banner shows the error, with Fix with AI.

All three buttons for an offer continue one conversation. Once you’ve clicked one, it reads Open AI chat and reopens that conversation without starting again; a different error starts a fresh diagnosis, and so does a click after you’ve moved to another chat. While either banner shows on a form, the header’s Fill with AI is hidden, so the form has one AI button. An Update Offer Failed alert has no AI button.

AWS Marketplace offer statuses

AWS private offers follow a straightforward lifecycle: Draft → Active → Accepted. If the buyer doesn’t act in time, the offer moves to Expired instead.

StatusWhat it meansWhat to do
DraftThe offer is incomplete.Finish filling in all required fields, then publish to send it to the buyer.
ActiveThe offer has been published and is available to the buyer.Share the offer link with the buyer if you haven’t already. See Share the offer with your buyer.
AcceptedThe buyer subscribed and an agreement (entitlement) has been created.Go to the Entitlement menu in the Fours Console to track the deal going forward.
ExpiredThe offer reached its deadline before the buyer accepted.Extend the expiration date or create a new offer.
Pending CancelThe buyer requested to cancel their subscription. This status applies to public offers and usually lasts about one hour.No immediate action needed. Wait for the status to move to Cancelled.
CancelledThe agreement was cancelled, either by the buyer or the seller.If the cancellation was unintended, contact AWS support. To continue the deal, create a new private offer.

Source: AWS Marketplace Seller Guide – Creating and managing private offers

Key things to know about AWS offers

  • Private offers renew automatically only if they carry renewal terms. A Contract, Professional Services, or Container offer with committed pricing can include pre-authorized auto-renewal terms, which the buyer accepts along with the offer; resale (CPPO) and agreement-based offers can’t. Without renewal terms, create a new private offer to renew when the contract ends.
  • Pending Cancel and Cancelled are Fours-specific events. You won’t see these labels in the AWS console. In AWS, a seller-initiated cancellation changes the offer’s expiration date so it appears as Expired.
  • Buyers receive both a PENDING_CANCEL and a CANCEL webhook event when they unsubscribe, typically about one hour apart. This is normal behavior.

Azure Marketplace offer statuses

Azure requires two separate actions from the buyer: accepting the offer terms and then completing the purchase. This means a deal can show as Accepted while the subscription is still pending.

StatusWhat it meansWhat to do
DraftYou have started creating the offer but haven’t submitted it yet.Complete all required fields and submit.
In ProgressThe offer is being published. This typically takes up to 15 minutes.Wait for the status to update before contacting the buyer.
Pending AcceptanceThe offer is live and waiting for the buyer to accept.Make sure you have shared the offer link with the buyer. See Share the offer with your buyer.
AcceptedThe buyer accepted the offer terms.Check the sub-status (below) to see if the purchase step is still pending.
ExpiredThe offer deadline passed before the buyer accepted.Withdraw the offer, make any needed edits, and resubmit.
EndedThe offer passed its end date.Create a new offer if you need to continue the deal.
WithdrawnYou recalled the offer before the buyer accepted it.Edit and resubmit when ready.

Source: Microsoft Learn – Manage ISV-to-customer private offers

Purchase sub-statuses (after acceptance)

After the buyer accepts, these sub-statuses track whether they have completed the purchase step.

StatusWhat it meansWhat to do
Pending PurchaseThe buyer accepted the terms but hasn’t completed the purchase yet.It can take 15–60 minutes for the Purchase button to become available. Let the buyer know to check back.
SubscribedThe buyer subscribed and you activated the SaaS subscription.No action needed. The deal is active.
PurchasedFor VM software reservations, the buyer completed the purchase.No action needed.
CancelledThe subscription was cancelled due to a buyer request or non-payment.Reach out to the buyer to resolve, or create a new offer if needed.
Expired (subscription)The subscription has expired.Create a new offer to renew.

For multiparty (channel partner) offers

StatusWhat it meansWhat to do
Pending Partner ActionThe offer is ready for the channel partner to review and send to the buyer.Follow up with the channel partner to confirm they have received and reviewed the offer.

Source: Microsoft Learn – Multiparty private offers for ISVs

GCP Marketplace offer statuses

GCP has the most granular status lifecycle of the three marketplaces. After a buyer accepts an offer, you (the seller) may need to manually approve it before it activates. GCP also distinguishes between an offer expiring before the buyer acts and an order expiring after the contract ends.

Offer statuses (Producer Portal)

StatusWhat it meansWhat to do
DraftThe offer is created but not finalized.Continue editing, then submit.
Pending Google ApprovalGoogle is reviewing the offer before it can be sent to the buyer.Wait for approval. This is a Google-controlled step.
CreatedThe offer URL is ready.Send the offer link to the buyer. See Share the offer with your buyer.
Pending AcceptanceThe offer has been sent but the buyer hasn’t accepted yet.Follow up with the buyer if needed.
Account Pending ApprovalThe buyer’s account needs to be approved before the offer can proceed.Review and approve the account in your GCP settings.
Account RejectedThe buyer’s account was rejected.Contact the buyer if the rejection was unintended.
Needs Your ApprovalThe buyer accepted and is waiting for you to confirm.Go to the GCP Producer Portal and approve the offer.
ApprovingYour approval is being processed. This takes a few minutes.Wait for the status to update.
Approval FailedAn error occurred during approval.Wait for the status to reset, then re-approve.
ActivatingThe offer is nearly ready. It will activate at its scheduled start time.No action needed.
ScheduledA replacement offer was approved and will activate on the contract start date.No action needed until the start date.
ActiveThe buyer is actively using the offer.No action needed.
Offer ExpiredThe buyer did not accept before the deadline.Create a new offer if you want to continue the deal.
Order ExpiredThe contract end date has passed.Create a renewal offer if needed.
CancelledYou withdrew the offer before the buyer accepted.Create a new offer if the deal should continue.
RejectedYou declined an offer the buyer had already accepted.Contact the buyer and create a new offer if the deal should proceed.
UnavailableThis is a legacy offer that is no longer supported.Migrate to a current offer type if needed.

Reseller offer statuses (Partner Sales Console)

If an offer is managed through a GCP reseller, you’ll see this simplified set of statuses instead.

StatusWhat it meansWhat to do
PublishedThe reseller published the offer; the buyer hasn’t accepted yet.Follow up with the buyer or reseller if there is no response.
AcceptedThe buyer accepted but the contract hasn’t started yet.Wait for the contract start date.
ActiveThe contract is in effect.No action needed.
EndedThe contract passed its end date.Create a renewal offer if needed.
ExpiredThe buyer didn’t accept before the deadline.Work with the reseller to reissue the offer.
CanceledThe reseller withdrew the offer.Coordinate with the reseller to reissue if needed.

Key things to know about GCP offers

  • SaaS offers require manual approval by default unless you have enabled automatic offer approval. Check your GCP settings to avoid deal delays.
  • Replacement offers (for renewals or upsells) follow the same status lifecycle but can’t change the product, plan, or pricing model of the original offer.
  • As of April 2025, GCP supports multiple active flat-fee offers for the same buyer.

Cross-cloud status comparison

Use this table to quickly compare where a deal stands across all three marketplaces.

Lifecycle stageAWSAzureGCP
Being createdDraftDraftDraft
Publishing— (immediate)In ProgressPending Google Approval
Awaiting buyerActivePending AcceptanceCreated / Pending Acceptance
Buyer agreedAcceptedAcceptedNeeds Your Approval
Fully activeAgreement activeSubscribed / PurchasedActive
Not accepted in timeExpiredExpiredOffer Expired
Contract endedAgreement endedEndedOrder Expired
Seller withdrewCancelled (pre-accept)WithdrawnCancelled

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