Flxpoint Knowledge

Contact us

Zanders as Source

Table of Contents

How To Connect Product Operations Order Operations

Kroll is a trusted wholesale distributor specializing in tactical, outdoor, and law enforcement products. When integrated as a source in Flxpoint, it allows you to efficiently import product catalogs, synchronize inventory, and automate order fulfillment via FTP or API connections. With Kroll, you gain access to up-to-date inventory data and seamless order processing for their extensive product range. 
 

 

How To Connect

📋 Phase 1: Creating Your Zanders 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 "Zanders" 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 Zanders
  • Send Fulfillment Requests - Sends orders to Zanders automatically
  • Get Shipments - Pulls shipping information from Zanders
  • Get Inventory [Secondary] - Sets up an additional inventory feed
Note: You can activate any combination of these integrations based on your business needs.
🔐 Phase 2: Setting Up FTP Connection +
Select Zanders FTP Integration
From the integration list, select Zanders FTP to open the connection setup screen for inventory retrieval.
Configure FTP Connection Details
Fill out the New Connection form with these FTP credentials (used for Get Inventory operations):
  • Connection Name: "Zanders FTP Connection" (or any descriptive name)
  • FTP Protocol: Choose FTP or SFTP as specified by Zanders
  • FTP Host: The server address (e.g., ftp.zanders.com)
  • FTP Port: Usually 21 for standard FTP
  • FTP User: Your Zanders-provided FTP username
  • FTP Password: Your Zanders-provided FTP password
Important: These credentials are provided by Zanders when your account is set up. If you don't have them, contact your Zanders representative.
Advanced FTP Settings
Click on Advanced Settings to configure additional options:
  • File Transfer Mode: Choose ASCII for text files or Binary for most other files
  • Maintain Constant Connection: Toggle ON to keep connection active throughout the integration
  • Use Unbuffered Private Data Channel: Usually leave OFF unless needed for troubleshooting
Tip: After configuring all settings, 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, you'll need to create a separate connection with your account credentials:
  • Connection Name: "Zanders Account Connection" (or similar)
  • Main Account Username: Your primary Zanders account username
  • Main Account Password: Your primary Zanders account password
  • Environment: Production (or Test if available)
Category-Specific Account Setup (if applicable)
If you have separate accounts for different product categories, enter those credentials too:
  • Accessory Account Username/Password: For accessory products
  • Firearm Account Username/Password: For firearm products
Note: Leave these fields blank if you use a single account for all product types.
Automated Order Settings
Configure how orders will be processed:
  • Toggle Automatically Send Orders ON to have Flxpoint automatically send orders to Zanders
  • Set any additional order rules or conditions as needed
Click Test Connection and then Save Connection once verified.
✅ Phase 4: Mapping and Activation +
Create Field Mapping
After setting up your connection, you'll need to map Zanders 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, make sure to 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 to identify Zanders products in your system.
Activate and Verify
Complete the setup by clicking Save and Complete. Your Zanders integration is now active and will run based on your settings.
Next Steps: The initial inventory sync may take some time to complete. You can monitor the progress in the Integrations section of your Flxpoint dashboard.
Zanders FTP Authentication
Zanders Order Processing

   


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 | Zanders - Get Inventory [Primary]

Introduction to Zanders - Get Inventory [Primary] Integration
The Zanders - Get Inventory [Primary] integration automates the process of updating your product inventory by pulling detailed data from Zanders through a static FTP feed. It keeps your inventory—SKUs, prices, quantities, and attributes like dimensions—fresh and accurate in your Flxpoint system at both Parent and Variant levels. The process involves connecting to Zanders’ FTP server, setting up configurations, mapping fields, applying custom rules, and running the integration (either manually or on a schedule). Let’s dive into each step to get you started!

The Zanders - Get Inventory [Primary] integration connects your Flxpoint system to Zanders to:
  • Retrieve detailed product data, including SKUs, pricing, quantities, and attributes, from a static FTP feed.
  • Map Zanders’ product fields to your Flxpoint system for accurate inventory management at both Parent and Variant levels.
  • Ensure seamless updates to keep your inventory data current with minimal manual intervention.

This integration follows a clear, step-by-step process to bring Zanders’ product data into your Flxpoint system:
  • FTP Connection: Establishes a secure connection to Zanders’ FTP server using the credentials they provide.
  • File Retrieval: Downloads product data files from the specified Inbound Remote File Folder. These files contain key details like SKU, Description, Price, and Quantity.
  • Inventory Processing: Extracts the data and updates your Flxpoint inventory, mapping it to Parent fields (like Parent SKU, Brand) and Variant fields (like SKU, Cost, Quantity).
What Does the Product Data Look Like?
Let’s take a peek at a sample product data structure from Zanders. This is what the integration retrieves and processes:
{
  "ItemNumber": "ZND12345",
  "Description1": "Zanders Rifle Scope",
  "Description2": "High Precision 4x Zoom",
  "Manufacturer": "Zanders Optics",
  "MSRP": 199.99,
  "MAPPrice": 179.99,
  "Price1": 150.00,
  "Quantity1": 50,
  "UPC": "012345678905",
  "Height": 5,
  "Length": 10,
  "Width": 3,
  "Weight": 2.5,
  "Serialized": "Yes"
}
Understanding the Data: Each entry represents a product. For example, "ItemNumber": "ZND12345" is the SKU, which maps to Flxpoint’s Parent SKU and Variant SKU fields. The integration uses this data to update your inventory, ensuring all details are accurate.

Let’s set up the integration by customizing a few key settings to match your needs:
  • FTP Connection Settings:
    • Connection Name: Give your connection a name, like "ZandersFTP".
    • FTP Protocol: Choose the protocol Zanders uses—FTP, SFTP, or FTPS.
    • FTP Host: Enter the server address provided by Zanders, such as ftp.zanders.com.
    • FTP Port: Use standard ports (e.g., 21 for FTP, 22 for SFTP).
    • FTP User & Password: Input the credentials Zanders gave you.
    • Maintain Constant Connection: Turn this on if you’re dealing with large files to avoid interruptions (optional).
  • Inbound Remote File Folder: Specify the folder on Zanders’ FTP server where the product data files are stored, like /zanders-products. This is where the integration will look for files to download.
  • Sender/Receiver Identifiers: These settings ensure smooth communication between your system and Zanders’ system:
    • Our Sender/Receiver ID: Set to FLXPOINT—this identifies your system.
    • Our Sender/Receiver Qualifier: Use ZZ, a standard code for a mutually defined identifier.
    • Their Sender/Receiver ID: Enter the ID provided by Zanders, such as ZANDERSID.
    • Their Sender/Receiver Qualifier: Set to 12, which typically represents a telephone number or similar identifier in EDI standards.
What’s an Inbound Remote File Folder? Imagine this as a shared mailbox on Zanders’ server where they drop the product data files. The integration checks this folder to pick up the latest files.
Sender/Receiver Identifiers: Think of these as a secret handshake between your system and Zanders’—they ensure both sides know who’s sending and receiving the data.

Follow these steps to get the Zanders - Get Inventory [Primary] integration up and running:
  • 1 Establish FTP Connection: Enter the FTP credentials provided by Zanders (Connection Name, FTP Protocol, FTP Host, FTP Port, FTP User, FTP Password). Click the Test Connection button to verify it works, then save.
  • 2 Configure Advanced Settings (Optional): Enable "Maintain Constant Connection" if you’re handling large files to ensure smooth downloads.
  • 3 Define File Location: Set the Inbound Remote File Folder (e.g., /zanders-products) where the integration will retrieve product data files.
  • 4 Set Sender/Receiver Identifiers: Configure the identifiers (Our Sender/Receiver ID: FLXPOINT, Qualifier: ZZ; Their Sender/Receiver ID: e.g., ZANDERSID, Qualifier: 12).
  • 5 Create a Mapping Template: Head to the Mapping Dashboard ("Zanders - Get Inventory [Primary]") to define how Zanders’ fields map to your inventory (see the "Mapping Template" section below).
  • 6 Configure Mapping Rules: Set up custom rules to transform data during mapping (see the "Mapping Rules" section below).
  • 7 Run the Integration: Click to run manually, or set up a schedule for automatic updates.

