Flxpoint Help Center
All DocsContact support

Amazon as a Channel

June 26, 2026

Summary

Amazon connects to Flxpoint over Amazon's SP-API using an Amazon Seller Portal (OAuth2) connection. It supports importing and publishing listings, syncing price and quantity, retrieving orders, and pushing tracking back to Amazon. It is one of the most-used sales channels in Flxpoint, and most support issues trace back to mapping misconfigurations or Amazon-side policy constraints rather than platform bugs.

Import Listings
Pulls your existing Amazon listings into Flxpoint via the GET_MERCHANT_LISTINGS_ALL_DATA feed
Publish Listings
Publishes Flxpoint products to Amazon using a mapping template (SKU, Title, Product ID, Quantity, Condition)
Sync & Link Listings
Links imported listings by SKU and syncs Price, Quantity and Handling Time to Amazon
Get Orders
Retrieves Amazon orders and maps totals, shipping addresses and item details into Flxpoint
Sync Orders
Sends shipment tracking and carrier/service back to Amazon as an order fulfillment feed

In Flxpoint go to Channels › + Add Channel, choose Amazon, name it (e.g. "Amazon US Store") and click Get Started. Select Amazon Seller Portal (OAuth2) as the integration type, then enter the values below and click Test Connection & Continue.

Connection NameSetting
A label for this Amazon connection so you can identify it later, e.g. My Amazon US Link.
Free-text; used only inside Flxpoint.
Marketplace IDRequired
The Amazon marketplace this connection targets. Use ATVPDKIKX0DER for Amazon US or A2EUQ1WTGCTBG2 for Amazon Canada.
Must match the region your Seller account sells in.
Refresh TokenRequired
The OAuth2 refresh token for your Amazon Seller account. Generate it in Amazon Seller Central under Developers › Apps & Services. A new token is generated automatically if the previous one expires.
Open Seller Central
Selling Partner IDRequired
Your Amazon Selling Partner (seller) ID, e.g. 123456789012. Find it in Seller Central under Settings › User Permissions › Account Info.
Treat this like a secret key. Canada sellers find it at sellercentral.amazon.ca.
Getting an "Invalid Token" error on Test Connection? Re-check every field one character at a time - the Refresh Token and Selling Partner ID are the most common typos. If the store was disconnected for a while, re-authenticate via the channel connection settings and run Test Connection again before re-enabling any schedules.

Listing linking matches on SKU only - not ASIN or UPC

Import Listings saves UPC and ASIN as reference data, but linking always matches by SKU. If your Amazon SKU differs from your Flxpoint Master SKU, listings will remain stuck in "Ready to Link" regardless of whether an ASIN is present.

Handling Time has conditional send logic

Flxpoint only sends Handling Time (lead_time_to_ship_max_days) to Amazon when your fulfillment channel is non-DEFAULT, or when you explicitly map it in Sync & Link Listings. If neither condition is met, Amazon keeps whatever was last set in Seller Central - which can cause unexpected handling time discrepancies.

Auto-Detect overrides your carrier mapping rules

The Auto-Detect Shipping Carrier from Tracking Number toggle in Sync Orders is ON by default. When enabled, the auto-detected carrier/service overrides any carrier mapping rules you have configured. Turn it OFF if you rely on custom normalization rules.

Bundle tracking holds until all components ship

For bundle orders, Flxpoint sends a single shipment update to Amazon only after all component SKUs are fully shipped. If even one component remains unshipped, no tracking is sent - the bundle is treated as partially shipped and skipped in that sync run.


