Products
Browse, create, and manage all of your cloud marketplace listings in one catalog.
Overview
The Products page is your catalog of every marketplace listing in your workspace. From here you can browse products, create new listings, track their status through their lifecycle, and drill into any product to see its offers, entitlements, and revenue records.
Sections of the Products page
The Products page lists its sections in a rail on the left: Product, the catalog this page describes, and, for seller, reseller, and partner organizations, Settings, set apart at the bottom of the rail. Other organizations see the catalog alone.
Settings section
Settings is split into two sub-tabs:
- Sign-up page — the New Client Signup Page Configs panel: the self-serve signup form your new clients land on. Settings opens on this sub-tab. The form used to be under Settings › New Client Signup, and an old link to that location now opens this sub-tab. Its fields and its Preview are unchanged; for what the form does and when to use it, see Signup URL Redirect.
- Product tagging — the Product Tagging panel: the product line each product belongs to, and whether contacts are routed by it. It moved here from the Products sub-tab of the Offers page’s Settings. See Tag products by product line.
The page’s address keeps the sub-tab you open, so a reload or a shared link opens the same one. Save a Product tagging change before you switch to Sign-up page: the panel reads your saved settings again each time you open it, so a change you haven’t saved is dropped.
Browse your product catalog
Your catalog displays all products in your workspace. Switch between list view and tile view with the two icons at the top right of the page, after New Product; their tooltips read Table view and Card view. While a saved view is open, the page always shows the list and the two icons are hidden.
List view
Shows products in a table format with detailed columns (name, ID, partner, type, status, and more). Hover a product’s logo in the Partner column to see the ID of the integration it belongs to, such as an AWS account ID or an Azure App Registration client ID. That ID tells products apart when your organization connects more than one account of the same cloud.
The list view’s toolbar ends with Columns and Export CSV; tile view has neither.
- Columns — pick the columns to show. Five are marked New and start hidden: Listing ID, Partner Account, Currency, Fulfillment URL, and Last Updated. Tag is listed only while contact routing is on (see Product tags). Drag a column header to move the column; the first column stays first.
- Export CSV — downloads every product that matches your search and filters, from all pages, with the columns you show, in their order.
See Export a list to CSV and Reorder columns and add new ones for how both work across the console’s lists.

Tile view
Shows products as cards for a more visual, high-level overview.

