One or Multiple AWS Marketplace Seller Accounts?

An AWS Marketplace seller account is the AWS account registered as the seller of record for your products: AWS reports, disburses and communicates through it. You can run several, one per AWS account, but a product can’t move between them once it’s listed. This guide covers when a second account is worth it, what it costs, what you can’t undo, and how to run several in AWS Partner Central and Fours.

---

Acme sells on AWS Marketplace from a seller account registered to its US company. It has just acquired Globex, which sells two products from its own seller account, and Acme wants its new EU subsidiary to be the seller for European buyers. Its marketplace operations lead has three questions: can Globex’s listings move onto Acme’s account, does the EU entity need its own, and what changes in AWS Partner Central and in Fours if the answer is three accounts?

AWS answers the first two directly, and the third comes down to connecting the accounts on both sides. One related question isn’t about accounts at all: which AWS entity invoices your European buyers depends on KYC, covered in AWS EMEA SARL and seller KYC.

What is an AWS Marketplace seller account?

An AWS Marketplace seller account is an AWS account registered to sell in AWS Marketplace, which AWS says “will become the seller of record for your products and will be used for reporting, disbursement, and communication from AWS Marketplace to you.”

• One per AWS account. “Each AWS account can have only one registered seller account and address,” so a second seller account means a second AWS account.
• Several are allowed. “You can have multiple seller accounts if your business requires it. Each seller account corresponds to a separate AWS account and operates independently of AWS Organizations.”
• A new account is AWS’s default. “AWS Marketplace recommends using a new account to register as a seller,” though an existing one works “as long as it was created after September 27, 2017.”

The registration itself is covered in how AWS Marketplace seller registration and listing work.

Should you run one seller account or several?

One, unless a different legal entity has to be the seller of record, or a business unit or compliance requirement needs a seller of record of its own. AWS’s reasons for several are “operating in multiple territories, separating different business units, or meeting specific compliance requirements,” and it notes that “some sellers prefer a single global account for simplicity.”

The middle column is our reading; the right-hand column is AWS’s.

Your situation	One account or several?	What AWS says
A different legal entity must be the seller, such as an EU entity for EU buyers	A separate account for that entity	”If you decide to use different business entities to sell in different countries or require different disbursement bank accounts for different products, you can create multiple AWS accounts and register them as individual seller accounts”
An acquired company already sells on AWS Marketplace	Keep its account, at least for the listings it has	Listings “cannot be transferred to another seller account”
A business unit or a compliance requirement needs its own seller of record	A separate account	Business units and compliance are two of the three reasons AWS names
Different disbursement bank accounts for different products	A separate account	The same sentence as the first row
Payouts in more than one currency	One	A seller account can have one or several disbursement bank accounts, including separate accounts per currency
Finance and product teams need different access	One	”IT teams can create roles within a single seller account to enable cross-functional collaboration”
AWS EMEA SARL should invoice your European buyers	One	”Sellers must complete the KYC process to use the AWS EMEA invoicing entity,” which your existing account can do
Buyers should see one brand across entities	Either	”Multiple seller accounts can use the same display name”

For Acme, two rows apply: the EU entity gets its own account, and Globex keeps its account.

What does each extra seller account cost?

Its own registration, catalog and root inbox, plus a decision about where it sits in AWS Organizations.

Cost	What AWS says
A separate catalog	”Each seller account maintains its own separate product catalog and requires independent management”
A registration per entity	”Each seller account must have a unique legal business name during registration,” and each provides its own tax and bank account information, and its own KYC to sell through AWS EMEA SARL
A monitored root email	It “cannot be an alias address, as certain AWS teams can only communicate with the registered root email address”
Tax inheritance	”When the management account in an AWS Organizations organization enables tax inheritance, member accounts inherit the management account’s billing address and legal entity information”

The last row is the one that catches multi-entity companies. Tax inheritance is a Billing setting that adds the management account’s tax registration information, including its business legal name and tax address, to member accounts, and AWS requires a member account’s seller country address to match the management account’s. When the seller entity differs from the management account’s (AWS’s example is a US management account and an Australian seller), AWS recommends “a standalone AWS account that’s not part of any organization,” or “a new AWS Organizations organization where all accounts represent the same business entity as your intended seller account.”

