Private Offers

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

Overview

The Offers page in Suger 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), and track offer statuses across all three cloud marketplaces.

After a private offer is sent, AWS does not allow you to edit it. Instead, you manage the offer through the actions on this page: cancel it, clone it into a corrected version, extend its expiry date, notify additional contacts, or download the EULA. To manage any offer, open the Offers section in the Suger 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.

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

Two ways to view offers

The Offers page gives you two ways to view your pipeline, depending on how your deals are structured. Switch between the Offer and Offer Set tabs.

Offer tab

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 tab (AWS only)

This view groups multiple AWS offers into a single bundle (up to 7 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

See Create an AWS Marketplace offer set below.

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.

Search

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.

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.

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.

Click the Columns button to add fields you want to see or remove fields you don’t need. Your changes affect only your view, not other users.

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. AWS does not allow editing an offer once it has been sent to the buyer, so canceling lets you remove the incorrect offer and start fresh.

1. Go to the Offers page in Suger Console.
2. Open the offer you want to cancel, then click Cancel in the top-right corner.
3. Confirm the action.

Once cancelled, the buyer can no longer see the offer in their AWS portal. The status moves to Pending_Cancel while Suger 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 Suger Console.
2. Open the offer you want to clone.
3. Click More actions, then select Clone.
4. Make your updates to the pre-filled offer draft.
5. Click Create to submit the new offer.

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
• Internal notes

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.

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.

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 on the Logs tab of the Offers page.

1. Go to the Offers page in Suger Console.
2. Open the offer you want to extend.
3. Click More actions, then select Extend Expiry Date.
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.

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 Suger. 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 Suger Console.
2. Open the offer and wait for the status to show Pending Acceptance.
3. Click Copy Offer URL in the top-right corner.
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 Suger.

1. Go to the Offers page in Suger Console.
2. Open the relevant offer.
3. Click More actions, then select Notify Contacts.
4. If the person you need to notify isn’t listed yet, add them first using Add Existing Contacts or Create New Contact.
5. Click Notify next to a specific contact, or click Notify All Contacts to send to everyone on the list at once.
6. Check the Notification Events section at the bottom.
   • 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 Suger 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, Suger downloads either the custom EULA (the exact file uploaded for that offer) or the standard marketplace contract (the default agreement provided by the marketplace).

1. Go to the Offers page in Suger Console.
2. Open the relevant offer.
3. Click More actions, then select EULA. This opens the EULA in a new browser tab.
4. Click the Download icon on the page.

Suger 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 Suger Console and click EULA again.
• If the document can’t be retrieved, the new tab closes and the console shows Unable to download EULA. Please try again.

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.

Review an offer’s history

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

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

Each entry shows when it happened and what happened, followed — where Suger 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, Suger AI, or Suger backend. See what each one means under Products → History. Entries recorded before Suger 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 Suger records while it carries that out — starting with Pending_Create for a new offer — name you on the By: line, with Source: User. On Google Cloud offers, the status changes Suger records after your request finishes don’t name anyone yet. Entries nobody on your team caused, such as the offer expiring, show Source: Suger 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.

Create an AWS Marketplace offer set

An offer set groups multiple AWS private offers (up to 7) 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.

Suger

• Admin access to the Suger 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:

Step 1: Set up offer set details (container)

Start by filling out the container details in order:

1. Go to the Suger Console, then Offer.
2. Click the Offer Set tab in the upper-left corner, then + New Offer Set.
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.
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 associate 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.

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

Repeat until you have added all required offers.

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 to publish.

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 Suger may differ slightly from what you see in the native AWS, Azure, or GCP consoles. Where this applies, the difference is called out below.

Suger Console / CRM status reference

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

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:

The offer page explains the failure in a Create Offer Failed alert. It shows the latest reason — in plain language where Suger 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.

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.

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

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.

For multiparty (channel partner) offers

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)

Reseller offer statuses (Partner Sales Console)

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

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.