CSV _ XLSX File as source

Table of Contents

How to Connect Product Operations Order Operations

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

Step 1: Log into your Flxpoint account and navigate to the Sources tab.

Step 2: Click on + Add Source and select Configure Single Source.

Step 3: In the Source Wizard, name your source (e.g., “CSV / XLSX”) and select the Source Type (e.g., Vendor Warehouse, Internal Warehouse, External Warehouse, or Product Data Source). Click Save & Next.

Step 4: Configure Order Fulfillment Settings:

Choose whether to use default settings (Yes) or customize them (No, Customize).

Set options like Override Auto Processing, Commit Stock?, Inventory Management, and Allow Backorders.

Click Save & Next.

Step 5: Set up Shipping Cost Estimations:

Choose to use Rate Shopping or Estimates via Rules.

If using Rate Shopping, ensure you have a rate shopping account set up.

Acknowledge that your source has product dimensions, weight, and a valid address for accurate estimates.

Click Save & Next.

Step 6: Under Integration Set-Up, select Get Inventory [Primary] and click Start Creating Integrations.

Step 7: Select CSV / XLSX File as your integration type, then click + New Connection.

Step 8: In the New CSV/XLSX File Connection popup, choose your Connection Type and fill in the required fields:

FTP (Basic Auth): Enter FTP host, port, user, password, etc.

Manual File: Upload your CSV/XLSX file directly.

HTTP: Provide the file URL (with optional Basic Auth).

Email (Inbound): Enter email server details (IMAP/POP), folder, etc.

Google Sheets File: Use the download URL for your Sheet in CSV format.

FTP (Token Based): Upload your token file and passphrase.

Click Save and Proceed.

Step 9: Complete the remaining steps in the wizard (e.g., Configure Settings and Define a Mapping Template) to finalize your CSV/XLSX integration. Your source is now set up to pull inventory data.

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]

This guide walks you through the Get Inventory [Primary] section, designed to help you fetch and map inventory data from a CSV or XLSX file for seamless integration into your inventory management system. Whether you’re importing a small product catalog or managing a large dataset, this section ensures your source data aligns with your system’s required fields, so your inventory is accurately represented. Let’s explore how to set up and use this feature effectively.

Purpose of This Section

The Get Inventory [Primary] section connects your CSV/XLSX file to your inventory system, enabling 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.

This ensures your inventory data is accurate, organized, and ready for use.

How to Connect

This process can pull full product data (including variation structure), inventory, and pricing via CSV/XLSX format files. The file can be either with headers or headerless (i.e., mapping via indices). You can also use this operation to just pull in the SKU with quantity and price information if product data is not provided by your vendor.

Sample File: To help you get started, you can view or download a sample CSV/XLSX file here: Get Inventory [Primary] CSV/XLSX Sample File.

About the Sample File:

- Columns A and B are required (typically Parent SKU and SKU).

- Weight Unit is set to "pound" by default – this can be configured in your mapping template.

- Dimension Unit is set to "inch" by default – this can be configured in your mapping template.

Note: If you’ve already selected the connection type in the channel wizard (e.g., FTP, local file upload), you can skip this step. Otherwise, ensure your CSV/XLSX file is accessible via your chosen connection method before proceeding.

How the Mapping Works

The mapping process links your source file columns (e.g., SKU, quantity) to your inventory system’s fields. Here’s how it works:

1. Template Creation: You create a mapping template to define how your CSV/XLSX data connects to inventory fields.

2. Data Alignment: The template ensures that when you import data, the right information (e.g., Parent SKU, Cost) is populated in your system.

3. Reusability: Once saved, you can reuse the template for future imports, saving time and effort.

If a field isn’t mapped correctly, your import may fail or result in incomplete data, so accuracy is key.

Configuration Options

You can tailor your inventory import with these customizable settings:

- Header vs. Column Index: Choose whether your file uses header names (e.g., "Parent SKU") or column index positions (e.g., Column A).

- Field Mapping: Map source columns to inventory fields (e.g., "Cost" to "Cost").

- Decimal Formatting: Specify whether decimal values use a period (e.g., 99.99) or comma (e.g., 99,99) for fields like Cost, Weight, and MSRP.

- Default Units: Weight Unit defaults to "pound," and Dimension Unit defaults to "inch." Adjust these in the mapping template if needed.

- Required Columns: Ensure Columns A and B (typically Parent SKU and SKU) are present in your file, as they are required for the import to succeed.

These options give you control over how your inventory data is imported and processed.

Setup Instructions

Follow these steps to configure your Get Inventory [Primary] template:

1. Create a New Template: Name your template (e.g., "Primary Inventory Mapping") to keep it organized.

2. Select Header Type: Choose "Column Header Name" if your file has headers, or "Column Index Positions" if it doesn’t.

3. Map Fields: Link your source data to inventory fields. For example, map "Parent SKU" to the "Parent SKU" field.

4. Configure Decimal Formatting: For fields like Cost, select whether to use a period or comma for decimal places.

5. Adjust Units (Optional): Change the Weight Unit or Dimension Unit if your file uses different units (e.g., "kilogram" instead of "pound").

6. Save and Use: Save your template and apply it when importing inventory data.

Once set up, you’re ready to import with confidence.

Mapping Template Details

A mapping template defines how your source data translates to inventory fields. Below, we’ll break down the interface and options available.

Interface Overview

- The mapping screen is labeled “Get Inventory [Primary]” at the top. You can name your template (e.g., “Primary Inventory Mapping”).

- Three buttons are available: Delete (remove the template), Duplicate (copy it), and Save (store your changes).

- The screen includes sections for:

- Header Name vs. Column Index: Choose how your file identifies data.

- Parent Fields (From Value → To Inventory Parent Field): Map product-level data (e.g., Parent SKU, Brand).

- Variant Fields (From Value → To Inventory Variant Field): Map variant-level data (e.g., SKU, Quantity).

Mapping Options For each field, you can choose how to handle the data. Here are the options with explanations:

- Don’t Map: Ignore the field entirely. Use this for optional fields like "Category 3" if not needed.

- Set To Empty: Map the field but leave it blank (e.g., no description will be imported).

- Column: Link a source column directly (e.g., map "Parent SKU" to "Parent SKU").

- Value: Set a static value (e.g., set "Brand" to "Generic" for all products).

- Mapping Set: Apply a predefined mapping group (e.g., for complex data).

- Rules: Use conditional logic (e.g., "If quantity < 0, set to 0").

Fields may include dropdowns for options like "Dimension Unit" (e.g., inch, centimeter) or radio buttons for decimal formatting (period or comma).

Available Inventory Fields Here are key inventory fields you can map to:

- Parent Fields: Parent SKU, Brand, Category 1-3, Description, Title, Product Options, Attributes, Product Images, Custom Fields.

- Variant Fields: SKU, ASIN, Cost, Quantity, UPC, MPN, MSRP, Weight, Weight Unit, Dimension Unit, Height, Length, Width, Variant Images, Custom Fields, Variant Option Values.

Complete Field Mappings Here’s a detailed list of key inventory fields, with examples and suggested mappings:

Parent SKU: The unique identifier for the parent product.

- Example: "PROD-001"

- Suggested Mapping: Map to your "Parent SKU" column using "Column."

- Reason: Required field to identify the parent product (Column A in the sample file).

Brand: The product’s brand name.

- Example: "Acme"

- Suggested Mapping: Map to "Brand" column using "Column."

- Reason: Helps categorize and identify products.

Category 1: The primary category of the product.

- Example: "Electronics"

- Suggested Mapping: Map to "Category 1" column using "Column."

- Reason: Organizes products into categories.

SKU: The unique identifier for the product variant.

- Example: "PROD-001-BLACK"

- Suggested Mapping: Map to "SKU" column using "Column."

- Reason: Required field to identify the variant (Column B in the sample file).

Cost: The cost of the variant.

- Example: "29.99"

- Suggested Mapping: Map to "Cost" column using "Column," and select "Use a period to indicate the decimal place."

- Reason: Ensures accurate cost tracking.

Quantity: The available stock quantity.

- Example: "50"

- Suggested Mapping: Map to "Quantity" column using "Column."

- Reason: Tracks inventory levels.

Weight Unit: The unit of measurement for weight.

- Example: "pound"

- Suggested Mapping: Set to "Option" and select "pound" from the dropdown (default setting).

- Reason: Standardizes weight measurements.

Dimension Unit: The unit of measurement for dimensions.

- Example: "inch"

- Suggested Mapping: Set to "Option" and select "inch" from the dropdown (default setting).

- Reason: Standardizes dimension measurements.

Source Data Fields Available source fields include:

- Parent Fields: Parent SKU (T), Brand (T), Category 1-3 (T), Description (T), Title (T), Product Options (K/V), Attributes (K/V), Product Images (L), Custom Fields (K/V).

- Variant Fields: SKU (T), ASIN (T), Cost (N), Quantity (N), UPC (T), MPN (T), MSRP (N), Weight (N), Weight Unit (T), Dimension Unit (T), Height (N), Length (N), Width (N), Variant Images (L), Custom Fields (K/V), Variant Option Values (K/V).

