--- title: "AWS Private Offer for Multiple Buyer Accounts" url: https://www.fours.com/resources/blog/aws-private-offer-multiple-buyer-accounts/ canonical: https://www.fours.com/resources/blog/aws-private-offer-multiple-buyer-accounts/ type: Blog description: "One AWS private offer for many buyer accounts: extend it to the management account, or name up to 24 accounts, and plan for each account to accept it." --- # AWS Private Offer for Multiple Buyer Accounts > Canonical HTML version: https://www.fours.com/resources/blog/aws-private-offer-multiple-buyer-accounts/ 1. [Home](/) 2. [Resources](/resources/) 3. [Blog](/resources/blog/) 4. AWS Private Offer for Multiple Buyer Accounts # AWS Private Offer for Multiple Buyer Accounts Your customer runs dozens of AWS accounts and wants one private offer for all of them. Here are the four ways to structure that deal, the account limits AWS publishes, and what can't change after release. [![Stacy Wu](/authors/stacy-wu.jpg)](/resources/blog/author/stacy-wu/) [Stacy Wu](/resources/blog/author/stacy-wu/) Oct 12, 2026 ![AWS Private Offer for Multiple Buyer Accounts](/images/blog/aws-private-offer-multiple-buyer-accounts/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Faws-private-offer-multiple-buyer-accounts%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Marketplaces. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Faws-private-offer-multiple-buyer-accounts%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Marketplaces. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Faws-private-offer-multiple-buyer-accounts%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Marketplaces. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Faws-private-offer-multiple-buyer-accounts%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Marketplaces. "Summarize with Perplexity") Table of Contents - [Can one AWS private offer cover many buyer accounts?](#can-one-aws-private-offer-cover-many-buyer-accounts) - [Which structure fits a customer with many AWS accounts?](#which-structure-fits-a-customer-with-many-aws-accounts) - [What are AWS’s rules for the accounts you name?](#what-are-awss-rules-for-the-accounts-you-name) - [What should you check before you send a multi-account offer?](#what-should-you-check-before-you-send-a-multi-account-offer) - [What does Fours record when several accounts accept?](#what-does-fours-record-when-several-accounts-accept) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _An AWS private offer for multiple buyer accounts is one private offer that several of a customer’s AWS accounts can accept, either because you named each account or because you extended it to the organization’s management account. Every account that wants the private terms accepts it on its own._ * * * Umbrella runs its AWS estate as one organization: a management account and dozens of member accounts, split by team and environment. Its procurement lead has agreed terms with Acme and asks Acme’s deal desk a fair question: can one private offer cover all of those accounts? It can, in more than one way, and the choice has to be made before the offer goes out, because AWS fixes the list of named accounts at release. AWS lets a customer accept an offer in its management account and share it across the organization. It lets you name accounts one by one, up to a limit that its own guides state three different ways. And for some product types, it lets one account buy and distribute the license. For a SaaS product, though, no route lets one account’s subscription cover another’s. What a buyer sees once an offer reaches an account is covered in [what buyers see when you send a private offer](/resources/blog/what-buyers-see-when-you-send-a-private-offer/). This guide is about getting the right accounts onto the offer: the four structures, AWS’s rules for named accounts, the checks to run before you send, and what Fours records when several accounts accept. ## Can one AWS private offer cover many buyer accounts? **Yes, in two ways: extend it to the customer’s management account, or name each account in the offer.** Either way, every account that wants the private terms accepts the offer itself, signed in to that account. - **Through the management account.** AWS’s seller guide says “Buyers can’t view the offer unless you extend it to either their linked account or their management account.” For a customer using consolidated billing in AWS Organizations, the buyer guide says the offer can be accepted “from either the organization’s management account or from a member account,” and “If you accept from the management account, the private offer can be shared with all member accounts in the organization.” - **By naming accounts.** On the **Add buyers** page in AWS Partner Central, you “provide an AWS account ID for each AWS Marketplace buyer you are extending the private offer to,” and “You can add up to 24 buyers to each private offer.” - **Either way, each account accepts.** “To view the offer, the buyer must be signed into the AWS account that received the offer.” Sharing from the management account doesn’t remove that step: “Member accounts that were previously subscribed to the product must also accept the new private offer to benefit from the pricing,” and member accounts that weren’t “must accept the private offer to be able to deploy the product.” Every acceptance is a purchase of its own. AWS’s buyer guide says that when you accept a private offer, “it becomes an agreement (also known as a contract or subscription) between you and the seller,” and Fours records a separate entitlement, with its own agreement ID, for each account that accepts. So write the offer’s price and payment schedule as what one accepting account takes on, not as the value of the whole deal. ## Which structure fits a customer with many AWS accounts? **Start with the management account, name accounts when the customer wants a defined set, and have one account buy when your product, not AWS, decides who gets access.** The table runs in that order. Managed entitlements come last because AWS allows license sharing only for some product types, and SaaS isn’t one of them. Structure Use it when What AWS says Watch for **1\. Extend it to the management account** The customer uses consolidated billing in AWS Organizations and wants the terms open to its member accounts ”If you accept from the management account, the private offer can be shared with all member accounts in the organization” The management account is the one buyer you name. Each member account that wants the terms still accepts, previously subscribed ones included **2\. Name the accounts** The customer wants a defined set of accounts on the terms, or its accounts don’t sit in one organization Up to 24 buyers per offer in AWS Partner Central (seller guide); 1 to 26 account IDs through the Catalog API (developer guide) Plan on 24. The list can’t change after release, and without Concurrent Agreements an account can hold only one active subscription to a SaaS contract product **3\. One account buys** Your product grants access to the customer’s other teams itself, so one subscription can serve them all SaaS licenses don’t share: “Only AMI, container, machine learning, data products and Oracle Database@AWS subscriptions have licenses that can be shared” The subscription stays with the account that bought it. Wider access is up to your product, not AWS **4\. Managed entitlements** The product is an AMI, container, machine learning, data or Oracle Database@AWS product License administrators “distribute rights of use, known as entitlements, to specific AWS accounts” through AWS License Manager License sharing has to be set up first, and each recipient accepts and activates its grant. [How managed entitlements reach member accounts](/resources/blog/managed-entitlements-for-foundation-models/) walks through it In row 1 you name a single account, the management account, and the organization’s member accounts reach the offer through it. Row 2 suits a customer that wants three business units on the terms and not the rest, or accounts spread across more than one organization. For a SaaS product, a customer that wants one purchase instead of many acceptances means row 3. ## What are AWS’s rules for the accounts you name? **Plan on 24 accounts, settle the list before release, and check each account for an existing subscription.** AWS’s documentation states the account limit three ways: Where AWS says it What it says Seller guide: the **Add buyers** page in AWS Partner Central ”You can add up to 24 buyers to each private offer” Developer guide: the Catalog API’s validation of `PositiveTargeting.BuyerAccounts` ”List size must be between 1 and 26,” each a 12-digit AWS account ID Buyer guide: Private offers in AWS Marketplace ”Each private offer can be made to up to 25 accounts” Twenty-four is the lowest of the three, and it’s the one AWS gives for the page where you add buyers in AWS Partner Central, so it’s the number to plan a deal around. The Catalog API also documents a separate error for too many accounts, `TOO_MANY_BUYER_ACCOUNTS`: “Provide BuyerAccounts within the allowed limits.” If the customer needs more accounts on the terms than that, use the management account, or split the accounts across more than one offer. Three more rules decide whether a named account can accept: - **The list is fixed at release.** The Catalog API refuses changes in either direction: “BuyerAccounts can’t be added after the offer is released,” and “BuyerAccounts can’t be removed after the offer is released.” A forgotten or mistyped account means a new offer. Fours’ docs give the fix: clone the offer, correct the account, send the new offer and cancel the original. - **One active SaaS contract per account.** AWS’s private offer FAQ says “Each buyer account can only have one active subscription to a SaaS contract or contract with consumption product.” A named account that already holds one gets “You already have an active contract” when it tries to accept, and AWS’s route for that account is an agreement-based offer on its existing agreement. - **Unless the product supports Concurrent Agreements.** AWS announced Concurrent Agreements on February 26, 2026, enabling buyers “to make multiple purchases for the same product within a single AWS account.” For SaaS, it’s available on products whose sellers have completed the integration, and AWS made support required for new SaaS products from June 1, 2026. ## What should you check before you send a multi-account offer? **Collect and count the account IDs, add the account AWS requires beyond the buyers, and clear anything that would stop an account from accepting.** Before you release the offer: 1. **Agree the route with the customer.** One AWS Organization with consolidated billing points to row 1; a defined set of accounts, or accounts in more than one organization, points to row 2. 2. **Collect every 12-digit account ID.** Fours’ docs spell out the format: exactly 12 digits, no dashes or spaces, and not an IAM user ID or a resource ARN. 3. **Count them against 24.** Over that, go back to row 1, or split the accounts across offers. 4. **Add the private marketplace administrator’s account.** AWS: “If the buyer account for your private offer is managed through a private marketplace, you must include both the buyer’s account and the account that includes their private marketplace administrator in the offer.” Leave room for it in your count. 5. **Check each account’s Region against the offer currency.** AWS: “Each selected buyer must have an AWS account in a AWS Region where the selected offer currency is supported.” 6. **Look for existing subscriptions.** For a named account that already holds an active SaaS contract for your product, AWS’s route is an agreement-based offer on that account’s agreement, unless your product supports Concurrent Agreements. 7. **Check countries, if you geo-target the offer.** [Why a buyer can’t accept an AWS private offer](/resources/blog/buyer-cannot-accept-aws-private-offer/) covers how AWS applies country targeting to linked accounts, and how to replace a released offer that missed an account. ## What does Fours record when several accounts accept? **One entitlement for each account that accepts, so you reconcile per account rather than per offer.** In Fours, the **Buyer(s)** field on an AWS private offer takes one or several buyer AWS account IDs. When they accept, each account gets its own entitlement, attributed to its own buyer record. As Fours’ docs put it, “the offer is shared, the entitlements are not.” - **Filtering by the offer returns several entitlements:** one per accepting account, each with its own agreement ID, dates and metering. - **Fours matches on the AWS account that holds each agreement**, rather than reusing whichever entitlement is already attached to the offer, so a second account accepting the same offer never lands on the first account’s entitlement. - **The same check covers an offer accepted by a different linked account** than the one it was sent to: the account that actually holds the agreement gets its own entitlement row, instead of the record being re-pointed. AWS’s own view works the same way. Its seller guide says that after an offer is accepted, “it will show up as an agreement in the Agreements tab. The status of the offer won’t change.” On a multi-account deal, count agreements and entitlements, not offer status, to see which accounts have accepted. Fours documents the behaviour in [how multi-buyer AWS offers get one entitlement per buyer](https://doc.fours.com/aws-marketplace/accept-private-offer/#multi-buyer-offers-get-one-entitlement-per-buyer-for-sellers). ## Frequently asked questions ### How many buyer accounts can one AWS private offer include? Plan on 24. AWS’s seller guide says you can add up to 24 buyers to each private offer in AWS Partner Central. The Catalog API accepts 1 to 26 account IDs, and the buyer guide says 25. Twenty-four is the lowest figure. ### Does every account have to accept the private offer? Yes. Each account that wants the private terms accepts while signed in to that account. If the management account accepts, AWS says the offer can be shared with member accounts, but previously subscribed ones must still accept to get the pricing, and others to deploy the product. ### Can you add a buyer account after the offer is released? No. AWS doesn’t allow buyer accounts to be added to or removed from a released offer. Clone the offer with the corrected list of accounts, send the new offer, and cancel the original. ### Can a customer share a SaaS subscription across its AWS accounts? Not through AWS. AWS says only AMI, container, machine learning, data products and Oracle Database@AWS subscriptions have licenses that can be shared. For SaaS, each account accepts the offer itself, or one account buys and your product gives the other teams access. ### What if a buyer account is governed by a private marketplace? Add the account that holds its private marketplace administrator to the offer too. AWS says an offer to a buyer account managed through a private marketplace must include both the buyer’s account and that administrator’s account. ### What does Fours record when several accounts accept one offer? One entitlement per accepting account, each attributed to its own buyer record, with its own agreement ID, dates and metering. Filtering by the offer returns all of them, so you reconcile a multi-account deal per account rather than per offer. ## Takeaways - Start with the customer’s organization: an offer accepted in its management account can be shared with member accounts, but every account that wants the terms still accepts it. - To name accounts, plan on 24 and include any private marketplace administrator’s account. Settle the list before release, because AWS won’t add or remove buyer accounts afterwards. - A SaaS subscription doesn’t share between accounts through AWS, and every account that accepts holds its own agreement, so price the offer per account. Fours records each acceptance as its own entitlement. Fours creates AWS private offers for one buyer account or several, and keeps every acceptance as its own entitlement for reconciliation. See how offers are built and tracked from draft to acceptance in [Fours’ private offer management](/platform/offers/). ## Sources Primary sources for the platform rules cited above. Last verified October 12, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [AWS Marketplace Seller Guide: Creating and managing private offers](https://docs.aws.amazon.com/marketplace/latest/userguide/creating-private-offer.html) — The Add buyers page in AWS Partner Central: an AWS account ID for each buyer, each buyer's account in a Region where the offer currency is supported, and up to 24 buyers per private offer; an accepted offer shows up as an agreement in the Agreements tab while the offer's status doesn't change - [AWS Marketplace Seller Guide: Preparing a private offer for your AWS Marketplace product](https://docs.aws.amazon.com/marketplace/latest/userguide/private-offers-overview.html) — Buyers can't view an offer unless it is extended to their linked account or their management account; the buyer must be signed in to the account that received the offer; a buyer account managed through a private marketplace needs both its own account and its private marketplace administrator's account in the offer - [AWS Marketplace Developer Guide: Work with private offers using the AWS Marketplace APIs](https://docs.aws.amazon.com/marketplace/latest/developerguide/work-with-private-offers.html) — The Catalog API's UpdateTargeting validation: PositiveTargeting.BuyerAccounts list size between 1 and 26, each a 12-digit account ID; the TOO\_MANY\_BUYER\_ACCOUNTS error; BuyerAccounts can't be added or removed after the offer is released - [AWS Marketplace Buyer Guide: Private offers in AWS Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers.html) — With consolidated billing in AWS Organizations, acceptance from the management account or a member account; sharing with all member accounts after the management account accepts; previously subscribed member accounts accept to get the pricing, others to deploy the product; an accepted private offer becomes an agreement; each private offer can be made to up to 25 accounts - [AWS Marketplace Seller Guide: Private offer FAQ](https://docs.aws.amazon.com/marketplace/latest/userguide/private-offer-faq.html) — Each buyer account can have only one active subscription to a SaaS contract or contract with consumption product; the 'You already have an active contract' error; the agreement-based offer as the route for an account that already holds one - [AWS What's New: AWS Marketplace now supports multiple purchases of SaaS & Professional Services products from the same account](https://aws.amazon.com/about-aws/whats-new/2026/02/concurrent-agreements-february/) — Posted February 26, 2026: Concurrent Agreements lets buyers make multiple purchases of the same product within one AWS account; on by default for Professional Services listings, available on SaaS products whose sellers have completed the integration, and required for new SaaS products starting June 1, 2026 - [AWS Marketplace Buyer Guide: Sharing your licenses](https://docs.aws.amazon.com/marketplace/latest/buyerguide/sharing-licenses.html) — Only AMI, container, machine learning, data products and Oracle Database@AWS subscriptions have licenses that can be shared; license sharing must be set up for the organization first - [AWS License Manager User Guide: Granted licenses in License Manager](https://docs.aws.amazon.com/license-manager/latest/userguide/granted-licenses.html) — License administrators distribute rights of use, known as entitlements, to specific AWS accounts; the recipient accepts and activates the granted license before the subscription is available to it - [Fours docs: Accept Private Offer](https://doc.fours.com/aws-marketplace/accept-private-offer/) — Fours behaviour: on a multi-buyer offer, each accepting account gets its own entitlement attributed to its own buyer record, with its own agreement ID, dates and metering; filtering by offer returns one entitlement per accepting account; the account-level check, including an offer accepted by a different linked account than the one it was sent to - [Fours docs: Create Private Offer](https://doc.fours.com/aws-marketplace/create-private-offer/) — Fours behaviour: the Buyer(s) field takes one or multiple buyer AWS account IDs; the 12-digit account ID format; clone the offer, update the account number, send the new offer and cancel the previous one to fix a wrong account ## Keep reading - [AWSAWS Marketplace Buyer Notifications: What to ChangeOct 14, 2026](/resources/blog/aws-marketplace-buyer-notifications/) - [AWSAWS Marketplace SaaS Registration Page ChecklistOct 14, 2026](/resources/blog/aws-marketplace-saas-registration-page/) - [AWSAWS Marketplace SaaS Security RequirementsOct 12, 2026](/resources/blog/aws-marketplace-saas-security-requirements/) - [AWSOne or Multiple AWS Marketplace Seller Accounts?Oct 12, 2026](/resources/blog/multiple-aws-marketplace-seller-accounts/) [Browse every post on the Fours Blog](/resources/blog/) ### Stay Updated New posts, product updates and marketplace strategy are shared on LinkedIn as they publish. [Follow Fours on LinkedIn](https://www.linkedin.com/company/suger-inc)