What is hard to undo?

The account a product is listed under, and the seller of record on every agreement sold from it. Qualification sharing in AWS Partner Central, and the accounts you connect to Fours, can be changed later.

Decision	Can you change it later?	What the source says
The seller account a product is listed under	No	”Once you register as a seller and list a product, you can’t change the account associated with your products”
The seller of record on an agreement already sold	No	”You can’t amend an agreement to specify a seller of record that’s different from the seller of record from the original agreement”
Associating qualifications in AWS Partner Central	Yes	”A subsidiary account can disassociate qualifications at any time”
The accounts connected to Fours, and the default	Yes, account by account	Deleting an integration is immediate and permanent, and that account’s products, offers and entitlements stop syncing

So settle which entity sells each product, and where its AWS account sits in AWS Organizations, before the first listing. If you can’t tell which account is the seller of record for a product, AWS says to contact the AWS Marketplace Seller Operations team.

Can you merge an acquired company’s seller account into yours?

Not its listings or its agreements, so in practice you keep the account and connect it. The rules above leave two paths:

1. Keep the acquired account selling, and connect it. In AWS Partner Central it becomes a subsidiary of your primary account, which AWS describes as “typically the acquiring company’s account for M&A scenarios.” In Fours it becomes another integration. Its listings, offers and buyers stay where they are.
2. List again under your own account, if the acquired account has to close eventually. The new listing is a new product, the acquired account remains the seller of record on agreements already sold from it, and buyers move only by accepting offers on the new listing.

For Acme, that means three accounts: its own; Globex’s, connected, with its two products unchanged; and a new one for the EU entity, outside the US company’s AWS organization.

How do several seller accounts connect in AWS Partner Central?

Through subsidiary connections to one primary partner account. In AWS’s words: “If you operate multiple AWS Marketplace seller accounts — for example, separate accounts by Region or business unit — connect them to your primary partner account.” Without that, their revenue “might not count toward your partner attribution,” which AWS says directly affects your funding eligibility.

The primary sends the request, with up to 10 AWS account IDs per submission, and each subsidiary accepts. AWS says the primary is “typically the account where both Partner and Seller registrations exist,” and its Partner Revenue Measurement guide recommends, for partners with several Marketplace accounts, “creating and linking a new AWS account to represent your global business.” Subsidiary connections need the new Partner Central experience, and AWS says to connect only accounts “that you own or that belong to an organization you have acquired.”

Level	How it starts	What changes
Connection	The primary sends a request and the subsidiary accepts	Partner Revenue Measurement counts the subsidiary’s revenue toward the primary’s attribution, and the primary gets a consolidated Attributed Revenue report. No profile, scorecard or display name changes
Associate qualifications	The subsidiary chooses it, and can disassociate at any time	The subsidiary’s display name becomes “[Subsidiary Name] by [Primary Name]”, connected accounts get a consolidated scorecard, tier eligibility is recalculated, and specializations, certifications and select program enrollments are shared

Funding stays with each account even at the second level: “only the account that originally enrolled in a program can apply for related funding. Wallets are not shared — each account retains its own wallet and can only draw funding against its own balance.” AWS announced qualification sharing on July 10, 2026, available that day in all commercial AWS Regions.

How does Fours handle several AWS Marketplace seller accounts?

Each seller account connects as its own AWS Marketplace integration in one Fours organization, and each product, offer and entitlement belongs to the account it was listed or sold under. Fours announced support for several AWS Marketplace accounts in one organization in our 2025 post on multiple AWS Marketplace integrations; the current steps are in the Multiple Integrations guide.

You add an account with Add Integration in the AWS Marketplace card’s ⋯ menu. Sign in to the AWS account you’re adding first, in another browser tab: the CloudFormation stack is created in whichever account is signed in, and that decides which account gets connected.

