Skip to content
E-commerce

Connect Channelengine to any app with two-way sync.

Two-way sync Channelengine across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Object catalog

What Stacksync syncs in Channelengine.

These objects sync between Channelengine and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Channelengine exposes them.

Orders
Marketplace and merchant-fulfilled orders; read via GET /v2/orders and GET /v2/orders/new (status NEW), then acknowledged with POST /v2/orders/acknowledge so later shipment, return, and cancellation calls can reference them.
Products (product content)
Catalog records created and updated via POST /v2/products and deactivated via DELETE; use a parent/child variant model where the parent is a non-purchasable blueprint. Written into ChannelEngine from a PIM, ERP, or database.
Offers (price and stock)
Price and stock updates via PUT /v2/offer/stock and the offers endpoints; separate from product content so fast-changing stock can be pushed often, and supports bulk updates across stock locations.
Shipments
Fulfillment records; write with POST /v2/shipments to mark an order shipped with tracking, read with GET /v2/shipments. Pushed back from a warehouse or ERP so marketplaces update the buyer.
Returns
Marketplace- and merchant-initiated returns; read via GET /v2/returns and created with POST /v2/returns. Synced two-way so customer-service and finance systems reconcile with the ERP.
Cancellations
Order cancellations; create with POST /v2/cancellations and read with GET /v2/cancellations. Written when stock is unavailable and read back for reconciliation.
Backorders
Records marking part of an order as temporarily out of stock; create with POST /v2/backorders and read with GET /v2/backorders by merchant reference or since a date.
Order documents
Invoices and other order documents; retrieved as a paginated, filterable list via GET /v2/orders/documents for finance and archiving systems. Read-only.
API surface

How Stacksync connects to Channelengine.

The connector runs on Channelengine's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
REST API (Merchant API v2); per-tenant base URL https://{tenant}.channelengine.net/api
Authentication
API key passed as the 'apikey' parameter; ChannelEngine recommends sending it in a request header rather than the URL because some webservers log full URLs
Change detection
Webhooks fire on order creation and on return and shipment/cancellation changes; product content and offers use change-tracking endpoints (GET /v2/products/data and /v2/products/offers) with an acknowledge pattern that returns only changed records, plus polling GET /v2/orders/new
Rate limits
Rate limits are per endpoint and returned in headers: x-rate-limit-limit (interval length in minutes), x-rate-limit-remaining, and retry-after (seconds to wait); e.g. POST /v2/supportorder allows 3 calls per minute.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
What ships with Channelengine

Connect Channelengine for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in Channelengine instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Channelengine data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Channelengine record.

Observability

Monitoring

Track your Channelengine sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Channelengine connector.

ChannelEngine is the marketplace-integration platform retailers and brands use to sell across global marketplaces such as Amazon, bol.com, Zalando, eBay, and Walmart. It is owned by ecommerce and marketplace operations teams and sits between the ERP, PIM, or OMS and every marketplace: product content and offers (price and stock) are pushed out to it, while orders, shipments, returns, and cancellations flow back through it. Keeping those objects in sync with the systems of record is what prevents overselling and manual order re-keying.

  • Ecommerce and marketplace managers
  • Operations and fulfillment teams
  • ERP and integration engineers
  • Inventory and supply-chain teams
  • Finance and reconciliation
  1. Push product content from a PIM, ERP, or database into ChannelEngine's Products endpoint so listings stay current across every connected marketplace.

  2. Stream stock and price to the Offers endpoint (PUT /v2/offer/stock) whenever inventory changes so marketplaces reflect availability and overselling is avoided.

  3. Pull new marketplace orders with GET /v2/orders/new into an ERP or OMS and acknowledge them so fulfillment runs from the system of record.

  4. Write Shipments with tracking back to ChannelEngine when the warehouse or ERP marks an order shipped, so each marketplace notifies the buyer.

  5. Sync Returns and Cancellations two-way so customer-service and finance systems reconcile marketplace returns and cancellations with the ERP.

  6. Load Orders and Returns into Postgres or a warehouse for marketplace sales, fulfillment, and margin reporting without manual CSV exports.

All Channelengine integrations

Pick the system you need to keep in sync with Channelengine. Each page covers the sync setup, field mapping, and common workflows for that pair.

How it works

Set up Channelengine in minutes, without APIs.

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Channelengine with its native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Channelengine connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Channelengine objects to sync — Stacksync auto-detects the schema, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Channelengine
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Channelengine database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp

FAQ

Channelengine connector FAQ

What can I sync with the Channelengine connector?

Channelengine's core objects — Orders, Products (product content), Offers (price and stock), Shipments and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Channelengine?

Via REST API (Merchant API v2); per-tenant base URL https://{tenant}.channelengine.net/api, authenticated with API key passed as the 'apikey' parameter; ChannelEngine recommends sending it in a request header rather than the URL because some webservers log full URLs. Changes are detected as follows — webhooks fire on order creation and on return and shipment/cancellation changes; product content and offers use change-tracking endpoints (GET /v2/products/data and /v2/products/offers) with an acknowledge pattern that returns only changed records, plus polling GET /v2/orders/new. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Channelengine connector two-way?

Yes. Changes made in Channelengine propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Channelengine integration take to set up?

Most Channelengine integrations go live in minutes: authenticate Channelengine and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Channelengine data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Channelengine data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.