Turn 14 Distribution as a source can be completely managed using Flxpoint integrations. We support all the functionalities for Turn 14 Distribution.
How to connect
Before You Begin: Test in Sandbox Mode
When setting up the integration between Turn 14 Distribution and Flxpoint, it’s essential to start by testing with the sandbox integration. This testing phase allows you to ensure that all configurations and workflows function as expected. Turn 14 Distribution requires that you complete this step successfully before they grant you production access, ensuring that your live environment is error-free and fully optimized.
📋 Phase 1: Initial Source Setup
+
Access Fulfillment Sources
Log into your Flxpoint account and navigate to the Connections tab, then select Fulfillment Sources.
Create a New Source
Under the Sources section, click on + Add Source to begin creating a new source for your Turn 14 Distribution connection.
Tip: Having your Turn 14 Distribution account credentials ready will make this process smoother.
Configure Source Details
In the Create Source popup:
- Enter the source name as "Turn 14 Distribution"
- Select the appropriate type from the dropdown (e.g., Vendor Warehouse)
- Click Save to proceed
Start the Integration Process
After saving, you'll see a message that says "You have not created any integrations yet." Click Get Started to set up the integration.
🔐 Phase 2: Supplier Connection & Authentication
+
Select Connection Method
In the Setup Integrations popup, select Flx Supplier Directory (recommended) to proceed with the Turn 14 Distribution integration.
Find Your Supplier
In the Let's Find Your Supplier popup, search for "Turn 14 Distribution" in the Search Suppliers field. Select Turn 14 Distribution from the list and click Select.
Confirm Relationship
In the Confirm Your Relationship With Supplier popup, check the box to confirm that you have a reseller account with Turn 14 Distribution. Click Continue.
Important: You must have an active reseller account with Turn 14 Distribution before proceeding with this integration.
Enter Authentication Details
To get your API credentials, log into your Turn 14 Distribution account:
Navigate to the Account Settings or API Access section (this may vary depending on Turn 14's dashboard layout).
Look for an option like Generate API Credentials or API Keys.
Generate a new set of credentials, which will include a Client ID and Client Secret.
Note down the Environment (e.g., Test for sandbox mode, as noted in the "Before You Begin" section).
In the Authenticate With Supplier popup, enter the authentication details provided by Turn 14 Distribution:
Connection Name: Enter a descriptive name like "Turn 14 API Connection"
Environment: Select the environment (e.g., Test for sandbox mode)
Client ID: Enter the Client ID provided by Turn 14 Distribution
Client Secret: Enter the Client Secret provided by Turn 14 Distribution
Click Continue to proceed.
Important: If you don’t see API access in your account, contact Turn 14 support at support@turn14.com or through their dealer portal to request API credentials.
🔄 Phase 3: Configuration & Feature Setup
+
Set Up SKU Mapping
In the Master SKU section, set up your SKU mapping (Inventory SKU → Master SKU → Listing SKU). Optionally, set an SKU prefix (e.g., "T14-") if needed for better organization.
Pro Tip: Using a prefix like "T14-" helps you quickly identify products sourced from Turn 14 Distribution in your inventory listings.
Configure Additional Features
Set up any additional features required for your integration:
- Get Inventory: Enable to retrieve current inventory data from Turn 14 Distribution
- Send Fulfillment Requests: Enable to automatically send orders to Turn 14 Distribution
- Get Shipments: Enable to pull shipping information from Turn 14 Distribution
- Automated Order Sending: Toggle ON to have Flxpoint automatically send orders to Turn 14 Distribution
Complete Setup
Review all your settings and click Save to finalize your Turn 14 Distribution integration.
Next Steps: After completing the setup, your Turn 14 Distribution source will begin syncing with Flxpoint. You can now manage your inventory, orders, and shipments directly from your Flxpoint dashboard. Once testing in sandbox mode is successful, contact Turn 14 to request production access.
×
![]()
Product Operations
The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, such as focusing on specific products or updates
Get Inventory and Pricing & Quantity
Supported | Turn 14 - Get Inventory and Pricing & Quantity
Introduction to Turn 14 Get Inventory and Pricing & Quantity Integration
Welcome to the Turn 14 Get Inventory and Pricing & Quantity integration guide! This integration helps you update inventory quantities and pricing in Flxpoint by syncing the latest stock data from Turn 14. It’s designed to focus on updates since the last sync, ensuring your stock levels and pricing are always accurate. Let’s dive into the setup process with clear steps and examples to get you started!
The Turn 14 Get Inventory Pricing & Quantity integration connects your Flxpoint system to Turn 14 to:
- Retrieve updated inventory quantities and pricing since the last sync, ensuring your stock levels are current.
- Sum quantities across all warehouses for a consolidated inventory view.
- Map inventory data to Flxpoint fields for seamless updates.
The integration follows a structured process to fetch updated inventory data from Turn 14 using their API. Here’s how it works:
-
Base URL: All API requests are made to
https://api.turn14.com. -
Generate Token: We start by generating an authentication token using the
/v1/tokenendpoint, passing yourclient_idandclient_secret. -
Fetch Inventory Updates: A GET request is made to the
/v1/inventory/updatesendpoint to retrieve inventory data. Query parameters include:- page: Specifies the page number for pagination (e.g., 1 for the first page).
- minutes: Indicates the time since the last sync in minutes (e.g., 60 to fetch updates from the last hour).
-
Sum Quantities: The integration sums the
Total Warehouse Inventoryquantities across all warehouses for each item, providing a consolidated stock level. - Syncing: The updated inventory data is mapped to Flxpoint fields (e.g., Quantity, Cost) and saved to your system. You can run this manually with Run Sync or schedule it via "Adjust Schedule."
Pro Tip: Set a shorter “minutes” parameter (e.g., 15) for more frequent updates if you need near-real-time stock levels, but keep in mind this may increase API calls.
You can customize the integration with these settings:
- Minutes Parameter: Set the time interval (in minutes) for fetching updates since the last sync (e.g., 60 minutes).
- Scheduling: Run the integration manually or schedule it (e.g., hourly) using "Adjust Schedule." Refer to the Job Scheduling Requirements section for recommended frequencies.
- Mapping Template: Define which fields to import and how they map to Flxpoint fields (see Mapping Templates section).
Note: Scheduling frequent syncs (e.g., every 5 minutes) ensures your inventory stays up-to-date but may impact API rate limits. Adjust based on your needs.
Follow these steps to configure the integration:
- 1 Add the Integration: Go to the Integrations section, select Turn 14 as the integration type, and choose “Get Inventory and Pricing & Quantity.”
-
2 Connect to Turn 14: Enter your API credentials:
- Client ID: Your Turn 14 client ID (e.g., client123).
- Client Secret: Your Turn 14 client secret (e.g., secret456).
- 3 Configure Settings: Set the “minutes” parameter to determine the time interval for updates and configure your sync schedule according to the Job Scheduling Requirements.
- 4 Create a Mapping Template: Use the "Manage Mapping" option to define which fields to import (see Mapping Templates section).
- 5 Run the Integration: Start manually with Run Sync or schedule via "Adjust Schedule."
To ensure optimal performance and avoid hitting API rate limits, please follow these required scheduling guidelines:
Job Schedule Settings
| Job Name | Recommended Frequency | Notes |
|---|---|---|
| Get Inventory Primary | Once per day | Avoid scheduling more than once daily to prevent API throttling. |
| Pricing & Quantity | Hourly | Can safely run hourly to fetch incremental updates efficiently. |
Important Notes
- Get Inventory Primary should not be scheduled more than once per 24 hours.
- Get Inventory Pricing & Quantity is designed to be run more frequently and is safe to schedule hourly.
- Running Get Inventory Primary too often can reduce overall performance and increase the chance of failures due to Turn 14's rate limits.
- When both Get Inventory Primary and Get Inventory Pricing & Quantity are enabled, Get Inventory Pricing & Quantity should be your primary recurring update job.
- Get Inventory Primary can still be run manually if needed, but consecutive executions should have a minimum interval.
A mapping template controls how inventory data from Turn 14 is imported into Flxpoint. You can choose which fields to import and how they map to your system’s fields.
Interface Overview
- The mapping screen is labeled “Turn 14 → Flxpoint” under “Get Inventory Pricing & Quantity.”
- Buttons: Cancel and Save Mapping.
- Columns: Left (Turn 14 fields), Right (Flxpoint fields), with an "Enabled" toggle for non-required fields.
Mapping Options
- Enabled/Disabled: Toggle to enable or disable non-required fields to control whether data is imported or synced.
- Required Fields: Certain fields (e.g., SKU, Parent SKU, Master SKU) are mandatory and cannot be disabled.
Available Source Fields
- Turn 14 Dimensions: Height (of largest package), Length (of largest package), Width (of largest package).
- Turn 14 Dropship Fee: Dropship Fee.
- Turn 14 Estimated Ground Continental US Base Rate: Maximum.
- Turn 14 Inventory: Total Warehouse Inventory.
- Turn 14 Item Attributes: All Images, Allow Backorders, Brand, Category, Sub Category, Custom Field 1 Name, Regular Stock, Part Description, Mfr Part Number, Product Name, Barcode, Weight (combined), Part Number.
- Turn 14 Pricing: Purchase Cost, MAP, Retail.
What the Mapping Interface Shows
The mapping interface for this integration is a detailed screen that helps you connect Turn 14 data to Flxpoint fields. At the top, you’ll see the title “Get Inventory Pricing & Quantity” along with action buttons: Cancel and Save Mapping. The interface is divided into two main sections: mapping to Flxpoint Inventory Parent fields and mapping to Flxpoint Inventory Variant fields.
- Inventory Parent Fields: Includes fields like Parent SKU, All Images, Brand, Category 1, Category 2, Description, and Title. Each field shows the mapped Turn 14 field and its enabled status.
- Inventory Variant Fields: Includes fields like SKU, Master SKU, All Images, Allow Backorders, Cost, Custom Field 1 Name, Custom Field 1 Value, Dropship Fee, Height, Length, MAP, MPN, MSRP, Quantity, Reference Identifier, Shipping Cost, Title, UPC, Weight, and Width. Each field shows the mapped Turn 14 field and its enabled status, with required fields like SKU and Master SKU marked as mandatory.
Complete Field Mappings
| Turn 14 Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Turn 14 Dimensions: Height (of largest package) | Flxpoint Inventory Variant: Height | 10.00 | Records the height of the largest package | Enabled |
| Turn 14 Dimensions: Length (of largest package) | Flxpoint Inventory Variant: Length | 20.00 | Records the length of the largest package | Enabled |
| Turn 14 Dimensions: Width (of largest package) | Flxpoint Inventory Variant: Width | 15.00 | Records the width of the largest package | Enabled |
| Turn 14 Dropship Fee: Dropship Fee | Flxpoint Inventory Variant: Dropship Fee | 5.00 | Records the calculated dropship fee | Enabled |
| Turn 14 Estimated Ground Continental US Base Rate: Maximum | Flxpoint Inventory Variant: Shipping Cost | 12.50 | Records the maximum estimated shipping cost | Enabled |
| Turn 14 Inventory: Total Warehouse Inventory | Flxpoint Inventory Variant: Quantity | 50 | Records the summed stock quantity across all warehouses | Enabled |
| Turn 14 Item Attributes: All Images | Flxpoint Inventory Variant: All Images | - | Imports variant images | Enabled |
| Turn 14 Item Attributes: All Images | Flxpoint Inventory Parent: All Images | - | Imports product images | Enabled |
| Turn 14 Item Attributes: Allow Backorders | Flxpoint Inventory Variant: Allow Backorders | - | Determines if backorders are allowed | Enabled |
| Turn 14 Item Attributes: Brand | Flxpoint Inventory Parent: Brand | Acme | Records the product brand | Enabled |
| Turn 14 Item Attributes: Category | Flxpoint Inventory Parent: Category 1 | Accessories | Assigns the first-level category | Enabled |
| Turn 14 Item Attributes: Sub Category | Flxpoint Inventory Parent: Category 2 | Helmets | Assigns the second-level category | Enabled |
| Turn 14 Item Attributes: Custom Field 1 Name | Flxpoint Inventory Variant: Custom Field 1 Name | - | Records the name of the first custom field | Enabled |
| Turn 14 Item Attributes: Regular Stock | Flxpoint Inventory Variant: Custom Field 1 Value | - | Records the value of the first custom field | Enabled |
| Turn 14 Item Attributes: Part Description | Flxpoint Inventory Parent: Description | A high-quality helmet for safety. | Provides the product description | Enabled |
| Turn 14 Item Attributes: Mfr Part Number | Flxpoint Inventory Variant: MPN | MPN123 | Records the Manufacturer Part Number | Enabled |
| Turn 14 Item Attributes: Brand | Flxpoint Inventory Variant: Reference Identifier | Acme | Records the brand as a reference identifier | Enabled |
| Turn 14 Item Attributes: Product Name | Flxpoint Inventory Variant: Title | Acme Safety Helmet | Sets the variant title | Enabled |
| Turn 14 Item Attributes: Product Name | Flxpoint Inventory Parent: Title | Acme Safety Helmet | Sets the product title | Enabled |
| Turn 14 Item Attributes: Barcode | Flxpoint Inventory Variant: UPC | 012345678905 | Records the Universal Product Code | Enabled |
| Turn 14 Item Attributes: Weight (combined) | Flxpoint Inventory Variant: Weight | 2.5 | Records the combined weight of the item | Enabled |
| Turn 14 Item Attributes: Part Number | Flxpoint Inventory Variant: SKU | PART123 | Identifies the variant in Flxpoint | Required |
| Turn 14 Item Attributes: Part Number | Flxpoint Inventory Parent: Parent SKU | PART123 | Identifies the parent product in Flxpoint | Required |
| Turn 14 Item Attributes: Part Number | Flxpoint Inventory Variant: Master SKU | PART123 | Primary identifier for linking in Flxpoint | Required |
| Turn 14 Pricing: Purchase Cost | Flxpoint Inventory Variant: Cost | 50.00 | Records the cost to purchase the item | Enabled |
| Turn 14 Pricing: MAP | Flxpoint Inventory Variant: MAP | 75.00 | Records the Minimum Advertised Price | Enabled |
| Turn 14 Pricing: Retail | Flxpoint Inventory Variant: MSRP | 100.00 | Records the Manufacturer's Suggested Retail Price | Enabled |
If issues arise, here are some steps to help you troubleshoot:
-
Authentication Failure:
- Verify your Turn 14 API credentials (Client ID and Client Secret).
- Test the connection using the Test Connection button.
-
Inventory Not Updating:
- Ensure the “Total Warehouse Inventory” field is enabled in the mapping template.
- Check the “minutes” parameter; if set too low, it may miss updates (e.g., set to 60 to cover the last hour).
- Verify the API response by reviewing logs using "View Logs."
-
Sync Failure:
- Review logs using the "View Logs" option to identify specific errors, such as API rate limits or authentication failures.
- Contact Flxpoint support if problems persist, providing the item ID and log details for investigation.
Diagnostic Tip: If quantities aren’t updating, check the “minutes” parameter. For example, if set to 5 minutes but the last sync was 10 minutes ago, you might miss updates. Adjust to a larger value like 15 minutes.
This section provides key details about the Turn 14 Get Inventory Pricing & Quantity integration to help you understand the process:
- Current Date and Time: As of 07:08 PM -04 on Thursday, May 22, 2025, this integration is fully operational for retrieving updated inventory from Turn 14.
-
API Connection: Uses the Turn 14 API at
https://api.turn14.comto fetch inventory updates via the/v1/inventory/updatesendpoint. - Incremental Updates: Only fetches inventory changes since the last sync, based on the “minutes” parameter.
- Quantity Summation: Combines stock quantities across all warehouses for a unified total.
Pro Tip: Regularly check your API credentials to ensure uninterrupted access to Turn 14’s data.
Conclusion
With the Turn 14 Get Inventory Pricing & Quantity integration, you can keep your inventory quantities and pricing in Flxpoint up-to-date by syncing the latest stock updates from Turn 14. The detailed mapping template and flexible scheduling options make it easy to manage your inventory with precision. Happy syncing!
Order Operations
It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring a seamless integration between order processing and shipment tracking.
Send Orders
Supported | Turn 14 - Send Orders
Introduction to Turn 14 Send Orders Integration
Welcome to the Turn 14 Send Orders integration guide! This integration allows you to send orders to Turn 14 directly from Flxpoint, automating the process of creating orders with the cheapest available shipping method. It ensures efficient order processing by selecting optimal shipping options and saving the order confirmation for tracking. Let’s walk through the setup process with clear steps and examples to get you started!
The Turn 14 Send Orders integration connects your Flxpoint system to Turn 14 to:
- Send orders to Turn 14, streamlining the order creation process.
- Automatically select the cheapest shipping method, with options to exclude methods or filter by transit days.
- Map order details to Turn 14 fields for accurate order processing.
- Store the Turn 14 order confirmation number in Flxpoint for easy tracking.
The integration follows a structured process to send orders to Turn 14 using their API. Here’s how it works:
-
Base URL: All API requests are made to
https://api.turn14.com. -
Generate Token: We start by generating an authentication token using the
/v1/tokenendpoint, passing yourclient_idandclient_secret. -
Request a Quote: A GET request is made to the
/v1/quoteendpoint to retrieve a quote, which returns aquote_idand available shipping methods. -
Select Shipping Method: The integration selects the cheapest shipping method by default, with the following filters:
- If a shipping method is marked for exclusion in the integration config, it’s excluded from the available options.
- If a transit days filter is set in the mapping template (e.g., “Max Transit Days”), methods with transit days exceeding this value are excluded.
-
Create Order: Using the selected shipping method and
quote_id, an order is created via the/v1/order/from_quoteendpoint. The response includes anorder_id, which is saved as the confirmation number in Flxpoint’s database. - Syncing: Order details (e.g., notes, shipping preferences) are mapped to Turn 14 fields as per the mapping template and sent during the order creation process. You can run this manually with Run Sync or schedule it via "Adjust Schedule."
Pro Tip: Use the transit days filter in the mapping template to prioritize faster shipping methods for urgent orders, balancing cost and speed.
You can customize the integration with these settings:
- Shipping Method Exclusion: Specify shipping methods to exclude from the selection process (e.g., exclude “Express Shipping” if it’s too costly).
- Max Transit Days: Set a transit days filter in the mapping template to exclude shipping methods with longer transit times (e.g., exclude methods with more than 5 days).
- Scheduling: Run the integration manually or schedule it (e.g., every 15 minutes) using "Adjust Schedule."
- Mapping Template: Define how Flxpoint fields map to Turn 14 fields for order details (see Mapping Templates section).
Note: Excluding costly shipping methods can help control expenses, but ensure at least one viable method remains available to avoid order failures.
Follow these steps to configure the integration:
- 1 Add the Integration: Go to the Integrations section, select Turn 14 as the integration type, and choose “Send Orders.”
-
2 Connect to Turn 14: Enter your API credentials:
- Client ID: Your Turn 14 client ID (e.g., client123).
- Client Secret: Your Turn 14 client secret (e.g., secret456).
- 3 Configure Settings: Set up shipping method exclusions, define the Max Transit Days in the mapping template if needed, and configure your sync schedule.
- 4 Create a Mapping Template: Use the "Manage Mapping" option to define which fields to send to Turn 14 (see Mapping Templates section).
- 5 Run the Integration: Start manually with Run Sync or schedule via "Adjust Schedule."
A mapping template controls how data from Flxpoint is sent to Turn 14 for order creation. You can choose which fields to send and how they map to Turn 14’s fields.
Interface Overview
- The mapping screen is labeled “Flxpoint → Turn 14” under “Send Orders.”
- Buttons: Delete, Duplicate, and Save.
- Columns: Left (Flxpoint fields), Right (Turn 14 fields).
Mapping Options
- Don’t Map: Ignore the field entirely.
- Set To Empty: Clear any existing data in that field.
- Direct Copy: Directly copy the Flxpoint field to the Turn 14 field.
- Field: Map a specific Flxpoint field to a Turn 14 field.
- Value: Set a constant value for all orders.
- Mapping Set: Apply a predefined transformation or mapping table.
Available Source Fields
- Order: Max Transit Days, Order Notes, Hold Until Entire Order Can Ship.
What the Mapping Interface Shows
The mapping interface for this integration is a streamlined screen designed to map Flxpoint data to Turn 14 fields for order creation. At the top, you’ll see the title “Send Orders” with action buttons: Delete, Duplicate, and Save. The interface focuses on mapping Flxpoint order fields to Turn 14 fields.
- Turn 14 Order Fields: Includes fields like Max Transit Days, Order Notes, and Hold Until Entire Order Can Ship. These fields allow you to configure shipping method selection and add order-specific details.
Complete Field Mappings
| Flxpoint Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Max Transit Days | Turn 14 Order Field: Max Transit Days | 5 | Sets a transit days filter to exclude slower shipping methods | Don't Map |
| Order Notes | Turn 14 Order Field: Order Notes | - | Adds notes to the order for Turn 14 | Don't Map |
| Hold Until Entire Order Can Ship | Turn 14 Order Field: Hold Until Entire Order Can Ship | True | Determines if the order waits until all items are ready | Direct Copy |
If issues arise, here are some steps to help you troubleshoot:
-
Authentication Failure:
- Verify your Turn 14 API credentials (Client ID and Client Secret).
- Test the connection using the Test Connection button.
-
No Shipping Methods Available:
- Check if you’ve excluded too many shipping methods in the integration config, leaving no viable options.
- Ensure the Max Transit Days filter isn’t too restrictive (e.g., set to 1 day might exclude all methods).
- Verify the API response by reviewing logs using "View Logs."
-
Order Creation Failure:
- Ensure required order details are correctly mapped in the template (e.g., shipping method preferences).
- Check for API errors (e.g., rate limits, invalid quote ID) in the logs using "View Logs."
-
Sync Failure:
- Review logs using the "View Logs" option to identify specific errors, such as API rate limits or authentication failures.
- Contact Flxpoint support if problems persist, providing the order ID and log details for investigation.
Diagnostic Tip: If no shipping methods are available, try removing exclusions or increasing the Max Transit Days value to allow more options.
This section provides key details about the Turn 14 Send Orders integration to help you understand the process:
- Current Date and Time: As of 06:50 PM -04 on Thursday, May 22, 2025, this integration is fully operational for sending orders to Turn 14.
-
API Connection: Uses the Turn 14 API at
https://api.turn14.comto send orders via the/v1/quoteand/v1/order/from_quoteendpoints. - Shipping Method Selection: Automatically selects the cheapest method, with options to exclude methods or filter by transit days.
-
Confirmation Number: The Turn 14
order_idis saved as the confirmation number in Flxpoint for tracking.
Pro Tip: Regularly check your API credentials to ensure uninterrupted access to Turn 14’s data.
Conclusion
With the Turn 14 Send Orders integration, you can automate the process of sending orders to Turn 14, ensuring efficient order creation with the cheapest shipping methods. The flexible configurations and mapping options make it easy to customize order details, while the streamlined API workflow ensures reliability. Happy ordering!
Get Shipments
Supported | Turn 14 - Get Shipments
Introduction to Turn 14 Get Shipments Integration
Welcome to the Turn 14 Get Shipments integration guide! This integration allows you to retrieve shipment details, such as tracking numbers and carrier information, from Turn 14 and sync them into Flxpoint. It helps you keep your fulfillment records up-to-date by mapping shipment data to specific fulfillment requests. Let’s walk through the setup process with clear steps and examples to get you started!
The Turn 14 Get Shipments integration connects your Flxpoint system to Turn 14 to:
- Retrieve shipment details, including tracking numbers, carrier names, and shipping methods, for fulfilled orders.
- Sync shipment data for multiple fulfillment requests using the Fulfillment Request Number (FR#) for accurate mapping.
- Map shipment and item details to Flxpoint fields for seamless tracking and record-keeping.
The integration follows a structured process to fetch shipment data from Turn 14 using their API. Here’s how it works:
-
Base URL: All API requests are made to
https://api.turn14.com. -
Generate Token: We start by generating an authentication token using the
/v1/tokenendpoint, passing yourclient_idandclient_secret. -
Fetch Tracking Details: A GET request is made to the
/v1/tracking/package_detailsendpoint to retrieve shipment data. Query parameters include:- start_date: Specifies the start date for the shipment data range (e.g., 2025-05-01).
- end_date: Specifies the end date for the shipment data range (e.g., 2025-05-22).
- Map Shipments to Fulfillment Requests: The integration retrieves tracking details for multiple fulfillment requests. The Fulfillment Request Number (FR#) is used to map tracking data to the corresponding request in Flxpoint.
- Syncing: Shipment data (e.g., tracking number, carrier, ship date) is mapped to Flxpoint fields as per the mapping template and saved to your system. You can run this manually with Run Sync or schedule it via "Adjust Schedule."
Pro Tip: Set a narrow date range (e.g., a single day) when initially testing the integration to avoid pulling too much data and ensure accurate mapping.
You can customize the integration with these settings:
-
Date Range: Specify the
start_dateandend_dateparameters to control the range of shipment data retrieved (e.g., last 7 days). - Scheduling: Run the integration manually or schedule it (e.g., daily) using "Adjust Schedule."
- Mapping Template: Define which shipment fields to import and how they map to Flxpoint fields (see Mapping Templates section).
Note: A shorter date range reduces API load and speeds up the sync process, especially if you only need recent shipment updates.
Follow these steps to configure the integration:
- 1 Add the Integration: Go to the Integrations section, select Turn 14 as the integration type, and choose “Get Shipments.”
-
2 Connect to Turn 14: Enter your API credentials:
- Client ID: Your Turn 14 client ID (e.g., client123).
- Client Secret: Your Turn 14 client secret (e.g., secret456).
- 3 Configure Settings: Set the date range for shipment data retrieval and configure your sync schedule.
- 4 Create a Mapping Template: Use the "Manage Mapping" option to define which fields to import (see Mapping Templates section).
- 5 Run the Integration: Start manually with Run Sync or schedule via "Adjust Schedule."
A mapping template controls how shipment data from Turn 14 is imported into Flxpoint. You can choose which fields to import and how they map to Flxpoint’s fields.
Interface Overview
- The mapping screen is labeled “Turn 14 → Flxpoint” under “Get Shipments.”
- Buttons: Delete, Duplicate, and Save.
- Columns: Left (Turn 14 fields), Right (Flxpoint fields).
Mapping Options
- Don’t Map: Ignore the field entirely.
- Set To Empty: Clear any existing data in that field.
- Direct Copy: Directly copy the Turn 14 field to the Flxpoint field (available for certain fields like All Custom Fields).
- Field: Map a specific Turn 14 field (e.g., “Tracking Number”) to a Flxpoint field.
- Value: Set a constant value for all shipments.
- Mapping Set: Apply a predefined transformation or mapping table.
Available Source Fields
- Turn 14 Package: Carrier Name, Service (Method), Ship Date, Tracking Number.
- Turn 14 Package Item: Part Number, Product Group Part Number, Quantity.
What the Mapping Interface Shows
The mapping interface for this integration is a detailed screen designed to map Turn 14 shipment data to Flxpoint fields. At the top, you’ll see the title “Get Shipments” with action buttons: Delete, Duplicate, and Save. The interface is divided into two main sections: mapping to Flxpoint Shipment fields and mapping to Flxpoint Shipment Item fields.
- Shipment Fields: Includes fields like Tracking Number, Carrier, Fulfillment Request Number, Method, Note, Shipped At, Shipping Cost, and Tracking URL. For each field, you can select mapping options (e.g., Don’t Map, Set To Empty, Direct Copy, Field, Value, Mapping Set) and apply rules if needed.
- Shipment Item Fields: Includes fields like Quantity, All Custom Fields (with a note that Direct Copy imports all serial numbers), and SKU. Similar mapping options and rules are available for each field.
- Rules Section: A predefined rule named “Get Shipments - Part number” is visible, which has 1 condition and 1 action modifying the Incoming Value. You can also create new rules using the “New Rule” button or test existing rules with the “Test Rules” button.
Complete Field Mappings
| Turn 14 Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Turn 14 Package: Tracking Number | Flxpoint Shipment Field: Tracking Number | 1Z9999W99999999999 | Records the tracking number for the shipment | Direct Copy |
| Turn 14 Package: Carrier Name | Flxpoint Shipment Field: Carrier | UPS | Records the carrier used for the shipment | Direct Copy |
| Fulfillment Request Number | Flxpoint Shipment Field: Fulfillment Request Number | - | Maps the shipment to the correct fulfillment request | Don't Map |
| Turn 14 Package: Service (Method) | Flxpoint Shipment Field: Method | Ground | Records the shipping method used | Direct Copy |
| Note | Flxpoint Shipment Field: Note | - | Adds any notes related to the shipment | Don't Map |
| Turn 14 Package: Ship Date | Flxpoint Shipment Field: Shipped At | 2025-05-20 | Records the date the shipment was sent | Direct Copy |
| Shipping Cost | Flxpoint Shipment Field: Shipping Cost | - | Records the cost of shipping | Don't Map |
| Tracking URL | Flxpoint Shipment Field: Tracking URL | - | Provides a URL to track the shipment | Don't Map |
| Turn 14 Package Item: Quantity | Flxpoint Shipment Item Field: Quantity | 2 | Records the quantity of items shipped | Direct Copy |
| All Custom Fields | Flxpoint Shipment Item Field: All Custom Fields | - | Imports all serial numbers if set to Direct Copy | Don't Map |
| Turn 14 Package Item: Product Group Part Number | Flxpoint Shipment Item Field: SKU | ABC123 | Records the SKU for the shipped item | Direct Copy |
Mapping Rules
-
Get Shipments - Part number Rule: A predefined rule named "Get Shipments - Part number" is applied. It:
- Has 1 condition and 1 action modifying the Incoming Value.
- Can be tested or modified using the "Test Rules" or "New Rule" options in the mapping interface.
If issues arise, here are some steps to help you troubleshoot:
-
Authentication Failure:
- Verify your Turn 14 API credentials (Client ID and Client Secret).
- Test the connection using the Test Connection button.
-
No Shipment Data Returned:
- Ensure the
start_dateandend_dateparameters cover a period where shipments exist (e.g., check the date range in Turn 14). - Verify the API response by reviewing logs using "View Logs."
- Ensure the
-
Incorrect Mapping of Shipments:
- Ensure the Fulfillment Request Number (FR#) is correctly mapped in the template to match shipments to the right requests.
- Check the "Get Shipments - Part number" rule to ensure it’s not altering data unexpectedly.
-
Sync Failure:
- Review logs using the "View Logs" option to identify specific errors, such as API rate limits or authentication failures.
- Contact Flxpoint support if problems persist, providing the shipment ID and log details for investigation.
Diagnostic Tip: If shipments aren’t mapping correctly, double-check that the Fulfillment Request Number field is mapped, as it’s critical for linking tracking data to the correct request.
This section provides key details about the Turn 14 Get Shipments integration to help you understand the process:
- Current Date and Time: As of 06:53 PM -04 on Thursday, May 22, 2025, this integration is fully operational for retrieving shipment data from Turn 14.
-
API Connection: Uses the Turn 14 API at
https://api.turn14.comto fetch shipment details via the/v1/tracking/package_detailsendpoint. -
Date Range Parameters: Requires
start_dateandend_dateto specify the shipment data range. - Mapping by FR#: Uses the Fulfillment Request Number (FR#) to map tracking details to specific fulfillment requests.
Pro Tip: Regularly check your API credentials to ensure uninterrupted access to Turn 14’s data.
Conclusion
With the Turn 14 Get Shipments integration, you can effortlessly sync shipment details like tracking numbers and carrier information into Flxpoint, keeping your fulfillment records accurate. The detailed mapping template and flexible configurations make it easy to manage your shipment data, ensuring seamless tracking for your orders. Happy tracking!