The integration setup interface for “Zanders - Get Inventory [Primary]” is where you begin connecting Zanders (or any other integration) to your Flxpoint system. Let’s explore what you’ll see and interact with when setting up this connection:
  • Integration Title: At the top, you’ll see the integration name, such as “Zanders - Get Inventory [Primary],” clearly labeled to indicate which integration you’re configuring.
  • FTP Connection Settings Section: This section contains a form with fields to input your FTP credentials:
    • Connection Name: A text field where you can name your connection, like "ZandersFTP".
    • FTP Protocol: A dropdown menu to select the protocol:
    • FTP Host: A text field for the server address, such as ftp.zanders.com.
    • FTP Port: A numeric field for the port number (e.g., 21 for FTP, 22 for SFTP).
    • FTP User & Password: Text fields to enter the username and password provided by Zanders.
    • Maintain Constant Connection: A toggle switch you can enable if you’re dealing with large files to prevent interruptions.
  • Inbound Remote File Folder Field: A text field where you specify the folder on Zanders’ FTP server where product data files are stored, such as /zanders-products.
  • Sender/Receiver Identifiers Section: This section includes fields to configure communication identifiers:
    • Our Sender/Receiver ID & Qualifier: Text fields to set your system’s identifier (e.g., FLXPOINT) and qualifier (e.g., ZZ).
    • Their Sender/Receiver ID & Qualifier: Text fields for Zanders’ identifier (e.g., ZANDERSID) and qualifier (e.g., 12).
  • Action Buttons: At the bottom, you’ll find buttons to manage your setup:
    • Test Connection: A button to verify that your FTP credentials work and the connection to Zanders’ server is successful.
    • Save: A button to save your configuration settings.
Next Steps
Once you’ve set up the integration connection, you’ll move on to defining how Zanders’ data maps to your Flxpoint inventory in the "Mapping Template" section below.

The Mapping Template is where you define how Zanders’ product data fields connect to your Flxpoint inventory fields. Think of it as a bridge that ensures the data flows correctly into your system, whether it’s for Parent fields (like a product’s main SKU) or Variant fields (like a specific product’s cost or quantity). Let’s break it down!
Mapping Fields
Below is a table of fields you can map, complete with examples and purposes. The labels (T for text, N for numbers) match what you’ll see in the dashboard:
Field Maps To Example Purpose Status
Item Number (T) Parent: Parent SKU ZND12345 Identifies the product at the parent level Required
Item Number (T) Variant: SKU ZND12345 Identifies the product at the variant level Required
Item Number (T) Variant: Master SKU ZND12345 Links the variant to the parent SKU Required
Manufacturer (T) Parent: Brand Zanders Optics Records the brand of the product Optional
Category (T) Parent: Category 1 Optics Records the primary category of the product Optional
Description 1 (T) Parent: Description Zanders Rifle Scope Records the primary description of the product Optional
Description 1 (T) Variant: Title Zanders Rifle Scope Records the title of the variant (rule: combines with Description 2) Optional
Description 2 (T) Variant: Description High Precision 4x Zoom Records the secondary description of the variant Optional
Price 1 (N) Variant: Cost 150.00 Records the cost of the variant Optional
MAP Price (N) Variant: MAP 179.99 Records the Minimum Advertised Price Optional
MSRP (N) Variant: MSRP 199.99 Records the Manufacturer’s Suggested Retail Price Optional
Quantity 1 (N) Variant: Quantity 50 Records the available quantity for the variant Optional
UPC (T) Variant: UPC 012345678905 Records the UPC code for the variant (rule: removes leading zeros) Optional
Manufacturer Part Number (T) Variant: MPN ZND-MPN-123 Records the Manufacturer Part Number Optional
Height (N) Variant: Height 5 Records the height of the product Optional
Length (N) Variant: Length 10 Records the length of the product Optional
Width (N) Variant: Width 3 Records the width of the product Optional
Weight (N) Variant: Weight 2.5 Records the weight of the product Optional
Serialized (T) Variant: Requires FFL True (if Yes) Indicates if the product requires an FFL (rule: maps "Yes" to True) Optional
Available Source Fields
Zanders provides a rich set of fields in their FTP feed that you can map to your Flxpoint inventory:
  • Zanders Product: Allow Direct Ship (T), Available (N), Category (T), Description 1 (T), Description 2 (T), Height (N), Item Number (T), Large Description (T), Length (N), MAP Price (N), MSRP (N), Manufacturer (T), Manufacturer Part Number (T), Price 1 (N), Price 2 (N), Price 3 (N), Quantity 1 (N), Quantity 2 (N), Quantity 3 (N), Serialized (T), UPC (T), Weight (N), Width (N).
Let’s Break It Down: "Item Number" is Zanders’ way of saying SKU—it’s a unique identifier for each product, like "ZND12345". You’ll map this to Flxpoint’s "Parent SKU" or "Variant SKU" to keep your inventory organized.
Mapping Options
For each field mapping, you can choose from several options to customize how the data is handled:
  • Field: Link a Zanders field (e.g., Item Number) to a Flxpoint field (e.g., Parent SKU). This is the most straightforward way to map data.
  • Value: Set a fixed value for the field (e.g., always set "Category 1" to "Optics"). Handy for applying the same value to all products.
  • Mapping Set: Use tools to combine or manipulate data (e.g., concatenate fields). You can create custom Mapping Sets in Flxpoint for more complex transformations.
  • Rules: Add "if-then" logic to transform data during mapping (e.g., combine Description 1 and Description 2 for Title). Check out the "Mapping Rules" section below for more details.
  • Don’t Map: Skip the field entirely, leaving it unmapped in Flxpoint.
  • Set to Empty: Clear the field in Flxpoint, removing any existing data for that field.
Try This: If you want all products to be categorized under "Optics", select "Value" for the Category 1 field and enter "Optics". Or, use a Mapping Set to combine fields—like merging Description 1 and Description 2 into a single Title.
Summary
You’ve now mapped a total of 19 fields from Zanders to your Flxpoint inventory, covering both Parent and Variant levels. This setup ensures your inventory reflects Zanders’ data accurately. Next, you can fine-tune your mappings with custom rules in the "Mapping Rules" section below.

Mapping Rules let you transform Zanders’ product data as it’s being mapped into Flxpoint. Whether you’re combining fields, applying conditions, or cleaning up data, rules give you the power to shape the data to fit your needs. Think of them as a set of instructions the integration follows to "tweak" the data before it lands in your inventory.
Configured Mapping Rules
Here are the rules currently set up for the Zanders - Get Inventory [Primary] integration:
  • Set True if Serialized = Yes:
    • Type: Conditional (Boolean)
    • Description: Sets the "Requires FFL" field to True if Zanders’ "Serialized" field is "Yes".
    • Logic: 1 condition (Serialized = "Yes"), 1 action (set output to True).
    • Example: If Serialized = "Yes", then Requires FFL becomes True.
  • Remove leading 0 in UPC:
    • Type: Conditional (String)
    • Description: Strips leading zeros from the UPC field for a cleaner format.
    • Logic: 2 conditions (e.g., UPC starts with "0", UPC is not empty), 1 action (remove leading zeros).
    • Example: If UPC = "0012345678905", the rule changes it to "12345678905".
  • Get Source Products - Rule #2:
    • Type: Conditional (String)
    • Description: A custom rule with multiple actions to modify incoming data.
    • Logic: Always runs, with 4 actions (details not specified, but could include cleaning, combining, or formatting data).
    • Example: Might clean up text fields or apply specific formatting to ensure consistency.
  • Desc1 + Desc2:
    • Type: Conditional (String)
    • Description: Combines Description 1 and Description 2 into a single field for the Variant Title.
    • Logic: Always runs, with 2 actions (concatenates Description 1 and Description 2 with a space).
    • Example: If Description 1 = "Zanders Rifle Scope" and Description 2 = "High Precision 4x Zoom", the Title becomes "Zanders Rifle Scope High Precision 4x Zoom".