Pulls your existing Amazon listings into Flxpoint using the GET_MERCHANT_LISTINGS_ALL_DATA feed type. It saves SKU and Title, and also captures UPC and ASIN as reference data on each listing (re-run the job to backfill UPC/ASIN on previously imported listings). Import matches and links Amazon listings to your catalog by SKU only - UPC and ASIN are never used for linking. Your Amazon listing report must include the UPC and ASIN fields for those values to import.
FieldMaps To – Notes
SKUAmazon Product Field: SKU. Identifies the product.
TitleAmazon Product Field: Title. Sets the product name.
Product IDAmazon Product Field: Product ID. Choose the identifier type: ASIN, ISBN, UPC or EAN. ASIN is the most accurate and recommended whenever possible; fall back to UPC only when ASIN is unavailable, and publish in small batches to validate mappings first (e.g. a rule "If no ASIN use UPC").
QuantityAmazon Product Field: Quantity. Sets stock or handling-time options.
Item ConditionAmazon Product Field: Item Condition. Defines the product condition, e.g. New or Used - Like New.
FieldMaps To – Notes
PriceAmazon Product (Price & Quantity) Field: Price. Sets the selling price on Amazon.
QuantityAmazon Product (Price & Quantity) Field: Quantity. Updates available stock; when quantity drops to 0 the product can be marked Out of Stock and hidden on your storefront.
Handling TimeAmazon Product (Price & Quantity) Field: Handling Time. Sent only when your fulfillment channel is non-DEFAULT (Flxpoint passes 1 day if blank) or when you explicitly map it here; otherwise Amazon keeps the last value set in Seller Central.
Amazon FieldMaps To – Notes
Amazon Order IDOrder Field: Reference Number. Links the order in Flxpoint.
Address Line 1Shipping Address Field: Address Line 1. Sets the primary shipping address.
CityShipping Address Field: City. Specifies the shipping city.
Order Total - AmountChannel Invoice Field: Total. Records the order total.
Purchase DateOrder Field: Ordered On. Sets the order date.
Flxpoint FieldMaps To – Notes
Shipment CarrierFulfillment Data - Carrier Name. Use Field to pull the carrier per shipment or Value to set one for all. Note: when Auto-Detect Shipping Carrier from Tracking Number is ON (default), the carrier inferred from the tracking number overrides this mapping.
Shipment Tracking NumberFulfillment Data - Shipper Tracking Number. Must match the carrier's tracking format.
Shipment MethodFulfillment Data - Shipping Method. Set a fixed Value (e.g. Ground) or pull the service from your data.

