CSV _ XLSX File as Channel

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

📋 Phase 1: Initial Channel Setup +
Access the Channels Section
Log into your Flxpoint account and navigate to the Sales Channels (or Reseller Channels) section on the left sidebar.
Create a New Channel
Click on + Add Channel to open the Channel Wizard and start the setup process.
Tip: If you’re managing multiple channels, consider naming them clearly to avoid confusion (e.g., "CSV Channel - Supplier A").
Select CSV/XLSX File as Channel Type
In the wizard, choose CSV/XLSX File from the list of supported channels. Name your channel (e.g., "My CSV/XLSX Channel") and select the processes you want to enable, such as Publish Listings, Get Orders, Sync Listings, and Sync Orders. Then click Next.
🔧 Phase 2: Configure Integration Type +
Confirm CSV/XLSX Integration
In the Configure Integration Type step, verify that CSV/XLSX File is selected as the integration type. Click Next to proceed.
🔐 Phase 3: Connect Channel +
Set Up Inbound Connection
Under CSV/XLSX File (Inbound), select how Flxpoint will receive data. Options include:
  • 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.
Fill in the required details and click Save Connection.
Set Up Outbound Connection
Under CSV/XLSX File (Outbound), select how Flxpoint will send data. Options include:
  • 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.
Fill in the required details and click Save Connection.
Verify Connections
Test each connection by clicking Test Connection to ensure Flxpoint can access the inbound and outbound sources. Once successful, click Next.
✅ Phase 4: Confirm Integrations +
Review and Confirm
In the Confirm Integrations step, review your settings:
  • 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.
Check the box to acknowledge that the information is correct, then click Confirm Integrations.
Note: After confirming, you won’t be able to modify these settings until you exit the channel setup.
🚀 Phase 5: Finalize Setup +
Complete Remaining Steps
Continue through the wizard’s remaining steps, such as Listing Management, Pricing & Quantity Rules, and Order Fulfillment. You can configure these now or click Set Up Later to handle them later.
Start Syncing
Once setup is complete, your CSV/XLSX File Channel will appear in the Channels list with a status of 100% Onboarded. You can now start syncing by configuring integrations for processes like Import Listings or Get Orders.
Next Steps: Go to the Import Listings section to start syncing your product data, or configure other processes as needed.

 

 

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 

Sync & Link Listings

Introduction to CSV/XLSX File Integration
Use this integration to import or update listings using a CSV or XLSX file. You’ll connect your file source, map file columns to listing fields, then run the sync manually or on a schedule.

Follow these steps:
  • 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.
Recommended: Keep your file columns consistent over time. If you rename headers, update your mapping.
Key Settings (Client-Facing)
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

Mapping tells the system which column in your file updates each listing field. Save your mapping once and reuse it each time your file updates.
SKU Mapping (Recommended)
In most setups, SKU is used to match each row to the correct listing.
Tip: If you use a different unique identifier, make sure it’s consistent in every file you sync.
Common Mapping Examples
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

Quick checks (most common fixes)
  • 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.
FAQs
Do I need headers?
It’s recommended. Headers make mapping easier and reduce mistakes as your file grows.
Can I test before syncing everything?
Yes—start with a small sample file (10–20 rows) to confirm mapping and expected results.
What should I share with support if I still need help?
A small sample file, your column headers, and the time you ran the sync.
Pricing tip: Keep price/quantity values clean (no currency symbols, no commas in numbers) to avoid parsing issues.

Publish Listings 

Publish Listings

Introduction to CSV/XLSX Listing Publishing
Use this integration to export listings from your system into a CSV or XLSX file and deliver that file to a destination (for example: a hosted location, FTP/SFTP, or email—based on your account setup). This helps keep your external listings updated with minimal manual effort.

Follow these steps:
  • 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.
Recommended: Start with a small test set of listings first, confirm the file format is accepted by the destination, then scale up.
Key Export Settings (Crucial)
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
Note: If the destination system has a required format, match its delimiter/quotes/headers exactly.

Mapping templates control which listing data is exported and how it appears in the output file (which column each field goes to).
Required Field: SKU
SKU should be mapped so each exported row is uniquely identified in the destination.
If SKU isn’t mapped: the destination system may reject the file or update the wrong listings.
Example Export Layout (Recommended)
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
Recommendation: If your destination requires specific column names/order, align your mapping to that spec and keep it consistent.

Most common issues
  • 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.
FAQs
Should I include headers?
Usually yes—most destinations expect a header row. Only turn it off if your destination explicitly requires no headers.
CSV or XLSX?
CSV is the most common and widely compatible. Use XLSX if your destination specifically requires Excel format.
What should I send support if I need help?
A sample export file, your expected destination format (if provided), and the time you ran the export.
Tip: If the destination has a template file, use it as your reference for column order and naming.
Conclusion
Publish Listings exports your listing data into a CSV/XLSX file and delivers it to your destination. With the right export settings and a saved mapping template, you can keep external listings updated automatically.

 

 

Order Operations 