Why Use Rules? Rules are like a chef’s recipe for your data. For example, "Desc1 + Desc2" mixes two ingredients (Description 1 and Description 2) to create a tastier Title. You can also use rules to clean up data—like removing extra zeros from a UPC—or apply logic, like setting Requires FFL to True for serialized items.
Creating a New Rule
Want to create your own rule? Use the "Create New Rule" feature in the Mapping Dashboard:
  • Rule Name: A text field where you can enter a friendly name to identify the rule later, such as "Set True if Serialized = Yes".
  • Rule Type: A dropdown menu with the following options:
    • Conditional: Use logic to transform data (e.g., if Serialized = "Yes", set Requires FFL to True).
    • Tier: Apply tiered logic, often for pricing or quantities (e.g., if Quantity > 100, set a discount).
  • Input Type: A dropdown menu with the following options:
    • String: For text fields like UPC or Description.
    • Number: For numeric fields like Price or Quantity.
    • Boolean: For true/false fields like Requires FFL.
    • Option Field: For fields with predefined options, like units (e.g., "inch", "pound").
Heads Up: Once you create a rule, you can’t change its Rule Type or Input Type because mappings rely on the structure you define. Plan carefully before hitting Create!
Try This: Create a rule named "Set High Price Flag". Set Rule Type to Conditional and Input Type to Boolean. Add a condition: if Price 1 > 200, set a custom field "HighPrice" to True. This helps you flag expensive items automatically.

Here are some essential details to understand the Zanders - Get Inventory [Primary] integration:
  • Current Date and Time: As of 09:55 AM -04 on Tuesday, May 20, 2025, this integration is fully operational for retrieving inventory data from Zanders.
  • Zanders Integration: Retrieves detailed product data via FTP, including SKUs, pricing, quantities, and attributes like dimensions and weight.
  • Supported Features: Maps product data to both Parent and Variant fields, with custom rules for data transformation (e.g., combining Description 1 and Description 2, removing leading zeros in UPC).
Pro Tip: Test your FTP connection before saving to ensure smooth file retrieval, and double-check your custom rules in the Mapping Dashboard to make sure your data maps perfectly.

If something goes wrong with the integration, here are some steps to help you fix it:
  • FTP Connection Failure: Double-check your FTP credentials (host, port, user, password) and click to test the connection again.
  • File Not Found: Make sure the Inbound Remote File Folder is set correctly and that Zanders has uploaded the product data files to that location.
  • Data Mapping Errors: Review your custom rules (e.g., combining Description 1 and Description 2, removing leading zeros in UPC) in the Mapping Dashboard to ensure they’re working as expected.
  • Incomplete Product Data: Verify that the product data files include all the fields you expect (e.g., Item Number, Price 1) so the mapping works correctly.

Conclusion
With the Zanders - Get Inventory [Primary] integration, you can effortlessly retrieve and map detailed product data from Zanders into your Flxpoint system, keeping your inventory accurate at both Parent and Variant levels. With flexible mapping options, custom rules, and automated retrieval, managing your inventory has never been easier or more reliable.
 
 

Get Inventory (Secondary)

Supported | Zanders - Get Inventory [Secondary]

Introduction to Zanders - Get Inventory [Secondary] Integration
The Zanders - Get Inventory [Secondary] integration automates the process of updating your product inventory by pulling streamlined data from Zanders through a static FTP feed. Unlike the Primary integration, this focuses on updating key Variant-level fields such as SKU, Cost, MAP, MSRP, and Quantity in your Flxpoint system. The process involves connecting to Zanders’ FTP server, setting up configurations, mapping fields, applying custom rules, and running the integration (either manually or on a schedule). Let’s dive into each step to get you started!

The Zanders - Get Inventory [Secondary] integration connects your Flxpoint system to Zanders to:
  • Retrieve essential inventory data, including SKUs, pricing, and quantities, from a static FTP feed.
  • Map Zanders’ inventory fields to your Flxpoint system for accurate Variant-level inventory updates.
  • Ensure seamless updates to keep your inventory data current with minimal manual intervention.

This integration follows a clear, step-by-step process to bring Zanders’ inventory data into your Flxpoint system:
  • FTP Connection: Establishes a secure connection to Zanders’ FTP server using the credentials they provide.
  • File Retrieval: Downloads inventory data files from the specified Inbound Remote File Folder. These files contain key details like SKU, Price, and Quantity.
  • Inventory Processing: Extracts the data and updates your Flxpoint inventory, mapping it to Variant fields (like SKU, Cost, Quantity).
What Does the Inventory Data Look Like?
Let’s take a peek at a sample inventory data structure from Zanders. This is what the integration retrieves and processes:
{
  "ItemNumber": "ZND12345",
  "Available": 1,
  "Price1": 150.00,
  "Price2": 145.00,
  "Price3": 140.00,
  "Quantity1": 50,
  "Quantity2": 30,
  "Quantity3": 20
}
Understanding the Data: Each entry represents a product variant. For example, "ItemNumber": "ZND12345" is the SKU, which maps to Flxpoint’s Variant SKU field. The integration uses this data to update your inventory, focusing on Variant-level fields like pricing and quantity.

Let’s set up the integration by customizing a few key settings to match your needs:
  • FTP Connection Settings:
    • Connection Name: Give your connection a name, like "ZandersFTP_Secondary".
    • FTP Protocol: Choose the protocol Zanders uses—FTP, SFTP, or FTPS.
    • FTP Host: Enter the server address provided by Zanders, such as ftp.zanders.com.
    • FTP Port: Use standard ports (e.g., 21 for FTP, 22 for SFTP).
    • FTP User & Password: Input the credentials Zanders gave you.
    • Maintain Constant Connection: Turn this on if you’re dealing with large files to avoid interruptions (optional).
  • Inbound Remote File Folder: Specify the folder on Zanders’ FTP server where the inventory data files are stored, like /zanders-inventory-secondary. This is where the integration will look for files to download.
  • Sender/Receiver Identifiers: These settings ensure smooth communication between your system and Zanders’ system:
    • Our Sender/Receiver ID: Set to FLXPOINT—this identifies your system.
    • Our Sender/Receiver Qualifier: Use ZZ, a standard code for a mutually defined identifier.
    • Their Sender/Receiver ID: Enter the ID provided by Zanders, such as ZANDERSID.
    • Their Sender/Receiver Qualifier: Set to 12, which typically represents a telephone number or similar identifier in EDI standards.
What’s an Inbound Remote File Folder? Imagine this as a shared mailbox on Zanders’ server where they drop the inventory data files. The integration checks this folder to pick up the latest files.
Sender/Receiver Identifiers: Think of these as a secret handshake between your system and Zanders’—they ensure both sides know who’s sending and receiving the data.