Product tags
A product tag names the product line a product belongs to. When your organization routes contacts by product, each product’s tag shows in two places:
- A Tag column in list view.
- Beside the product’s status at the top of its detail page.
Each product carries one tag. Tags are read-only here, and you can’t filter the list by them. With contact routing off, the Tag column is hidden and product pages show no tag.
Products are tagged, and contact routing is switched on, in the Product Tagging panel on the Product tagging sub-tab of Product › Settings; the panel is marked BETA in the console — see Tag products by product line. Contact routing files the contacts on a product’s offers under that product’s tag, which is how the Salesforce app groups an account’s Buyer Contacts — see Buyer Contacts. Removing a product’s tag takes the contacts routing filed under it for that product back out, so they don’t reappear under the product’s next tag; contacts you filed by hand aren’t affected.
Tag products by product line
Product Tagging records the product line each product belongs to. With Contact routing on, Fours files the buyer contacts on a product’s offers under its product line — the Salesforce app groups an account’s Buyer Contacts that way — and the Products page shows each product’s tag. A tag can also add its contacts to new private offers on its own; see Add tagged contacts to new private offers.
The panel is on the Product tagging sub-tab of the Products page’s Settings section, which seller, reseller, and partner organizations have. It used to be on the Products sub-tab of the Offers page’s Settings.
- Open Product in the console’s main navigation, select Settings, the last item in the page’s section rail, and then the Product tagging sub-tab.
- Click New Config and choose the cloud: AWS, AZURE, or GCP. That cloud’s tagging dialog opens.
- Tag each product: click + Tag on its row, then pick an existing tag or type a new one. In Search or create…, what you type matches the start of a word in a tag’s name, best matches first:
secfinds Security and Cloud Security, but not InfoSec. To tag several products at once, select them — or Select all visible — and use Add tag to selection. Search by product name or ID and Untagged only narrow the list. A tag can’t be named ”.” or ”..”. Click Save. A product carries one product tag and at most 100 tags in all. If a save stops part-way, the products saved before the failure stay saved and the error says how many of the changed products were saved; check the dialog, which re-reads the stored tags, and save again. - Turn on Contact routing, then click Save in the Product Tagging panel.
New Config, Save, and the Contact routing switch stay disabled until the panel has loaded your organization’s settings; meanwhile the configuration table reads Loading…. If loading fails, the table reads We couldn’t load product tagging. Refresh the page and try again. While a save is in progress, Save reads Saving…, and Save, New Config, each configuration’s trash icon, and the tagging dialog’s Auto-add contacts to new private offers switch wait until it finishes, so one click sends one save.
The Coverage column tracks each cloud — for example, 12/40 tagged · 3 tags — and the pencil icon reopens its tagging dialog.
- One product line per product, up to 100 characters. Casing counts: Security and security are two product lines.
- Only buyer contacts are filed. Your own sales reps, your partners’ contacts, and anyone at your organization’s email domain are left out.
- Turning on Contact routing also files the contacts of products tagged while it was off. Turning it off hides the product lines and stops filing contacts.
- Deleting a cloud’s configuration (trash icon) first removes the tags from each of that cloud’s tagged products. If the delete fails, the console says We couldn’t delete that configuration.: try deleting it again, and if it keeps failing, contact Fours at support@suger.io.
- Removing a product’s tag takes the contacts that routing filed under it for that product back out, so they don’t reappear under the product’s next tag. Tagging the product again files only the contacts still on its offers. Contacts you filed by hand aren’t affected.
- Roles. Tagging products needs the
entity_tag.editpermission, which the Editor and Admin roles carry — without it the tagging dialog is read-only. Removing a product’s tag, and moving a tagged product to another product line, also needentity_tag.delete, which the Editor and Admin roles carry too. A custom role withentity_tag.editbut notentity_tag.deletecan tag only untagged products; tagging a selection of tagged products says Only untagged products can take a tag. Ask an admin for permission to remove tags. Creating or deleting a configuration, saving Contact routing, and changing Auto-add contacts to new private offers need the Admin role. Because deleting a configuration removes its products’ tags, its trash icon also needsentity_tag.delete.
Add tagged contacts to new private offers
Each tag can put the contacts that carry it on new private offers for its products.
- In a cloud’s tagging dialog, click a tag in the list of tags at the top. The product list narrows to that tag, and Auto-add contacts to new private offers appears under the tags.
- Switch it on, then click Save.
From then on, a new direct private offer for a product with that tag starts with every contact that carries the tag and whose email domain has the same company name as the company email domain of one of the offer’s buyers. The ending and any subdomain are ignored, so a buyer at acme.com also matches contacts at acme.net or eu.acme.co.uk.
- Which offers. Direct private offers created through Fours — in the console, the Fours Salesforce or HubSpot app, or the Fours API. Resale authorizations and other partner-led offers, public offers, and offers created in a marketplace’s own portal are left alone. An offer you saved as a draft before submitting it, or resubmit after a failed create, keeps the contacts it already has.
- Which contacts. A contact counts whether the tag was filed on it by hand or by contact routing, so Contact routing doesn’t need to be on. A buyer with no company email domain, or one on a consumer email domain such as gmail.com, adds nobody.
- The email. Adding the contacts sends nothing. They receive the ready-to-accept email when the offer reaches
Pending_Acceptance, if the Pending Acceptance row in your email configuration has the Offer Notification Contacts rule — see Email an offer’s contacts.
Explore a product’s details
Click any product to open its detail page. Each tab covers a different part of the product’s lifecycle.
Overview
Key product information, configuration details, and a revenue summary at a glance. The information shown here may vary depending on the product type.
On an AWS product, an AWS Partner ID row shows the ID of the AWS seller account the product belongs to, with a copy button. It’s the same ID the product’s logo shows on hover in list view, and it tells products apart when your organization connects more than one AWS Marketplace account. The row is left out when the product has no account recorded.

