Flxpoint Knowledge

Contact us

Turn 14 Distribution as source

Table of Contents

How to connect Product Operations Order Operations

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: Creating Your Turn 14 Source +
Create Source in Flxpoint
Log into your Flxpoint account, navigate to the Sources tab, and click + Add Source to begin.
Set Up Source Details
Enter "Turn 14 Distribution" as the source name, select the appropriate source type (e.g., Vendor Warehouse), and choose whether to assign a vendor (recommended for better reporting). Click Save & Next to continue.
Tip: Assigning a vendor improves your reporting capabilities and helps with product organization.
Choose Integration Type
After creating your source, you'll see the Integrations section. If no integrations are set up yet, click Start Creating Integrations. You can set up any of these integrations based on your needs:
  • Get Inventory - Retrieves current inventory data from Turn 14
  • Send Fulfillment Requests - Sends orders to Turn 14 automatically
  • Get Shipments - Pulls shipping information from Turn 14
Note: You can activate any combination of these integrations based on your business needs.
🔐 Phase 2: Setting Up API Connection +
Select Turn 14 API Integration
From the integration list, select Turn 14 API to open the connection setup screen for inventory retrieval and order processing.
Obtain API Credentials from Turn 14
To get your API credentials, log into your Turn 14 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., Production or Test) that Turn 14 specifies for API usage.
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.
Configure API Connection Details
Fill out the New Turn 14 Distribution Connection form with the credentials you obtained:
  • Connection Name: "Turn 14 API Connection" (or any descriptive name)
  • Environment: Select the environment (e.g., Test for sandbox mode initially, as noted in the "Before You Begin" section)
  • Client ID: Enter the Client ID provided by Turn 14
  • Client Secret: Enter the Client Secret provided by Turn 14
Tip: After filling in all details, click Test Connection to verify everything works before saving.
🛒 Phase 3: Setting Up Order Processing +
Configure Order Processing Connection
For Send Fulfillment Requests or Get Shipments integrations, use the same API connection you set up in Phase 2:
  • Ensure the connection name matches the one you created (e.g., "Turn 14 API Connection").
  • Verify that the Environment, Client ID, and Client Secret are correctly entered.
Automated Order Settings
Configure how orders will be processed:
  • Toggle Automatically Send Orders ON to have Flxpoint automatically send orders to Turn 14.
  • Set any additional order rules or conditions as needed (e.g., order thresholds or specific product categories).
Click Test Connection and then Save Connection once verified.
✅ Phase 4: Mapping and Activation +
Create Field Mapping
After setting up your connection, map Turn 14 fields to Flxpoint fields:
  • Choose an existing mapping template or create a new one.
  • Map essential fields like SKU, Price, Quantity, etc.
  • Set up any transformations needed (e.g., price markups).
Tip: For inventory feeds, ensure you map both product details and inventory quantity fields.
Configure SKU Mapping
In the Master SKU section, set up your preferred SKU mapping (Inventory SKU → Master SKU → Listing SKU). Consider adding a SKU prefix like "T14-" to identify Turn 14 products in your system.
Activate and Verify
Complete the setup by clicking Save and Complete. Your Turn 14 integration is now active and will run based on your settings.
Next Steps: The initial inventory sync may take some time. Monitor the progress in the Integrations section of your Flxpoint dashboard. Once testing in sandbox mode is successful, contact Turn 14 to request production access.
Turn 14 API Connection Setup


 

 

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 (Primary)

Supported | Turn 14 - Get Inventory [Primary]

Introduction to Turn 14 Get Inventory [Primary] Integration
Welcome to the Turn 14 Get Inventory [Primary] integration guide! This integration helps you bring product inventory data from Turn 14 into Flxpoint, so you can manage your stock, pricing, and more—all in one place. Whether you’re syncing product details, pricing, or shipping estimates, this guide will walk you through the setup process with easy steps and examples. Let’s get started!

The Turn 14 Get Inventory [Primary] integration connects your Flxpoint system to Turn 14 to:
  • Retrieve product inventory data, including stock levels, pricing, and shipping estimates.
  • Sync detailed product attributes like brand, category, and descriptions for better catalog management.
  • Support automotive-specific data, such as vehicle fitment IDs, for more precise inventory tracking.
  • Calculate dropship fees automatically to help with cost planning.