This section covers the operations related to processing orders, including retrieving new orders and syncing shipment data.

Get Orders 

Get Orders

Introduction to CSV/XLSX Order Integration
Welcome to the CSV/XLSX Order Integration guide for retrieving orders! This integration allows you to import order data from CSV or XLSX files into your system. It ensures your orders, including billing and shipping details, are accurately synced. Let's get started!

Purpose of This Integration
The CSV/XLSX Order Integration enables you to:
  • 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.
This ensures your order records are up-to-date with minimal manual effort.
How the Integration Works
The integration follows these steps:
  • 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).
Pro Tip: Schedule regular syncs to keep your order data updated automatically.
Note: File retrieval failures will pause the integration and trigger notifications.
Setup Instructions
Follow these steps:
  • 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.
Configuration Options
Use these settings to set up how your CSV or XLSX file containing order data will be processed. Each option helps the system understand your file's structure and schedule the sync.
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 Actions (Move / Delete / Append)
Flxpoint now supports Move, Delete, and Append file actions for FTP/SFTP Get Orders integrations in channel setups. These actions allow you to control what happens to a file after it has been successfully processed.
What File Actions Are Supported?
You may configure any of the following actions on your CSV/XLSX File Channel → Get Orders:
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).
These settings are located inside the CSV/XLSX File Channel → Get Orders → Configure Settings.
CSV/XLSX File Channel - Get Orders - Configure Settings
How It Works
  • 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.
Example: Move File to Archive Folder
If Move File is selected:
  • 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.
Notes & Troubleshooting
  • 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).
Note: Setting the correct delimiter and quote character ensures your file is parsed accurately. If your file fails to load, double-check these settings.

Mapping templates control which CSV/XLSX file order data is imported into your system.
Interface Overview
  • 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).
Mapping Options
  • 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.
Order Number Mapping Requirement
The Order Number field must be mapped to ensure proper order identification.
  • 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.
Recommendation: Always map Order Number and SKU for reliable order syncing.
Complete Field Mappings
Below are the fields you can map from your CSV/XLSX file:
Billing Address
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
Email 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
Channel Invoice
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
Order
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
Order Line Item
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
Shipping Address
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
Email 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

Limitations
Be aware of these limitations:
  • 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.
Most common issues
  • 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.
FAQs
Should my file have 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).
CSV or XLSX?
Choose the format of your file. Most users use CSV, but if you're uploading an Excel file, select XLSX.
Can I schedule the import?
Yes. After testing a manual run, set an automated schedule (e.g., daily at 6 AM UTC) to keep orders synced automatically.
What should I send support if I need help?
A sample order file, your mapping template name, the error message (if any), and the time you ran the import.
Tip: Schedule regular syncs to keep your order data updated automatically. File retrieval failures will pause the integration and trigger notifications.
Conclusion
The CSV/XLSX Order Integration automates order retrieval, ensuring your system reflects accurate order details, including billing and shipping information. Customize settings and mappings to fit your workflow, streamlining the process. Happy syncing!

Sync Orders 

Sync Orders

Introduction to CSV/XLSX Order Sync
Use this integration to export updated order data—such as statuses and tracking numbers—from your system into a CSV or XLSX file and deliver it to a destination (for example: a hosted location, FTP/SFTP, or email, based on your account setup). This keeps your external records in sync with minimal manual effort.

Follow these steps:
  • 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.
Recommended: Start with a small test set of orders first, confirm the file format is accepted by the destination, then scale up.
Key Export Settings (Crucial)
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
Note: Ensure the delimiter and quote character match the requirements of the external system receiving the file.

Mapping templates control which order data from your system is exported and how it appears in the output file.
Required Field: Order Number
Order Number must be mapped so each exported row is uniquely identified in the destination.
If Order Number isn't mapped: the export may fail with:
Invalid request: Missing required field 'Order Number' for order sync
Fix: Go to Channels > CSV/XLSX File > Templates > Sync Orders > Field Mapping, map Order Number to a column, save, and re-run sync.
Mapping Options
  • 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).
Complete Field Mappings
Order Details
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
Order Line Item
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
Recommendation: Always map Order Number for reliable syncing. If your destination requires specific column names or order, align your mapping to that spec.

Most common issues
  • 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.
FAQs
Should I include headers?
Usually yes—most destinations expect a header row. Only turn it off if your destination explicitly requires no headers.
CSV or XLSX?
CSV is the most common and widely compatible. Use XLSX if your destination specifically requires Excel format.
Only mapped fields are exported.
Any field not mapped in your template will not appear in the output file. Double-check your template includes all fields the destination needs.
What should I send support if I need help?
A sample export file, your expected destination format (if provided), and the time you ran the export.
Tip: Schedule regular syncs to keep your external systems updated automatically. If a destination has a template file, use it as your reference for column order and naming.
Conclusion
The CSV/XLSX Order Sync integration exports your updated order data—statuses, tracking numbers, and more—into a file and delivers it to your destination. With the right export settings and a saved mapping template, you can keep external records updated automatically.