Follow these steps to get the Zanders - Get Inventory [Secondary] integration up and running:
  • 1 Establish FTP Connection: Enter the FTP credentials provided by Zanders (Connection Name, FTP Protocol, FTP Host, FTP Port, FTP User, FTP Password). Click the Test Connection button to verify it works, then save.
  • 2 Configure Advanced Settings (Optional): Enable "Maintain Constant Connection" if you’re handling large files to ensure smooth downloads.
  • 3 Define File Location: Set the Inbound Remote File Folder (e.g., /zanders-inventory-secondary) where the integration will retrieve inventory data files.
  • 4 Set Sender/Receiver Identifiers: Configure the identifiers (Our Sender/Receiver ID: FLXPOINT, Qualifier: ZZ; Their Sender/Receiver ID: e.g., ZANDERSID, Qualifier: 12).
  • 5 Create a Mapping Template: Head to the Mapping Dashboard ("Zanders - Get Inventory [Secondary]") to define how Zanders’ fields map to your inventory (see the "Mapping Template" section below).
  • 6 Configure Mapping Rules (Optional): Set up custom rules to transform data during mapping if needed (see the "Mapping Rules" section below).
  • 7 Run the Integration: Click to run manually, or set up a schedule for automatic updates.

-Jin>
The integration setup interface for “Zanders - Get Inventory [Secondary]” is where you begin connecting Zanders to your Flxpoint system. Let’s explore what you’ll see and interact with when setting up this connection:
  • Integration Title: At the top, you’ll see the integration name, “Zanders - Get Inventory [Secondary],” clearly labeled to indicate which integration you’re configuring.
  • FTP Connection Settings Section: This section contains a form with fields to input your FTP credentials:
    • Connection Name: A text field where you can name your connection.
    • FTP Protocol: A dropdown menu to select the protocol (FTP, SFTP, or FTPS).
    • FTP Host: A text field for the server address.
    • FTP Port: A numeric field for the port number.
    • FTP User & Password: Text fields to enter the username and password provided by Zanders.
    • Maintain Constant Connection: A toggle switch you can enable if you’re dealing with large files to prevent interruptions.
  • Inbound Remote File Folder Field: A text field where you specify the folder on Zanders’ FTP server where inventory data files are stored.
  • Sender/Receiver Identifiers Section: This section includes fields to configure communication identifiers:
    • Our Sender/Receiver ID & Qualifier: Text fields to set your system’s identifier and qualifier.
    • Their Sender/Receiver ID & Qualifier: Text fields for Zanders’ identifier and qualifier.
  • Action Buttons: At the bottom, you’ll find buttons to manage your setup:
    • Test Connection: A button to verify that your FTP credentials work and the connection to Zanders’ server is successful.
    • Save: A button to save your configuration settings.
Next Steps
Once you’ve set up the integration connection, you’ll move on to defining how Zanders’ data maps to your Flxpoint inventory in the "Mapping Template" section below.

The Mapping Template is where you define how Zanders’ inventory data fields connect to your Flxpoint inventory fields. For this integration, the focus is on Variant-level fields like SKU, Cost, and Quantity. Let’s break it down!
Mapping Fields
Below is a table of fields you can map, complete with examples and purposes. The labels (T for text, N for numbers) match what you’ll see in the dashboard:
Field Maps To Example Purpose Status
Item Number (T) Variant: SKU ZND12345 Identifies the product at the variant level Required
Price 1 (N) Variant: Cost 150.00 Records the cost of the variant Optional
Price 2 (N) Variant: MAP 145.00 Records the Minimum Advertised Price Optional
Price 3 (N) Variant: MSRP 140.00 Records the Manufacturer’s Suggested Retail Price Optional
Quantity 1 (N) Variant: Quantity 50 Records the available quantity for the variant Optional
Available Source Fields
Zanders provides a focused set of fields in their FTP feed for this integration, which you can map to your Flxpoint inventory:
  • Zanders Inventory: Available (N), Item Number (T), Price 1 (N), Price 2 (N), Price 3 (N), Quantity 1 (N), Quantity 2 (N), Quantity 3 (N).
Let’s Break It Down: "Item Number" is Zanders’ SKU identifier for each product variant, like "ZND12345". You’ll map this to Flxpoint’s "Variant SKU" to keep your inventory organized. Fields like "Price 1" and "Quantity 1" are typically used for Cost and Quantity, respectively.
Mapping Options
For each field mapping, you can choose from several options to customize how the data is handled:
  • Field: Link a Zanders field (e.g., Item Number) to a Flxpoint field (e.g., Variant SKU). This is the most straightforward way to map data.
  • Value: Set a fixed value for the field (e.g., always set "Quantity" to "0"). Handy for applying the same value to all variants.
  • Mapping Set: Use tools to combine or manipulate data (e.g., concatenate fields). You can create custom Mapping Sets in Flxpoint for more complex transformations.
  • Rules: Add "if-then" logic to transform data during mapping (e.g., set Quantity to 0 if Available is 0). Check out the "Mapping Rules" section below for more details.
  • Don’t Map: Skip the field entirely, leaving it unmapped in Flxpoint.
  • Set to Empty: Clear the field in Flxpoint, removing any existing data for that field.
Try This: If you want to set a default cost for all variants, select "Value" for the Cost field and enter "150.00". Or, use a Rule to set Quantity to 0 if the "Available" field is 0.
Summary
You’ve now mapped a total of 5 fields from Zanders to your Flxpoint inventory, focusing on Variant-level updates. This setup ensures your inventory reflects Zanders’ data accurately. Next, you can fine-tune your mappings with custom rules in the "Mapping Rules" section below.

Mapping Rules let you transform Zanders’ inventory data as it’s being mapped into Flxpoint. Whether you’re adjusting values, applying conditions, or cleaning up data, rules give you the power to shape the data to fit your needs. Think of them as a set of instructions the integration follows to "tweak" the data before it lands in your inventory.
Configured Mapping Rules
Currently, there are no mapping rules configured for the Zanders - Get Inventory [Secondary] integration. You can add custom rules to transform the data as needed—see below for how to create them.
Creating a New Rule
Want to create your own rule? In the Mapping Dashboard, you’ll find a "Create New Rule" option that opens a form with the following fields:
  • Rule Name: A text field where you can enter a friendly name to identify the rule later, such as "Set Quantity to Zero if Unavailable".
  • Rule Type: A dropdown menu with the following options:
    • Conditional: Use logic to transform data (e.g., if Available = 0, set Quantity to 0).
    • Tier: Apply tiered logic, often for pricing or quantities (e.g., if Quantity > 100, set a discount).
  • Input Type: A dropdown menu with the following options:
    • String: For text fields like Item Number.
    • Number: For numeric fields like Price or Quantity.
    • Boolean: For true/false fields (e.g., mapping Available to a true/false condition).
    • Option Field: For fields with predefined options, like units (e.g., "piece", "unit").
Notice: You won’t be able to change the rule type or input type once you create the rule, this is because mapping templates using the rule will be expecting to pass in and receive back the original input type the rule defines.
Once you’ve filled out the form, click the Create button to save your rule.
Try This: Create a rule named "Set Quantity to Zero if Unavailable". In the form, set the Rule Type to "Conditional" and the Input Type to "Number". Add a condition: if Available = 0, set Quantity to 0. Then click "Create" to save the rule. This ensures your inventory reflects accurate stock levels.

Here are some essential details to understand the Zanders - Get Inventory [Secondary] integration:
  • Current Date and Time: As of 09:08 AM -04 on Tuesday, May 20, 2025, this integration is fully operational for retrieving inventory data from Zanders.
  • Zanders Integration: Retrieves streamlined inventory data via FTP, focusing on SKUs, pricing, and quantities for Variant-level updates.
  • Supported Features: Maps inventory data to Variant fields, with the option to add custom rules for data transformation.
