Amazon serves as a robust channel integration within Flxpoint, empowering businesses to efficiently manage their product listings, inventory, and orders on the global Amazon Marketplace. This integration delivers real-time synchronization of product data, advanced pricing controls, and streamlined order fulfillment, ensuring that your operations remain accurate, competitive, and fully aligned with Amazon’s dynamic marketplace standards.
How to Connect
📋 Phase 1: Initial Channel Setup
+
Access the Channels Section
Log into Flxpoint (flxpoint.com) and click Channels in the left menu.
Create a New Channel
Click + Add Channel to start.
Tip: Have your Amazon credentials ready!
Select Channel Type & Name
Select Amazon, name it (e.g., "Amazon US Store"), and click Save.
Start the Integration Process
Click Get Started on the "No integrations created yet" message.
🔐 Phase 2: Authentication & Connection
+
Select the Integration Type
Choose Amazon Seller Portal (OAuth2) in the wizard.
Clarification: OAuth2 is a secure connection method—no tech skills needed!
Connect Your Account
Enter these details:
- Connection Name - E.g., "My Amazon US Link".
- Marketplace ID - Use "ATVPDKIKX0DER" (US) or "A2EUQ1WTGCTBG2" (CA).
- Refresh Token - Get from Amazon Seller Central > Developers > Apps & Services.
- Selling Partner ID - Find in Seller Central > Settings > User Permissions > Account Info.
Important Note: Keep this ID safe—it’s like your account’s secret key. Get it from sellercentral.amazon.com or sellercentral.amazon.ca > Settings > User Permissions > Account Info (e.g., 123456789012).
Tip: Double-check each field to avoid errors.
Verify Connection
Click Test Connection & Continue. Fix any errors (e.g., "Invalid Token") by rechecking credentials.
Tip: Take your time here for a smooth setup!
🔄 Phase 3: Configuration & Mapping
+
Set Up SKU Mapping
Map Flxpoint SKUs (e.g., "WIDGET-123") to Amazon SKUs (e.g., "AMZ-WIDGET-123").
- Match SKUs carefully.
- Add a prefix like "AMZ-" if needed.
Tip: Check Amazon Inventory > Manage Inventory for SKUs.
Configure Integration Settings
Enable:
- Inventory & Pricing: Sync stock and prices.
- Order Sync: Pull orders (e.g., every 15 minutes).
- Shipment Tracking: Update tracking info.
Tip: Start with one feature and add more as needed.
Complete Setup
Review and click Save.
Next Steps: Test a product sync and check Amazon.
Listing Operations
Import Listings
Supported | Amazon Channel - Import Listings
Introduction to Amazon Channel - Import Listings Integration
The Amazon Channel - Import Listings integration helps you bring your Amazon product listings into Flxpoint seamlessly. Using the GET_MERCHANT_LISTINGS_ALL_DATA feed type, it imports data like SKU and Title, making it easy to manage your inventory. A new token is generated if the previous one expires, ensuring a smooth connection. This guide will walk you through connecting to Amazon, configuring settings, and saving the essential details—let’s get started!
The Amazon Channel - Import Listings integration connects your Flxpoint system to Amazon to:
- Import product listings from Amazon using the GET_MERCHANT_LISTINGS_ALL_DATA feed type.
- Save key data like SKU and Title for easy inventory management in Flxpoint.
- Automate the import process with a new token generated if the previous one expires, keeping your connection secure.
This integration follows a simple process to bring Amazon listings into Flxpoint:
- Data Retrieval: Pulls listing data from Amazon using the GET_MERCHANT_LISTINGS_ALL_DATA feed type, including SKU and Title.
- Data Import: Saves the retrieved data (SKU and Title) into Flxpoint for inventory management.
- Token Management: Generates a new token if the previous one expires to maintain a secure connection.
What Does the Imported Data Look Like?
Here’s a sample of the data imported from Amazon:
{
"Listings": [
{
"SKU": "AMZ12345",
"Title": "Blue Widget"
},
{
"SKU": "AMZ67890",
"Title": "Red Gadget"
}
]
}
"Listings": [
{
"SKU": "AMZ12345",
"Title": "Blue Widget"
},
{
"SKU": "AMZ67890",
"Title": "Red Gadget"
}
]
}
Understanding the Data: The data includes SKU (e.g., "AMZ12345") and Title (e.g., "Blue Widget"), which are saved in Flxpoint for managing your listings. Other fields are ignored to keep it simple!
Let’s set up the integration with these key settings:
-
Connection Settings:
- Connection Name: Name it something like "AmazonImport2025".
- Amazon OAuth2: Use the Amazon Seller Portal (OAuth2) credentials to connect.
- Feed Type: Set to GET_MERCHANT_LISTINGS_ALL_DATA to import all listing data.
- Data to Save: Configure to save only SKU and Title fields from the imported data.
What’s the Feed Type? The GET_MERCHANT_LISTINGS_ALL_DATA feed type pulls all your Amazon listings, and we filter it to save just SKU and Title for simplicity.
New Token: If your token expires, a new one is automatically generated to keep the integration running smoothly.
New Token: If your token expires, a new one is automatically generated to keep the integration running smoothly.
Follow these steps to set up the Amazon Channel - Import Listings integration:
- 1 Connect to Amazon: Enter your Amazon Seller Portal (OAuth2) credentials and click "Save and Proceed" to establish the connection.
- 2 Configure Settings: Set the feed type to GET_MERCHANT_LISTINGS_ALL_DATA and save only SKU and Title data. Click "Save and Complete" when done.
- 3 Run the Integration: Click "Run Integration" to import your listings manually, or schedule it for automatic updates.
The interface for setting up the Amazon Channel - Import Listings integration is user-friendly. Here’s what you’ll see:
- Integration Title: Labeled as "Amazon Channel - Import Listings" at the top.
- Connection Section: Includes fields for Amazon Seller Portal (OAuth2) credentials.
- Settings Section: Allows you to set the feed type and data to save (SKU and Title).
- Action Buttons: Features "Save and Proceed" and "Save and Complete" to move through the setup.
Next Steps
After setup, run the integration to start importing your Amazon listings!
Here are some important points about this integration:
- Current Date and Time: As of 02:23 PM -04 on Monday, June 23, 2025, this integration is ready to use.
- Feed Type: Uses GET_MERCHANT_LISTINGS_ALL_DATA to import all listings.
- Data Saved: Only SKU and Title are saved in Flxpoint.
Pro Tip: Double-check your Amazon credentials to ensure a smooth connection, especially if a new token is generated!
Conclusion
With the Amazon Channel - Import Listings integration, you can easily bring your Amazon listings into Flxpoint, saving time and effort. By focusing on SKU and Title and using a new token when needed, you’ll have a streamlined inventory management process!
Publish Listings
Supported | Amazon Channel - Publish Listings
Introduction to Amazon Channel - Publish Listings Integration
The Amazon Channel - Publish Listings integration lets you publish your Flxpoint product listings to Amazon effortlessly. Using a flexible mapping template, you can map fields like SKU, Title, and more to Amazon’s format. This guide will walk you through setup, mapping, and management—let’s get started!
The Amazon Channel - Publish Listings integration connects your Flxpoint system to Amazon to:
- Publish product listings from Flxpoint to Amazon marketplaces (e.g., AMAZON_NA, AMAZON_EU, AMAZON_JP).
- Map Flxpoint fields (like SKU, Title, Description) to Amazon product fields using a customizable template.
This integration follows a simple process to publish listings to Amazon:
- Data Mapping: Maps Flxpoint fields (e.g., SKU, Title) to Amazon product fields using the mapping template.
- Rule Application: Applies custom rules (e.g., "If no ASIN use UPC") to handle special cases.
- Publishing: Sends the mapped data to Amazon.
Sample Mapped Data
Here’s an example of mapped data:
{
"SKU": "FLX12345",
"Title": "Blue Widget",
"Description": "High-quality blue widget",
"ProductIDType": "ASIN",
"ProductID": "B07X4K9Y9Z",
}
"SKU": "FLX12345",
"Title": "Blue Widget",
"Description": "High-quality blue widget",
"ProductIDType": "ASIN",
"ProductID": "B07X4K9Y9Z",
}
Understanding the Data: SKU and Title are mapped, with "ProductIDType" set to "ASIN" as the preferred identifier. If ASIN is unavailable, UPC (e.g., "123456789012") can be used instead.
Configure the integration with these options:
-
Connection Settings:
- Amazon Marketplace: Choose from DEFAULT, AMAZON_NA, AMAZON_EU, or AMAZON_JP.
- OAuth2 Credentials: Use your Amazon Seller Portal credentials.
- Fulfillment Center ID: Set a value or map a field (optional).
Marketplace Selection: Pick the right marketplace (e.g., AMAZON_NA) to target your audience.
Follow these steps to publish your listings:
- 1 Connect to Amazon: Enter your OAuth2 credentials, select your marketplace, and save.
- 2 Configure Mapping: Use the Mapping Template to map fields (see below).
- 3 Apply Rules: Set up rules (e.g., "If no ASIN use UPC") and save.
- 4 Publish Listings: Click "Save" to publish or use "Duplicate" to test.
The Mapping Template defines how Flxpoint fields map to Amazon fields. Here’s the details:
Mapping Fields
Map fields with options like "Field", "Value", or "Rules". Key fields include:
| Field | Maps To | Options | Purpose |
|---|---|---|---|
| SKU | Amazon Product Field: SKU | Don't Map, Set To Empty, Field, Value, Mapping Set, Rules | Identifies the product |
| Title | Amazon Product Field: Title | Field, Value, Mapping Set, Rules | Sets the product name |
| Product ID | Amazon Product Field: Product ID | Don't Map, Set To Empty, Field, Option (ASIN, ISBN, UPC, EAN), Rules | Sets the product identifier; ASIN is the most accurate identifier and recommended whenever possible. If ASINs are unavailable, UPCs may be used instead, but publish in batches and validate mappings to avoid errors. |
| Quantity | Amazon Product Field: Quantity | Don't Map, Set To Empty, Field, Option (3-5 Business Days, 4-14 Business Days), Rules | Sets stock or handling time |
| Item Condition | Amazon Product Field: Item Condition | Don't Map, Set To Empty, Field, Value, Mapping Set, Rules (e.g., New, Used - Like New) | Defines product condition |
Try This: Map "SKU" to "Amazon Product Field: SKU" with a Field option, or set "Item Condition" to "New" with a Value. For "Product ID", prioritize ASIN (e.g., "B07X4K9Y9Z") or use UPC (e.g., "123456789012") if ASIN is missing.
Rules add logic to your mappings. Here’s an example:
Configured Rules
-
If no ASIN use UPC:
- Type: Conditional
- Description: Uses UPC if ASIN is missing.
- Logic: 1 condition, 1 action.
- Example: Sets Product ID to "123456789012" if ASIN is empty.
Why Use Rules? This ensures a valid Product ID, which is key for publishing! ASIN is preferred, but UPC serves as a fallback when necessary.
Keep these in mind:
- Current Date and Time: As of 10:31 PM -04 on Monday, June 23, 2025, this integration is ready.
Pro Tip: Use "Duplicate" to test mappings before publishing!
Conclusion
The Amazon Channel - Publish Listings integration makes publishing to Amazon a breeze. With mapping and rules, you’ll have everything you need to succeed—enjoy the process!
Sync & Link Listings
Supported | Amazon Channel - Sync and Link Listings
Introduction to Amazon Channel - Sync and Link Listings Integration
The Amazon Channel - Sync and Link Listings integration keeps your Flxpoint listings in sync with Amazon, focusing on price and quantity updates. Using a mapping template, you can link fields like Quantity and Price to Amazon’s Product (Price & Quantity) fields. If a product is marked Out of Stock (OOS), it can be hidden on your storefront. This guide will walk you through the setup—let’s get syncing!
The Amazon Channel - Sync and Link Listings integration connects your Flxpoint system to Amazon to:
- Sync price and quantity data from Flxpoint to Amazon marketplaces (e.g., AMAZON_NA, AMAZON_EU, AMAZON_JP).
- Link Flxpoint fields (like Quantity, Price) to Amazon’s Product (Price & Quantity) fields.
- Hide products marked OOS on your storefront for a cleaner user experience.
This integration follows a simple process to sync and link listings:
- Data Mapping: Maps Flxpoint fields (e.g., Quantity, Price) to Amazon’s Product (Price & Quantity) fields.
- Data Sync: Updates Amazon with the latest price and quantity values from Flxpoint.
- OOS Handling: Marks products as OOS and hides them on your storefront if stock is zero.
Sample Synced Data
Here’s an example of synced data:
{
"SKU": "FLX12345",
"Price": 29.99,
"Quantity": 5,
"Status": "Active"
}
"SKU": "FLX12345",
"Price": 29.99,
"Quantity": 5,
"Status": "Active"
}
Understanding the Data: If Quantity drops to 0, the product is marked OOS and hidden on your storefront.
Configure the integration with these settings:
-
Connection Settings:
- Amazon Marketplace: Choose from DEFAULT, AMAZON_NA, AMAZON_EU, or AMAZON_JP.
- OAuth2 Credentials: Use your Amazon Seller Portal credentials.
- Price and Quantity: Map fields like Price and Quantity to sync with Amazon.
- OOS Handling: Enable hiding products marked OOS on your storefront.
Marketplace Selection: Pick the right marketplace (e.g., AMAZON_NA) for your region.
Hiding OOS: When a product is OOS, it’s hidden from your storefront to avoid confusion.
Hiding OOS: When a product is OOS, it’s hidden from your storefront to avoid confusion.
Follow these steps to sync and link your listings:
- 1 Connect to Amazon: Enter your OAuth2 credentials, select your marketplace, and save.
- 2 Configure Mapping: Use the Mapping Template to map Price and Quantity (see below).
- 3 Enable OOS Hiding: Turn on the option to hide OOS products on your storefront.
- 4 Sync Listings: Click "Save" to sync or use "Duplicate" to test.
The Mapping Template defines how Flxpoint fields sync with Amazon’s Product (Price & Quantity) fields. Here’s the details:
Mapping Fields
Map fields with options like "Field", "Value", or "Rules". Key fields include:
| Field | Maps To | Options | Purpose |
|---|---|---|---|
| Price | Amazon Product (Price & Quantity) Field: Price | Don't Map, Set To Empty, Field, Value, Rules | Sets the selling price on Amazon |
| Quantity | Amazon Product (Price & Quantity) Field: Quantity | Field, Value, Rules | Updates available stock |
| Handling Time | Amazon Product (Price & Quantity) Field: Handling Time | Don't Map, Set To Empty, Field, Value, Rules | Sets the processing time |
Try This: Map "Quantity" to update stock, or set a fixed "Handling Time" value like "3-5 Business Days".
Handling Time (SKU‑Level)
Flxpoint now sends
lead_time_to_ship_max_days only when one of two conditions is true:
-
Your fulfillment channel ≠
DEFAULT.
Amazon’s schema requires a value in this case, so Flxpoint passes1day if the field is blank. -
You explicitly map Handling Time in the template (even if your channel is
DEFAULT).
Example PATCH body (unmapped Handling Time,
DEFAULT channel)
{
"header": { … },
"messages": [ {
"sku": "ABC123",
"operationType": "PATCH",
"productType": "PRODUCT",
"patches": [ {
"path": "/attributes/fulfillment_availability",
"value": [ {
"fulfillment_channel_code": "DEFAULT",
"quantity": 25
} ]
} ]
} ]
}
"header": { … },
"messages": [ {
"sku": "ABC123",
"operationType": "PATCH",
"productType": "PRODUCT",
"patches": [ {
"path": "/attributes/fulfillment_availability",
"value": [ {
"fulfillment_channel_code": "DEFAULT",
"quantity": 25
} ]
} ]
} ]
}
Tip: Map Handling Time to a fixed value or attribute whenever you need to control SLAs; otherwise Amazon keeps whatever you last saved in Seller Central.
Keep these in mind:
- Current Date and Time: As of 02:42 PM ‑04 on Monday, June 23, 2025, this integration is ready.
- OOS Behavior: Products marked OOS are hidden on your storefront.
Pro Tip: Test your sync with "Duplicate" to ensure prices and quantities update correctly before saving!
Invalid Product Type Error
Error returned: “The Amazon product type specified is invalid or not supported.”
What Flxpoint does when you link products:
What Flxpoint does when you link products:
- Reads and stores the product type from Amazon.
- If unavailable, falls back to
PRODUCT.
- Confirm the product‑type value in Seller Central.
- Verify it with Amazon’s Product Type Definitions API (search by keyword).
- Update the listing with a supported value and re‑sync.
Conclusion
The Amazon Channel - Sync and Link Listings integration keeps your prices and quantities in sync with Amazon effortlessly. With OOS products hidden from your storefront, you’ll maintain a polished online presence—happy syncing!
Order Operations
Get Orders
Supported | Amazon Channel - Get Orders
Introduction to Amazon Channel - Get Orders Integration
The Amazon Channel - Get Orders integration allows you to retrieve orders from Amazon and map them into Flxpoint. With a flexible mapping template, you can pull details like order totals, shipping addresses, and item information. This guide will walk you through the setup process—let’s get those orders flowing!
The Amazon Channel - Get Orders integration connects your Flxpoint system to Amazon to:
- Retrieve order data from Amazon marketplaces (e.g., AMAZON_NA, AMAZON_EU, AMAZON_JP).
- Map Amazon order fields (like Amazon Order ID, Address Line 1) to Flxpoint fields.
- Import billing, shipping, and invoice details for seamless order management.
This integration follows a clear process to get orders from Amazon:
- Data Retrieval: Pulls order data from Amazon, including Amazon Order ID, shipping addresses, and item details.
- Data Mapping: Maps Amazon fields to Flxpoint fields using the mapping template.
- Data Import: Imports the mapped data into Flxpoint for processing.
Sample Retrieved Data
Here’s an example of order data from Amazon:
{
"AmazonOrderID": "AMZ202306231234",
"OrderTotal": {
"Amount": 49.99,
"CurrencyCode": "USD"
},
"ShippingAddress": {
"AddressLine1": "123 Main St",
"City": "Austin",
"PostalCode": "78701"
},
"OrderItem": {
"SellerSKU": "FLX12345",
"QuantityOrdered": 1
}
}
"AmazonOrderID": "AMZ202306231234",
"OrderTotal": {
"Amount": 49.99,
"CurrencyCode": "USD"
},
"ShippingAddress": {
"AddressLine1": "123 Main St",
"City": "Austin",
"PostalCode": "78701"
},
"OrderItem": {
"SellerSKU": "FLX12345",
"QuantityOrdered": 1
}
}
Understanding the Data: The Amazon Order ID "AMZ202306231234" links the order, while shipping details and item quantities are mapped to Flxpoint fields.
Set up the integration with these options:
-
Connection Settings:
- Amazon Marketplace: Choose from DEFAULT, AMAZON_NA, AMAZON_EU, or AMAZON_JP.
- OAuth2 Credentials: Use your Amazon Seller Portal credentials.
- Billing and Shipping Mapping: Map fields like Address Line 1 and City to Flxpoint billing or shipping addresses.
- Invoice Mapping: Optionally map invoice fields like Total to Flxpoint order fields.
Marketplace Selection: Select the marketplace (e.g., AMAZON_NA) to fetch orders from the right region.
Address Mapping: Ensure shipping addresses are correctly mapped for accurate delivery.
Address Mapping: Ensure shipping addresses are correctly mapped for accurate delivery.
Follow these steps to get orders from Amazon:
- 1 Connect to Amazon: Enter your OAuth2 credentials, select your marketplace, and save.
- 2 Configure Mapping: Use the Mapping Template to map fields like Amazon Order ID and Address Line 1 (see below).
- 3 Run the Integration: Click "Save" to fetch orders or use "Duplicate" to test.
The Mapping Template defines how Amazon order fields map to Flxpoint. Here’s a breakdown:
Mapping Fields
Map fields with options like "Field", "Value", or "Rules". Key fields include:
| Amazon Field | Maps To | Options | Purpose |
|---|---|---|---|
| Amazon Order ID | Order Field: Reference Number | Field, Value, Rules | Links the order in Flxpoint |
| Address Line 1 | Shipping Address Field: Address Line 1 | Don't Map, Set To Empty, Field, Value, Mapping Set, Rules | Sets the primary shipping address |
| City | Shipping Address Field: City | Don't Map, Set To Empty, Field, Value, Mapping Set, Rules | Specifies the shipping city |
| Order Total - Amount | Channel Invoice Field: Total | Don't Map, Set To Empty, Field, Value, Rules | Records the order total |
| Purchase Date | Order Field: Ordered On | Field, Value, Mapping Set, Rules | Sets the order date |
Try This: Map "Address Line 1" to "Shipping Address Field: Address Line 1" using a Field option, or set a fixed "City" value like "Austin" for testing.
Here are some essentials:
- Current Date and Time: As of 02:48 PM -04 on Monday, June 23, 2025, this integration is ready to use.
- Supported Fields: Includes order details, billing, shipping, and invoice data from Amazon.
Pro Tip: Test your mappings with "Duplicate" to ensure all order data imports correctly before saving!
Conclusion
The Amazon Channel - Get Orders integration makes it easy to bring your Amazon orders into Flxpoint. With customizable mappings, you’ll have all the details you need to manage orders efficiently—happy ordering!
Sync Orders
Supported | Amazon Channel - Sync Orders
Introduction to Amazon Channel - Sync Orders Integration
The Amazon Channel - Sync Orders integration lets you send shipment details from Flxpoint to Amazon, updating tracking and fulfillment info. Using your Amazon connection, this guide will walk you through it step-by-step—let’s get started!
This integration connects Flxpoint to Amazon to:
- Send shipment details (like Tracking Number and Carrier) to Amazon.
- Update Amazon fulfillment fields with a custom mapping template.
- Keep tracking and shipping info accurate for your orders.
Here’s the flow:
- Configuration: Starts with your Amazon channel settings (SP-API or MWS).
- Receive Shipped Orders: Gets a list of orders with shipments from Flxpoint.
- Process Shipments: Handles each shipment, inferring Carrier and Method.
- Map to Amazon Format: Converts data into the format Amazon expects with rules and IDs.
- Filter Empty Fulfillments: Removes data with no items.
- Categorize Orders: Separates managed and non-managed orders.
- Submit to Amazon: Sends data as an order fulfillment feed.
- Process Response: Marks shipments as successful or failed based on Amazon’s feedback.
- Return Results: Provides a sync summary.
Sample Synced Data
{
"FulfillmentRequestNumber": "FR202306231234",
"Carrier": "UPS",
"TrackingNumber": "1Z9999W999999999"
}
"FulfillmentRequestNumber": "FR202306231234",
"Carrier": "UPS",
"TrackingNumber": "1Z9999W999999999"
}
Tip: Ensure your Tracking Number is correct for accurate updates!
Set up with these options:
- Connection Settings: Choose marketplace (DEFAULT, AMAZON_NA, AMAZON_EU, AMAZON_JP) and use your Amazon credentials.
- Shipment Mapping: Map fields like Carrier and Tracking Number.
Your Amazon connection keeps shipment updates secure.
Accurate mappings are key.
Accurate mappings are key.
Carrier & Service sent to Amazon: Auto-Detect vs Mappings
You control how Flxpoint chooses the Carrier and Shipping Service that get posted to Amazon:
-
Auto-Detect Shipping Carrier from Tracking Number (Advanced) — default: ON
When ON, Flxpoint identifies the carrier (and sometimes service) from the tracking number pattern and uses that value when posting to Amazon. - Use Your Mapping Rules — Turn Auto-Detect OFF to prioritize your own mapping rules (for example, normalize vendor inputs into your preferred carrier names).
Precedence logic:
1) Auto-Detect = ON → auto-detected carrier/service override mappings.
2) Auto-Detect = OFF → your mappings determine the carrier/service sent to Amazon.
1) Auto-Detect = ON → auto-detected carrier/service override mappings.
2) Auto-Detect = OFF → your mappings determine the carrier/service sent to Amazon.
When to turn Auto-Detect OFF? If your SLA/metrics depend on a specific carrier/service or you maintain strict normalization rules, disable Auto-Detect so your rules always win.
Follow these steps:
- 1 Connect to Amazon: Enter your Amazon credentials, select marketplace, and save.
- 2 Configure Mapping: Use the Mapping Template below.
- 3 Sync Orders: Run a test sync before enabling on a schedule.
This template links Flxpoint fields to Amazon fulfillment fields. It uses options like "Field" (to pull data directly), "Value" (to set a fixed value), or "Rules" (for custom logic). Here’s how it works:
| Flxpoint Field | Maps To | Example |
|---|---|---|
| Shipment Carrier | Fulfillment Data - Carrier Name | Use "Field" to pull "UPS" from your system, or set "Value" to "USPS" for all shipments. |
| Shipment Tracking Number | Fulfillment Data - Shipper Tracking Number | Map "Field" to "1Z9999W999999999" for a specific order, ensuring it matches your carrier’s format. |
| Shipment Method | Fulfillment Data - Shipping Method | Set "Value" to "Ground" or use "Field" to pull "Priority Mail" from your data. |
Context: If all your shipments use USPS, set "Shipment Carrier" to "Value: USPS" to simplify the process. For varied carriers, use "Field" to pull the correct carrier per shipment.
Heads-up: When Auto-Detect is ON, the inferred carrier/service from the tracking number will override your mappings. Turn Auto-Detect OFF if you need your mappings to take priority.
The system automatically determines the Carrier and Method based on your Tracking Number’s pattern. This saves time by recognizing common formats from carriers like USPS, UPS, and FedEx. Here’s how it works with examples:
| Condition | Action | Example |
|---|---|---|
| Length is 22 characters, starts with "94A0" | Carrier: "USPS", Method: "First Class" | Tracking Number: "94A0123456789012345678" → USPS First Class. |
| Length is 22 characters, starts with "94A05" or "92A05" | Carrier: "USPS", Method: "Priority Mail" | Tracking Number: "94A0512345678901234567" → USPS Priority Mail. |
| Starts with "93G1" | Carrier: "USPS", Method: "Parcel Select" | Tracking Number: "93G123456789" → USPS Parcel Select. |
| Starts with "9374" | Carrier: "USPS", Method: "Parcel Select Lightweight" | Tracking Number: "9374123456789" → USPS Parcel Select Lightweight. |
| None of the above USPS prefixes (length 22) | Carrier: "USPS", Method: "(empty string)" | Tracking Number: "ZZ12345678901234567890" → USPS with no method. |
| Length is 18 characters, starts with "1Z" and 9th & 10th chars are "YW" | Carrier: "UPS", Method: "SurePost" | Tracking Number: "1Z999YW9999999999" → UPS SurePost. |
| Length is 18 characters, starts with "1Z" and 9th & 10th chars are "03" | Carrier: "UPS", Method: "Ground" | Tracking Number: "1Z9990399999999999" → UPS Ground. |
| Starts with "9274" and length is 26 characters | Carrier: "UPS", Method: "Mail Innovations" | Tracking Number: "92741234567890123456789012" → UPS Mail Innovations. |
| Matches regex ^[0-9]{20}$ OR ^[0-9]{15}$ OR ^[0-9]{12}$ | Carrier: "FedEx", Method: "(empty string) if not FedEx, otherwise preserved" | Tracking Number: "12345678901234567890" → FedEx with no method. |
Example mappings (used when Auto-Detect = OFF)
| Input | Type | Mapped To | Notes |
|---|---|---|---|
| "GOSO" | Carrier value | GLS US | Normalizes vendor-provided value to your preferred carrier name. |
| "GOLDEN STATE OVERNIGHT" | Service value | Other | Maps long-form service label to a standardized value. |
Tip: Keep your mapping keys exact (spacing/case) for reliable matches.
General behavior
- Authentication: Uses the Amazon connection configured on your channel.
- Shipment scope: Syncs tracking for shipments created in Flxpoint that are ready to send to Amazon.
Bundle orders & partial shipments
For Amazon bundle items, Sync Orders uses the Amazon Order Item ID for the line item, not the individual component SKUs. Because Amazon expects a single shipment update per order item, bundle tracking is sent only when the bundle is fully shipped in Flxpoint.
- If all component SKUs for the bundle are shipped, Sync Orders sends a single shipment update for the bundled item to Amazon.
- If at least one component SKU is still unshipped, the bundle line is treated as partially shipped and that shipment is skipped during that sync run.
- Once all components are shipped in Flxpoint, the next Sync Orders run will include the tracking for the bundle line and update Amazon.
Example: An Amazon bundle SKU is made up of two component SKUs in Flxpoint. If only one component is shipped, no tracking is sent to Amazon yet. When both components are shipped, Sync Orders sends one shipment update for the bundled order item and tracking appears on Amazon.
Important: If you notice tracking on a bundled order in Flxpoint but not on Amazon, check whether all bundle components are fully shipped. Tracking will not sync until the bundle is complete.
If Amazon shows an unexpected carrier/service:
- Check the toggle: In Sync Orders → Advanced, confirm the Auto-Detect Shipping Carrier from Tracking Number setting is as intended.
- Review a recent order in Flxpoint: Open the shipment and confirm the final carrier/service before sync.
- Verify your mapping rules: Ensure exact key matches (case/spacing) and that each rule targets the correct field (Carrier vs Service).
- Re-sync after changes: If you adjusted the toggle or mappings, re-run the sync (or next cycle) for updated results.
Reminder: Auto-Detect = ON will override mappings. Disable it if your normalization rules must win.
Conclusion
This integration helps you keep Amazon order tracking in sync with Flxpoint, including how bundle and partial shipments are handled—happy syncing!