The integration follows a structured process to fetch 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/token endpoint, passing your client_id and client_secret.
  • Fetch Item IDs: A GET request is made to the /v1/items endpoint to retrieve item_id and dropship_id for each product.
  • Retrieve Product Data: Using the item_id, we make GET requests to multiple endpoints:
    • /v1/items/data: Fetches full product data (e.g., brand, category, descriptions).
    • /v1/pricing: Retrieves pricing details (e.g., MAP, retail).
    • /v1/inventory: Gets inventory levels (e.g., total warehouse inventory).
    • /v1/shipping/item_estimation: Obtains shipping cost estimates.
    • /v1/dropship/{dropship_id}: Fetches dropship fee data.
    • /v1/items/fitment: Retrieves vehicle fitment IDs (only if the "Save Vehicle Fitments Ids" config is enabled; runs on Mondays and Thursdays).
  • Dropship Fee Calculation: The dropship fee is calculated in the backend:
    • If getChargedFee is null, the fee is set to 0.
    • If getChargedFee has a value, that value is used.
    • If getChargedPercent has a value, the fee is calculated by multiplying getChargedPercent with getPurchaseCost.
  • Hardcoded Attributes: Some attributes are hardcoded and not configurable:
    • Shipped in Multiple Boxes
    • EPA
    • Prop65
    • Carb Acknowledgement Required
    • Vehicle Fitment ID
  • Syncing: The retrieved data is mapped to Flxpoint fields (e.g., SKU, Quantity) and saved to your system. You can run this manually with Run Sync or schedule it via "Adjust Schedule."
Pro Tip: If you’re using vehicle fitment data, enable the "Save Vehicle Fitments Ids" setting to sync this data on Mondays and Thursdays for up-to-date automotive compatibility.

You can customize the integration with these settings:
  • Save Vehicle Fitments Ids: Enable to retrieve vehicle fitment data on Mondays and Thursdays (options: Yes/No).
  • Scheduling: Run the integration manually or schedule it (e.g., daily at 8 AM UTC) 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: If you don’t need automotive fitment data, you can disable the "Save Vehicle Fitments Ids" setting to reduce API calls and speed up the sync process.

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 [Primary].”
  • 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).
    Click Test Connection to verify it works, then save.
  • 3 Configure Settings: Decide if you want to enable "Save Vehicle Fitments Ids" for automotive data and set 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 (GIP) Once per day Avoid scheduling more than once daily to prevent API throttling.
Get Inventory Secondary (GIS) Hourly Can safely run hourly. Only pulls updates since the last successful run.
Important Notes
  • GIP should not be scheduled more than once per 24 hours.
  • GIS is designed to be run more frequently and is safe to schedule hourly.
  • Running GIP too often can reduce overall performance and increase the chance of failures due to Turn 14's rate limits.
  • When both GIP and GIS are enabled, GIS should be your primary recurring update job.
  • GIP 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 [Primary].”
  • 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.
  • Field: Map a specific Turn 14 field (e.g., “Brand”) to a Flxpoint field.
  • Value: Set a constant value for all inventory items.
  • Mapping Set: Apply a predefined transformation or mapping table.
Available Source Fields
  • Turn 14 Item Attributes: Barcode, Brand, Category, Mfr Part Number, Part Description, Part Number, Product Name, Regular Stock, Sub Category, Weight (combined).
  • Turn 14 Item Data: AAIA Part Type Description, Application Summary, Associated Comments, Label Description, Market Description, Product Description (Abbreviated, Extended, Invoice, Long, Short), Slang Description, UN/SPSC Description.
  • Turn 14 Pricing: Dealer, Jobber, MAP, Purchase Cost, Retail.
  • Turn 14 Inventory: Total Warehouse Inventory.
  • Turn 14 Dimensions: Height, Length, Width (of largest package).
  • Turn 14 Dropship Fee: Dropship Fee.
  • Turn 14 Estimated Ground Continental US Base Rate: Average, Maximum, Minimum.
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 [Primary]” along with action buttons: Delete, Duplicate, and Save. 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, Category 3, Description, and Title. 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.
  • Inventory Variant Fields: Includes fields like Master SKU, SKU, ASIN, All Images, Allow Backorders, Archived, Bin Location, Cost, Description, Dimension Unit, Dropship Fee, GTIN, Height, Length, MAP, MPN, MSRP, Quantity, Reference Identifier, Shipping Cost, Source List Price, Title, UPC, Weight, Weight Unit, and Width. Similar mapping options and rules are available for each field.
  • Custom Fields: There are sections for 100 custom parent fields, 100 custom variant fields, and 10 custom aggregate fields, allowing for additional flexibility in mapping.
  • Rules Section: A specific rule named “Automotive Master SKU (First 3 letters of Brand+MPN)” is visible, which combines the first three letters of the Brand with the MPN to create a unique Master SKU. You can also create new rules using the “New Rule” button.