Offer
Private offers and resale authorizations tied to this product, including lifecycle status and buyer details.

Entitlement
Customer access records, including active and past entitlements, billing, and invoice values.

An entitlement that has ended shows how it ended, in a neutral color, when the marketplace’s own record says so:
- Expired — its term ran out.
- Renewed — it was renewed.
- Replaced — a new agreement replaced it.
On AWS, any of the three can appear; on Google Cloud, only Expired. A status chip with a small ⓘ in its corner has more to show: hover it to read the marketplace’s own status for the entitlement, after Partner status:. Every other ended entitlement shows Cancelled, including every ended Azure entitlement, because Azure doesn’t report how an entitlement ended. The Status filter lists Expired, Renewed, and Replaced as options of their own, so Cancelled finds only the entitlements labeled Cancelled.
When an AWS or Google Cloud entitlement with usage dimensions ended one of these ways, its page (click its name) reminds you: Usage reported before it ended is still billed on this entitlement. It does not need to be reported again on a new agreement.
Revenue record
Detailed financial records including invoice amounts, fees, disbursement status, and refunds.

Create a new product
Click + New Product in the top-right corner to start a new marketplace listing.

- On Create New Product, pick the Marketplace: AWS, Azure, GCP, or Stripe. For AWS, also pick the Product Type: SaaS or Professional Services.
- The listing’s form opens below, on one page. Fill it in; each marketplace’s fields are described in List a product on AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace.
- Click Create, at the bottom right.
A guide on the right of the form helps you finish it:
- What to fill in counts the required fields left and lists them by section; click a blue link to jump to that field. It reads Everything required is filled in once none is left.
- Need help? offers Ask the AI assistant, which opens the console’s AI chat; Read the guide, which opens the listing guide in a new tab; and Contact support, which opens a new support ticket over the form, so you don’t lose what you’ve typed.
Fill with AI, at the top of the form, opens the AI assistant to fill in the listing. It looks up your company’s website, and you can paste a product description too. It lists what it would fill and asks before it fills the form (Fill the form or Cancel), and it leaves fields you’ve already filled alone, even when your description says something else; a field still showing the form’s default can be filled. Creating the product stays your step. Each field it fills is marked AI until you change it, so check each one before you create the product.
At the bottom, Back sits on the left, and Save as draft and Preview (AWS, Azure, and GCP) sit beside Create. If you leave the form with changes you haven’t saved — with Back, the browser’s back button, or a link elsewhere in the console — it asks Save a draft before you leave?: Keep editing, Leave, or Save as draft. Reloading or closing the tab gets your browser’s own warning instead.
If the marketplace’s checks reject a listing you haven’t saved as a draft when you click Create, the console shows the reason and adds nothing to your catalog, so retrying never leaves extra drafts behind. Fix the field and click Create again.
Find and filter products
As your catalog grows, use search and filters to quickly find what you need.

- Show Resale — toggle to include products you are authorized to resell alongside your own products.
- Search — find products by Name, ID, Partner, Type, and Status, or by the ID of the integration a product belongs to, such as an AWS account ID.
- Quick filters
- Cloud Partner — filter by marketplace.
- Type — filter by product type (for example, SaaS, Subscription, Contract).
- Status — filter by product status (Draft, Limited, Public, and so on).
To build more specific queries, click Filters (funnel icon):
- Click Add Filter to choose a field, condition, and value.
- Combine multiple conditions using AND.
- Click Search to apply your filters.
To keep a set of filters for your whole organization, click Save view as, which appears after the filters once you change them. The product list’s saved views are listed in the page’s rail under Saved views · Product; Settings has none. A view keeps the filters, the search, Show Resale, and the columns, and always opens as the list. See Save and share a filtered list.
Track operations and history
Use Operations and History to understand what’s happening behind the scenes when you create or update a product.
Operations
The Operations window shows the status of background tasks (such as publishing or updating a listing). Use it to check whether a change is still processing or if something failed.
- Open the product.
- Click More actions in the top-right corner, then Operations.

