Comers Core · integrations
Your ecommerce ecosystem connected to one operational platform
Comers combines native integrations, automation platforms, public APIs, events and webhooks so it can work with marketplaces, stores, carriers, finance, communication, AI and thousands of other services — without turning the Core into plugin chaos.
9,000+ apps and services within reach
- Connected deeply where operational context matters
- Open boundaries where reach matters
- Every integration runs inside platform standards
native comers integrations
- Sales
- Shipping
- Finance
- Communication
- AI
open ecosystem
- n8n
- Make
- Zapier
- Public API
- Events
- Webhooks
contracts · controlled boundaries
Comers Core
Two ways in, one communication standard. The integration knows the provider — Core does not have to.
01 · ecosystem scale
A broad ecosystem, none of the chaos
Below, the reach of the ecosystem builds in two steps: first the native integration categories, then the open ecosystem of automation platforms and public interfaces. The counter on the left grows with it.
9,000+ apps and services within reach
native comers integrations
Categories where an integration needs full operational context — dedicated Comers services and adapters.
Sales
- WooCommerce
- eBay
- Amazon
- Allegro
- Shopify
- PrestaShop
- Magento
- Shopware
- Shoper
- IdoSell
Shipping
- InPost
- DHL
- DPD
- GLS
- UPS
- FedEx
Finance
- Accounting
- Invoicing
- ERP
Communication
- Mailgun
- SendGrid
- Email providers
AI
- OpenAI
- OpenRouter
- Other AI providers
open ecosystem
automation platforms
- n8n
- Make
- Zapier
comers public boundaries
- Public API
- Comers Events
- Webhooks
9,000+ apps and services within reach
// the scale of the open automation ecosystem, complemented by native Comers integrations
02 · open ecosystem
Automation platforms and public interfaces extend the reach
Not every integration needs a dedicated service inside the platform. Where secure interfaces are enough, Comers exposes a public API, events and webhooks.
That lets your team connect Comers to the tools they already use — through automation platforms or their own systems — without waiting for a dedicated integration.
-
n8n
automationVisually built automation flows, including self-hosted setups, with full control over how data moves.
// flows triggered by Comers events
-
Make
automationRich multi-step scenarios connecting Comers with sales, marketing and operations tooling.
// scenarios built on the public API
-
Zapier
automationThe fastest route from Comers to a broad catalogue of widely used business applications.
// simple connections, no development
-
Public API
A stable, versioned interface for reading and acting on operational data within granted permissions.
-
Comers Events
Operational events external systems can react to, instead of polling the platform in a loop.
-
Webhooks
Notifications delivered to declared endpoints, signed and access-controlled.
03 · two ways to connect
Native where depth matters. Open where scale matters.
This is not an either-or choice. Comers uses both routes deliberately: some connections need full operational context inside the platform, others work perfectly well across secure public boundaries.
depth
Native integrations
Sales channels, store platforms, carriers, finance, communication and AI can be integrated natively — through specialized services and adapters that understand each provider.
-
Full operational context
Order, listing, stock, shipment and settlement stay connected inside one model.
-
Provider specifics mapped
Channel statuses, identifiers and rules are normalized into the Comers model.
-
Resilient to API differences
Retries, rate limits and delays are handled by the integration, not by your process.
scale
Open ecosystem
The remaining, very broad ecosystem of tools connects across Comers public boundaries — with no reach into the platform internals and no dedicated code in Core.
-
Thousands of services in reach
Automation platforms expose large app catalogues Comers can work with.
-
Your own systems
Your ERP, data warehouse or internal tool connects through the API and events.
-
Fast to adopt
A new connection needs no change in Core and no waiting for a platform release.
Deeply connected where context decides. Widely open where reach decides. Always inside one standard.
04 · integration standards
Connected deeply. Isolated by design.
Integrations in Comers are not plugins reaching into the system internals. They are separate, isolated platform elements that talk to Core only through contracts.
A broad ecosystem therefore does not mean growing risk: an outage, an API change or a new provider does not compromise the system structure or the data of other integrations.
-
boundaries
Isolated by design
Every integration runs inside its own boundary with no direct access to Core internals.
-
contracts
Contract-driven
Communication happens through explicitly defined interfaces and data models, not shared state.
-
security
Secure by default
Service communication is encrypted and integration identity is short-lived and verified.
-
secrets
Secrets stay isolated
Provider keys and credentials live in isolated storage, outside application code and logs.
-
events
Event-first and resilient
Event-driven flows with retries absorb temporary failures on the provider side.
-
audit
Auditable by design
Integration activity is recorded, so what happened, when and on whose behalf stays visible.
external platform
- Marketplace
- Store platform
- Carrier
- External service
integration adapter
- Data mapping
- Provider authorization
- Retries and limits
- Event normalization
contracts · controlled boundary
Comers Core
- Orders
- Products
- Listings
- Inventory
- Fulfillment
- Finance
05 · open with rules
Open does not mean unrestricted
The Comers public boundaries are not a way around platform standards. External automations and custom systems operate exactly within the access they are granted — and only inside your organization.
comers public boundaries
- Public API
- Comers Events
- Webhooks
external automations and systems
- n8n
- Make
- Zapier
- Custom systems
Still governed by Comers standards
-
Authorization
Every call is authenticated and tied to a specific access grant, not to an anonymous key.
-
Access scopes
An integration receives only the permissions its task actually requires.
-
Controlled capability
What an integration can do is defined by the platform, not by the API client.
-
Tenant isolation
Data stays inside your environment — with no access to other organizations.
-
Limits and protection
Rate limits and traffic control protect operational stability under heavy automation.
-
Audit trail
Actions performed by integrations remain visible in operational history.
Integrations are one of three layers of the same story
OMS covers operations around the order, Multichannel covers many channels in one model, Integrations covers the connection to your ecosystem.
FAQ
Frequently asked questions
Does Comers only integrate with marketplaces?
No. Marketplaces are one category. Beyond sales, Comers connects with store platforms, carriers, finance, communication, AI and — through the open ecosystem — thousands of other services.
Are all integrations native?
No, and that is not the goal. We integrate natively where full operational context is required. The rest of the ecosystem connects through the public API, events and webhooks, and through automation platforms.
Can I connect Comers to my own system?
Yes. Your ERP, data warehouse or internal tool can use the public API and react to events and webhooks, within the permissions granted to it.
Does Comers support automation through n8n, Make and Zapier?
Yes — this is the backbone of the open ecosystem. Automation platforms connect Comers to a broad catalogue of business apps without writing a dedicated integration.
How does Comers secure its integrations?
Integrations are isolated, communicate through contracts, use encrypted service communication and short-lived identity, and provider secrets stay in isolated storage. Activity is auditable.
Can an integration compromise the system structure?
No. Neither native integrations nor systems using the public boundaries have direct access to Core internals. Every connection works through a controlled boundary and granted permissions.
Connect Comers to the systems your business depends on
Bring sales channels, carriers, finance, communication, AI and thousands of other services into one operational platform.