Pro Tip: Test your FTP connection before saving to ensure smooth file retrieval, and consider adding custom rules in the Mapping Dashboard if you need to transform data during mapping.

If something goes wrong with the integration, here are some steps to help you fix it:
  • FTP Connection Failure: Double-check your FTP credentials (host, port, user, password) and click to test the connection again.
  • File Not Found: Make sure the Inbound Remote File Folder is set correctly and that Zanders has uploaded the inventory data files to that location.
  • Data Mapping Errors: Review your mappings in the Mapping Dashboard to ensure they’re set up correctly (e.g., mapping Item Number to Variant SKU).
  • Incomplete Inventory Data: Verify that the inventory data files include all the fieldsJon fields you expect (e.g., Item Number, Price 1) so the mapping works correctly.

Conclusion
With the Zanders - Get Inventory [Secondary] integration, you can efficiently retrieve and map streamlined inventory data from Zanders into your Flxpoint system, keeping your Variant-level inventory accurate. With flexible mapping options and the ability to add custom rules, managing your inventory updates has never been easier or more reliable.
 
 



 

Order Operations

It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring an integration between order processing and shipment tracking.    
 

Send Fulfillment Requests

Supported | Zanders - Send Fulfillment Requests

Introduction to Zanders - Send Fulfillment Requests Integration
The Zanders - Send Fulfillment Requests integration automates the process of sending purchase orders (POs) to Zanders for fulfillment. This integration takes your fulfillment requests from Flxpoint—details like shipping addresses, item quantities, and shipping methods—and maps them to Zanders’ required purchase order format, then sends them via FTP. It ensures your orders are accurately communicated to Zanders, streamlining your dropshipping process. The setup involves connecting to Zanders’ FTP server, configuring settings, mapping fields, applying custom rules, and sending the requests. Let’s walk through each step to get you started!

The Zanders - Send Fulfillment Requests integration connects your Flxpoint system to Zanders to:
  • Send purchase orders to Zanders by converting Flxpoint fulfillment requests into Zanders’ required format.
  • Map Flxpoint fields—like shipping addresses, item details, and shipping methods—to Zanders’ purchase order fields for accurate order fulfillment.
  • Automate the delivery of purchase orders to Zanders via FTP, reducing manual effort and ensuring timely order processing.

This integration follows a clear, step-by-step process to send fulfillment requests from Flxpoint to Zanders:
  • Data Extraction: Pulls fulfillment request data from Flxpoint, including shipping addresses, item details (like SKU and quantity), and shipping methods.
  • Field Mapping: Maps Flxpoint data to Zanders’ purchase order fields, such as PO Number, Ship To Address, and Item Number, using a mapping template.
  • FTP Delivery: Sends the formatted purchase order to Zanders’ FTP server in the specified Outbound Remote File Folder for processing.
What Does the Fulfillment Request Data Look Like?
Let’s take a peek at a sample fulfillment request data structure from Flxpoint. This is what the integration maps and sends to Zanders:
{
  "FulfillmentRequest": {
    "FulfillmentRequestNumber": "FR12345",
    "GeneratedAt": "2025-05-20T09:00:00Z",
    "TotalCost": 250.00,
    "Note": "Urgent delivery requested"
  },
  "ShippingAddress": {
    "AddressLine1": "123 Main St",
    "AddressLine2": "Apt 4B",
    "City": "Austin",
    "StateCode": "TX",
    "PostalCode": "78701",
    "FullName": "Jane Doe",
    "Phone": "512-555-1234"
  },
  "FulfillmentRequestItem": {
    "SKU": "ZND12345",
    "Quantity": 2,
    "Cost": 125.00,
    "POLineItemNumber": 1
  },
  "SourceShippingMethod": {
    "Carrier": "UPS",
    "Method": "Ground",
    "ShippingCode": "UPS-GND"
  }
}
Understanding the Data: This data represents a fulfillment request in Flxpoint. For example, "FulfillmentRequestNumber": "FR12345" becomes the PO Number in Zanders’ system, and "ShippingAddress" fields like Address Line 1 and City are mapped to Zanders’ Ship To fields. The integration ensures all necessary details are sent to Zanders for fulfillment.

Let’s set up the integration by customizing a few key settings to match your needs:
  • FTP Connection Settings:
    • Connection Name: Give your connection a name, like "ZandersFTP_Fulfillment".
    • FTP Protocol: Choose the protocol Zanders uses—FTP, SFTP, or FTPS.
    • FTP Host: Enter the server address provided by Zanders, such as ftp.zanders.com.
    • FTP Port: Use standard ports (e.g., 21 for FTP, 22 for SFTP).
    • FTP User & Password: Input the credentials Zanders gave you.
    • Maintain Constant Connection: Turn this on if you’re sending large files to avoid interruptions (optional).
  • Outbound Remote File Folder: Specify the folder on Zanders’ FTP server where the purchase order files will be uploaded, like /zanders-fulfillment-requests. This is where Zanders will look for the files to process.
  • Sender/Receiver Identifiers: These settings ensure smooth communication between your system and Zanders’ system:
    • Our Sender/Receiver ID: Set to FLXPOINT—this identifies your system.
    • Our Sender/Receiver Qualifier: Use ZZ, a standard code for a mutually defined identifier.
    • Their Sender/Receiver ID: Enter the ID provided by Zanders, such as ZANDERSID.
    • Their Sender/Receiver Qualifier: Set to 12, which typically represents a telephone number or similar identifier in EDI standards.
What’s an Outbound Remote File Folder? Think of this as a dropbox on Zanders’ server where you’ll place your purchase order files. The integration uploads the files here for Zanders to pick up and process.
Sender/Receiver Identifiers: These are like a digital handshake between your system and Zanders’—they ensure both sides know who’s sending and receiving the data.

Follow these steps to get the Zanders - Send Fulfillment Requests integration up and running:
  • 1 Establish FTP Connection: Enter the FTP credentials provided by Zanders (Connection Name, FTP Protocol, FTP Host, FTP Port, FTP User, FTP Password). Click the Test Connection button to verify it works, then save.
  • 2 Configure Advanced Settings (Optional): Enable "Maintain Constant Connection" if you’re sending large files to ensure smooth uploads.
  • 3 Define File Location: Set the Outbound Remote File Folder (e.g., /zanders-fulfillment-requests) where the integration will upload purchase order files.
  • 4 Set Sender/Receiver Identifiers: Configure the identifiers (Our Sender/Receiver ID: FLXPOINT, Qualifier: ZZ; Their Sender/Receiver ID: e.g., ZANDERSID, Qualifier: 12).
  • 5 Create a Mapping Template: Head to the Mapping Dashboard ("Zanders - Send Fulfillment Requests") to define how Flxpoint fields map to Zanders’ purchase order fields (see the "Mapping Template" section below).
  • 6 Configure Mapping Rules (Optional): Set up custom rules to transform data during mapping if needed (see the "Mapping Rules" section below).
  • 7 Send the Fulfillment Requests: Click to send the requests manually, or set up a schedule for automatic sending.

