CSV and HTML files can serve as flexible and reliable sources for data integration. Flxpoint offers multiple ways to establish a connection, allowing seamless data ingestion from various hosting platforms or storage methods. Whether your files are stored locally, on cloud platforms, or hosted on external servers, the following methods ensure compatibility and ease of access:
FTP/SFTP: Connect to your own FTP/SFTP server or create a new account specifically for file transfers.
HTTP: Use publicly accessible download links from platforms like Dropbox, Google Drive, or any other hosting service.
Google Sheets: Share your file via a "Share" link, ensuring that "Anyone with the link" has view access.
By choosing the appropriate connection method, you can ensure streamlined data transfer while maintaining security and flexibility. This guide will walk you through setting up these connections step by step.
How To Connect
📋 Phase 1: Initial Source Setup+
Navigate to Connections
Log into your Flxpoint account and navigate to the Connections tab on the left menu.
Access Fulfillment Sources
Within the Connections section, go to the Fulfillment Sources tab.
Create a New Source
In the Fulfillment Sources tab, click +Add Source to start setting up a new source.
Tip: Have your CSV/XLSX file or connection details ready to streamline the setup process.
Configure Source Details
Enter a name for your source (e.g., "CSV/XLSX Source").
Select Product Data Source as the type.
Click Configure Manually to proceed.
🔐 Phase 2: Establish Connection+
Initiate a New Connection
Click Add Connection, then select New Connection to set up a new data source connection.
Specify Source Type
Choose CSV/XLSX as the source type for your connection.
Select Connection Method
In the New CSV/XLSX File Connection popup, select your preferred connection method:
Manual File: Upload your CSV/XLSX file directly.
HTTP: Provide the file URL (with optional Basic Auth).
For a Google Sheets file:
Open your Google Sheet and copy the document ID from its URL (between /d/ and /edit).
Construct the CSV download URL as:
https://spreadsheets.google.com/feeds/download/spreadsheets/Export?key=yourDocId&exportFormat=csv
Replace yourDocId with your Google Sheet ID.
Test the URL in a browser to confirm the CSV downloads correctly.
FTP (Basic Auth): Enter FTP host, port, username, password, etc.
FTP (Token Based): Upload your token file and passphrase.
Email (Inbound): Provide email server details (IMAP/POP), folder, etc.
Google Sheets File: Use the download URL for your Sheet in CSV format.
Click Save and Proceed after entering the details.
Tip: Verify your connection details by testing the URL or credentials to avoid issues later.
Enter FTP Credentials (if applicable)
If you selected an FTP method, provide the required credentials (nickname, host, port, username, password) or set up a new FTP account.
🔄 Phase 3: Configure Integrations+
Set Up Integration Options
Choose the integrations to enable based on your needs:
Get Inventory and Pricing & Quantity: Retrieve inventory data, including pricing and quantity. Set sync frequency and map fields (e.g., SKU, Price, Quantity).
Note: Ensure accurate field mapping to reflect the correct inventory details.
🛒 Phase 4: Order and Shipment Setup+
Configure Order and Shipment Integrations
Set up the following integrations:
Send Orders: Enable to send orders for fulfillment. Map order fields (e.g., Customer Name, Shipping Address).
Get Shipments: Enable to retrieve shipment updates. Set sync frequency and map fields (e.g., Tracking Number, Shipment Date).
Tip: Accurate field mapping ensures seamless order and shipment processing.
✅ Phase 5: Finalize and Verify+
Save Configuration
Review all settings, then save your connection and integration details.
Monitor Sync Progress
Your connection will begin syncing. Monitor the progress in the dashboard under the Fulfillment Sources tab.
Next Steps: The initial sync may take some time. Check the status regularly to ensure everything is functioning as expected.
×
Product Operations
The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, such as focusing on specific products or updates.
Get Inventory and Pricing & Quantity
Supported | Get Inventory and Pricing & Quantity
Introduction to Get Inventory and Pricing & Quantity
Welcome to the Get Inventory and Pricing & Quantity integration guide! This integration allows you to fetch product data and pricing/quantity/status (PQS) data from CSV or XLSX files into your inventory management system. It ensures your inventory data is accurately represented and up-to-date. Let’s get started!
The Get Inventory and Pricing & Quantity integration enables you to:
Fetch product data (Primary) and PQS data (Secondary) from specified sources (e.g., FTP, local file upload).
Map your data to inventory fields for accurate import and updates.
Customize and manage mapping templates for streamlined imports.
This ensures your inventory reflects accurate product details and stock levels.
The integration follows these steps:
1Connecting to Source: Establish a connection using methods like FTP (Basic Auth), manual file upload, or Google Sheets to access your CSV/XLSX file.
2Fetching Data: Retrieve product data (Primary) or PQS data (Secondary) from the specified file, supporting both header-based and headerless formats.
3Extracting Details: Extract fields like Parent SKU, SKU, Quantity, and Cost from the file.
4Mapping Data: Map file fields (e.g., Parent SKU, Quantity) to your system’s inventory fields using a mapping template.
5Syncing Data: Import the mapped data into your system, updating inventory records.
6Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep your inventory up-to-date.
Note: File access failures (e.g., incorrect FTP credentials) pause the integration and trigger notifications.
Customize the integration with these settings:
File Has Headers: Specify if your file uses header names (e.g., "Parent SKU") or column indices (e.g., Column A).
File Format: Select CSV, TSV, or XLSX.
Download Files Modified in the Last X Days: Set the number of days (e.g., 14) for recent files.
Archive/Un-Archive Inventory: Enable to archive inventory not found in the source feed or un-archive when added back.
Number of Rows to Skip: Skip rows (e.g., 4) if data starts after blank rows or comments.
Excel Sheet Index: Specify the sheet index (e.g., 0 for the first sheet) for XLSX files.
Quote Character: Define a quote character if double quotes cause issues.
Delimiter: Set the delimiter (e.g., comma, pipe) for CSV/TSV files (e.g., “SKU|UPC|COST”).
File to Extract: Specify the file name (e.g., “usethis.csv”) if extracting from a zip/rar archive.
Save Products in Small Batch: Enable to process data in smaller batches for smoother integration.
Process Feed Even If Some Headers/Columns Are Missing: (Header-based feeds only) Enable to proceed even if non-required headers are missing (default on for integrations created on or after 20 May 2025).
Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
Mapping Template: Define how file fields sync to your system (e.g., “Parent SKU” to “Parent SKU”).
Google Sheet Requirements: Ensure all columns in your Google Sheet are formatted as "Plain Text." If the operation fails to import new data, reformat the sheet and try again.
Follow these steps:
1Add the Integration: Go to Channels > Integrations, select “Get Inventory and Pricing & Quantity.”
2Connect to Source: Choose a connection type (e.g., FTP, manual file upload) and set up the connection.
3Configure Settings:
Specify if the file has headers.
Select the file format (CSV, TSV, XLSX).
Set the number of days for downloading modified files (e.g., 14).
Enable archive/un-archive inventory if needed.
(Optional) Enable "Process Feed Even If Some Headers/Columns Are Missing" for header-based feeds.
Configure advanced settings like rows to skip, sheet index, or delimiter.
Configure scheduling.
4Create Mapping Template: Configure field mappings (see Mapping Template Details).
5Run the Integration: Start with Run Sync or schedule.
Mapping templates control which file data is imported into your inventory system.
Interface Overview
Screen labeled “Get Inventory and Pricing & Quantity” at the top; name your template (e.g., “Inventory Mapping”).
Buttons: Delete, Duplicate, Save Mapping.
Columns: File fields (left), your system fields (right).
Mapping Options
Enable: Send the field (e.g., Parent SKU).
Disable: Ignore the field (e.g., Category 3).
Required Fields: Parent SKU (Primary), SKU (Primary and Secondary).
Parent SKU and SKU Mapping Requirement
The Parent SKU (Primary) and SKU fields must be mapped to ensure proper inventory identification.
Required Field: Parent SKU (Primary) and SKU (Primary and Secondary) uniquely identify products and variants.
Mapping Indicators: A green checkmark indicates the field was automatically mapped. A yellow exclamation mark indicates the field was not automatically mapped and requires manual mapping.
Error Scenario: Unmapped required fields may cause:
Invalid request: Missing required field 'Parent SKU' or 'SKU' for inventory sync
Fix: Go to Channels > Templates > Get Inventory and Pricing & Quantity > Field Mapping, enable Parent SKU and SKU, save, and re-run sync.
Recommendation: Always enable Parent SKU (Primary) and SKU (Primary and Secondary) for reliable inventory syncing.
Mapping Template Setup
Configure your mapping template with these options:
Use the toggle to enable or disable field imports for specific headers.
The dropdown menu allows you to manually adjust which fields headers are mapped to.
Once mapping is complete, click Save Changes to confirm.
This ensures accurate mapping integration of your data.
Missing Headers: If a required header (e.g., SKU) is missing, the job will fail unless "Process Feed Even If Some Headers/Columns Are Missing" is enabled.
Google Sheets Formatting: Ensure all columns are formatted as "Plain Text" in Google Sheets to avoid import issues.
Contact Support: Reach out to your system administrator with error details.
Diagnostic Tip: Missing data often results from disabled required fields or incorrect Google Sheets formatting.
Key information:
Date: As of 11:00 AM -04, June 01, 2025, this integration is operational.
Required Fields: Parent SKU (Primary) and SKU (Primary and Secondary) must be enabled.
File Requirements: Ensure required columns (e.g., Parent SKU, SKU) are present in your file.
Image Support: Get Inventory Images are supported for Secondary imports.
Pro Tip: Enable all required fields to ensure accurate inventory syncing.
Conclusion
The Get Inventory and Pricing & Quantity integration automates inventory data imports, ensuring your system reflects accurate product and PQS details. Customize mappings and schedules to fit your workflow, streamlining inventory management. Happy syncing!
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 Orders
Supported | Send Orders
Introduction to Send Orders
Welcome to the Send Orders integration guide! This integration allows you to submit orders via a CSV or XLSX file, which can be sent through an email connection. It streamlines the process of requesting fulfillment from your vendors, ensuring efficient order processing. Let’s get started!
The Send Orders integration enables you to:
Submit orders using a CSV/XLSX file, with support for both header-based and headerless formats.
Send orders via email, using a default or custom "Send From" email address.
Automate retrieval of CSV/XLSX files through an email connection for seamless processing.
This ensures your orders are efficiently communicated to your vendors.
The integration follows these steps:
1Connecting to Email Source: Set up an email connection to retrieve CSV/XLSX files containing order data, or manually upload the file.
2Fetching Order Data: The system retrieves order details from the specified CSV/XLSX file, supporting both header-based and headerless formats.
3Extracting Order Details: Extract necessary fields (e.g., Order ID, SKUs) from the file to create orders.
4Mapping Data: Map file fields to your system’s order fields using a mapping template.
5Sending Orders via Email: Send the orders to the specified email addresses, with options to CC or BCC additional recipients.
6Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular sends to automate your order submission process.
Note: Email delivery failures (e.g., invalid email addresses) will pause the integration and trigger notifications.
Customize the integration with these settings:
File Has Headers: Specify if your file uses header names (e.g., "Order ID") or column indices (e.g., Column A).
File Format (Advanced Settings): Choose the output file format: Default (same as input), CSV, TSV, or TXT.
Email Connection: Set up an email connection to retrieve CSV/XLSX files (see Email Connection Configuration below).
Email Address (To): Specify the recipient email addresses (multiple addresses can be separated by commas).
Email Address (From): Default is notify@flxpoint.com; contact support@flxpoint.com for a custom "Send From" email.
Email Address (CC): Add email addresses to CC on the order email.
Email Address (BCC): Add email addresses to BCC on the order email.
Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
Mapping Template: Define how file fields sync to your system (e.g., “Order ID” to “Order ID”).
Google Sheet Requirements: Ensure all columns in your Google Sheet are formatted as "Plain Text." If the operation fails to import new data, reformat the sheet and try again.
For CSV/XLSX sources, you can configure an email connection to automatically retrieve files for processing. Follow these steps:
1Navigate to Email Connection Settings: Go to Integrations > Sources, and select Email Connection.
2Input the Required Fields:
Connection Name: Enter a descriptive name (e.g., "Supplier CSV Email").
Email Host: Input the email server (e.g., smtp.gmail.com).
Email Protocol: Select IMAP or POP3.
Port: Use 993 for IMAP or 995 for POP3.
Email User: Use internal-accounts@flxpoint.com.
Email Password: Use the password provided by Flxpoint support (e.g., tigbajawjocoru).
Email Folder: Enter the AID (Account ID) to organize incoming files.
3Enable Email Connection: Click Save Connection, then use the Test Connection option to verify settings.
Important: Contact support@flxpoint.com for a new email address or backend email group configurations.
Follow these steps:
1Add the Integration: Go to Channels > Integrations, select “Send Orders.”
2Set Up Email Connection: Configure an email connection to retrieve files (see Email Connection Configuration), or manually upload your CSV/XLSX file.
3Configure Settings:
Specify if the file has headers.
Select the file format under Advanced Settings (Default, CSV, TSV, TXT).
Enter the recipient email addresses (To, CC, BCC).
(Optional) Contact support@flxpoint.com to set up a custom "Send From" email address.
Configure scheduling.
4Create Mapping Template: Configure field mappings (see Mapping Template Details).
5Run the Integration: Start with Run Sync or schedule.
Mapping templates control which file data is used to create orders.
Interface Overview
Screen labeled “Send Orders” at the top; name your template (e.g., “Order Mapping Template”).
Buttons: Delete, Duplicate, Save Mapping.
Columns: File fields (left), your system fields (right).
Mapping Options
Enable: Send the field (e.g., Order ID).
Disable: Ignore the field (e.g., optional fields).
Required Fields: Order ID.
Order ID Mapping Requirement
The Order ID field must be mapped to ensure proper order identification.
Required Field: Order ID uniquely identifies the order.
Mapping Indicators: A green checkmark indicates the field was automatically mapped. A yellow exclamation mark indicates the field was not automatically mapped and requires manual mapping.
Error Scenario: Unmapped Order ID may cause:
Invalid request: Missing required field 'Order ID' for order submission
Fix: Go to Channels > Templates > Send Orders > Field Mapping, enable Order ID, save, and re-run sync.
Recommendation: Always enable Order ID for reliable order submission.
Mapping Template Setup
Configure your mapping template with these options:
You must map a field to SKU for successful imports.
Use the toggle to enable or disable field imports for specific headers.
The dropdown menu allows you to manually adjust which fields headers are mapped to.
Once mapping is complete, click Save Changes to confirm.
This ensures accurate mapping integration of your data.
Complete Field Mappings
Below are the fields you can enable for syncing:
Order Fields
File Field
Maps To
Example
Purpose
Status
Order ID
Order ID
ORD-12345
Identifies the order
Required
SKU
SKU
PROD-001-BLACK
Specifies the product to fulfill
Optional
Quantity
Quantity
5
Specifies the number of items to fulfill
Optional
Shipping Method
Shipping Method
Standard
Specifies the shipping method
Optional
Requested Ship Date
Requested Ship Date
2025-06-10
Specifies the desired ship date
Optional
Be aware of these limitations:
Email Delivery Limits: Invalid email addresses or server issues may prevent delivery.
Data Scope: Only processes data available in the CSV/XLSX file.
Required Fields: Order ID must be enabled.
Troubleshoot issues with these steps:
Email Connection Issues: Verify email settings (host, port, credentials) and test the connection.
File Errors: Ensure the file format matches the selected output format (CSV, TSV, TXT).
Missing Data: Check mapping template for enabled fields (e.g., Order ID).
Email Delivery Failures: Confirm recipient email addresses are valid and check for server issues.
Google Sheets Formatting: Ensure all columns are formatted as "Plain Text" in Google Sheets to avoid import issues.
Contact Support: Reach out to support@flxpoint.com for assistance with email setup or delivery issues.
Diagnostic Tip: Missing order data often results from disabled required fields like Order ID.
Key information:
Date: As of 11:00 AM -04, June 01, 2025, this integration is operational.
Required Fields: Order ID must be enabled.
Email Requirements: Default "Send From" email is notify@flxpoint.com; contact support@flxpoint.com for a custom email.
Email Connection: Use the provided credentials (e.g., internal-accounts@flxpoint.com) and AID folder setup for email retrieval.
Pro Tip: Enable all required fields and test email connections to ensure reliable order submission.
Conclusion
The Send Orders integration automates the submission of orders via email, ensuring efficient communication with your vendors. Customize email settings, map fields accurately, and schedule sends to fit your workflow, streamlining your order fulfillment process. Happy sending!
Get Shipments
Supported | Get Shipments
Introduction to Get Shipments
Welcome to the Get Shipments integration guide! This integration allows you to retrieve shipment details for submitted orders via an API connection. It ensures you can track and update shipment information, such as tracking numbers and shipping costs, seamlessly in your system. Let’s get started!
The Get Shipments integration enables you to:
Retrieve shipment details for submitted orders via an API connection.
Map shipment data to your system’s fields for accurate tracking and updates.
Customize and manage mapping templates to streamline your shipment import process.
This ensures your shipment information is accurate and up-to-date, enhancing your order fulfillment workflow.
The integration follows these steps:
1Connecting to API: Establish a connection using API credentials or OAuth2 authentication to access your shipment data system.
2Fetching Shipment Data: A GET call to the /shipments endpoint retrieves shipment details for submitted orders.
3Extracting Shipment Details: Extract fields like Fulfillment Request Number, Tracking Number, and Shipped At from the API response.
4Mapping Data: Map API fields (e.g., Fulfillment Request Number, Carrier) to your system’s fields using a mapping template.
5Syncing Data: Import the mapped data into your system, updating shipment records.
6Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep your shipment tracking information current.
Note: API failures pause the integration and trigger notifications.
Customize the integration with these settings:
Sync Frequency: Choose to sync shipment data for orders within a specific time frame (e.g., last 7 days).
API Endpoint: Specify the /shipments endpoint for retrieving shipment data.
Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
Mapping Template: Define how API fields sync to your system (e.g., Fulfillment Request Number to Shipment ID).
Note: Ensure your API credentials are valid to avoid sync failures.
Follow these steps:
1Add the Integration: Go to Channels > Integrations, select “Get Shipments.”
2Connect to API: Use your API credentials or set up a new connection via OAuth2 authentication.
3Configure Settings:
Set sync frequency (e.g., last 7 days).
Specify the /shipments endpoint.
Configure scheduling.
4Create Mapping Template: Configure field mappings (see Mapping Template Details).
5Run the Integration: Start with Run Sync or schedule.
Mapping templates control which API shipment data is imported into your system.
Interface Overview
Screen labeled “Get Shipments” at the top; name your template (e.g., “Shipment Mapping 1”).
Buttons: Delete, Duplicate, Save Mapping.
Columns: API fields (left), your system fields (right).
Mapping Options
Enable: Send the field (e.g., Fulfillment Request Number).
Disable: Ignore the field (e.g., Note).
Required Fields: Fulfillment Request Number.
Fulfillment Request Number Mapping Requirement
The Fulfillment Request Number field must be mapped to ensure proper shipment identification.
Required Field: Fulfillment Request Number uniquely identifies the shipment.
Error Scenario: Unmapped Fulfillment Request Number may cause:
Invalid request: Missing required field 'Fulfillment Request Number' for shipment sync
Fix: Go to Channels > Templates > Get Shipments > Field Mapping, enable Fulfillment Request Number, save, and re-run sync.
Recommendation: Always enable Fulfillment Request Number for reliable shipment syncing.
Complete Field Mappings
Below are the fields you can enable for syncing:
Shipment Fields
API Field
Maps To
Example
Purpose
Status
Fulfillment Request Number
Shipment ID
FR-12345
Identifies the shipment
Required
Carrier
Carrier
UPS
Specifies the shipping carrier
Optional
Method
Shipping Method
Ground
Specifies the shipping method
Optional
Note
Shipment Note
Handle with care
Adds additional shipment notes
Optional
Shipped At
Shipped Date
2025-06-01
Records the shipment date
Optional
Shipping Cost
Shipping Cost
10.00
Records the shipping cost
Optional
Tracking Number
Tracking Number
1Z9999W999999999
Tracks the shipment
Optional
Tracking URL
Tracking URL
https://track.ups.com/1Z9999W999999999
Provides a link to track the shipment
Optional
Shipment Item Fields
API Field
Maps To
Example
Purpose
Status
Sku
SKU
PROD-001-BLACK
Identifies the shipped item
Optional
Quantity
Quantity Shipped
5
Specifies the shipped quantity
Optional
Be aware of these limitations:
API Rate Limits: Exceeding API limits pauses the integration.
Data Scope: Only fetches data available via the /shipments endpoint.
Required Fields: Fulfillment Request Number must be enabled.
Troubleshoot issues with these steps:
Connection Issues: Verify API credentials and connectivity.
API Errors: Ensure the /shipments endpoint is accessible.
Contact Support: Reach out to support with error details.
Diagnostic Tip: Missing shipment data often results from disabled required fields.
Key information:
Date: As of 10:54 AM -04, June 01, 2025, this integration is operational.
Required Fields: Fulfillment Request Number must be enabled.
API Limits: Monitor to avoid sync interruptions.
Pro Tip: Enable all required fields to ensure accurate shipment syncing.
Conclusion
The Get Shipments integration automates the retrieval of shipment details, ensuring your system reflects accurate tracking and shipping information. Customize mappings and schedules to fit your workflow, streamlining order fulfillment. Happy syncing!