This interface provides a comprehensive way to map Turn 14 data, with dropdowns for selecting source fields and options to fine-tune the import process.
Complete Field Mappings
Turn 14 Field Maps To Example Purpose Status
Part Number (Item Attributes) Flxpoint Inventory Parent: Parent SKU PART123 Identifies the parent product in Flxpoint Don't Map
All Images Flxpoint Inventory Parent: All Images - Imports product images Don't Map
Brand (Item Attributes) Flxpoint Inventory Parent: Brand Acme Records the product brand Direct Copy
Category (Item Attributes) Flxpoint Inventory Parent: Category 1 Accessories Assigns the first-level category Direct Copy
Sub Category (Item Attributes) Flxpoint Inventory Parent: Category 2 Helmets Assigns the second-level category Direct Copy
Category 3 Flxpoint Inventory Parent: Category 3 - Assigns the third-level category Don't Map
Product Description - Long (Item Data) Flxpoint Inventory Parent: Description A high-quality helmet for safety. Provides the product description Direct Copy
Product Name (Item Attributes) Flxpoint Inventory Parent: Title Acme Safety Helmet Sets the product title Direct Copy
Part Number (Item Attributes) Flxpoint Inventory Variant: Master SKU PART123 Primary identifier for linking in Flxpoint Direct Copy
SKU Flxpoint Inventory Variant: SKU - Identifies the variant in Flxpoint Don't Map
ASIN Flxpoint Inventory Variant: ASIN - Records the Amazon Standard Identification Number Don't Map
All Images Flxpoint Inventory Variant: All Images - Imports variant images Don't Map
Allow Backorders Flxpoint Inventory Variant: Allow Backorders - Determines if backorders are allowed Don't Map
Archived Flxpoint Inventory Variant: Archived - Marks the variant as archived Don't Map
Bin Location Flxpoint Inventory Variant: Bin Location - Records the warehouse bin location Don't Map
Purchase Cost (Pricing) Flxpoint Inventory Variant: Cost 50.00 Records the cost to purchase the item Direct Copy
Description Flxpoint Inventory Variant: Description - Provides the variant description Don't Map
Dimension Unit Flxpoint Inventory Variant: Dimension Unit - Specifies the unit for dimensions (e.g., inches) Don't Map
Dimension Unit (Abbreviated) Flxpoint Inventory Variant: Dimension Unit (Abbreviated) - Short form of the dimension unit (e.g., in) Don't Map
Dropship Fee (Dropship Fee) Flxpoint Inventory Variant: Dropship Fee 5.00 Records the calculated dropship fee Direct Copy
GTIN Flxpoint Inventory Variant: GTIN - Records the Global Trade Item Number Don't Map
Height (of largest package) (Dimensions) Flxpoint Inventory Variant: Height 10.00 Records the height of the largest package Direct Copy
Length (of largest package) (Dimensions) Flxpoint Inventory Variant: Length 20.00 Records the length of the largest package Direct Copy
MAP (Pricing) Flxpoint Inventory Variant: MAP 75.00 Records the Minimum Advertised Price Direct Copy
Mfr Part Number (Item Attributes) Flxpoint Inventory Variant: MPN MPN123 Records the Manufacturer Part Number Direct Copy
Retail (Pricing) Flxpoint Inventory Variant: MSRP 100.00 Records the Manufacturer's Suggested Retail Price Direct Copy
Total Warehouse Inventory (Inventory) Flxpoint Inventory Variant: Quantity 50 Records the available stock quantity Direct Copy
Reference Identifier Flxpoint Inventory Variant: Reference Identifier - Additional identifier for the variant Don't Map
Shipping Cost Flxpoint Inventory Variant: Shipping Cost - Records the shipping cost for the variant Don't Map
Source List Price Flxpoint Inventory Variant: Source List Price - Records the source list price Don't Map
Title Flxpoint Inventory Variant: Title - Sets the variant title Don't Map
Barcode (Item Attributes) Flxpoint Inventory Variant: UPC 012345678905 Records the Universal Product Code Direct Copy
Weight (combined) (Item Attributes) Flxpoint Inventory Variant: Weight 2.5 Records the combined weight of the item Direct Copy
Weight Unit Flxpoint Inventory Variant: Weight Unit - Specifies the unit for weight (e.g., pounds) Don't Map
Weight Unit (Abbreviated) Flxpoint Inventory Variant: Weight Unit (Abbreviated) - Short form of the weight unit (e.g., lb) Don't Map
Width (of largest package) (Dimensions) Flxpoint Inventory Variant: Width 15.00 Records the width of the largest package Direct Copy
Mapping Rules
  • Automotive Master SKU Rule: A predefined rule named "Automotive Master SKU (First 3 letters of Brand+MPN)" is applied. It:
    • Runs always with 3 actions modifying the Incoming Value.
    • Combines the first 3 letters of the Brand (e.g., "Acme" → "Acm") with the MPN (e.g., "MPN123") to create a Master SKU (e.g., "AcmMPN123").
  • Hardcoded Attributes: The following attributes are hardcoded and not configurable:
    • Shipped in Multiple Boxes
    • EPA
    • Prop65
    • Carb Acknowledgement Required
    • Vehicle Fitment ID

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.
  • Missing Inventory Data:
    • Ensure required fields like “Quantity” are mapped correctly in the mapping template.
    • Check if the Turn 14 API is returning data by reviewing logs using "View Logs."
  • Fitment Data Not Syncing:
    • Confirm that the "Save Vehicle Fitments Ids" setting is enabled.
    • Ensure the sync is running on a Monday or Thursday, as fitment data is only retrieved on those days.
  • 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 inventory quantities aren’t updating, check the “Total Warehouse Inventory” field in the mapping template. If it’s set to “Don’t Map,” Flxpoint won’t import stock levels.