The integration setup interface for “Zanders - Send Fulfillment Requests” is where you begin connecting Zanders to your Flxpoint system. Let’s explore what you’ll see and interact with when setting up this connection:
  • Integration Title: At the top, you’ll see the integration name, “Zanders - Send Fulfillment Requests,” clearly labeled to indicate which integration you’re configuring.
  • FTP Connection Settings Section: This section contains a form with fields to input your FTP credentials:
    • Connection Name: A text field where you can name your connection.
    • FTP Protocol: A dropdown menu to select the protocol (FTP, SFTP, or FTPS).
    • FTP Host: A text field for the server address.
    • FTP Port: A numeric field for the port number.
    • FTP User & Password: Text fields to enter the username and password provided by Zanders.
    • Maintain Constant Connection: A toggle switch you can enable if you’re sending large files to prevent interruptions.
  • Outbound Remote File Folder Field: A text field where you specify the folder on Zanders’ FTP server where purchase order files will be uploaded.
  • Sender/Receiver Identifiers Section: This section includes fields to configure communication identifiers:
    • Our Sender/Receiver ID & Qualifier: Text fields to set your system’s identifier and qualifier.
    • Their Sender/Receiver ID & Qualifier: Text fields for Zanders’ identifier and qualifier.
  • Action Buttons: At the bottom, you’ll find buttons to manage your setup:
    • Test Connection: A button to verify that your FTP credentials work and the connection to Zanders’ server is successful.
    • Save: A button to save your configuration settings.
Next Steps
Once you’ve set up the integration connection, you’ll move on to defining how Flxpoint data maps to Zanders’ purchase order fields in the "Mapping Template" section below.

The Mapping Template is where you define how Flxpoint’s fulfillment request data maps to Zanders’ purchase order fields. This ensures Zanders receives the order details in the format they expect, like shipping addresses and item quantities. Let’s break it down!
Mapping Fields
Below is a table of key fields you can map, complete with examples and purposes. The labels (T for text, N for numbers, D for dates) match what you’ll see in the dashboard:
Field Maps To Example Purpose Status
Fulfillment Request Number (T) Zanders PO: PO Number FR12345 Identifies the purchase order in Zanders’ system Required
Shipping Address: Address Line 1 (T) Zanders PO: Ship To Address1 123 Main St Specifies the primary address line for shipping Required
Shipping Address: Address Line 2 (T) Zanders PO: Ship To Address2 Apt 4B Provides additional address details (e.g., apartment number) Optional
Shipping Address: City (T) Zanders PO: Ship To City Austin Specifies the city for the shipping address Required
Shipping Address: State Code (T) Zanders PO: Ship To State TX Specifies the state for the shipping address Required
Shipping Address: Postal Code (T) Zanders PO: Ship To Zip 78701 Specifies the postal code for the shipping address Required
Shipping Address: Full Name (T) Zanders PO: Ship To Name Jane Doe Identifies the recipient’s name for shipping Required
Source Shipping Method: Shipping Code (T) Zanders PO: Ship Via Code UPS-GND Specifies the shipping method Zanders should use Optional
Fulfillment Request: Note (T) Zanders PO: Ship Instructions Urgent delivery requested Provides special instructions for shipping (rule: adds phone number) Optional
Fulfillment Request Item: SKU (T) Zanders PO Item: Item Number ZND12345 Identifies the product to be fulfilled Required
Fulfillment Request Item: Quantity (N) Zanders PO Item: Quantity 2 Specifies the quantity of the item to be fulfilled Required
Available Source Fields
Flxpoint provides a comprehensive set of fields from the fulfillment request that you can map to Zanders’ purchase order fields:
  • Billing Address: Address Line 1 (T), Address Line 2 (T), City (T), Company Name (T), Country (T), Country Code (T), Email (T), First Name (T), Full Name (T), Last Name (T), Phone (T), Postal Code (T), State (T), State Code (T).
  • Fulfillment Request: Estimated Dropship Fee (N), Estimated Shipping Cost (N), Fulfillment Request Number (T), Generated At (D), Note (T), Sent At (D), Total Cost (N), Total Weight (lbs) (N).
  • Fulfillment Request Item: Bin Location (T), Cost (N), MPN (T), PO Line Item # (N), Quantity (N), SKU (T), Subtotal (N), Title (T), UPC (T).
  • Shipping Address: Address Line 1 (T), Address Line 2 (T), City (T), Company Name (T), Country (T), Country Code (T), Email (T), First Name (T), Full Name (T), Last Name (T), Phone (T), Postal Code (T), State (T), State Code (T).
  • Source Shipping Method: Carrier (T), Description (T), Method (T), Shipping Code (T).
Let’s Break It Down: The "Fulfillment Request Number" is Flxpoint’s identifier for the order, like "FR12345", which maps to Zanders’ "PO Number" to track the order. "Shipping Address: Address Line 1" ensures Zanders knows where to ship the order, like "123 Main St".
Mapping Options
For each field mapping, you can choose from several options to customize how the data is handled:
  • Field: Link a Flxpoint field (e.g., Fulfillment Request Number) to a Zanders field (e.g., PO Number). This is the most straightforward way to map data.
  • Value: Set a fixed value for the field (e.g., always set "Ship Via Code" to "UPS-GND"). Handy for applying the same value to all orders.
  • Mapping Set: Use tools to combine or manipulate data (e.g., concatenate fields). You can create custom Mapping Sets in Flxpoint for more complex transformations.
  • Rules: Add "if-then" logic to transform data during mapping (e.g., add the phone number to Ship Instructions). Check out the "Mapping Rules" section below for more details.
  • Don’t Map: Skip the field entirely, leaving it unmapped in Zanders’ system.
  • Set to Empty: Clear the field in Zanders’ system, removing any existing data for that field.
Try This: If you always use the same shipping method, select "Value" for the Ship Via Code field and enter "UPS-GND". Or, use a Rule to append the customer’s phone number to the Ship Instructions for better communication with Zanders.
Summary
You’ve now mapped a total of 11 key fields from Flxpoint to Zanders’ purchase order format, ensuring accurate order fulfillment. This setup covers essential details like the PO number, shipping address, and item quantities. Next, you can fine-tune your mappings with custom rules in the "Mapping Rules" section below.

Mapping Rules allow you to transform Flxpoint’s fulfillment request data as it’s being mapped to Zanders’ purchase order fields. Whether you’re adding extra information, applying conditions, or formatting data, rules help you customize the data to meet Zanders’ requirements. Think of them as a set of instructions the integration follows to "tweak" the data before sending it to Zanders.
Configured Mapping Rules
Here are the rules currently set up for the Zanders - Send Fulfillment Requests integration:
  • Add Phone number to Shipping Instruction (First Instance):
    • Type: Conditional (String)
    • Description: Appends the customer’s phone number from the Shipping Address to the Ship Instructions field.
    • Logic: Always runs, with 2 actions modifying the Incoming Value (concatenates the phone number to the existing Ship Instructions).
    • Timestamp: Created at 9:13:05 AM.
    • Example: If Ship Instructions is "Urgent delivery requested" and the phone number is "512-555-1234", the result becomes "Urgent delivery requested - Phone: 512-555-1234".
  • Add Phone number to Shipping Instruction (Second Instance):
    • Type: Conditional (String)
    • Description: A duplicate rule that also appends the customer’s phone number to the Ship Instructions field (likely created for testing or redundancy).
    • Logic: Always runs, with 2 actions modifying the Incoming Value (same as the first instance).
    • Timestamp: Created at 9:13:38 AM.
    • Example: Same as above, resulting in "Urgent delivery requested - Phone: 512-555-1234".
Why Use Rules? Rules are like a personal assistant for your data. For example, "Add Phone number to Shipping Instruction" ensures Zanders has the customer’s contact info directly in the Ship Instructions, making communication easier during delivery.
Creating a New Rule
Want to create your own rule? In the Mapping Dashboard, you’ll find a "Create New Rule" option that opens a form with the following fields:
  • Rule Name: A text field where you can enter a friendly name to identify the rule later, such as "Format Ship To Name".
  • Rule Type: A dropdown menu with the following options:
    • Conditional: Use logic to transform data (e.g., if Shipping Address: Country = "US", add a specific prefix to Ship To Name).
    • Tier: Apply tiered logic, often for quantities or costs (e.g., if Quantity > 10, add a bulk order note to Ship Instructions).
  • Input Type: A dropdown menu with the following options:
    • String: For text fields like Ship Instructions or Ship To Name.
    • Number: For numeric fields like Quantity or Cost.
    • Boolean: For true/false fields (e.g., a condition like "Is urgent?").
    • Option Field: For fields with predefined options, like shipping methods (e.g., "UPS", "FedEx").
