Business structure

Before connecting several sales channels or importing a large amount of data, it is worth defining the business structure that Comers should operate in.

The basic relationship is:

Organization → Seller → sales channel/account

This structure tells Comers which business owns the operational data and which selling context an integration belongs to.

flowchart TD
    O[Organization] --> S1[Seller A]
    O --> S2[Seller B]
    S1 --> E[eBay account]
    S1 --> W[WooCommerce store]
    S2 --> A[Amazon account]

Organization

An Organization is the customer-level boundary in Comers.

It groups the business context that belongs together, including users, Sellers, integrations, Products, Orders, stock, and other operational data.

An Organization is normally the level at which you think about the Comers environment as a whole.

A user can belong to more than one Organization, but data and access do not automatically cross between them.

Seller

A Seller represents a business, brand, or commercial identity that sells through one or more channels.

One Organization can operate several Sellers.

For example, a company that runs two separate brands can represent them as two Sellers while still managing both inside the same Organization.

A Seller is not the same thing as a marketplace account. One Seller can use multiple sales channels and can also have more than one account where the business requires it.

Sales channel and account

A sales channel/account represents the external selling endpoint connected to the Seller.

Examples include:

• an eBay selling account,
• an Amazon account,
• a WooCommerce store,
• another supported marketplace or store connection.

This is the level where provider-specific account context belongs.

When an integration is connected, make sure it is attached to the Seller and sales-channel account that actually owns the external business data.

Example: one brand, several channels

A simple multichannel business can use one Seller with several connected channels:

Organization → Seller → eBay + Amazon + WooCommerce

The internal Product catalog can then remain independent from the individual marketplace offers, while Orders and Listings still retain their source channel.

This is usually simpler than creating a separate Seller only because another marketplace was added.

Example: several brands

If one company operates separate brands, a structure can look like:

Organization → Seller A → its channels

Organization → Seller B → its channels

This keeps the brands inside one customer Organization while preserving separate selling contexts where they matter.

The exact split should follow the way the business actually needs to separate operations, access, catalog context, or integrations.

Multiple accounts on the same platform

Having two accounts on the same marketplace does not automatically require two Organizations.

The important question is which Seller each account belongs to and whether the accounts represent the same or different commercial contexts.

For example, one Seller can have several sales-channel accounts when the business operates multiple marketplace accounts for the same brand.

Why the structure matters

The business structure is used throughout Comers to keep operational records in the correct context.

It helps determine where data such as these belong:

• integrations,
• Orders,
• Listings,
• Products and their assignments,
• Warehouse stock,
• Messages,
• team access.

A clear structure reduces the risk of importing data into the wrong business context or creating unnecessary duplicates.

Set the structure before large imports

Whenever possible, establish the Organization, Seller, and sales-channel structure before importing a large catalog or synchronizing substantial operational history.

Changing the structure later can require reviewing relationships that have already been created around imported data.

Relationship with Products and Listings

A Product is an internal catalog record and can be used across channel contexts according to its assignments.

A Listing represents the channel-specific offer.

Keeping these concepts separate allows the business structure to describe where you sell without forcing every sales channel to become a separate internal product catalog.

Relationship with integrations

An Integration connects an external account with the corresponding Comers business context.

Before authorizing a new integration, verify:

1. which Organization should own the connection,
2. which Seller the external account belongs to,
3. which sales-channel account is being connected.

Then review the first synchronization before relying on the imported data operationally.

Practical guidance

Use the smallest structure that accurately represents the business.

Do not create an additional Organization or Seller only because another integration exists. Add a separate business context when the business itself needs that separation.

If you are unsure, start by asking:

• Is this the same customer Organization?
• Is this the same brand or commercial identity?
• Is this simply another place where that Seller sells?

Those answers usually identify the correct level.