This section provides key details about the Turn 14 Get Inventory [Primary] integration to help you understand the process:
  • Current Date and Time: As of 06:05 PM -04 on Thursday, May 22, 2025, this integration is fully operational for retrieving inventory from Turn 14.
  • API Connection: Uses the Turn 14 API at https://api.turn14.com to fetch inventory data via multiple endpoints.
  • Fitment Data Schedule: If "Save Vehicle Fitments Ids" is enabled, fitment data is synced only on Mondays and Thursdays.
  • Dropship Fee Logic: Automatically calculated based on getChargedFee and getChargedPercent values.
Pro Tip: Regularly check your API credentials to ensure uninterrupted access to Turn 14’s data.

Conclusion
With the Turn 14 Get Inventory [Primary] integration, you can effortlessly sync inventory data like stock levels, pricing, and product details into Flxpoint. The detailed mapping template and flexible configurations make it easy to manage your inventory, while automotive-specific features like vehicle fitment IDs help you cater to specialized needs. Happy syncing!
 
 

Get Inventory (Secondary)

Supported | Turn 14 - Get Inventory [Secondary]

Introduction to Turn 14 Get Inventory [Secondary] Integration
Welcome to the Turn 14 Get Inventory [Secondary] integration guide! This integration helps you update inventory quantities in Flxpoint by syncing the latest stock data from Turn 14. It’s designed to focus on inventory updates since the last sync, making sure your stock levels are always accurate. Let’s dive into the setup process with clear steps and examples to get you started!

The Turn 14 Get Inventory [Secondary] integration connects your Flxpoint system to Turn 14 to:
  • Retrieve updated inventory quantities 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/token endpoint, passing your client_id and client_secret.
  • Fetch Inventory Updates: A GET request is made to the /v1/inventory/updates endpoint 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 Inventory quantities across all warehouses for each item, providing a consolidated stock level.
  • Syncing: The updated inventory data is mapped to Flxpoint fields (e.g., Quantity) 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., every 15 minutes) 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 [Secondary].”
  • 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).
    Click Test Connection to verify it works, then save.
  • 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 (GIP) Once per day Avoid scheduling more than once daily to prevent API throttling.