Notice: You won’t be able to change the rule type or input type once you create the rule, this is because mapping templates using the rule will be expecting to pass in and receive back the original input type the rule defines.
Once you’ve filled out the form, click the Create button to save your rule.
Try This: Create a rule named "Add Urgent Note". In the form, set the Rule Type to "Conditional" and the Input Type to "String". Add a condition: if Fulfillment Request: Note contains "urgent", append " - URGENT ORDER" to Ship Instructions. Then click "Create" to save the rule. This ensures Zanders prioritizes urgent orders.

Here are some essential details to understand the Zanders - Send Fulfillment Requests integration:
  • Current Date and Time: As of 09:17 AM -04 on Tuesday, May 20, 2025, this integration is fully operational for sending fulfillment requests to Zanders.
  • Zanders Integration: Sends purchase orders to Zanders via FTP, including details like shipping addresses, item quantities, and shipping methods.
  • Supported Features: Maps Flxpoint fulfillment request data to Zanders’ purchase order fields, with custom rules for data transformation (e.g., adding phone numbers to shipping instructions).
Pro Tip: Test your FTP connection before saving to ensure smooth file uploads, and double-check your mapping rules in the Mapping Dashboard to ensure Zanders receives accurate order details.

If something goes wrong with the integration, here are some steps to help you fix it:
  • FTP Connection Failure: Double-check your FTP credentials (host, port, user, password) and click to test the connection again.
  • File Not Uploaded: Ensure the Outbound Remote File Folder is set correctly and that Zanders has granted write access to that location.
  • Data Mapping Errors: Review your custom rules (e.g., adding phone numbers to Ship Instructions) in the Mapping Dashboard to ensure they’re working as expected.
  • Missing Order Details: Verify that your fulfillment requests in Flxpoint include all required fields (e.g., Fulfillment Request Number, Shipping Address) so the mapping works correctly.

Conclusion
With the Zanders - Send Fulfillment Requests integration, you can seamlessly send purchase orders to Zanders, ensuring accurate and timely order fulfillment. By mapping Flxpoint data to Zanders’ purchase order fields and applying custom rules, you can automate your dropshipping process with confidence.
 
 

Get Shipments

Supported | Zanders - Get Shipments

Introduction to Zanders - Get Shipments Integration
The Zanders - Get Shipments integration automates the process of retrieving shipment data from Zanders and updating your Flxpoint system with tracking details. This integration pulls shipment information—like tracking numbers, carriers, and ship dates—from Zanders via a static FTP feed, ensuring you can keep your customers informed about their order statuses. The process involves connecting to Zanders’ FTP server, setting up configurations, mapping fields, applying custom rules if needed, and processing ganze shipment data (either manually or on a schedule). Let’s walk through each step to get you started!

The Zanders - Get Shipments integration connects your Flxpoint system to Zanders to:
  • Retrieve shipment data, including tracking numbers, carriers, and ship dates, from a static FTP feed.
  • Map Zanders’ shipment fields to your Flxpoint system to update order statuses with accurate tracking information.
  • Ensure seamless updates to keep your shipment data current with minimal manual intervention.

This integration follows a clear, step-by-step process to bring Zanders’ shipment data into your Flxpoint system:
  • FTP Connection: Establishes a secure connection to Zanders’ FTP server using the credentials they provide.
  • File Retrieval: Downloads shipment data files from the specified Inbound Remote File Folder. These files contain details like Tracking Number, Ship Date, and Carrier.
  • Shipment Processing: Extracts the data and updates your Flxpoint shipment records, mapping Zanders’ fields to Flxpoint fields like Tracking Number and Shipped At.
What Does the Shipment Data Look Like?
Let’s take a peek at a sample shipment data structure from Zanders. This is what the integration retrieves and processes:
{
  "ShipCode": "SH12345",
  "ShipCompany": "UPS",
  "ShipDate": "2025-05-19",
  "ShipVia": "Ground",
  "TrackingNumber": "1Z9999W99999999999"
}
Understanding the Data: Each entry represents a shipment update from Zanders. For example, "TrackingNumber": "1Z9999W99999999999" maps to Flxpoint’s Tracking Number field, allowing you to update the order status and share tracking details with your customer.

Let’s set up the integration by customizing a few key settings to match your needs:
  • FTP Connection Settings:
    • Connection Name: Give your connection a name, like "ZandersFTP_Shipments".
    • FTP Protocol: Choose the protocol Zanders uses—FTP, SFTP, or FTPS.
    • FTP Host: Enter the server address provided by Zanders, such as ftp.zanders.com.
    • FTP Port: Use standard ports (e.g., 21 for FTP, 22 for SFTP).
    • FTP User & Password: Input the credentials Zanders gave you.
    • Maintain Constant Connection: Turn this on if you’re dealing with large files to avoid interruptions (optional).
  • Inbound Remote File Folder: Specify the folder on Zanders’ FTP server where the shipment data files are stored, like /zanders-shipments. This is where the integration will look for files to download.
  • Sender/Receiver Identifiers: These settings ensure smooth communication between your system and Zanders’ system:
    • Our Sender/Receiver ID: Set to FLXPOINT—this identifies your system.
    • Our Sender/Receiver Qualifier: Use ZZ, a standard code for a mutually defined identifier.
    • Their Sender/Receiver ID: Enter the ID provided by Zanders, such as ZANDERSID.
    • Their Sender/Receiver Qualifier: Set to 12, which typically represents a telephone number or similar identifier in EDI standards.
What’s an Inbound Remote File Folder? Imagine this as a shared Mailbox on Zanders’ server where they drop the shipment data files. The integration checks this folder to pick up the latest files.
Sender/Receiver Identifiers: Think of these as a secret handshake between your system and Zanders’—they ensure both sides know who’s sending and receiving the data.

Follow these steps to get the Zanders - Get Shipments integration up and running:
  • 1 Establish FTP Connection: Enter the FTP credentials provided by Zanders (Connection Name, FTP Protocol, FTP Host, FTP Port, FTP User, FTP Password). Click the Test Connection button to verify it works, then save.
  • 2 Configure Advanced Settings (Optional): Enable "Maintain Constant Connection" if you’re handling large files to ensure smooth downloads.
  • 3 Define File Location: Set the Inbound Remote File Folder (e.g., /zanders-shipments) where the integration will retrieve shipment data files.
  • 4 Set Sender/Receiver Identifiers: Configure the identifiers (Our Sender/Receiver ID: FLXPOINT, Qualifier: ZZ; Their Sender/Receiver ID: e.g., ZANDERSID, Qualifier: 12).
  • 5 Create a Mapping Template: Head to the Mapping Dashboard ("Zanders - Get Shipments") to define how Zanders’ fields map to your shipment records (see the "Mapping Template" section below).
  • 6 Configure Mapping Rules (Optional): Set up custom rules to transform data during mapping if needed (see the "Mapping Rules" section below).
  • 7 Run the Integration: Click to run manually, or set up a schedule for automatic updates.