When	What Fours does
Your second account connects	Every AWS Marketplace card shows its AWS account ID, and your first account is marked Default. The products, offers, entitlements and referrals you already had stay with it
You create a SaaS or Professional Services product	The AWS Marketplace Integration field asks which account to list it under. The product, and the offers you create for it, belong to that account
A buyer arrives from a fulfillment URL with no partnerId	Typically a listing created before you connected your second account. Fours uses the default account and, if that account can’t read the buyer’s registration token, tries your other connected accounts before failing the signup
An API request names no account	Fours uses the default account, for example for a product created without a partnerID
One buyer subscribes under two of your accounts	Fours keeps two buyer records rather than treating the second as a duplicate
You need one account’s products	Search the product list by AWS account ID, or hover a product’s logo in the Partner column of the list view
You delete one account’s integration	The other accounts keep working, and if it was the default, the oldest remaining account takes over. Its products, offers and entitlements stay in Fours, but Fours can no longer sync them or act on them

Keep each listing’s fulfillment URL pointing at its own account. Its partnerId tells Fours which integration a purchase came through, and AWS’s listing review exercises that path, so a wrong value shows up as a failed test purchase. The format is in set up your fulfillment URL.

Checklist: running several AWS Marketplace seller accounts

Register each account for one entity, connect it in AWS Partner Central and in Fours, and keep the owning account explicit on every listing. For each seller account:

Before you register it

• One legal entity, with its own legal business name. Reuse the display name if buyers know one brand.
• A standalone AWS account, or an organization whose accounts all represent that entity.
• A real, monitored root email address, not an alias.
• Tax and bank account information, and KYC if it sells through AWS EMEA SARL.

In AWS Partner Central

• Connect it to your primary partner account as a subsidiary, unless it is the primary.
• Decide whether it associates qualifications, after reviewing the preview of its new display name.
• Apply for program funding from the account that enrolled in the program.

In Fours

• Add it as its own AWS Marketplace integration, signed in to that AWS account, and give it a name: unnamed, it shows in the product field as AWS - MARKETPLACE - followed by its account ID.
• Choose the default on purpose: it’s tried first for every signup whose fulfillment URL has no partnerId.
• Point each listing’s partnerId at the account that owns the listing, and choose the account on every new product.
• Before deleting an integration, accept that its products, offers and entitlements stop syncing, then remove its CloudFormation stack from that AWS account.

Frequently asked questions

Can you have more than one AWS Marketplace seller account?

Yes. AWS allows multiple seller accounts “if your business requires it,” one per AWS account. Each registers its own unique legal business name and keeps its own product catalog, though several can share one display name.

Can you move a product listing to another AWS seller account?

No. AWS says that once you list a product, “you can’t change the account associated with your products,” and an agreement can’t be amended to name a different seller of record. To sell the product from another account, list it again there.

Does an acquired company need to keep its own AWS seller account?

To keep selling its current listings, yes, because they can’t be transferred to another seller account. Connect it to your primary partner account in AWS Partner Central so its revenue counts toward your partner attribution, and to Fours as another integration.

Do connected AWS seller accounts share partner funding?

No. When a subsidiary associates qualifications, connected accounts share select program enrollments, but only the account that originally enrolled can apply for the related funding. AWS says “Wallets are not shared,” so each account draws only on its own balance.

How does Fours handle several AWS Marketplace seller accounts?

Each account connects as its own AWS Marketplace integration in one Fours organization, and every product, offer and entitlement stays with the account it was listed or sold under. One account is the default, used when a signup or API request doesn’t name an account.

Takeaways

• Run a second seller account when a different legal entity has to be the seller of record, or for a reason AWS names; team access, payout currencies and EMEA invoicing don’t need one.
• Decide before the first listing: a product can’t move to another seller account, and an agreement can’t be amended to a different seller of record.
• Connect the accounts on both sides: as subsidiaries of one primary partner account in AWS Partner Central, so their revenue counts toward your attribution, and in Fours, each as its own integration, with a deliberate default.

Fours connects each AWS Marketplace seller account as its own integration and keeps every product, offer and entitlement with the account that owns it, all in one organization. See how listings, offers and fulfillment come together in Fours for AWS Marketplace.