Get Inventory Secondary (GIS) Hourly Can safely run hourly. Only pulls updates since the last successful run.
Important Notes
  • GIP should not be scheduled more than once per 24 hours.
  • GIS is designed to be run more frequently and is safe to schedule hourly.
  • Running GIP too often can reduce overall performance and increase the chance of failures due to Turn 14's rate limits.
  • When both GIP and GIS are enabled, GIS should be your primary recurring update job.
  • GIP 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 [Secondary].”
  • 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.
  • Field: Map a specific Turn 14 field (e.g., “Total Warehouse Inventory”) to a Flxpoint field.
  • Value: Set a constant value for all inventory items.
Available Source Fields
  • Turn 14 Inventory: Total Warehouse Inventory.
What the Mapping Interface Shows
The mapping interface for this integration is a focused screen designed to map Turn 14’s inventory updates to Flxpoint fields. At the top, you’ll see the title “Get Inventory [Secondary]” with action buttons: Delete, Duplicate, and Save. The interface focuses solely on mapping to Flxpoint Inventory Variant fields.
  • Inventory Variant Fields: Includes fields like Allow Backorders and Quantity. For each field, you can select mapping options (e.g., Don’t Map, Set To Empty, Direct Copy, Field, Value) and apply rules if needed.
  • Custom Aggregate Fields: There’s a section for 5 custom aggregate fields, allowing for additional flexibility in mapping.
  • Minimal Mapping: Since this integration focuses on inventory updates, only a few fields are available, primarily centered around stock quantities.
This interface is streamlined to ensure quick and efficient mapping of inventory updates, with dropdowns for selecting source fields and options to customize the import process.
Complete Field Mappings
Turn 14 Field Maps To Example Purpose Status
Allow Backorders Flxpoint Inventory Variant: Allow Backorders - Determines if backorders are allowed Don't Map
Total Warehouse Inventory (Inventory) Flxpoint Inventory Variant: Quantity 50 Records the summed stock quantity across all warehouses 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.
  • Inventory Not Updating:
    • Ensure the “Total Warehouse Inventory” field is mapped correctly 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 [Secondary] integration to help you understand the process:
  • Current Date and Time: As of 06:05 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.com to fetch inventory updates via the /v1/inventory/updates endpoint.
  • 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 [Secondary] integration, you can keep your inventory quantities in Flxpoint up-to-date by syncing the latest stock updates from Turn 14. The streamlined 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 Fulfillment Requests

Supported | Turn 14 - Send Fulfillment Requests

Introduction to Turn 14 Send Fulfillment Requests Integration
Welcome to the Turn 14 Send Fulfillment Requests integration guide! This integration allows you to send fulfillment requests to Turn 14 directly from Flxpoint, streamlining your order fulfillment process. It handles everything from selecting the cheapest shipping method to creating orders with Turn 14, ensuring your orders are processed efficiently. Let’s walk through the setup process with clear steps and examples to get you started!

The Turn 14 Send Fulfillment Requests integration connects your Flxpoint system to Turn 14 to:
  • Send fulfillment requests to Turn 14, automating the order creation process.
  • Select the cheapest shipping method automatically, with options to exclude specific methods or filter by transit days.
  • Map order details like recipient information and fulfillment settings 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 fulfillment requests 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/token endpoint, passing your client_id and client_secret.
  • Request a Quote: A GET request is made to the /v1/quote endpoint to retrieve a quote, which returns a quote_id and 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 Fulfillment 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_quote endpoint. The response includes an order_id, which is saved as the confirmation number in Flxpoint’s database.
  • Syncing: Order details (e.g., recipient address, order notes) 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 ensure faster shipping methods are selected, especially for time-sensitive orders.

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 Fulfillment 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 Fulfillment Requests.”
  • 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).
    Click Test Connection to verify it works, then save.
  • 3 Configure Settings: Set up shipping method exclusions, define the Max Fulfillment 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 fulfillment requests. 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 Fulfillment Requests.”
  • 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 (e.g., “Shipping Address: Address Line 1”) to a Turn 14 field.
  • Value: Set a constant value for all fulfillment requests.
  • Mapping Set: Apply a predefined transformation or mapping table.
