Channel Advisor as a Channel

July 20, 2026

Summary

ChannelAdvisor (Rithum) connects to Flxpoint as a channel, supporting Link and Sync Listings plus Get and Sync Orders. Publishing new listings from Flxpoint is not supported, so items must already exist on ChannelAdvisor before they can be linked. Shipping Mappings must be configured before Get Orders will import orders correctly.

What this integration does

Link Listings

Matches Flxpoint listings to existing ChannelAdvisor items via SKU and other IDs.

Sync Listings

Pushes price and quantity updates to already-linked ChannelAdvisor listings.

Get Orders

Imports ChannelAdvisor orders with items, addresses, invoice, and bundle SKUs.

Sync Orders

Sends shipment SKU, quantity, and order item ID back to ChannelAdvisor.

How to connect - credentials you need

Add a ChannelAdvisor channel, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter your Access Token, Refresh Token, and Profile ID, then Test Connection → Save Connection.

Access TokenRequired

OAuth access token issued for your ChannelAdvisor account.

Refresh TokenRequired

OAuth refresh token used to keep the connection authorized.

Profile IDRequired

Your ChannelAdvisor Profile ID.

Configure Shipping Mappings before running Get Orders — the ChannelAdvisor Shipping Method name (Fulfil > Settings > Mappings) must match the Channel Shipping Text in Flxpoint exactly, or orders will not import.

Important - read before configuring

Publishing is not supported

Flxpoint cannot publish new listings to ChannelAdvisor. Create the item on ChannelAdvisor first, then use Link Listings to connect it in Flxpoint.

Shipping Mappings required before Get Orders

The ChannelAdvisor Shipping Method name (Fulfil > Settings > Mappings) must match the Channel Shipping Text in Flxpoint exactly, or orders will not import.

Broken Link on deleted products

Deleting a product on the store without delisting it through Flxpoint leaves it Linked until the next sync, then flips it to Broken Link. Unlink and relink the item to fix it.

Bundle and order-field mapping

BundleComponents is an array; map it carefully into custom order fields. Flxpoint uses the Sku field when saving order item data, and fields like Adjustments and Promotions appear only when the order contains them.

Operations - fields to know

Link ListingsSync ListingsGet OrdersSync Orders

Field	Maps To — Notes
Sku	→ Listing Link → SKU. Primary identifier used to match the ChannelAdvisor item.
Upc / Ean / Asin / Mpn	→ Listing Link → Identifiers. Additional identifiers used for matching when SKU alone isn't enough.
ParentProductId / IsParent	→ Listing Link → Parent/Variant Relationship. Associates child variants to their parent listing.

Field mapping for this operation is configured with Flxpoint Support.

Field	Maps To — Notes
ProductId	→ Order Item → External Listing ID. Links the order line to the matched listing.
Id (order item)	→ Order Item → External Order Item ID. ChannelAdvisor's internal line-item ID.
BundleComponents	→ Order Item → Bundle Components SKU. An array — map carefully into custom order fields.
FulfillmentItems	→ Order Item → Fulfillment Items SKU. SKUs tied to the order's fulfillment record.
Id (order)	→ Order Invoice → Invoice Number. Uses the ChannelAdvisor order ID as the invoice number.

Field	Maps To — Notes
ExternalOrderItemId	→ Ship Item → Order Item ID. Required. Associates the shipped line to the ChannelAdvisor order item.
Sku	→ Ship Item → SKU. Item SKU sent with the shipment.
Quantity	→ Ship Item → Quantity. Required. Units shipped for the line.
Distribution Center ID	→ Shipment → Distribution Center ID. Configured per connection; sent with every shipment.

Common issues

404 Not Found: [no body] when syncing tracking to ChannelAdvisor

Reported on Sync Orders when pushing a shipment back to ChannelAdvisor (for example, Failed to sync Shipment # ... to channel: 404 Not Found: [no body]). This has been flagged as a possible integration issue and is under investigation; if you hit it, capture the order and shipment numbers and raise a ticket so it can be traced.

Failed to fetch orders during Get Orders for Channel ID

Reported intermittently on the first run or on scheduled runs, then succeeding on a manual re-run. If a scheduled Get Orders fails to fetch, re-running it manually usually completes; if it fails consistently rather than intermittently, raise a ticket.

FAQs

My orders are not importing. What should I do?▸

Confirm your Shipping Mappings are configured first, since Get Orders will not import without them. Then check that the store order status matches your Get Orders configuration, and that the order is not older than the Get Orders Created within the last X Days limit.

Back to Marketplace & eCommerce Integrations