The integration setup interface for “Zanders - Get Shipments” is where you begin connecting Zanders to your Flxpoint system. Let’s explore what you’ll see and interact with when setting up this connection:
  • Integration Title: At the top, you’ll see the integration name, “Zanders - Get Shipments,” clearly labeled to indicate which integration you’re configuring.
  • FTP Connection Settings Section: This section contains a form with fields to input your FTP credentials:
    • Connection Name: A text field where you can name your connection.
    • FTP Protocol: A dropdown menu to select the protocol (FTP, SFTP, or FTPS).
    • FTP Host: A text field for the server address.
    • FTP Port: A numeric field for the port number.
    • FTP User & Password: Text fields to enter the username and password provided by Zanders.
    • Maintain Constant Connection: A toggle switch you can enable if you’re dealing with large files to prevent interruptions.
  • Inbound Remote File Folder Field: A text field where you specify the folder on Zanders’ FTP server where shipment data files are stored.
  • Sender/Receiver Identifiers Section: This section includes fields to configure communication identifiers:
    • Our Sender/Receiver ID & Qualifier: Text fields to set your system’s identifier and qualifier.
    • Their Sender/Receiver ID & Qualifier: Text fields for Zanders’ identifier and qualifier.
  • Action Buttons: At the bottom, you’ll find buttons to manage your setup:
    • Test Connection: A button to verify that your FTP credentials work and the connection to Zanders’ server is successful.
    • Save: A button to save your configuration settings.
Next Steps
Once you’ve set up the integration connection, you’ll move on to defining how Zanders’ shipment data maps to your Flxpoint shipment records in the "Mapping Template" section below.

The Mapping Template is where you define how Zanders’ shipment data fields connect to your Flxpoint shipment records. This ensures your system is updated with accurate tracking information, like tracking numbers and ship dates, so you can keep your customers informed. Let’s break it down!
Mapping Fields
Below is a table of fields you can map, complete with examples and purposes. The labels (T for text, D for dates) match what you’ll see in the dashboard:
Field Maps To Example Purpose Status
Ship Company (T) Shipment: Carrier UPS Identifies the carrier used for the shipment Required
Ship Via (T) Shipment: Method Ground Specifies the shipping method used by the carrier Optional
Ship Date (D) Shipment: Shipped At 2025-05-19 Records the date the shipment was sent Required
Tracking Number (T) Shipment: Tracking Number 1Z9999W99999999999 Provides the tracking number for the shipment Required
Available Source Fields
Zanders provides a focused set of fields in their FTP feed for shipment data that you can map to your Flxpoint shipment records:
  • Zanders Shipment: Ship Code (T), Ship Company (T), Ship Date (D), Ship Via (T), Tracking Number (T).
Let’s Break It Down: "Ship Company" identifies the carrier, like "UPS", which maps to Flxpoint’s Carrier field. "Tracking Number" is crucial for updating your order status, ensuring you can share "1Z9999W99999999999" with your customer.
Mapping Options
For each field mapping, you can choose from several options to customize how the data is handled:
  • Field: Link a Zanders field (e.g., Tracking Number) to a Flxpoint field (e.g., Tracking Number). This is the most straightforward way to map data.
  • Value: Set a fixed value for the field (e.g., always set "Method" to "Ground"). Handy for applying the same value to all shipments.
  • Mapping Set: Use tools to combine or manipulate data (e.g., concatenate fields). You can create custom Mapping Sets in Flxpoint for more complex transformations.
  • Rules: Add "if-then" logic to transform data during mapping (e.g., format the Ship Date). Check out the "Mapping Rules" section below for more details.
  • Don’t Map: Skip the field entirely, leaving it unmapped in Flxpoint.
  • Set to Empty: Clear the field in Flxpoint, removing any existing data for that field.
Try This: If Zanders always uses the same shipping method, select "Value" for the Method field and enter "Ground". Or, use a Rule to format the Ship Date into a specific format required by your system.
Summary
You’ve now mapped a total of 4 fields from Zanders to your Flxpoint shipment records, ensuring accurate tracking updates. This setup covers essentials like the carrier, tracking number, and ship date. Next, you can fine-tune your mappings with custom rules in the "Mapping Rules" section below.

Mapping Rules let you transform Zanders’ shipment data as it’s being mapped into Flxpoint. Whether you’re formatting dates, combining fields, or applying conditions, rules give you the power to shape the data to fit your needs. Think of them as a set of instructions the integration follows to "tweak" the data before it lands in your shipment records.
Configured Mapping Rules
Currently, there are no mapping rules configured for the Zanders - Get Shipments integration. You can add custom rules to transform the data as needed—see below for how to create them.
Creating a New Rule
Want to create your own rule? In the Mapping Dashboard, you’ll find a "Create New Rule" option that opens a form with the following fields:
  • Rule Name: A text field where you can enter a friendly name to identify the rule later, such as "Format Ship Date".
  • Rule Type: A dropdown menu with the following options:
    • Conditional: Use logic to transform data (e.g., if Ship Company = "UPS", set Carrier to "UPS").
    • Tier: Apply tiered logic, often for quantities or costs (e.g., if Shipping Cost > 50, add a note).
  • Input Type: A dropdown menu with the following options:
    • String: For text fields like Tracking Number or Ship Company.
    • Number: For numeric fields like Shipping Cost.
    • Boolean: For true/false fields (e.g., a condition like "Is shipped?").
    • Option Field: For fields with predefined options, like shipping methods (e.g., "Ground", "Express").
Notice: You won’t be able to change the rule type or input type once you create the rule, this is because mapping templates using the rule will be expecting to pass in and receive back the original input type the rule defines.
Once you’ve filled out the form, click the Create button to save your rule.
Try This: Create a rule named "Format Ship Date". In the form, set the Rule Type to "Conditional" and the Input Type to "String". Add a condition: if Ship Date is not empty, reformat it to "MM/DD/YYYY" (e.g., "2025-05-19" becomes "05/19/2025"). Then click "Create" to save the rule. This ensures your shipment dates are in a consistent format.

Here are some essential details to understand the Zanders - Get Shipments integration:
  • Current Date and Time: As of 09:27 AM -04 on Tuesday, May 20, 2025, this integration is fully operational for retrieving shipment data from Zanders.
  • Zanders Integration: Retrieves shipment data via FTP, including tracking numbers, carriers, and ship dates.
  • Supported Features: Maps shipment data to Flxpoint fields, with the option to add custom rules for data transformation.
Pro Tip: Test your FTP connection before saving to ensure smooth file retrieval, and consider adding custom rules in the Mapping Dashboard if you need to transform data during mapping (e.g., formatting dates or generating tracking URLs).

If something goes wrong with the integration, here are some steps to help you fix it:
  • FTP Connection Failure: Double-check your FTP credentials (host, port, user, password) and click to test the connection again.
  • File Not Found: Make sure the Inbound Remote File Folder is set correctly and that Zanders has uploaded the shipment data files to that location.
  • Data Mapping Errors: Review your mappings in the Mapping Dashboard to ensure they’re set up correctly (e.g., mapping Tracking Number to Shipment: Tracking Number).
  • Incomplete Shipment Data: Verify that the shipment data files include all the fields you expect (e.g., Tracking Number, Ship Date) so the mapping works correctly.

Conclusion
With the Zanders - Get Shipments integration, you can efficiently retrieve and map shipment data from Zanders intoulfonic your Flxpoint system, keeping your order statuses up-to-date with tracking details. With flexible mapping options and the ability to add custom rules, managing your shipment updates has never been easier or more reliable.
 
 

 

Related Articles

Entrenue as Source

Entrenue is a wholesale distributor specializing in adult products, boutique plea...

Petra Industries as Source

Petra Industries is a wholesaler of consumer electronics and accessories. Flxpoin...

Mirage Pet Products as Source

Mirage Pet Products is a wholesaler of pet apparel, accessories, and supplies. Fl...