Available Source Fields
  • Billing Address: Address Line 1, Address Line 2, City, Company Name, Country, Country Code, Email, First Name, Full Name, Last Name, Phone, Postal Code, State, State Code.
  • Fulfillment Request: Estimated Dropship Fee, Estimated Shipping Cost, Fulfillment Request Number, Generated At, Note, Sent At, Total Cost, Total Weight (lbs).
  • Fulfillment Request Item: Bin Location, Cost, MPN, PO Line Item #, Quantity, SKU, Subtotal, Title, UPC.
  • Shipping Address: Address Line 1, Address Line 2, City, Company Name, Country, Country Code, Email, First Name, Full Name, Last Name, Phone, Postal Code, State, State Code.
What the Mapping Interface Shows
The mapping interface for this integration is a detailed screen designed to map Flxpoint data to Turn 14 fields for fulfillment requests. At the top, you’ll see the title “Send Fulfillment Requests” with action buttons: Delete, Duplicate, and Save. The interface is organized into several sections, each mapping Flxpoint fields to specific Turn 14 field categories.
  • Turn 14 Max Fulfillment Days Field: Includes the Max Fulfillment Days field, where you can set a transit days filter (e.g., to exclude shipping methods with transit times exceeding a specified value).
  • Turn 14 Order Field: Includes the Order Notes field, allowing you to send additional notes with the order.
  • Turn 14 Quote Location Field: Includes the Hold Until Entire Order Can Ship field, which determines if the order should wait until all items are ready to ship.
  • Turn 14 Recipient Field: Includes fields like Address Line 1, City, Is Shop Address?, Name, Phone Number, State, Zip, Address Line 2, Company, Country, and Email Address. These fields map recipient details for the order, such as the shipping address.
Each field offers mapping options (e.g., Don’t Map, Set To Empty, Direct Copy, Field, Value, Mapping Set) and a rules section for further customization. This interface ensures you can precisely control which order details are sent to Turn 14.
Complete Field Mappings
Flxpoint Field Maps To Example Purpose Status
Max Fulfillment Days Turn 14 Max Fulfillment Days Field: Max Fulfillment Days - 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 Quote Location Field: Hold Until Entire Order Can Ship True Determines if the order waits until all items are ready Direct Copy
Shipping Address: Address Line 1 Turn 14 Recipient Field: Address Line 1 123 Main St Sets the primary address line for the recipient Direct Copy
Shipping Address: City Turn 14 Recipient Field: City New York Sets the city for the recipient’s address Direct Copy
Is Shop Address? Turn 14 Recipient Field: Is Shop Address? False Indicates if the address is a shop address Direct Copy
Shipping Address: Full Name Turn 14 Recipient Field: Name John Doe Sets the recipient’s name Direct Copy
Shipping Address: Phone Turn 14 Recipient Field: Phone Number 555-123-4567 Sets the recipient’s phone number Direct Copy
Shipping Address: State Turn 14 Recipient Field: State New York Sets the state for the recipient’s address Direct Copy
Shipping Address: Postal Code Turn 14 Recipient Field: Zip 10001 Sets the zip code for the recipient’s address Direct Copy
Shipping Address: Address Line 2 Turn 14 Recipient Field: Address Line 2 - Sets the secondary address line for the recipient Don't Map
Shipping Address: Company Name Turn 14 Recipient Field: Company - Sets the company name for the recipient Don't Map
Shipping Address: Country Turn 14 Recipient Field: Country - Sets the country for the recipient’s address Don't Map
Shipping Address: Email Turn 14 Recipient Field: Email Address - Sets the recipient’s email address Don't Map

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 Fulfillment 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 fields like Address Line 1, City, Name, Phone Number, State, and Zip are mapped correctly in the mapping template.
    • 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 fulfillment request ID and log details for investigation.
Diagnostic Tip: If no shipping methods are available, try removing exclusions or increasing the Max Fulfillment Days value to allow more options.