Practice Mapping Try mapping the "Parent SKU" field to understand the process:

Troubleshooting

If you encounter issues, try these steps:

- Check that all required fields (e.g., Parent SKU, SKU) are mapped. Missing mappings can cause import failures.

- Ensure Columns A and B (Parent SKU and SKU) are present in your file, as they are required.

- Ensure the correct header type is selected ("Column Header Name" or "Column Index Positions"). Incorrect settings may lead to mapping errors.

- If decimal fields (e.g., Cost, Weight) fail to import, verify the decimal format setting (period vs. comma) matches your file.

For persistent issues, contact your system administrator.

Conclusion

With your Get Inventory [Primary] template configured, you can efficiently import accurate inventory data from your CSV/XLSX file. By mapping fields carefully, setting decimal formats, and adjusting units as needed, you’ll ensure your inventory is ready for use. Start importing and take control of your inventory management!

Get Inventory (Secondary)

Yes, we support Get Inventory (Secondary)

This file operation is only used if you are provided two separate files from your vendor in which one is for just product data (Get Inventory [Primary]) and another file is for just price/quantity/status (Get Inventory [Secondary])

This process can pull PQS (pricing, quantity, and status) data via CSV/XLSX format files. The file can be either with headers or headerless (i.e. mapping via indices).

Get Inventory [Secondary] CSV/XLSX Sample File: View/download sample file here

Get Inventory Images: SUPPORTED

Warning: For Google Sheet operations, it's required that you have the formatting on all of your columns set to "Plain Text". If you are running any operation and the operation is not importing new data, please reformat the Google sheet and try again. This should resolve your issue.

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

Yes, we support Send Fulfillment Requests!

This process will submit Fulfillment Requests/fulfillment orders (FRs/FOs) via CSV/XLSX file. The file can be either with headers or headerless.

Send FRs/FOs CSV Sample File: View/download sample file here

How to Change the File Format

In Configure Settings step under Advanced Settings you click File Extension

The 4 Options

Default (The same as format)
CSV
TSV
TXT

Sending FRs/FOs Via Email Connection

The Fulfillment requests will come from notify@flxpoint.com
- If you want a custom "Send From" email, you'll need to set up a Email Connection in your Flxpoint account. Please contact support@flxpoint.com to assist you with this.

Required Connections

Connection Name
Email Address (can have multiple separated by commas)

Advanced Settings

Email Address (From)

Default set to notify@flxpoint.com

Email Address (CC)

Select the email you want to CC

Email Address (BCC)

Select the email you want to BCC

Not Supported: Google Sheet connections do not support send FR/FOs.

Email Connection Configuration

For CSV/XLSX sources, you can configure an email connection to automatically retrieve files for processing. Follow these steps to set up your email connection:

Navigate to Email Connection Settings

Go to the Integrations > Sources section.
Select Email Connection under the connection setup.

Input the Required Fields:

Connection Name: Enter a descriptive name for the connection (e.g., "Supplier CSV Email").
Email Host: Input the email server (e.g., smtp.gmail.com).
Email Protocol: Select the appropriate protocol (IMAP/POP3).
Port: Use 993 for IMAP or 995 for POP3.
Email User: Replace the client-specific email with internal-accounts@flxpoint.com.
Email Password: Use the assigned password provided by Flxpoint support. (Example: tigbajawjocoru)
Email Folder: Enter the AID (Account ID) associated with the request to organize incoming files.

Enable Email Connection:

Click Save Connection to complete the setup.
Use the Test Connection option to verify email settings.

Important:

Use the provided email credentials and AID folder setup to configure your email connection.
If you need a new email address or require backend email group configurations, please contact Flxpoint support for assistance.

Get Shipments

Yes, we support Get Shipments integration!

This process will retrieve shipments for submitted FRs/FOs when they become available via CSV/XLSX file.

"Get Shipments" CSV/XLSX Sample File: View/download sample file here

Get Fulfillment Acknowledgments

Yes, we support Get Fulfillment Request Acknowledgements.

This process will retrieve FR/FO acknowledgements for submitted FRs/FOs when they become available via CSV/XLSX file.

Get Invoices

This process will retrieve invoices for submitted FRs/FOs when they become available via CSV/XLSX file.

"Get Invoices" CSV/XLSX Sample File: View/Download Sample File here

About This Template:

- Invoice Status is set to "Paid" by default. This can be configured in your mapping template.
- By default, the mapping template will not support itemized invoices, such as product, shipping, fees on separate rows. You can customize your mapping template to support this.

Flxpoint Knowledge