Channel Engine as a Channel
July 2, 2026
Summary
ChannelEngine is a multi-marketplace aggregator that sits between Flxpoint and the marketplaces (such as Bol.com, Zalando, and others) where your products are listed. This integration publishes new products to ChannelEngine, syncs price and quantity, imports orders, and syncs shipment tracking. Because ChannelEngine is a hub, several operations native to direct marketplace channels - Import Listings, hiding listings, and shipping passthrough - are not supported here.
What this integration does
Publish Listings
Creates new products in ChannelEngine from your Flxpoint catalog
Sync & Link Listings
Pushes real-time price and quantity updates to your existing ChannelEngine listings
Get Orders
Retrieves new and updated orders from ChannelEngine into Flxpoint
Sync Orders
Sends shipment and tracking updates back to ChannelEngine
How to connect - credentials you need
In Flxpoint go to Channels → + Add Channel, search for and select ChannelEngine, and complete the wizard (channel name and which operations to run). Then click to create a ChannelEngine Connection, enter the values below, and click Test Connection → Save Connection.
Connection NameRequired
A descriptive label for this connection inside Flxpoint.
Any name that helps you identify the connection.
API KeyRequired
Your ChannelEngine Merchant API key. In ChannelEngine, go to Settings → Merchant API keys to retrieve it.
Found in ChannelEngine under Settings → Merchant API keys.
Server URLRequired
Your ChannelEngine environment's API URL, copied from your environment settings - typically in the form
Copy the API URL from your ChannelEngine environment settings.
https://[yoursubdomain].channelengine.net/api.Can't find your credentials? In ChannelEngine both live under Settings - the key under Merchant API keys and the Server URL in your environment settings. If Test Connection fails right after a ChannelEngine maintenance window, wait for the window to close and retry.
Important - read before configuring
Import Listings is not supported
You cannot pull existing ChannelEngine listings back into Flxpoint - the integration is publish-out only, with products flowing from Flxpoint to ChannelEngine. Any products you need in Flxpoint must be created there manually or via import before they can be synced.
Publish always creates a new product - overwriting is not supported
Each Publish Listings run creates a new product via the /api/v2/products endpoint; there is no overwrite mode. To update an existing product's price/quantity use Sync & Link Listings; content changes (title, images, description) must be made directly in ChannelEngine.
Hiding and delisting are not supported
Flxpoint cannot hide or delist individual ChannelEngine listings. If inventory drops to zero the quantity syncs to 0, but the listing is not removed or suppressed - removal must be done directly within your ChannelEngine account.
Categories must use ChannelEngine's hierarchy format
When publishing, categories must be sent in hierarchy form - for example MainCategory >> Category >> Subcategory. A flat or incorrectly formatted category string will cause the product to fail publish validation in ChannelEngine.
Mapping - fields to know
Creates new products in ChannelEngine from your Flxpoint catalog via the
/api/v2/products endpoint. Products are built top-down - grandparent first, then parent, then variant children - and the Parent SKU is set as the ChannelEngine MerchantProductNo. Multiple images per product are supported. Categories must be sent in hierarchy form (e.g. MainCategory >> Category >> Subcategory). Overwriting is not supported - each publish call creates a new listing.Updates price and quantity on your existing ChannelEngine listings in real time via the
/api/v2/offer endpoint, matching on MerchantProductNo. Your Flxpoint SKUs must match the ChannelEngine MerchantProductNo for updates to land. Hiding/delisting, Inventory Tracking Configs and Custom Fields are not supported.Retrieves new and updated orders via the
/api/v2/orders endpoint. Select one or more status values - New, InProgress, Shipped - to control what's pulled; Flxpoint can acknowledge orders in New status. Multi-currency orders are supported (add rules to convert or tag as needed). Payment status is not differentiated, and shipping selection, weight and dimensions are not returned in the order data.Sends shipment and tracking updates to ChannelEngine via the
/api/v2/shipments endpoint; on a successful response the order is marked synced. Partial shipments are supported. Manually added order items do not sync back, and Flxpoint does not push post-shipment status changes beyond the shipment info.Common issues
Publish job completes but products do not appear in ChannelEngine
The most common cause is an incorrectly formatted Category - ChannelEngine requires full hierarchy form (
MainCategory >> Category >> Subcategory), and a flat value or missing level fails silently. Verify the category string in your Publish Listings mapping template matches this format, and confirm the Server URL points to the correct ChannelEngine environment.Price and quantity not updating on ChannelEngine after sync runs
Sync & Link Listings matches on
MerchantProductNo via /api/v2/offer. If your Flxpoint SKU does not exactly match the ChannelEngine MerchantProductNo, the offer update won't find the product. Check the Linking Priority in your sync settings and run Link Listings before Sync Listings if the items aren't linked yet.Orders not importing from ChannelEngine
Confirm your Get Orders status filters include at least New. Payment status is not differentiated, so you can't filter by payment state. Verify the Get Orders mapping template is saved and the connection test passes. If ChannelEngine was recently down for scheduled maintenance, re-run Get Orders manually once service resumes to catch any orders from that window.
Manually added order items are not syncing back to ChannelEngine
This is a known limitation: items added to an order in Flxpoint after it was imported will not sync back via Sync Orders. Only the original ChannelEngine line items can have shipment data pushed back - any manually added items must be updated in ChannelEngine directly.
Connection test fails after ChannelEngine scheduled maintenance
ChannelEngine periodically schedules maintenance windows during which its API and web app are temporarily unavailable, and all Flxpoint jobs to ChannelEngine fail during them. No data is lost. Wait for the window to close, run Test Connection to confirm the link is restored, then re-enable scheduled jobs.
Shipping method or weight/dimensions missing from imported orders
These are known integration limitations: shipping selection (service name/text) is not passed back to Flxpoint, and weight and dimensions are not included in the order data ChannelEngine provides. If your fulfillment routing depends on shipping method or dimensions, set those values via order routing rules in Flxpoint rather than expecting them from the ChannelEngine order.
FAQs
Where do I find my ChannelEngine API key and Server URL?▸
Log into ChannelEngine and go to Settings. The API key is listed under Merchant API keys. The Server URL is your environment's API URL, typically in the format
https://[yoursubdomain].channelengine.net/api. Copy both values and paste them into Flxpoint when creating the ChannelEngine connection.How does Flxpoint match listings to ChannelEngine products for sync?▸
Flxpoint matches on ChannelEngine's MerchantProductNo, which is set to the Flxpoint Parent SKU during publish. For sync to work, the SKU in your Flxpoint listing must exactly match the product's
MerchantProductNo in ChannelEngine - any mismatch will cause updates to fail silently or target the wrong product.Does the integration support partial shipments?▸
Yes - Sync Orders supports partial shipments. ChannelEngine accepts shipment updates per line item, so Flxpoint can push tracking for individual items as they ship without waiting for the full order to be fulfilled. Each shipment must use a unique tracking number.
Are multi-currency orders supported?▸
Yes - multi-currency orders are supported in Get Orders. Because ChannelEngine connects to marketplaces across multiple countries, orders may arrive in different currencies. Use mapping rules in the Get Orders template to convert or tag orders by currency as needed for your downstream processing.
What order statuses can I filter when importing orders?▸
Get Orders can filter by multiple ChannelEngine status values at once - the main ones are New, InProgress, and Shipped. Select at minimum New to capture incoming orders that need fulfillment. Flxpoint can also acknowledge orders in New status after download to keep state aligned between the two systems.