This section provides key details about the Turn 14 Send Fulfillment Requests integration to help you understand the process:
  • Current Date and Time: As of 06:29 PM -04 on Thursday, May 22, 2025, this integration is fully operational for sending fulfillment requests to Turn 14.
  • API Connection: Uses the Turn 14 API at https://api.turn14.com to send fulfillment requests via the /v1/quote and /v1/order/from_quote endpoints.
  • Shipping Method Selection: Automatically selects the cheapest method, with options to exclude methods or filter by transit days.
  • Confirmation Number: The Turn 14 order_id is 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 Fulfillment Requests integration, you can automate the process of sending orders to Turn 14, ensuring efficient fulfillment with the cheapest shipping methods. The detailed mapping template and flexible configurations make it easy to customize order details, while the streamlined API workflow ensures reliability. Happy fulfilling!
 
 

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/token endpoint, passing your client_id and client_secret.
  • Fetch Tracking Details: A GET request is made to the /v1/tracking/package_details endpoint 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_date and end_date parameters 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).
    Click Test Connection to verify it works, then save.
  • 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 your system’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.
This interface provides a comprehensive way to map shipment data, with dropdowns for selecting source fields and options to fine-tune the import process.
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_date and end_date parameters 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."
  • 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:33 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.com to fetch shipment details via the /v1/tracking/package_details endpoint.
  • Date Range Parameters: Requires start_date and end_date to 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!
 
 

Get Invoices 

Supported | Turn 14 - Get Fulfillment Request Invoices

Introduction to Turn 14 Get Fulfillment Request Invoices Integration
Welcome to the Turn 14 Get Fulfillment Request Invoices integration guide! This integration allows you to retrieve invoice details for fulfillment requests from Turn 14 and sync them into Flxpoint. It helps you manage financial records by mapping invoice data, such as invoice numbers, totals, and item details, to your system. Let’s walk through the setup process with clear steps and examples to get you started!

The Turn 14 Get Fulfillment Request Invoices integration connects your Flxpoint system to Turn 14 to:
  • Retrieve invoice details, including invoice numbers, dates, totals, and itemized costs, for fulfilled orders.
  • Sync invoice data for fulfillment requests, linking them via the Fulfillment Request Number.
  • Map invoice and invoice item details to Flxpoint fields for accurate financial tracking.

The integration follows a structured process to fetch invoice 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/token endpoint, passing your client_id and client_secret.
  • Fetch Invoice Details: A GET request is made to the /v1/invoices endpoint with query parameters:
    • start_date: Calculated as the `end_date` minus the number of days specified in the integration config.
    • end_date: Set to the current date (the date of the sync).
    For example, if the number of days is set to 7 and the sync runs on 2025-05-22, then `end_date` is 2025-05-22, and `start_date` is 2025-05-15.
  • Map Invoices to Fulfillment Requests: The integration retrieves invoice data for fulfillment requests, using the Fulfillment Request Number to link invoices to the corresponding requests in Flxpoint.
  • Syncing: Invoice data (e.g., invoice number, total price, item quantities) 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 smaller number of days (e.g., 3) in the integration config when testing to pull a manageable amount of invoice data and ensure accurate mapping.

You can customize the integration with these settings:
  • Number of Days: Specify a numeric value in the integration config to define the date range for invoice retrieval (e.g., 7 days to pull invoices from the last week).
  • Scheduling: Run the integration manually or schedule it (e.g., daily) using "Adjust Schedule."
  • Mapping Template: Define which invoice 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 invoice data.

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 Fulfillment Request Invoices.”
  • 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).
    Click Test Connection to verify it works, then save.
  • 3 Configure Settings: Set the number of days for invoice 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 invoice 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 Fulfillment Request Invoices.”
  • 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., “Invoice Number”) to a Flxpoint field.
  • Value: Set a constant value for all invoices.
  • Mapping Set: Apply a predefined transformation or mapping table.
  • Option: Select a specific option for certain fields (e.g., Invoice Date, Cost).
Available Source Fields
  • Turn 14 Invoice: Comments, Date, Discount Amount, Freight, Invoice Number, Purchase Order Number, Total Price, Website Order Number.
  • Turn 14 Invoice Item: Line Notes, Part Description, Part Number, Product Group Part Number, Quantity, Total Price, Unit Price.
What the Mapping Interface Shows
The mapping interface for this integration is a detailed screen designed to map Turn 14 invoice data to Flxpoint fields. At the top, you’ll see the title “Get Fulfillment Request Invoices” with action buttons: Delete, Duplicate, and Save. The interface is divided into two main sections: mapping to Flxpoint Source Invoice fields and mapping to Flxpoint Source Invoice Item fields.
  • Source Invoice Fields: Includes fields like Fulfillment Request Number, Invoice Number, Fee Cost, Invoice Date, Invoice Status, Other Cost, Shipping Cost, and Tax Cost. For each field, you can select mapping options (e.g., Don’t Map, Set To Empty, Direct Copy, Field, Value, Mapping Set, Option) and apply rules if needed.
  • Source Invoice Item Fields: Includes fields like Quantity, All Custom Fields, Cost, Invoice Item Type, Per Unit Cost, SKU, and Title. Similar mapping options and rules are available for each field.
