This guide walks you through setting up a CSV/XLSX File as a Sales Channel in Flxpoint, empowering you to seamlessly manage your product listings and orders. You’ll learn how to:
- Create and name your channel.
- Select the best processes for syncing listings or processing orders.
- Configure file connections using FTP/SFTP, HTTP, or Email.
Flxpoint’s CSV/XLSX integrations simplify the management of regularly updated product data. Whether you're maintaining a consistent data feed for your sales channel, business, or partners, this method ensures your information stays current with minimal setup effort.
How to Connect
- FTP (Basic Auth) - Provide FTP server details, username, and password.
- Manual File - Upload files manually through the Flxpoint interface.
- HTTP - Provide a URL where Flxpoint can fetch the file.
- Email (Inbound) - Set up an email address for Flxpoint to retrieve files.
- Google Sheets File - Link a Google Sheet with the necessary permissions.
- FTP (Token Based) - Use a token for secure FTP access.
- S3 HTTP File - Provide an S3 bucket URL and credentials.
- Email (Outbound) - Specify an email address to send files.
- FTP (Basic Auth) - Provide FTP server details.
- FTP (Token Based) - Use a token for secure FTP access.
- Channel Name: Ensure it matches your intended name (e.g., "My CSV/XLSX Channel").
- Processes: Verify the selected processes (e.g., Sync Listings, Get Orders).
- Connections: Confirm the inbound and outbound connections are correct.
Listing Operations
This section covers the operations for managing your listings using a CSV/XLSX channel.
Import Listings
Status: NOT SUPPORTED
The Link Listings feature is not currently available with CSV/XLSX integration processes.
Sync & Link Listings
- 1 Add the integration: Navigate to your listings import/sync area and select the CSV/XLSX listing sync option.
- 2 Choose your file source: Select where the file will come from (for example: a hosted URL, FTP/SFTP, or email attachment—based on your account setup).
- 3 Select file type: Choose CSV or XLSX.
- 4 Confirm file layout: Decide if your file has a header row (column names) and whether you need to skip any rows.
- 5 Set scheduling: Run manually or set an automated schedule (daily/hourly/etc.).
- 6 Run a test: Start with a small file to confirm mapping and expected updates.
| Setting | What it means | Example |
|---|---|---|
| File Has Headers | Turn on if the first row contains column names (SKU, Title, Price, etc.). | Row 1 = SKU,Title,Price → Headers = Yes |
| Delimiter (CSV) | The character separating values in your CSV file. |
SKU|UPC|Price → Delimiter = Pipe |
| Rows to Skip | Use if your file has extra lines before headers/data. | Headers start on row 5 → Skip = 4 |
| Sheet Index (XLSX) | Which Excel tab to read (starting at 0 for the first tab). | Second tab → Index = 1 |
| File Name / Pattern | Useful if your file name changes daily or includes a date. | listings_YYYYMMDD.csv |
| File Column | Maps To | Example | Purpose |
|---|---|---|---|
| SKU | Listing SKU | ABC123 | Matches rows to the correct listing |
| Title | Product Title | Blue Widget | Updates the listing name |
| Price | Listing Price | 19.99 | Updates the selling price |
| Quantity | Available Quantity | 50 | Updates inventory available to sell |
- No updates after a sync: Confirm you used the latest file and saved your mapping.
- “Columns shifted” / data misaligned: Check the CSV delimiter (comma vs pipe vs tab).
- Missing or wrong updates: Confirm SKU is present on every row and mapped correctly.
- XLSX reads the wrong tab: Confirm the correct sheet index.
- Headers not detected: Turn File Has Headers on (if row 1 contains column names).
- Extra lines above data: Increase Rows to Skip so the sync starts at the correct row.
It’s recommended. Headers make mapping easier and reduce mistakes as your file grows.
Yes—start with a small sample file (10–20 rows) to confirm mapping and expected results.
A small sample file, your column headers, and the time you ran the sync.
Publish Listings
- 1 Add the integration: Go to your CSV/XLSX file integrations area and select Publish Listings.
- 2 Connect to the destination: Choose where the exported file should be sent (based on your setup).
- 3 Choose file format: Select CSV or XLSX.
- 4 Choose file naming: Set a file name (and a date pattern if your destination expects a daily file).
- 5 Create your mapping template: Decide which listing fields export to which columns.
- 6 Run a test export: Export once and confirm the destination receives the file correctly.
- 7 Schedule it: Set an automated schedule to keep the destination up-to-date.
| Setting | What it controls | Example |
|---|---|---|
| File Name | The name of the exported file that will be created/sent. | listings_publish.csv |
| File Name Date Format (optional) | Use if your destination expects a dated file name. | listings_publish_YYYYMMDD.csv |
| Include Headers in File | Exports a header row (SKU, Title, Price, etc.). | Headers = Yes |
| File Format | CSV or XLSX output format. | CSV |
| Delimiter (CSV) | Character that separates values in the exported file. |
SKU|Title|Price → Pipe |
| Quote Character (CSV) | Wraps values that contain commas or special characters. |
"Blue Widget" → Double Quote |
| Line Separator (CSV) | Controls line breaks for compatibility (Windows vs others). | CRLF for Windows |
| Excel Sheet Index (XLSX) | Which sheet/tab to write to (starting at 0). | First sheet = 0 |
| File Extension | Usually matches the format (.csv or .xlsx). | .csv |
| System Field | Export Column | Example | Why it matters |
|---|---|---|---|
| Product SKU | Column 0 | ABC123 | Unique identifier for each row |
| Product Title | Column 1 | Blue Widget | Listing name in the destination |
| Description | Column 2 | A high-quality blue widget | Optional details for marketplaces |
| Image URL | Column 3 | https://example.com/image.jpg | Optional image reference |
| Product Price | Column 4 | 19.99 | Pricing in the destination |
| Inventory Quantity | Column 5 | 50 | Stock levels in the destination |
- Destination doesn’t receive the file: Confirm destination connection details and try a manual run.
- Destination rejects the file: Match the destination’s required delimiter, quote character, and header expectations.
- File opens but data looks misaligned: Delimiter mismatch (comma vs pipe vs tab) is the most common cause.
- Listings aren’t identifiable in the destination: Confirm SKU is mapped and exported.
- Special characters cause issues: Use Double Quote for quote character and confirm encoding expectations (if provided by the destination).
- Windows import problems: Try CRLF line separators.
Usually yes—most destinations expect a header row. Only turn it off if your destination explicitly requires no headers.
CSV is the most common and widely compatible. Use XLSX if your destination specifically requires Excel format.
A sample export file, your expected destination format (if provided), and the time you ran the export.
Order Operations
This section covers the operations related to processing orders, including retrieving new orders and syncing shipment data.
Get Orders
- Import order data, including billing and shipping addresses, from CSV or XLSX files.
- Update your system with order details like order numbers, line items, and costs.
- Automate the retrieval process using connection types like S3 HTTP, FTP, or Email.
- 1 Connecting to the Source: Establish a connection using methods like S3 HTTP, FTP, or Email to access your CSV/XLSX file.
- 2 Fetching File Data: The system retrieves the file from the specified source (e.g., an S3 bucket URL).
- 3 Extracting Order Details: Extract data such as Order Number, SKU, and Address Line 1 from the file.
- 4 Mapping Data: Map file columns (e.g., Order Number, Quantity) to your system's fields using a mapping template.
- 5 Syncing Data: Import the mapped data into your system, updating order records.
- 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
- 1 Add the Integration: Go to Channels > CSV/XLSX File > Integrations, select "Get Orders."
- 2 Connect to the Source: Choose a connection type (e.g., S3 HTTP, FTP, Email) and provide the necessary credentials or URL.
-
3 Configure Settings:
- Specify the file name or pattern (e.g., orders.csv).
- Set the number of rows to skip (e.g., 4 if headers start on row 5).
- Select the Excel sheet index (e.g., 0 for the first sheet).
- Define the delimiter (e.g., comma for CSV).
- Configure scheduling (e.g., daily at 6 AM UTC).
- 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
- 5 Run the Integration: Start with Run Sync or schedule.
| Setting | What it controls | Example |
|---|---|---|
| File Name Date Format | If your file name includes a date (e.g., orders_20250601.csv), specify the format here using placeholders like YYYY for year, MM for month, and DD for day. | orders_YYYYMMDD.csv |
| File Name | Enter the exact name of your file or a pattern if it includes dates (as set above). | orders.csv |
| File Has Headers | If your file has a header row (e.g., "Order Number,Address Line 1,SKU"), select "Yes." If it's just data without headers, select "No," and the system will use column numbers (e.g., Column 0, Column 1). | Yes |
| File Format | Choose the format of your file. Most users use CSV, but if you're uploading an Excel file, select XLSX. | CSV |
| Number of Rows to Skip | If your file starts with blank rows or comments before the actual data, specify how many rows to skip. | 4 (if headers start on row 5) |
| Excel Sheet Index | For XLSX files, specify which sheet to read (starting at 0). Use "0" for the first sheet, "1" for the second, etc. | 0 |
| Quote Character | If your file uses quotes around values (e.g., "12345","123 Main St"), specify the quote character. Usually, this can be auto-detected. | Double Quote |
| Delimiter | Choose the delimiter that separates values in your file. A CSV typically uses commas, but some files use pipes or tabs. | Comma (,) |
| Line Separator | Specify the line separator in your file. Most systems can auto-detect this, so you can usually leave it as "Default". | Auto-detect |
| File Extension | Override the default file extension if needed (normally .csv or .xlsx). | .csv |
| File Action | Description |
|---|---|
| Move File | After the order file is processed, Flxpoint moves it to a specified archive folder. |
| Delete File | Deletes the file from the server after successful import. |
| Append File | Appends content or flags to the file based on the configured append behavior (varies by file type). |
- In the configure settings, select Move, Delete, or Append under file actions and specify any required folder paths (e.g., an Archive directory).
- When Get Orders runs and successfully imports the file:
- The selected file action is executed.
- Files will move to the archive folder, be deleted, or be appended accordingly.
- If the file cannot be moved (e.g., permissions issue), it remains in place and the error is logged.
- Processed files are automatically moved to the configured archive directory.
- This prevents re-processing on future Get Order runs.
- Reduces clutter in the primary import folder.
- Ensure the FTP/SFTP user has write/move/delete permissions in the destination directory.
- Confirm that the folder path exists on the server.
- Check logs if files remain in the source folder after import.
- Files are moved only after a successful Get Orders run (never on failure).
- Screen labeled "Get Orders" at the top; name your template (e.g., "Get Orders 1").
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: File fields (left), your system fields (right).
- Don't Map: Ignore the field (e.g., Notes).
- Set To Empty: Clear the field in your system.
- Column: Map to a specific column in your file (e.g., Order Number to Column 0).
- Value: Set a static value for the field.
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., only sync orders from the last 7 days).
- Required Fields: Order Number, SKU.
- Required Field: Order Number uniquely identifies the order.
-
Error Scenario: Unmapped Order Number may cause:
Invalid request: Missing required field 'Order Number' for order sync
- Fix: Go to Channels > CSV/XLSX File > Templates > Get Orders > Field Mapping, map Order Number to a field, save, and re-run sync.
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Address Line 1 | Billing Address Line 1 | 123 Main St | Primary billing address line | Recommended |
| City | Billing City | New York | Billing city | Recommended |
| Country | Billing Country | USA | Billing country | Recommended |
| Full Name | Billing Full Name | John Doe | Billing recipient's name | Recommended |
| Postal Code | Billing Postal Code | 10001 | Billing postal code | Recommended |
| State | Billing State | NY | Billing state | Optional |
| Address Line 2 | Billing Address Line 2 | Apt 4B | Secondary billing address line | Optional |
| Company Name | Billing Company Name | Acme Corp | Billing company name | Optional |
| Country Code | Billing Country Code | US | Billing country code | Optional |
| Billing Email | john.doe@example.com | Billing email address | Optional | |
| First Name | Billing First Name | John | Billing first name | Optional |
| Last Name | Billing Last Name | Doe | Billing last name | Optional |
| Phone | Billing Phone | 555-123-4567 | Billing phone number | Optional |
| State Code | Billing State Code | NY | Billing state code | Optional |
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Created On | Invoice Created On | 2025-06-01 | Date invoice was created | Optional |
| Invoice Number | Invoice Number | INV12345 | Invoice identifier | Optional |
| Other Cost | Other Cost | 5.00 | Additional invoice costs | Optional |
| Shipping Cost | Shipping Cost | 10.00 | Shipping cost on invoice | Optional |
| Subtotal | Subtotal | 135.00 | Invoice subtotal | Optional |
| Tax Cost | Tax Cost | 5.00 | Tax amount on invoice | Optional |
| Total | Total | 150.00 | Total invoice amount | Optional |
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Order Number | Order Number | ORD12345 | Uniquely identifies the order | Required |
| Ordered On | Order Date | 2025-06-01 | Date the order was placed | Recommended |
| Reference Number | Reference Number | REF12345 | Additional order reference | Optional |
| Channel Shipping Text | Channel Shipping Text | Standard Shipping | Shipping method description | Optional |
| Note | Order Note | Customer requested gift wrap | Additional order notes | Optional |
| Order Total | Order Total | 150.00 | Total order amount | Optional |
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Quantity | Item Quantity | 2 | Number of items ordered | Recommended |
| SKU | Item SKU | ABC123 | Identifies the product | Required |
| Cost | Item Cost | 50.00 | Cost per item | Optional |
| Default Weight Unit | Default Weight Unit | kg | Unit for item weight | Optional |
| Price | Item Price | 75.00 | Price per item | Optional |
| Title | Item Title | Blue Widget | Item description | Optional |
| Weight | Item Weight | 1.5 | Weight of the item | Optional |
| File Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Address Line 1 | Shipping Address Line 1 | 123 Main St | Primary shipping address line | Recommended |
| City | Shipping City | New York | Shipping city | Recommended |
| Country | Shipping Country | USA | Shipping country | Recommended |
| Full Name | Shipping Full Name | John Doe | Shipping recipient's name | Recommended |
| Postal Code | Shipping Postal Code | 10001 | Shipping postal code | Recommended |
| State | Shipping State | NY | Shipping state | Optional |
| Address Line 2 | Shipping Address Line 2 | Apt 4B | Secondary shipping address line | Optional |
| Company Name | Shipping Company Name | Acme Corp | Shipping company name | Optional |
| Country Code | Shipping Country Code | US | Shipping country code | Optional |
| Shipping Email | john.doe@example.com | Shipping email address | Optional | |
| First Name | Shipping First Name | John | Shipping first name | Optional |
| Last Name | Shipping Last Name | Doe | Shipping last name | Optional |
| Phone | Shipping Phone | 555-123-4567 | Shipping phone number | Optional |
| State Code | Shipping State Code | NY | Shipping state code | Optional |
- File Availability: The file must be accessible at the specified source, or the sync will fail.
- Data Scope: Only data within the specified sheet and rows (after skipping) will be processed.
- Required Fields: Order Number and SKU must be mapped in the template.
- File not found or retrieval fails: Confirm the file is accessible at the specified source (S3 bucket, FTP path, etc.) and try a manual run.
- Import fails with missing field error: Ensure Order Number and SKU are both mapped in your template.
- Data looks misaligned or garbled: Delimiter mismatch (comma vs pipe vs tab) is the most common cause—double-check the delimiter setting.
- Wrong rows are imported: Check the "Number of Rows to Skip" and "File Has Headers" settings to make sure data starts where expected.
- Special characters cause issues: Use Double Quote for the quote character and confirm encoding expectations.
- XLSX reads wrong sheet: Confirm the Excel Sheet Index matches the sheet containing your order data (0 = first sheet).
- File action not working: Verify the File Action setting (Move, Delete, or Append) is correctly configured under Configure Settings.
If your file has a header row (e.g., "Order Number,Address Line 1,SKU"), select "Yes." If it's just data without headers, select "No," and the system will use column numbers (e.g., Column 0, Column 1).
Choose the format of your file. Most users use CSV, but if you're uploading an Excel file, select XLSX.
Yes. After testing a manual run, set an automated schedule (e.g., daily at 6 AM UTC) to keep orders synced automatically.
A sample order file, your mapping template name, the error message (if any), and the time you ran the import.
Sync Orders
- 1 Add the integration: Go to Channels > CSV/XLSX File > Integrations and select Sync Orders.
- 2 Connect to the destination: Choose where the exported file should be sent (e.g., S3 HTTP, FTP, Email) and provide the necessary credentials or URL.
- 3 Choose file format: Select CSV or XLSX.
- 4 Choose file naming: Set a file name (and a date pattern if your destination expects a daily file).
- 5 Create your mapping template: Decide which system fields export to which columns (see Mapping Utilities).
- 6 Run a test export: Export once and confirm the destination receives the file correctly.
- 7 Schedule it: Set an automated schedule (e.g., daily) to keep external records up-to-date.
| Setting | What it controls | Example |
|---|---|---|
| File Name | The name of the exported file that will be created/sent. | order_sync.csv |
| File Name Date Format (optional) | Use if your destination expects a dated file name. | order_sync_YYYYMMDD.csv |
| Include Headers in File | Exports a header row (Order Number, Status, Tracking Number, etc.). | Headers = Yes |
| File Format | CSV or XLSX output format. | CSV |
| Delimiter (CSV) | Character that separates values in the exported file. |
Order Number|Status|Tracking → Pipe |
| Quote Character (CSV) | Wraps values that contain commas or special characters. |
"Shipped" → Double Quote |
| Line Separator (CSV) | Controls line breaks for compatibility (Windows vs others). | CRLF for Windows |
| Excel Sheet Index (XLSX) | Which sheet/tab to write to (starting at 0). | First sheet = 0 |
| File Extension | Usually matches the format (.csv or .xlsx). | .csv |
- Don't Map: Ignore the field in the export.
- Set To Empty: Leave the field empty in the exported file.
- Column: Map to a specific column in the exported file (e.g., Order Status to Column 1).
- Value: Set a static value for the field.
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., only export orders updated in the last 24 hours).
| System Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Order Number | File Column 0 | ORD12345 | Uniquely identifies the order | Required |
| Order Status | File Column 1 | Shipped | Current status of the order | Recommended |
| Tracking Number | File Column 2 | 1Z9999W99999999999 | Shipping tracking number | Recommended |
| Updated On | File Column 3 | 2025-06-01 | Date the order was last updated | Optional |
| Note | File Column 4 | Delivered on time | Additional order notes | Optional |
| System Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| SKU | File Column 5 | ABC123 | Identifies the product | Recommended |
| Quantity | File Column 6 | 2 | Number of items in the order | Optional |
- Destination doesn't receive the file: Confirm destination connection details and try a manual run.
- Destination rejects the file: Match the destination's required delimiter, quote character, and header expectations.
- File opens but data looks misaligned: Delimiter mismatch (comma vs pipe vs tab) is the most common cause.
- Orders aren't identifiable in the destination: Confirm Order Number is mapped and exported.
- Special characters cause issues: Use Double Quote for the quote character and confirm encoding expectations.
- Windows import problems: Try CRLF line separators.
- Connection failures: The integration will pause and trigger notifications—check your connection credentials and destination availability.
Usually yes—most destinations expect a header row. Only turn it off if your destination explicitly requires no headers.
CSV is the most common and widely compatible. Use XLSX if your destination specifically requires Excel format.
Any field not mapped in your template will not appear in the output file. Double-check your template includes all fields the destination needs.
A sample export file, your expected destination format (if provided), and the time you ran the export.