Create and Manage Listings

A listing is your provider organisation's sellable version of a marketplace product.

Create a listing when you want to make a published product available to your customers. Manage the listing later when you need to change visibility, update markup, review pricing, or remove the product from a storefront.

Before You Start

Confirm:

• the product is available in Discover,
• the base price is acceptable,
• the provider markup is known or ready to be reviewed,
• the product belongs in the selected provider instance,
• the product should be visible to customers after listing.

Create a Listing in the Dashboard

1. Open Marketplace.
2. Select the marketplace instance.
3. Open Provider.
4. Open Discover.
5. Open the product.
6. Click Create Listing.
7. Enter the provider markup amount.
8. Review the listed price.
9. Create the listing.

The listing appears under Listings. Open it to review product details, images, listed price, developer profile, visibility, and listing history.

Update an Existing Listing

Use Listings to manage products your organisation already sells.

1. Open Marketplace.
2. Select the marketplace instance.
3. Open Provider.
4. Open Listings.
5. Search or filter listings.
6. Open the listing.
7. Review the current price, markup, visibility, and history.
8. Apply the change.

Common listing updates include:

• changing provider markup,
• making a listing visible or hidden,
• pausing a listing while you review support, pricing, or compatibility,
• reactivating a listing after it is ready to sell again,
• reviewing prior listing versions and commercial changes.

When markup changes, Infuse records a new listing version so previous commercial states can be reviewed later.

Visibility and Storefronts

Listing visibility controls whether the product should appear in customer-facing storefront catalogue results for that provider instance.

Hide or pause a listing when:

• you no longer want customers to buy the product,
• pricing needs review,
• the product should only be sold to a different customer group,
• support or install readiness is temporarily blocked,
• you are preparing a replacement listing strategy.

Hiding a listing removes it from future storefront discovery and checkout selection. It does not delete historical purchases, purchase records, entitlements, or install history.

When Updates Take Effect

Listing updates affect future customer actions.

After you update a listing:

• storefront catalogue results should reflect the latest visible listing state,
• future checkout sessions should use the latest valid price and visibility,
• existing purchases keep the purchase details captured at checkout,
• customer entitlements created from previous successful purchases remain tied to those purchase records.

If you run a custom storefront, refresh listing and catalogue data before creating checkout sessions. This prevents customers from checking out with stale pricing or a product that is no longer visible.

What Happens Behind the Scenes

A listing records your provider organisation's commercial settings for a published product. The listed price is calculated from the product price and your provider markup. That listed price is the price customers see through your storefront or supported checkout flow.

Infuse remains the source of truth for listing visibility, active listing version, checkout pricing, purchases, and entitlements.

API Equivalent

Use the dashboard for normal listing administration. Use the API when you need to automate listing management or connect provider listings to your own internal tools.

POST /marketplace/providers/listings/{marketplaceItemId}
Authorization: Bearer {provider_access_token}
Content-Type: application/json

{
  "marketplaceInstanceId": "11111111-1111-1111-1111-111111111111",
  "markupAmount": 5.00
}

GET /marketplace/providers/listings?marketplaceInstanceId={marketplaceInstanceId}
Authorization: Bearer {provider_access_token}

Use the listing visibility endpoint to hide or reactivate a listing.

POST /marketplace/providers/listings/{id}/visibility
Authorization: Bearer {provider_access_token}
Content-Type: application/json

{
  "visible": false
}