Listings stuck in "Ready to Link" or "Linking" status and never complete
Linking is driven entirely by SKU match. Confirm the Amazon SKU on the imported listing exactly matches the Master SKU in your Flxpoint catalog (case-sensitive). If they differ, update the Master SKU to match or link the listing manually. Having an ASIN present does not trigger auto-linking.
Qty and pricing not updating on Amazon even though the sync job runs
Verify the listing is fully linked (not just imported). Open the Sync & Link Listings mapping template and confirm Quantity and Price are mapped to the correct Flxpoint fields - unmapped fields are silently skipped. If the job reports success but Amazon shows no change, check the Amazon feed submission logs for item-level errors.
"Sync Errors: Failure to map product to sync" on thousands of SKUs
Flxpoint cannot find a matching catalog product for the listing at sync time - usually caused by a Master SKU change after the listing was linked. Re-link the affected listings with the Sync & Link Listings job after confirming SKUs are consistent, then re-run the sync.
Handling time on Amazon does not match what is configured in Flxpoint
Handling Time is only sent when the fulfillment channel is non-DEFAULT or when you explicitly map it in the Sync & Link Listings template. If neither applies, Flxpoint omits the field and Amazon keeps whatever was previously set in Seller Central. Add a Handling Time mapping in the template to control it from Flxpoint.
Tracking not sending to Amazon / Amazon metrics impacted by missing tracking
Confirm the Sync Orders job is scheduled and that shipments in Flxpoint have a tracking number assigned. If Auto-Detect Shipping Carrier from Tracking Number is ON, verify the detected carrier is one Amazon accepts. For bundles, tracking will not send until all component SKUs are fully shipped. Check shipment-level sync errors for item-specific failure reasons.
Publication errors due to lack of sales authorization or GTIN exemption issues
Brand-restriction and GTIN-exemption failures are Amazon-side policy blocks, not Flxpoint errors. Confirm in Amazon Seller Central that your account has the required brand approval or GTIN exemption for each affected ASIN/category. Once Amazon grants authorization, re-run the Publish Listings job.
Publish Error: Product ID is required when Product ID Type is provided
Amazon requires an ASIN or UPC to complete the publish operation - if neither is found, this error is thrown. Map both Product ID and Product ID Type to the same identifier (e.g. ASIN), or add a rule in the Publish Listings mapping template to use UPC when ASIN is blank (or ASIN when UPC is blank).
"Failed to run Sync Listings for this channel" after reconnecting the Amazon store
After reconnecting, re-run the Import Listings job and then the Sync & Link Listings job before attempting to sync. If the channel was disconnected for a while, the OAuth token may also need refreshing - re-authenticate via the channel connection settings and run Test Connection before re-enabling the schedule.
Amazon order failing to import with a "Deliver By Date" error
Some Amazon orders include a "Deliver By Date" field that Flxpoint does not automatically map into the standard order fields, causing import failures. Open the Get Orders mapping template and add a mapping for the Deliver By Date field to a custom field or order note field, then re-run Get Orders.
Publish Error: "Product ID is required when Product ID Type is provided"
When publishing listings on Amazon, an ASIN or UPC is required to complete the operation. If neither is found, Amazon throws this error. To push the SKU via ASIN, a rule must be created in the Publish Listings mapping template for Product ID and Product ID Type: either map both fields with ASIN, or create a rule to use UPC if ASIN is blank (or ASIN if UPC is blank). The field still has to be mapped for the rule to apply.

How does Flxpoint link my existing Amazon listings to my catalog?
Flxpoint links Amazon listings to catalog products by matching the Amazon SKU to your Master SKU. Run the Import Listings job first to pull your Amazon listings in, then run the Sync & Link Listings job - Flxpoint auto-links where SKUs match. Listings that cannot be matched stay in "Ready to Link" status and must be linked manually.
Does Flxpoint sync only FBM orders, or does it also import FBA orders?
By default, the Amazon Get Orders integration retrieves all orders regardless of fulfillment type - there is no native FBM-only filter at the channel level. If you only want FBM orders to flow into Flxpoint for routing, use order routing rules or workflow conditions to filter out FBA orders from processing.
Why isn't my price rule applying to Amazon listings even though it tests correctly?
Price rules that pass the in-app test but fail on actual listings are almost always a mapping issue - verify that the Price field in your Sync & Link Listings mapping template is mapped to the field your rule outputs to, and that the rule references the correct custom field or formula. If the listing is unlinked, price syncs will not run at all.
What marketplace IDs do I use for Amazon US and Canada?
Use ATVPDKIKX0DER for Amazon US and A2EUQ1WTGCTBG2 for Amazon Canada. Your Selling Partner ID is found in Seller Central under Settings › User Permissions › Account Info.
Can I use ASIN to publish new listings instead of UPC?
Yes - ASIN is the preferred Product ID type for publishing and is more accurate than UPC. If ASIN is unavailable, you can use UPC as a fallback. Set a conditional rule in your Publish Listings mapping template to use UPC when ASIN is empty, and publish in smaller batches when using UPC to validate results before scaling.
How do I stop Flxpoint from pushing tracking for Amazon Buy Shipping orders?
Amazon Buy Shipping orders are already marked as shipped by Amazon, so when Flxpoint attempts to push tracking, Amazon rejects it with error 30721. Clear the sync error on the affected shipment in Flxpoint and re-run the Sync Orders job - Flxpoint will recognize the order is already fulfilled and skip re-attempting the push.
© 2026 Flxpoint. All rights reserved.