Suger Adds Multi-Account AWS Marketplace Management and Real-Time Offer Sync
Suger's September 14 release connects more than one AWS Marketplace seller account to a single organization, syncs offers created outside the console as EventBridge events arrive, and lets sellers reprice pre-authorized renewal uplifts before the deadline.
Suger's September 14 release lets a single Suger organization connect more than one AWS Marketplace seller account. According to Suger's documentation, additional accounts are added from an "Add AWS account" card in the console, one account is set as the default that Suger uses when a request does not name an account, and a SaaS or Professional Services product created while multiple accounts are connected is assigned its owning account at creation. Existing assets stay under the account that created them.
Offer synchronization also becomes event-driven. Suger reports that offers released outside its console, whether from the AWS Marketplace Management Portal, the Catalog API, or renewals AWS generates itself, now sync as the EventBridge event arrives rather than on the hourly cycle. The event stream is AWS behavior and requires the EventBridge integration to be connected. What changed is that Suger now acts on those events for offer release.
On private offers carrying pre-authorized renewal terms with a percentage-range uplift, sellers can reprice within the agreed range before the adjustment deadline from the console and from the Suger Salesforce and HubSpot apps, set a separate uplift per dimension, preview the resulting prices, and either save a draft or publish. Suger's documentation states that publishing is irreversible and that a daily check sends one reminder per entitlement cycle beginning 30 days before the deadline.
Two smaller changes target operational dead ends. Action buttons in co-sell and commission emails, covering accept co-sell, mark closed won or lost, and approve a commission change, are now personal to the recipient, work once, and expire after 24 hours. AWS rejection reasons for failed offer updates and co-sell referrals now appear on the offer and in the related email instead of a generic failure.
Our take: Suger has been marketing multi-account AWS Marketplace support since a February 2025 blog post, so the news is not the capability but that adding an account is finally a self-serve card in the console. The surfaced AWS rejection reasons are the tell: shipping "show the provider's error message" as a feature in 2026 means marketplace operators spent the prior years guessing why an offer update failed, or filing a support ticket to find out. The single-use, 24-hour email buttons are the most candid item in the release, an admission that co-sell approvals still happen in somebody's inbox rather than in the system where the deal lives. Worth noting that the current docs attach no plan or tier gate to any of this, which is not a given for multi-account features.
Original Link: Suger changelog, September 14 release