History
The Product History panel shows a timeline of changes made to the product, so you can see what was updated and when.
- Open the product.
- Click More actions in the top-right corner, then History.

Entries are listed newest first. Each shows when it happened and what happened, followed — where Fours recorded them — by a By: line naming who made the change and a Source: line naming where it came from:
| Source | Where the change came from |
|---|---|
| User | A person signed in to Fours — in the Fours Console, or through an MCP client they authorized. |
| Salesforce | The Fours Salesforce app. |
| HubSpot | The Fours HubSpot app. |
| API client | A call to the Fours API. |
| Fours AI | Fours’ AI service. |
| Fours backend | Fours’ own background processing — scheduled jobs, cloud marketplace events, and automatic notifications. If such an entry also has a By: line, it names the person whose action Fours was carrying out. |
| Cloud Partner | The cloud marketplace itself, for a change made there rather than through Fours. Today this covers an AWS SaaS listing edited outside Fours, for example in the AWS Marketplace Management Portal. Once AWS applies the change, Fours updates the product and records an entry reading Product … was changed in AWS Marketplace. A change that AWS rejected isn’t recorded. Neither is one Fours can’t apply because the listing is still a draft on AWS or is being edited in Fours at that moment. It also marks a request to make an AWS listing public that was cancelled in AWS Marketplace — see Requests to make an AWS listing public. |
Entries recorded before Fours began tracking the source have no Source: line. The same lines appear in an offer’s history — see Review an offer’s history.
For an AWS product, a failed create or update entry also shows a Why AWS rejected this panel with AWS’s error code and message, plus the latest attempts (up to three) with their change set IDs.
The panel shows every part of AWS’s reason:
- A review finding. When AWS’s review turns the listing down (error code
AUDIT_ERROR), the panel shows AWS’s opening line, then each numbered issue on a line of its own, cut to its first sentence — the requirement the listing missed — so no issue is left out. - Any other reason is shown whole, except that a long link or a long value AWS quotes back, such as your product description, is shortened in place, and a very long message loses its middle.
- Show full reason. When anything was shortened, click Show full reason under it to read AWS’s whole message.
The panel under a failed run in the Operations window works the same way.
Requests to make an AWS listing public
When you click More actions, then Publish Product on a Limited AWS SaaS listing, the request gets two History entries. The first is recorded when AWS accepts the request for review, and says the request was submitted to AWS Marketplace. The second is recorded when AWS is done with it:
| Entry | What happened |
|---|---|
| Product … is now Public in AWS Marketplace | AWS published the listing. |
| Request to publish product … was rejected by AWS Marketplace | AWS refused the request. |
| Request to publish product … was rejected in AWS Marketplace review | AWS turned the listing down in its review. |
| AWS Marketplace could not process the request to publish product …. Please try again. | The request failed on AWS’s side. Send it again. |
| Request to publish product … was cancelled in AWS Marketplace | The request was cancelled in AWS Marketplace. |
- Who asked: a result entry shows the By: and Source: lines of the request it answers. A cancellation shows Source: Cloud Partner, because it was made in AWS Marketplace.
- Why it failed: a rejected or failed request’s entry shows AWS’s reason in a Why AWS rejected this panel, or Why this failed when AWS gave no error code. The other entries show the request’s Change set ID.
- Older requests: requests made before Fours began recording them have no entries.
The listing’s status on its page follows the request:
Product statuses
Each product displays a status that tells you where it is in its lifecycle and whether any action is needed on your end.
In progress states
| Status | Definition | Next step |
|---|---|---|
Draft | Listing is being prepared and has not been submitted or published yet. | Complete required fields, validate pricing/content, and submit when ready. |
Pending Create | Fours has started creating the listing in the marketplace, but creation is not finished yet. | Wait briefly and refresh. If it remains stuck, check activity, error details, and integration health. |
Pending | Listing has been submitted and is waiting for marketplace review or processing. | Wait for provider processing, monitor for feedback, and respond if any required changes come back. |
Pending Update | The listing already exists, and a submitted change is still being processed. A Limited AWS SaaS listing you’ve asked to make public with Publish Product also shows Pending Update on its page while AWS reviews the request. | Wait and refresh. An AWS listing returns to its visibility status (Limited or Public) once AWS accepts the change, or moves to Update Failed with AWS’s reason in the Update Product Failed banner. During a publish review, the Update in progress banner at the top of the page says when the request was submitted. The listing then becomes Public, moves to Update Failed with AWS’s reason, or is Limited again if the request is cancelled; History records each step. If it stays stuck too long, review the last change and check for sync or integration issues. |
Published visibility states
| Status | Definition | Next step |
|---|---|---|
Public | Listing is live and publicly available/discoverable in the marketplace. | No action needed unless you want to update content, pricing, or visibility. |
Limited | Listing is published with limited visibility or access, often for testing, preview, or restricted audiences. Private offers can’t be sent while the listing is in Limited status. | Confirm whether limited visibility is intentional. If so, finish validation/testing. If not, review visibility settings and publishing requirements. |
Unlisted | Listing exists but isn’t publicly discoverable/searchable in the marketplace. | If intentional, no action is needed. If not, review marketplace visibility and publishing settings to confirm why it’s not public. |
Restricted | Listing is not publicly available to new buyers, usually due to provider restrictions or a seller-controlled visibility change. Private offers can’t be sent while the listing is in Restricted status. | Existing users can continue to use the product. Direct new prospects to an updated listing. |
Action-needed states
| Status | Definition | Next step |
|---|---|---|
Unknown | Fours can’t confidently determine the listing’s current marketplace state. | Refresh, compare with the marketplace console, and check integration/sync health if the status persists. |
Create Failed | Fours tried to create the listing, but the marketplace rejected it. | Open the listing and read the Create Product Failed banner at the top of its page: it gives the marketplace’s reason, for AWS as an error code and message, one per line, set out as in History. When part of the reason was shortened, Show full reason in the banner shows all of it. For the full error, open Operations and click View details on the failed run. Fix the first blocking issue, and retry creation. |
Update Failed | The listing already exists, but a later change was rejected or did not sync successfully. A rejected AWS listing edit, including one made with Edit Info, lands here. | Review the last change and read the error details: they’re in the Update Product Failed banner on the product page and, for AWS, under the failed entry in History, and Show full reason in either place opens a reason that was shortened. Fix or revert the invalid update, then retry. |
Attention Needed | The listing needs manual review or follow-up before it can move forward cleanly. | Open the listing details, review warnings or feedback, identify the blocking issue, and complete the required follow-up. |
Post-action states
| Status | Definition | Next step |
|---|---|---|
Edited | Listing has been modified from its previous version. This is a change-tracking state, not necessarily a publish or error state. | Review what changed, confirm whether the update still needs to be submitted/synced, and monitor for the next state (Pending Update, Update Success, or Update Failed). |
Update Success | The most recent listing update completed successfully. | No immediate action needed. Optionally confirm the expected change is reflected in the marketplace. |
Deleted | The listing was removed or marked as deleted. | Confirm whether deletion was intentional. If not, investigate whether it can be recreated or restored through the appropriate workflow. |
Spotted something wrong or out of date on this page? Tell us and we'll correct it.