Comers Core · multichannel
Multichannel ecommerce without multiple ways of working
Comers connects marketplaces, stores and sales accounts into one operational surface. Channel-specific data is normalized into a shared model so your team can work with orders, listings, inventory, fulfillment and customer conversations without organizing the company around the limitations of each marketplace.
- Channels are inputs, not separate ways of working
- One data model across accounts and stores
- The source stays visible where it matters
sales channels
- Marketplace · PL account
- Marketplace · DE account
- Brand store
- Sales account
normalization
Comers operating model
everyday operations
- Orders
- Products
- Listings
- Inventory
- Fulfillment
- Messages
01 · sales structure
Organization, Seller and Sales Channels — three levels, one model
Comers separates three levels that many systems mix together. A company can grow sideways — more brands, more accounts — without turning every channel into a separate operating system.
- Organization
- The customer / tenant in Comers — your company and its operational environment.
- Seller
- A brand, selling unit or operational commercial identity inside the organization.
- Sales Channel
- A concrete marketplace account or store the sale comes from.
- seller Brand A
- Marketplace · PL account marketplace
- Marketplace · DE account marketplace
- Brand store store
-
- seller Brand B
- Marketplace · EU account marketplace
- D2C store store
-
One organization can run multiple sellers, and each seller can connect multiple sales channels — without losing the shared operating model.
02 · channels differ, operations do not have to
Different channels. One operating model.
Every marketplace has its own statuses, identifiers, APIs and rules. Once several channels are involved, teams often end up maintaining a different operating process for each source.
Comers separates channel integration from everyday operations. The source remains visible where it matters, while orders and related data are normalized into the Comers model.
before a separate process per dashboard
Channel A
- orders
- own statuses and deadlines
- inventory
- separate numbers
- messages
- own inbox
- fulfillment
- own workflow
Channel B
- orders
- another handling process
- inventory
- another truth
- messages
- another inbox
- fulfillment
- different rules and labels
More channels means more variants of the same process — and a harder answer to “how do we actually do this?”.
with comers one process across channels
- Channel A
- Channel B
- Store
- Sales account
- Orders
- Products
- Listings
- Inventory
- Fulfillment
- Messages
The marketplace defines where a sale came from. Comers defines how your company handles it.
03 · connected operations
Orders, listings, inventory and messages stay connected
Multichannel commerce is more than aggregating orders. Products, available stock, listings, shipments and customer conversations need to stay connected across channels.
Comers keeps these areas inside one operational environment — regardless of which channel a particular sale came from.
sales from different channels
- Marketplace · PL account channel order
- Marketplace · DE account channel order
- Brand store store order
the same operational context
- Order
- Customer
- Product & listing
- Inventory
- Fulfillment
- Messages
The same set of relationships applies to sales from every connected channel.
-
orders
Orders
Sales from several channels land in one working list with shared statuses and deadlines instead of several separate dashboards.
// one handling process, many sources
-
listings
Listings
A listing stays channel-specific, but points at your own product model — content and relations do not live only inside a marketplace panel.
// the channel describes the offer, you describe the product
-
inventory
Inventory
Availability is based on real stock items rather than numbers maintained separately for each channel.
// one stock item behind many listings
-
fulfillment
Fulfillment
Shipping uses the same order and warehouse context, so packing and dispatch do not depend on where the sale came from.
// one fulfillment path
-
messages
Messages
Customer conversations stay connected to the sale, product and shipment instead of living in several independent inboxes.
// context instead of dashboard hunting
04 · shared inventory
One real inventory position can support many channels
Multichannel only works if selling in several places does not create several independent truths about the warehouse.
Comers models real stock independently from marketplace listings. Stock items can be connected to several offers across sales channels while staying part of one stock and warehouse model.
real stock item
Desk lamp — black
RT-1002 · main warehouse
- on hand
- 24 pcs
- reserved
- 3 pcs
- linked listings
- 3
- model
- product · variant
listings across channels
- Listing — PL account marketplacelinked
- Listing — DE account marketplacelinked
- Store product page brand storelinked
One real stock item should not become several independent “truths” just because you sell in several channels.
05 · integration boundary
Integrations should not define your company architecture
Channel adapters normalize external data into the internal Comers model. That lets operational workflows evolve independently from differences in external APIs, status models or temporary API delays.
The integration stays responsible for talking to the channel. Core stays the place where your organization runs its operations.
external channels
- Different APIs
- Different statuses
- Different identifiers
- Different rules
Comers Core
- Orders
- Products
- Listings
- Inventory
- Fulfillment
- Messages
your operations
- Operations team
- Warehouse & shipping
- Customer service
- Listing management
A channel can change. An API can change. Your company process should not be built around those differences.
See how Comers connects to your channels
Available channels and how they are connected are covered separately — the operating model stays the same.
06 · an agent across channels
Agent Comers works across the connected context
Because Agent Comers operates on the context available in Core, operational questions can span several channels at once.
Instead of asking marketplace by marketplace, teams work on the shared model of orders, customers, products, inventory, messages and shipments.
Which orders across our channels need operational attention today?
Across three channels there are 12 orders due today. 4 have no shipment prepared yet and 2 have an open customer conversation.
- 19-62930-40286 marketplace · PL account no shipment
- 31-58204-77613 marketplace · DE account open conversation
- 22-90311-10574 brand store ready to dispatch
// answer scope and available actions depend on permissions and the current agent tool set
FAQ
Frequently asked questions
Can Comers manage several marketplaces and sales accounts?
Yes. It is designed for multiple channels and accounts in one operating model. Actual availability depends on current integrations.
Does Comers normalize channel data?
Yes. Integrations map channel-specific data into the internal Comers operational model.
Does Comers replace every marketplace dashboard?
Not necessarily. Comers centralizes common operations. Channel-specific features still depend on the external API and integration scope.
Can multichannel operations use shared inventory?
Yes. Inventory can be modeled independently from individual listings and connected to offers across channels.
Run many sales channels as one operation
Connect channels to one model for orders, products, inventory, fulfillment and customer communication.