CSV/XLSX files enable flexible operations by serving as a source for importing data. These files support various configurations, with formats tailored to mapping templates, such as "header" or "index" configurations, ensuring compatibility with your specific workflow requirements.
How to Connect
📋 Phase 1: Initial Source Setup
+
Navigate to Connections
Log into your Flxpoint account. In the left panel, locate the Connections section (indicated by a building icon) and click to access it.
Access Sources
Within the Connections section, go to the Sources tab.
Create a New Source
In the Sources tab, click the + button to start setting up a new source.
Tip: Have your source 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:
Replace
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 (Primary): Retrieve primary inventory data. Set sync frequency and map fields (e.g., SKU, Description, Stock Level).
Get Inventory (Secondary): Set up an additional inventory feed. Configure sync frequency and field mappings.
Get Shipments: Retrieve shipment updates. Set sync frequency and map fields (e.g., Tracking Number, Shipment Date).
Get Fulfillment Acknowledgments: Receive updates on fulfillment request statuses.
Get Invoices: Retrieve invoice data. Map fields (e.g., Invoice Number, Amount).
Note: You can enable any combination of these integrations to suit your workflow.
🛒 Phase 4: Fulfillment Setup
+
Configure Fulfillment Integration
Set up the fulfillment-related integration:
Send Fulfillment Requests: Enable to send fulfillment requests. Ensure proper mapping of request fields.
Tip: Accurate field mapping ensures seamless fulfillment 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 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 (Primary)
Supported | Get Inventory [Primary]
Introduction to Get Inventory [Primary]
Welcome to the Get Inventory [Primary] (GIP) integration guide! This integration allows you to fetch and map inventory data from a CSV or XLSX file into your inventory management system. It ensures your inventory data is accurately represented and ready for use. Let’s get started!
Note: This guide focuses on Get Inventory [Primary] (GIP). A similar integration, Get Inventory [Secondary] (GIS), follows a comparable process and will be covered in a separate guide.
Note: This guide focuses on Get Inventory [Primary] (GIP). A similar integration, Get Inventory [Secondary] (GIS), follows a comparable process and will be covered in a separate guide.
The Get Inventory [Primary] (GIP) integration enables you to:
- Fetch inventory data from a specified source (e.g., FTP, local file upload).
- Map your source data to inventory fields for accurate data import.
- Customize and manage mapping templates for different inventory types, streamlining your import process.
The integration follows these steps:
- 1 Connecting to Source: Establish a connection using methods like FTP (Basic Auth), manual file upload, or Google Sheets to access your CSV/XLSX file.
- 2 Fetching Inventory Data: The system retrieves data from the specified CSV/XLSX file, supporting both header-based and headerless files.
- 3 Extracting Inventory Details: Extract fields like Parent SKU, SKU, Quantity, and Cost from the file.
- 4 Mapping Data: Map file fields (e.g., Parent SKU, Quantity) to your system’s inventory fields using a mapping template.
- 5 Syncing Data: Import the mapped data into your system, updating inventory records.
- 6 Execution: Run manually with Run Integration or schedule (e.g., daily).
Pro Tip: Schedule regular imports to keep your inventory up-to-date without manual intervention.
Note: File access failures (e.g., incorrect FTP credentials) 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., "Parent SKU") or column indices (e.g., Column A).
- File Format: Select the file format: CSV (Comma Separated Values), TSV (Tab Separated Values), or XLSX (Microsoft Excel Open XML Spreadsheet).
- Download Files Modified in the Last X Days: Set the number of days (e.g., 14) to download only recently modified 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 your 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 file reading issues (e.g., for CSVs with quoted fields).
- Delimiter: Set the delimiter (e.g., comma, pipe) for CSV/TSV files (e.g., “SKU|UPC|COST” for pipe-delimited).
- File to Extract: Specify the exact 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 allow the job to proceed even if mapped, non-required headers (e.g., Brand) are missing. Default is 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”).
Note: Ensure the delimiter matches your file’s format to avoid parsing errors.
Follow these steps:
- 1 Add the Integration: Go to Channels > Integrations, select “Get Inventory [Primary].”
- 2 Connect to Source: Choose a connection type (e.g., FTP, manual file upload) and set up the connection.
-
3 Configure 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) For header-based feeds, go to Advanced Config and enable "Process Feed Even If Some Headers/Columns Are Missing."
- Configure advanced settings like rows to skip, sheet index, or delimiter.
- Configure scheduling.
- 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
- 5 Run the Integration: Start with Run Integration or schedule.
Mapping templates control which file data is imported into your inventory system.
Interface Overview
- Screen labeled “Get Inventory [Primary]” at the top; name your template (e.g., “Primary Inventory Mapping”).
- Buttons: Delete, Duplicate, Save Mapping.
- Sections: Header Name vs. Column Index, Parent Fields (From Value → To Inventory Parent Field), Variant Fields (From Value → To Inventory Variant Field).
Mapping Options
- Don't Map: Ignore the field (e.g., Category 3).
- Set To Empty: Clear the field in your system.
- Column: Map to a specific column in your file (e.g., “Parent SKU” to “Parent SKU”).
- Value: Set a static value for the field (e.g., “Brand” to “Generic”).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., if quantity < 0, set to 0).
- Required Fields: Parent SKU, SKU.
Parent SKU Mapping Requirement
The Parent SKU field must be mapped to ensure proper inventory identification.
- Required Field: Parent SKU uniquely identifies the parent product.
-
Error Scenario: Unmapped Parent SKU may cause:
Invalid request: Missing required field 'Parent SKU' for inventory sync
- Fix: Go to Channels > Templates > Get Inventory [Primary] > Field Mapping, map Parent SKU to a column, save, and re-run the integration.
Recommendation: Always map Parent SKU and SKU for reliable inventory syncing.
Handling Missing Headers (Header-Based Feeds Only)
The "Process Feed Even If Some Headers/Columns Are Missing" setting affects how the integration handles missing headers in header-based feeds:
- Required Header Missing (e.g., SKU): Job fails with an error listing the missing required header.
- Non-Required Header Missing (e.g., Brand): If the setting is enabled, the job succeeds, treating the field as if it were set to "Don’t Map" (existing values remain unchanged).
- Index-Based Mapping: This setting is ignored; all columns must still be present in the correct order.
Recommendation: After enabling this setting, review your mapping to ensure critical fields like price and quantity have matching headers.
Complete Field Mappings
Below are the fields you can map from your file:
Parent Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Parent SKU | Parent SKU | PROD-001 | Identifies the parent product | Required |
| Brand | Brand | Acme | Categorizes products by brand | Optional |
| Category 1 | Category 1 | Electronics | Organizes products into categories | Optional |
| Description | Description | High-quality product | Provides product details | Optional |
| Title | Title | Product Title | Names the product | Optional |
Variant Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| SKU | SKU | PROD-001-BLACK | Identifies the variant | Required |
| Cost | Cost | 29.99 | Tracks cost of the variant | Optional |
| Quantity | Quantity | 50 | Tracks inventory levels | Optional |
| Weight Unit | Weight Unit | pound | Standardizes weight measurements | Optional |
| Dimension Unit | Dimension Unit | inch | Standardizes dimension measurements | Optional |
Practice Mapping
Try mapping File - Parent SKU:
Be aware of these limitations:
- File Access Limits: Connection issues (e.g., FTP downtime) pause the integration.
- Data Scope: Only fetches data available in the CSV/XLSX file.
- Required Fields: Parent SKU and SKU must be mapped.
- Index-Based Mapping: All columns must be present in the correct order, regardless of the "Process Feed Even If Some Headers/Columns Are Missing" setting.
Troubleshoot issues with these steps:
- Connection Issues: Verify connection details (e.g., FTP credentials, file path).
- File Errors: Ensure the file format and delimiter match your settings.
- Missing Data: Check mapping template for mapped fields (e.g., Parent SKU, SKU).
- Missing Headers: If a required header (e.g., SKU) is missing, the job will fail. Add the header back or mark the field as not required.
- Decimal Issues: Verify decimal format settings (period vs. comma) for fields like Cost.
- Contact Support: Reach out to your system administrator with error details.
Diagnostic Tip: Missing inventory data often results from unmapped required fields or missing required headers.
Key information:
- Date: As of 10:26 AM -04, June 01, 2025, this integration is operational.
- Required Fields: Parent SKU and SKU must be mapped.
- File Requirements: Ensure Columns A and B (Parent SKU and SKU) are present in your file.
- Process Feed Setting: The "Process Feed Even If Some Headers/Columns Are Missing" setting is on by default for integrations created on or after 20 May 2025, allowing jobs to proceed if non-required headers are missing.
Pro Tip: Map all required fields and review mappings after enabling the "Process Feed Even If Some Headers/Columns Are Missing" setting to ensure accurate inventory syncing.
Conclusion
The Get Inventory [Primary] (GIP) integration automates inventory data import, ensuring your system reflects accurate inventory details. Customize mappings, handle missing headers with the new setting, and schedule imports to fit your workflow, streamlining inventory management. Happy syncing!
Get Inventory (Secondary)
Supported | Get Inventory [Secondary]
Introduction to Get Inventory [Secondary]
Welcome to the Get Inventory [Secondary] (GIS) integration guide! This integration allows you to fetch pricing, quantity, and status (PQS) data from a secondary CSV or XLSX file into your inventory management system. It is designed for scenarios where your vendor provides two separate files: one for product data (handled by Get Inventory [Primary] or GIP) and another for PQS data (handled by GIS). This ensures your inventory's pricing and stock levels are accurately updated. Let’s get started!
The Get Inventory [Secondary] (GIS) integration enables you to:
- Fetch pricing, quantity, and status (PQS) data from a secondary source (e.g., FTP, local file upload).
- Map your PQS data to inventory variant fields for accurate updates.
- Customize and manage mapping templates to streamline your PQS import process.
The integration follows these steps:
- 1 Connecting to Source: Establish a connection using methods like FTP (Basic Auth), manual file upload, or Google Sheets to access your secondary CSV/XLSX file.
- 2 Fetching PQS Data: The system retrieves pricing, quantity, and status data from the specified CSV/XLSX file, supporting both header-based and headerless files.
- 3 Extracting PQS Details: Extract fields like SKU, Quantity, Cost, and Allow Backorders from the file.
- 4 Mapping Data: Map file fields (e.g., SKU, Quantity) to your system’s inventory variant fields using a mapping template.
- 5 Syncing Data: Update the mapped PQS data in your system’s inventory records.
- 6 Execution: Run manually with Run Integration or schedule (e.g., daily).
Pro Tip: Schedule regular imports to keep your pricing and stock levels current without manual intervention.
Note: File access failures (e.g., incorrect FTP credentials) 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., "SKU") or column indices (e.g., Column A).
- File Format: Select the file format: CSV (Comma Separated Values), TSV (Tab Separated Values), or XLSX (Microsoft Excel Open XML Spreadsheet).
- Download Files Modified in the Last X Days: Set the number of days (e.g., 14) to download only recently modified 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 your 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 file reading issues (e.g., for CSVs with quoted fields).
- Delimiter: Set the delimiter (e.g., comma, pipe) for CSV/TSV files (e.g., “SKU|QUANTITY|COST” for pipe-delimited).
- File to Extract: Specify the exact file name (e.g., “pqs_data.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 allow the job to proceed even if mapped, non-required headers (e.g., Cost) are missing. Default is 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., “SKU” to “SKU”).
Warning: For Google Sheets operations, ensure all columns are formatted as "Plain Text." Incorrect formatting may prevent data imports.
Follow these steps:
- 1 Add the Integration: Go to Channels > Integrations, select “Get Inventory [Secondary].”
- 2 Connect to Source: Choose a connection type (e.g., FTP, manual file upload, Google Sheets) and set up the connection.
-
3 Configure 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) For header-based feeds, go to Advanced Config and enable "Process Feed Even If Some Headers/Columns Are Missing."
- Configure advanced settings like rows to skip, sheet index, or delimiter.
- Configure scheduling.
- 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
- 5 Run the Integration: Start with Run Integration or schedule.
Sample File: View or download a sample CSV/XLSX file here: Get Inventory [Secondary] CSV/XLSX Sample File.
Mapping templates control which file data is imported into your inventory system.
Interface Overview
- Screen labeled “Get Inventory [Secondary]” at the top; name your template (e.g., “Secondary PQS Mapping”).
- Buttons: Delete, Duplicate, Save Mapping.
- Sections: Header Name vs. Column Index, Variant Fields (From Value → To Inventory Variant Field).
Mapping Options
- Don't Map: Ignore the field (e.g., Dropship Fee).
- Set To Empty: Clear the field in your system.
- Column: Map to a specific column in your file (e.g., “SKU” to “SKU”).
- Value: Set a static value for the field (e.g., “Cost” to “10.00”).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., if quantity < 0, set to 0).
- Required Fields: SKU.
SKU Mapping Requirement
The SKU field must be mapped to ensure proper inventory variant identification.
- Required Field: SKU uniquely identifies the variant.
-
Error Scenario: Unmapped SKU may cause:
Invalid request: Missing required field 'SKU' for inventory sync
- Fix: Go to Channels > Templates > Get Inventory [Secondary] > Field Mapping, map SKU to a column, save, and re-run the integration.
Recommendation: Always map SKU for reliable inventory syncing.
Handling Missing Headers (Header-Based Feeds Only)
The "Process Feed Even If Some Headers/Columns Are Missing" setting affects how the integration handles missing headers in header-based feeds:
- Required Header Missing (e.g., SKU): Job fails with an error listing the missing required header.
- Non-Required Header Missing (e.g., Cost): If the setting is enabled, the job succeeds, treating the field as if it were set to "Don’t Map" (existing values remain unchanged).
- Index-Based Mapping: This setting is ignored; all columns must still be present in the correct order.
Recommendation: After enabling this setting, review your mapping to ensure critical fields like Quantity and Cost have matching headers.
Complete Field Mappings
Below are the fields you can map from your file:
Variant Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| SKU | SKU | PROD-001-BLACK | Identifies the variant | Required |
| Allow Backorders | Allow Backorders | True | Determines if backorders are allowed | Optional |
| Cost | Cost | 29.99 | Tracks cost of the variant | Optional |
| Quantity | Quantity | 50 | Tracks inventory levels | Optional |
| MSRP | MSRP | 49.99 | Sets manufacturer’s suggested retail price | Optional |
| MAP | MAP | 39.99 | Sets minimum advertised price | Optional |
| Source List Price | Source List Price | 45.00 | Records vendor’s list price | Optional |
| Dropship Fee | Dropship Fee | 5.00 | Adds a dropshipping fee | Optional |
| Shipping Cost | Shipping Cost | 10.00 | Sets shipping cost for the variant | Optional |
| Weight | Weight | 2.5 | Records weight of the variant | Optional |
| Weight Unit | Weight Unit | pound | Standardizes weight measurements | Optional |
| Dimension Unit | Dimension Unit | inch | Standardizes dimension measurements | Optional |
| Height | Height | 10.0 | Records height of the variant | Optional |
| Length | Length | 15.0 | Records length of the variant | Optional |
| Width | Width | 8.0 | Records width of the variant | Optional |
Practice Mapping
Try mapping File - SKU:
Be aware of these limitations:
- File Access Limits: Connection issues (e.g., FTP downtime) pause the integration.
- Data Scope: Only fetches PQS data available in the secondary CSV/XLSX file; product data must be imported via GIP.
- Required Fields: SKU must be mapped.
- Index-Based Mapping: All columns must be present in the correct order, regardless of the "Process Feed Even If Some Headers/Columns Are Missing" setting.
Troubleshoot issues with these steps:
- Connection Issues: Verify connection details (e.g., FTP credentials, file path).
- File Errors: Ensure the file format and delimiter match your settings.
- Missing Data: Check mapping template for mapped fields (e.g., SKU).
- Missing Headers: If a required header (e.g., SKU) is missing, the job will fail. Add the header back or mark the field as not required.
- Google Sheets Formatting: Ensure all columns are formatted as "Plain Text" in Google Sheets to avoid import issues.
- Decimal Issues: Verify decimal format settings (period vs. comma) for fields like Cost.
- Contact Support: Reach out to your system administrator with error details.
Diagnostic Tip: Missing PQS data often results from unmapped required fields or incorrect Google Sheets formatting.
Key information:
- Date: As of 10:29 AM -04, June 01, 2025, this integration is operational.
- Required Fields: SKU must be mapped.
- File Requirements: Ensure the SKU column is present in your file.
- Process Feed Setting: The "Process Feed Even If Some Headers/Columns Are Missing" setting is on by default for integrations created on or after 20 May 2025, allowing jobs to proceed if non-required headers are missing.
- Image Support: Get Inventory Images are supported for this integration.
Pro Tip: Map all required fields and review mappings after enabling the "Process Feed Even If Some Headers/Columns Are Missing" setting to ensure accurate PQS syncing.
Conclusion
The Get Inventory [Secondary] (GIS) integration automates the import of pricing, quantity, and status data, ensuring your inventory reflects accurate PQS details. Customize mappings, handle missing headers with the new setting, and schedule imports 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 Fulfillment Requests
Supported | Send Fulfillment Requests
Introduction to Send Fulfillment Requests
Welcome to the Send Fulfillment Requests (FRs/FOs) integration guide! This integration allows you to submit fulfillment requests or fulfillment orders (FRs/FOs) via a CSV or XLSX file, which can be sent through an email connection. It streamlines the process of requesting fulfillment from your vendors or suppliers, ensuring efficient order processing. Let’s get started!
The Send Fulfillment Requests (FRs/FOs) integration enables you to:
- Submit fulfillment requests or orders using a CSV/XLSX file, with support for both header-based and headerless formats.
- Send fulfillment requests via email, using a default or custom "Send From" email address.
- Automate retrieval of CSV/XLSX files through an email connection for seamless processing.
The integration follows these steps:
- 1 Connecting to Email Source: Set up an email connection to retrieve CSV/XLSX files containing fulfillment request data, or manually upload the file.
- 2 Fetching FR/FO Data: The system retrieves the fulfillment request data from the specified CSV/XLSX file, supporting both header-based and headerless files.
- 3 Extracting FR/FO Details: Extract necessary fields (e.g., order IDs, SKUs) from the file to create fulfillment requests.
- 4 Mapping Data: Map file fields to your system’s fulfillment request fields using a mapping template.
- 5 Sending Requests via Email: Send the fulfillment requests to the specified email addresses, with options to CC or BCC additional recipients.
- 6 Execution: Run manually with Run Integration or schedule (e.g., daily).
Pro Tip: Schedule regular sends to automate your fulfillment request process, reducing manual effort.
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 to set up a custom "Send From" email.
- Email Address (CC): Add email addresses to CC on the fulfillment request email.
- Email Address (BCC): Add email addresses to BCC on the fulfillment request email.
- Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
- Mapping Template: Define how file fields map to your system’s fulfillment request fields (e.g., “Order ID” to “Order ID”).
Note: Ensure recipient email addresses are valid to avoid delivery failures.
For CSV/XLSX sources, you can configure an email connection to automatically retrieve files for processing. Follow these steps:
- 1 Navigate to Email Connection Settings: Go to Integrations > Sources, and select Email Connection under the connection setup.
-
2 Input 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.
- 3 Enable Email Connection: Click Save Connection, then use the Test Connection option to verify settings.
Important: Contact support@flxpoint.com if you need a new email address or backend email group configurations.
Follow these steps:
- 1 Add the Integration: Go to Channels > Integrations, select “Send Fulfillment Requests.”
- 2 Set Up Email Connection: Configure an email connection to retrieve files (see Email Connection Configuration), or manually upload your CSV/XLSX file.
-
3 Configure 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.
- 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
- 5 Run the Integration: Start with Run Integration or schedule.
Sample File: View or download a sample CSV file here: Send FRs/FOs CSV Sample File.
Mapping templates control which file data is used to create fulfillment requests.
Interface Overview
- Screen labeled “Send Fulfillment Requests” at the top; name your template (e.g., “FR Mapping Template”).
- Buttons: Delete, Duplicate, Save Mapping.
- Sections: Header Name vs. Column Index, Fulfillment Request Fields (From Value → To Fulfillment Request Field).
Mapping Options
- Don't Map: Ignore the field (e.g., optional fields not needed for the request).
- Set To Empty: Clear the field in the fulfillment request.
- Column: Map to a specific column in your file (e.g., “Order ID” to “Order ID”).
- Value: Set a static value for the field (e.g., “Priority” to “High”).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., if quantity < 1, skip the request).
- Required Fields: Order ID (or equivalent identifier).
Order ID Mapping Requirement
The Order ID (or equivalent identifier) field must be mapped to ensure proper fulfillment request identification.
- Required Field: Order ID uniquely identifies the fulfillment request.
-
Error Scenario: Unmapped Order ID may cause:
Invalid request: Missing required field 'Order ID' for fulfillment request submission
- Fix: Go to Channels > Templates > Send Fulfillment Requests > Field Mapping, map Order ID to a column, save, and re-run the integration.
Recommendation: Always map Order ID for reliable fulfillment request submission.
Complete Field Mappings
Below are example fields you can map from your file:
Fulfillment Request Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Order ID | Order ID | ORD-12345 | Identifies the fulfillment request | 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 |
Practice Mapping
Try mapping File - Order ID:
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; additional data must be added to the file.
- Required Fields: Order ID (or equivalent identifier) must be mapped.
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 mapped fields (e.g., Order ID).
- Email Delivery Failures: Confirm recipient email addresses are valid and check for server issues.
- Contact Support: Reach out to support@flxpoint.com for assistance with email setup or delivery issues.
Diagnostic Tip: Missing fulfillment request data often results from unmapped required fields like Order ID.
Key information:
- Date: As of 10:36 AM -04, June 01, 2025, this integration is operational.
- Required Fields: Order ID (or equivalent identifier) must be mapped.
- 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: Map all required fields and test email connections to ensure reliable fulfillment request submission.
Conclusion
The Send Fulfillment Requests (FRs/FOs) integration automates the submission of fulfillment requests 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 fulfillment requests or orders (FRs/FOs) via a CSV or XLSX file. 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 FRs/FOs from a specified source (e.g., FTP, local file upload).
- Map shipment data to your system’s fields for accurate tracking and updates.
- Customize and manage mapping templates to streamline your shipment import process.
The integration follows these steps:
- 1 Connecting to Source: Establish a connection using methods like FTP (Basic Auth), manual file upload, or Google Sheets to access your CSV/XLSX file.
- 2 Fetching Shipment Data: The system retrieves shipment details from the specified CSV/XLSX file, supporting both header-based and headerless files.
- 3 Extracting Shipment Details: Extract fields like Fulfillment Request Number, Tracking Number, and Shipped At from the file.
- 4 Mapping Data: Map file fields (e.g., Tracking Number, SKU) to your system’s shipment fields using a mapping template.
- 5 Syncing Data: Import the mapped shipment data into your system, updating shipment records.
- 6 Execution: Run manually with Run Integration or schedule (e.g., daily).
Pro Tip: Schedule regular imports to keep your shipment tracking information current without manual intervention.
Note: File access failures (e.g., incorrect FTP credentials) 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., "Tracking Number") or column indices (e.g., Column A).
- File Format: Select the file format: CSV (Comma Separated Values), TSV (Tab Separated Values), or XLSX (Microsoft Excel Open XML Spreadsheet).
- Download Files Modified in the Last X Days: Set the number of days (e.g., 14) to download only recently modified files.
- Number of Rows to Skip: Skip rows (e.g., 4) if your 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 file reading issues (e.g., for CSVs with quoted fields).
- Delimiter: Set the delimiter (e.g., comma, pipe) for CSV/TSV files (e.g., “TRACKING|CARRIER|SHIPPED_AT” for pipe-delimited).
- File to Extract: Specify the exact file name (e.g., “shipments.csv”) if extracting from a zip/rar archive.
- Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
- Mapping Template: Define how file fields sync to your system (e.g., “Tracking Number” to “Tracking Number”).
Note: Ensure the delimiter matches your file’s format to avoid parsing errors.
Follow these steps:
- 1 Add the Integration: Go to Channels > Integrations, select “Get Shipments.”
- 2 Connect to Source: Choose a connection type (e.g., FTP, manual file upload) and set up the connection.
-
3 Configure 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).
- Configure advanced settings like rows to skip, sheet index, or delimiter.
- Configure scheduling.
- 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
- 5 Run the Integration: Start with Run Integration or schedule.
Sample File: View or download a sample CSV/XLSX file here: Get Shipments CSV/XLSX Sample File.
Mapping templates control which file data is imported into your shipment records.
Interface Overview
- Screen labeled “Get Shipments” at the top; name your template (e.g., “Shipment Mapping Template”).
- Buttons: Delete, Duplicate, Save Mapping.
- Sections: Header Name vs. Column Index, Shipment Fields (From Value → To Shipment Field), Shipment Item Fields (From Value → To Shipment Item Field).
Mapping Options
- Don't Map: Ignore the field (e.g., Note).
- Set To Empty: Clear the field in your system.
- Column: Map to a specific column in your file (e.g., “Tracking Number” to “Tracking Number”).
- Value: Set a static value for the field (e.g., “Carrier” to “UPS”).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., if Shipped At is empty, set to current date).
- 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, map Fulfillment Request Number to a column, save, and re-run the integration.
Recommendation: Always map Fulfillment Request Number for reliable shipment syncing.
Complete Field Mappings
Below are the fields you can map from your file:
Shipment Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Fulfillment Request Number | Fulfillment Request Number | FR-12345 | Identifies the shipment | Required |
| Carrier | Carrier | UPS | Specifies the shipping carrier | Optional |
| Method | Method | Ground | Specifies the shipping method | Optional |
| Note | Note | Handle with care | Adds additional shipment notes | Optional |
| Shipped At | Shipped At | 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
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| SKU | SKU | PROD-001-BLACK | Identifies the shipped item | Optional |
| Quantity | Quantity | 5 | Specifies the shipped quantity | Optional |
Practice Mapping
Try mapping File - Fulfillment Request Number:
Be aware of these limitations:
- File Access Limits: Connection issues (e.g., FTP downtime) pause the integration.
- Data Scope: Only fetches shipment data available in the CSV/XLSX file.
- Required Fields: Fulfillment Request Number must be mapped.
Troubleshoot issues with these steps:
- Connection Issues: Verify connection details (e.g., FTP credentials, file path).
- File Errors: Ensure the file format and delimiter match your settings.
- Missing Data: Check mapping template for mapped fields (e.g., Fulfillment Request Number).
- Decimal Issues: Verify decimal format settings (period vs. comma) for fields like Shipping Cost.
- Date Format Issues: Ensure the date format for fields like Shipped At matches your file’s format.
- Contact Support: Reach out to your system administrator with error details.
Diagnostic Tip: Missing shipment data often results from unmapped required fields like Fulfillment Request Number.
Key information:
- Date: As of 10:39 AM -04, June 01, 2025, this integration is operational.
- Required Fields: Fulfillment Request Number must be mapped.
- File Requirements: Ensure the Fulfillment Request Number column is present in your file.
Pro Tip: Map 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 for submitted FRs/FOs. Customize mappings and schedule imports to fit your workflow, enhancing your order fulfillment process. Happy syncing!
Get Fulfillment Acknowledgments
Supported | Get Fulfillment Request Acknowledgements
Introduction to Get Fulfillment Request Acknowledgements
Welcome to the Get Fulfillment Request Acknowledgements (Get FRAs) integration guide! This integration allows you to retrieve acknowledgment details for submitted fulfillment requests or orders (FRs/FOs) via a CSV or XLSX file. It ensures you can track the status and confirmation of your fulfillment requests, such as acceptance or rejection by vendors, seamlessly in your system. Let’s get started!
The Get Fulfillment Request Acknowledgements (Get FRAs) integration enables you to:
- Retrieve acknowledgment details for submitted FRs/FOs from a specified source (e.g., FTP, local file upload).
- Map acknowledgment data to your system’s fields for accurate tracking and updates.
- Customize and manage mapping templates to streamline your acknowledgment import process.
The integration follows these steps:
- 1 Connecting to Source: Establish a connection using methods like FTP (Basic Auth), manual file upload, or Google Sheets to access your CSV/XLSX file.
- 2 Fetching Acknowledgment Data: The system retrieves acknowledgment details from the specified CSV/XLSX file, supporting both header-based and headerless files.
- 3 Extracting Acknowledgment Details: Extract fields like Fulfillment Request Number, Acknowledgment Status, and Acknowledgment Date from the file.
- 4 Mapping Data: Map file fields (e.g., Acknowledgment Status, SKU) to your system’s acknowledgment fields using a mapping template.
- 5 Syncing Data: Import the mapped acknowledgment data into your system, updating acknowledgment records.
- 6 Execution: Run manually with Run Integration or schedule (e.g., daily).
Pro Tip: Schedule regular imports to keep your acknowledgment records current without manual intervention.
Note: File access failures (e.g., incorrect FTP credentials) 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., "Acknowledgment Status") or column indices (e.g., Column A).
- File Format: Select the file format: CSV (Comma Separated Values), TSV (Tab Separated Values), or XLSX (Microsoft Excel Open XML Spreadsheet).
- Download Files Modified in the Last X Days: Set the number of days (e.g., 14) to download only recently modified files.
- Number of Rows to Skip: Skip rows (e.g., 4) if your 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 file reading issues (e.g., for CSVs with quoted fields).
- Delimiter: Set the delimiter (e.g., comma, pipe) for CSV/TSV files (e.g., “FR_NUM|STATUS|DATE” for pipe-delimited).
- File to Extract: Specify the exact file name (e.g., “acknowledgments.csv”) if extracting from a zip/rar archive.
- Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
- Mapping Template: Define how file fields sync to your system (e.g., “Acknowledgment Status” to “Acknowledgment Status”).
Note: Ensure the delimiter matches your file’s format to avoid parsing errors.
Follow these steps:
- 1 Add the Integration: Go to Channels > Integrations, select “Get Fulfillment Request Acknowledgements.”
- 2 Connect to Source: Choose a connection type (e.g., FTP, manual file upload) and set up the connection.
-
3 Configure 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).
- Configure advanced settings like rows to skip, sheet index, or delimiter.
- Configure scheduling.
- 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
- 5 Run the Integration: Start with Run Integration or schedule.
Mapping templates control which file data is imported into your acknowledgment records.
Interface Overview
- Screen labeled “Get Fulfillment Request Acknowledgements” at the top; name your template (e.g., “FRA Mapping Template”).
- Buttons: Delete, Duplicate, Save Mapping.
- Sections: Header Name vs. Column Index, Acknowledgment Fields (From Value → To Acknowledgment Field), Acknowledgment Item Fields (From Value → To Acknowledgment Item Field).
Mapping Options
- Don't Map: Ignore the field (e.g., Note).
- Set To Empty: Clear the field in your system.
- Column: Map to a specific column in your file (e.g., “Acknowledgment Status” to “Acknowledgment Status”).
- Value: Set a static value for the field (e.g., “Acknowledgment Status” to “Accepted”).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., if Acknowledgment Date is empty, set to current date).
- Required Fields: Fulfillment Request Number.
Fulfillment Request Number Mapping Requirement
The Fulfillment Request Number field must be mapped to ensure proper acknowledgment identification.
- Required Field: Fulfillment Request Number uniquely identifies the acknowledgment.
-
Error Scenario: Unmapped Fulfillment Request Number may cause:
Invalid request: Missing required field 'Fulfillment Request Number' for acknowledgment sync
- Fix: Go to Channels > Templates > Get Fulfillment Request Acknowledgements > Field Mapping, map Fulfillment Request Number to a column, save, and re-run the integration.
Recommendation: Always map Fulfillment Request Number for reliable acknowledgment syncing.
Complete Field Mappings
Below are the fields you can map from your file:
Acknowledgment Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Fulfillment Request Number | Fulfillment Request Number | FR-12345 | Identifies the acknowledgment | Required |
| Acknowledgment Status | Acknowledgment Status | Accepted | Indicates the status of the request (e.g., Accepted, Rejected) | Optional |
| Acknowledgment Date | Acknowledgment Date | 2025-06-01 | Records the date of acknowledgment | Optional |
| Note | Note | Request processed successfully | Adds additional acknowledgment notes | Optional |
Acknowledgment Item Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| SKU | SKU | PROD-001-BLACK | Identifies the acknowledged item | Optional |
| Quantity | Quantity | 5 | Specifies the acknowledged quantity | Optional |
| Item Status | Item Status | Confirmed | Indicates the status of the item (e.g., Confirmed, Backordered) | Optional |
Practice Mapping
Try mapping File - Fulfillment Request Number:
Be aware of these limitations:
- File Access Limits: Connection issues (e.g., FTP downtime) pause the integration.
- Data Scope: Only fetches acknowledgment data available in the CSV/XLSX file.
- Required Fields: Fulfillment Request Number must be mapped.
Troubleshoot issues with these steps:
- Connection Issues: Verify connection details (e.g., FTP credentials, file path).
- File Errors: Ensure the file format and delimiter match your settings.
- Missing Data: Check mapping template for mapped fields (e.g., Fulfillment Request Number).
- Date Format Issues: Ensure the date format for fields like Acknowledgment Date matches your file’s format.
- Contact Support: Reach out to your system administrator with error details.
Diagnostic Tip: Missing acknowledgment data often results from unmapped required fields like Fulfillment Request Number.
Key information:
- Date: As of 10:44 AM -04, June 01, 2025, this integration is operational.
- Required Fields: Fulfillment Request Number must be mapped.
- File Requirements: Ensure the Fulfillment Request Number column is present in your file.
Pro Tip: Map all required fields to ensure accurate acknowledgment syncing.
Conclusion
The Get Fulfillment Request Acknowledgements integration automates the retrieval of acknowledgment details, ensuring your system reflects accurate status updates for submitted FRs/FOs. Customize mappings and schedule imports to fit your workflow, enhancing your order fulfillment process. Happy syncing!
Get Invoices
Supported | Get Invoices
Introduction to Get Invoices
Welcome to the Get Invoices integration guide! This integration allows you to retrieve invoice details for submitted fulfillment requests or orders (FRs/FOs) via a CSV or XLSX file. It ensures you can track and manage invoice information, such as invoice numbers, costs, and statuses, seamlessly in your system. Let’s get started!
The Get Invoices integration enables you to:
- Retrieve invoice details for submitted FRs/FOs from a specified source (e.g., FTP, local file upload).
- Map invoice data to your system’s fields for accurate financial tracking.
- Customize and manage mapping templates to streamline your invoice import process.
The integration follows these steps:
- 1 Connecting to Source: Establish a connection using methods like FTP (Basic Auth), manual file upload, or Google Sheets to access your CSV/XLSX file.
- 2 Fetching Invoice Data: The system retrieves invoice details from the specified CSV/XLSX file, supporting both header-based and headerless files.
- 3 Extracting Invoice Details: Extract fields like Fulfillment Request Number, Invoice Number, and Invoice Date from the file.
- 4 Mapping Data: Map file fields (e.g., Invoice Number, SKU) to your system’s invoice fields using a mapping template.
- 5 Syncing Data: Import the mapped invoice data into your system, updating invoice records.
- 6 Execution: Run manually with Run Integration or schedule (e.g., daily).
Pro Tip: Schedule regular imports to keep your invoice records current without manual intervention.
Note: File access failures (e.g., incorrect FTP credentials) 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., "Invoice Number") or column indices (e.g., Column A).
- File Format: Select the file format: CSV (Comma Separated Values), TSV (Tab Separated Values), or XLSX (Microsoft Excel Open XML Spreadsheet).
- Download Files Modified in the Last X Days: Set the number of days (e.g., 14) to download only recently modified files.
- Number of Rows to Skip: Skip rows (e.g., 4) if your 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 file reading issues (e.g., for CSVs with quoted fields).
- Delimiter: Set the delimiter (e.g., comma, pipe) for CSV/TSV files (e.g., “INVOICE_NUM|DATE|COST” for pipe-delimited).
- File to Extract: Specify the exact file name (e.g., “invoices.csv”) if extracting from a zip/rar archive.
- Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
- Mapping Template: Define how file fields sync to your system (e.g., “Invoice Number” to “Invoice Number”).
Note: Ensure the delimiter matches your file’s format to avoid parsing errors.
Follow these steps:
- 1 Add the Integration: Go to Channels > Integrations, select “Get Invoices.”
- 2 Connect to Source: Choose a connection type (e.g., FTP, manual file upload) and set up the connection.
-
3 Configure 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).
- Configure advanced settings like rows to skip, sheet index, or delimiter.
- Configure scheduling.
- 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
- 5 Run the Integration: Start with Run Integration or schedule.
Sample File: View or download a sample CSV/XLSX file here: Get Invoices CSV/XLSX Sample File.
Mapping templates control which file data is imported into your invoice records.
Interface Overview
- Screen labeled “Get Invoices” at the top; name your template (e.g., “Invoice Mapping Template”).
- Buttons: Delete, Duplicate, Save Mapping.
- Sections: Header Name vs. Column Index, Source Invoice Fields (From Value → To Source Invoice Field), Source Invoice Item Fields (From Value → To Source Invoice Item Field).
Mapping Options
- Don't Map: Ignore the field (e.g., Other Cost).
- Set To Empty: Clear the field in your system.
- Column: Map to a specific column in your file (e.g., “Invoice Number” to “Invoice Number”).
- Value: Set a static value for the field (e.g., “Invoice Status” to “Paid”).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., if Cost < 0, set to 0).
- Required Fields: Fulfillment Request Number.
Fulfillment Request Number Mapping Requirement
The Fulfillment Request Number field must be mapped to ensure proper invoice identification.
- Required Field: Fulfillment Request Number uniquely identifies the invoice.
-
Error Scenario: Unmapped Fulfillment Request Number may cause:
Invalid request: Missing required field 'Fulfillment Request Number' for invoice sync
- Fix: Go to Channels > Templates > Get Invoices > Field Mapping, map Fulfillment Request Number to a column, save, and re-run the integration.
Recommendation: Always map Fulfillment Request Number for reliable invoice syncing.
About This Template
Key details about the default template configuration:
- Invoice Status: Set to "Paid" by default. You can configure this in the mapping template to "Unpaid" or map it to a column in your file.
- Itemized Invoices: By default, the template does not support itemized invoices (e.g., product, shipping, fees on separate rows). Customize the mapping template to enable this support.
Complete Field Mappings
Below are the fields you can map from your file:
Source Invoice Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Fulfillment Request Number | Fulfillment Request Number | FR-12345 | Identifies the invoice | Required |
| Invoice Number | Invoice Number | INV-98765 | Uniquely identifies the invoice | Optional |
| Fee Cost | Fee Cost | 5.00 | Records any additional fees | Optional |
| Invoice Date | Invoice Date | 2025-06-01 | Records the invoice issuance date | Optional |
| Invoice Status | Invoice Status | Paid | Indicates payment status (default: Paid) | Optional |
| Other Cost | Other Cost | 3.00 | Records miscellaneous costs | Optional |
| Shipping Cost | Shipping Cost | 10.00 | Records the shipping cost | Optional |
| Tax Cost | Tax Cost | 2.50 | Records the tax amount | Optional |
Source Invoice Item Fields
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Cost | Cost | 50.00 | Total cost of the item | Optional |
| Invoice Item Type | Invoice Item Type | Product | Specifies the item type (e.g., Product, Shipping, Fee) | Optional |
| Per Unit Cost | Per Unit Cost | 10.00 | Cost per unit of the item | Optional |
| Quantity | Quantity | 5 | Number of units invoiced | Optional |
| SKU | SKU | PROD-001-BLACK | Identifies the invoiced item | Optional |
| Title | Title | Black Widget | Describes the invoiced item | Optional |
Practice Mapping
Try mapping File - Fulfillment Request Number:
Be aware of these limitations:
- File Access Limits: Connection issues (e.g., FTP downtime) pause the integration.
- Data Scope: Only fetches invoice data available in the CSV/XLSX file.
- Required Fields: Fulfillment Request Number must be mapped.
- Itemized Invoices: Not supported by default; requires custom mapping configuration.
Troubleshoot issues with these steps:
- Connection Issues: Verify connection details (e.g., FTP credentials, file path).
- File Errors: Ensure the file format and delimiter match your settings.
- Missing Data: Check mapping template for mapped fields (e.g., Fulfillment Request Number).
- Decimal Issues: Verify decimal format settings (period vs. comma) for fields like Cost or Shipping Cost.
- Date Format Issues: Ensure the date format for fields like Invoice Date matches your file’s format.
- Itemized Invoices Not Importing: Customize your mapping template to support itemized invoices if needed (e.g., map Invoice Item Type).
- Contact Support: Reach out to your system administrator with error details.
Diagnostic Tip: Missing invoice data often results from unmapped required fields like Fulfillment Request Number.
Key information:
- Date: As of 10:42 AM -04, June 01, 2025, this integration is operational.
- Required Fields: Fulfillment Request Number must be mapped.
- File Requirements: Ensure the Fulfillment Request Number column is present in your file.
- Default Settings: Invoice Status defaults to "Paid"; itemized invoices are not supported by default.
Pro Tip: Map all required fields and customize the template for itemized invoices to ensure accurate financial tracking.
Conclusion
The Get Invoices integration automates the retrieval of invoice details, ensuring your system reflects accurate financial information for submitted FRs/FOs. Customize mappings, support itemized invoices if needed, and schedule imports to fit your workflow, enhancing your financial management process. Happy syncing!