This interface provides a comprehensive way to map invoice data, with dropdowns for selecting source fields and options to fine-tune the import process.
Complete Field Mappings
Turn 14 Field Maps To Example Purpose Status
Turn 14 Invoice: Purchase Order Number Flxpoint Source Invoice Field: Fulfillment Request Number FR12345 Links the invoice to the correct fulfillment request Direct Copy
Turn 14 Invoice: Invoice Number Flxpoint Source Invoice Field: Invoice Number - Records the invoice number from Turn 14 Don't Map
Fee Cost Flxpoint Source Invoice Field: Fee Cost - Records any additional fees on the invoice Don't Map
Invoice Date Flxpoint Source Invoice Field: Invoice Date - Records the date of the invoice Don't Map
Invoice Status Flxpoint Source Invoice Field: Invoice Status - Records the status of the invoice Don't Map
Other Cost Flxpoint Source Invoice Field: Other Cost - Records other miscellaneous costs Don't Map
Shipping Cost Flxpoint Source Invoice Field: Shipping Cost - Records the shipping cost on the invoice Don't Map
Tax Cost Flxpoint Source Invoice Field: Tax Cost - Records the tax amount on the invoice Don't Map
Turn 14 Invoice Item: Quantity Flxpoint Source Invoice Item Field: Quantity 3 Records the quantity of items invoiced Direct Copy
All Custom Fields Flxpoint Source Invoice Item Field: All Custom Fields - Imports all custom fields if set to Direct Copy Don't Map
Cost Flxpoint Source Invoice Item Field: Cost - Records the total cost of the item Don't Map
Invoice Item Type Flxpoint Source Invoice Item Field: Invoice Item Type - Records the type of invoice item Don't Map
Turn 14 Invoice Item: Unit Price Flxpoint Source Invoice Item Field: Per Unit Cost 25.00 Records the cost per unit of the item Direct Copy
Turn 14 Invoice Item: Product Group Part Number Flxpoint Source Invoice Item Field: SKU XYZ789 Records the SKU for the invoiced item Direct Copy
Title Flxpoint Source Invoice Item Field: Title - Records the title of the invoiced item Don't Map

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 Invoice Data Returned:
    • Ensure the date range (based on the number of days in the config) covers a period where invoices exist (e.g., check the date range in Turn 14).
    • Verify the API response by reviewing logs using "View Logs."
  • Incorrect Mapping of Invoices:
    • Ensure the Fulfillment Request Number field is correctly mapped in the template to match invoices to the right requests.
    • Check that required fields like Quantity and Per Unit Cost are mapped to capture essential invoice details.
  • 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 invoice ID and log details for investigation.
Diagnostic Tip: If invoices aren’t mapping correctly, double-check that the Fulfillment Request Number field is mapped, as it’s critical for linking invoice data to the correct request.

This section provides key details about the Turn 14 Get Fulfillment Request Invoices integration to help you understand the process:
  • Current Date and Time: As of 06:36 PM -04 on Thursday, May 22, 2025, this integration is fully operational for retrieving invoice data from Turn 14.
  • API Connection: Uses the Turn 14 API at https://api.turn14.com to fetch invoice details via the /v1/invoices endpoint.
  • Date Range Configuration: The date range is defined by a number of days in the config, with `end_date` as the current date and `start_date` calculated as `end_date` minus the specified days.
  • Mapping by FR#: Uses the Fulfillment Request Number to map invoice 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 Fulfillment Request Invoices integration, you can effortlessly sync invoice details like invoice numbers, totals, and itemized costs into Flxpoint, keeping your financial records accurate. The detailed mapping template and flexible configurations make it easy to manage your invoice data, ensuring seamless integration with your fulfillment process. Happy invoicing!
 
 

 

 

Related Articles

PartsNetWeb

PartsNetWeb is an integration source tailored connectivity with distributors offe...