Channel Advisor as a Channel
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.
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.
| Field | What to enter |
|---|---|
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. |
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.
Matches Flxpoint listings to existing ChannelAdvisor items via SKU and other IDs.
| 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. |
Pushes price and quantity updates to already-linked ChannelAdvisor listings.
Field mapping for this operation is configured with Flxpoint Support.
Imports ChannelAdvisor orders with items, addresses, invoice, and bundle SKUs.
| 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. |
Sends shipment SKU, quantity, and order item ID back to ChannelAdvisor.
| 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. |
404 Not Found: [no body] when syncing tracking to ChannelAdvisor
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
Promo amounts or custom order fields not importing?
My orders are not importing. What should I do?
Get Orders Created within the last X Days limit.What it does
When importing orders from ChannelAdvisor, specific financial data like promotion amounts or adjustments are often stored in nested API structures. By mapping these to Flxpoint order custom fields, you can ensure that discounts and promotional values are preserved for your accounting and reporting workflows.
Mapping promo amounts
To capture promotional data, you must configure your ChannelAdvisor Get Orders mapping template to target the correct data fields from the ChannelAdvisor API response.
Navigate to your ChannelAdvisor Sales Channel settings.
Open the Mapping Templates for the Get Orders integration.
Locate the Order Custom Fields section in the template.
Map the Flxpoint field (e.g., Promo Amount) to the corresponding ChannelAdvisor attribute, typically found within the
PromotionsorAdjustmentsdata objects.Save the template and run a manual sync to verify the data appears on new orders.
Troubleshooting missing data
Why is the promo amount not saving?
If an order imports but the custom field remains empty despite a promotion existing in ChannelAdvisor, check the following:
Path Validation: Ensure the mapping path correctly points to the specific promotion value rather than a generic header.
Data Type Mismatch: Verify that the Flxpoint custom field is configured to accept the data type (e.g., Decimal or String) being sent by ChannelAdvisor.
Sync Timing: If a promotion is added to an order after the initial import, Flxpoint may not update the custom field unless the order is re-synced.
Note: Mapping changes only apply to orders imported after the change is saved. Existing orders will not retroactively update their custom fields unless you manually trigger a re-import for those specific IDs.