How to Add & Configure a Source
Summary
Learn how to connect and manage fulfillment centers or supplier feeds by setting up integrations, importing inventory, and validating data. This guide is for users who need to automate product data, stock levels, and order routing between suppliers and their Flxpoint account.
Sources are located under the building icon in the left-hand navigation menu within the Sources tab. This screen provides a high-level view of all connected suppliers and warehouses. Each row represents a single source, while the columns display the status and configuration for specific operations like Get Inventory or Send Fulfillment Requests. To open a specific source's configuration and workflows, click the gear icon on its row.
To rename a source, open it, go to Basic Info, edit Source Name and click Update (in Flx Lite: Source Settings > Source Name). Source Type cannot be changed by non-staff. If you use accounting that matches vendors by source name (for example QuickBooks), renaming can break that match.
A source connects in one of four ways. Find your supplier's method below and gather what it needs before you start - the credentials all come from the supplier, not from Flxpoint.
| Field | What to enter |
|---|---|
API | An API key or client credentials from the supplier. Confirm the supplier's API supports Send FRs and Get Shipments before onboarding - not all supplier APIs expose these endpoints.
Where: the supplier's account or developer portal (API / integrations section). |
SFTP / FTP | Host, port, username, password, and the exact directory path where files are placed (whether files land in an
in/, out/, or root folder).Where: from the supplier - also confirm the file naming convention and update frequency. |
EDI | ISA/GS identifiers, transaction set codes, and the file exchange schedule. Requires coordination with the supplier's EDI team before setup.
Where: the supplier's EDI / integrations team. |
Built-in integration | Supplier account credentials (username/password or API token). For integrations like RSR, Keystone, Seawide, and Sports South.
Where: your supplier account portal - not your Flxpoint credentials. |
Using the Source Wizard
The Source Wizard is a guided setup for a new source. To open it, go to Sources, click the + button and choose Configure Single Source. Its steps are Getting Started, Create Source, Vendor Set-Up, Order Fulfillment and Integration Set-Up. The wizard creates the source and sets its vendor and order fulfillment settings. Its last step is an overview of the three main integrations (Get Inventory [Primary], Send Fulfillment Requests and Get Shipments); the wizard does not ask for credentials or a mapping template. You add those afterwards. When you finish the wizard, it takes you to the source's Get Inventory [Primary] page. Click Start Creating Integrations, choose the Integration Type under Connect an Integration, then click + New Connection and enter the credentials your supplier gave you. After that you can run your first Get Inventory job to populate the Source Inventory.
Adding one or more sources
To add a single source, navigate to Sources and click the + button, then select Configure Single Source. You must provide a Source Name and Source Type; you can assign or create a Vendor in the next step or skip it. Move through the wizard with Save & Next.
To add several sources at once, click the + button and choose Create Multiple Sources. Click Add Source to add a row for each origin, fill in Name and Type (Postal/Zip Code and Country Code are optional), then click Create Sources.
Confirm Send FRs and Get Shipments before onboarding
If orders will route to this source, confirm the supplier supports Send FRs and Get Shipments via their connection method - discovering they don't after catalog and listings are built causes significant rework. Confirm this before running the first Get Inventory.
Duplicate variant SKUs are dropped - a duplicate key error can appear
Variant SKUs must be unique in the supplier feed. If the feed has the same SKU on two rows, Flxpoint keeps only the first, and a duplicate error can be shown, something like a duplicate key error. Validate the raw feed for SKU duplicates before configuring the mapping template, especially for CSV and SFTP sources.
Every Get Inventory run can overwrite existing data
Each run updates source inventory records - including overwriting previously correct data if the supplier feed changes. Validate cost, price, and content after each new integration configuration, not just the first run.
Supplier outages affect all accounts simultaneously
When a built-in integration goes down (e.g. Sports South, RSR, Keystone), all Flxpoint accounts using it fail at once. If jobs suddenly fail across multiple sources from one supplier, check for a supplier-side outage before troubleshooting your configuration.
Primary vs Secondary Get Inventory are not interchangeable
Primary imports full product content - titles, images, descriptions, cost, and quantity. Secondary imports price and quantity only, runs more frequently. Running only Primary at high frequency on large catalogs creates unnecessary load and slower syncs.
Set an inventory buffer before enabling channel sync
Supplier feeds lag behind real inventory. Without a buffer, Flxpoint syncs reported quantity as-is and fast-moving SKUs oversell before the next update. Configure a buffer in Source → Settings → Enable Commit stock before the first Sync Listings run. Buffers reduce what's shown to the channel proactively; committed stock reduces available quantity reactively when an order is placed.
Sources without inventory pricing are restricted
Sources missing a Get Inventory Pricing (GIP) configuration are excluded from selection in onboarding steps 3.3 and 3.4. These sources appear at the bottom of dropdowns for Source Priority and internal warehouses, are disabled for selection, and cannot be sorted.
Imports new inventory items and full product data - titles, categories, images, content, cost, pricing, and quantity. The foundation import for every source: run it before anything else.
Price and quantity updates only - no product content. A lightweight feed for faster stock accuracy between Primary runs. Run more frequently than Primary (every 1-4 hours) when the supplier supports it.
Transmits orders to the supplier when an order routes to this source. Must be configured and test-transmitted before going live - required if you route orders to this source.
Pulls tracking numbers and shipment updates back from the supplier into Flxpoint, which then syncs tracking to the originating channel. Required if you route orders to this source.
Retrieves supplier invoices for processed fulfillment requests - used for cost reconciliation and accounting sync. For suppliers that provide invoice data electronically.
Retrieves product images from a separate FTP or ZIP file using a standard naming convention, independent of the main product feed. Use when the supplier delivers images separately from product data.
After running Get Inventory [Primary], all imported data appears in Products → Source Inventory. Validate before building your product catalog - bad data here propagates into published listings.
| View | Use for |
|---|---|
| Parents view | Confirming parent-level product data, category mapping, and image presence. Check that record count looks reasonable relative to the supplier's stated catalog size. |
| Variants view | Spot-checking individual SKU costs, quantities, and pricing. Confirm variants nest under the right parents - no floating variants without a parent. |
Importing all product images
To import more than just the primary image, locate the All Images mapping fields within the Get Inventory mapping utility. Unlike the Primary Image field which only pulls the first URL, the All Images fields allow you to map an array or list of secondary images. Set these fields to Direct Copy to ensure all available image URLs from your source feed are imported and stored on the product record.
Unclear source names make routing rules, reports, and troubleshooting significantly harder once you have more than a handful of sources. Recommended format: [Supplier Name] - [Type] - [Region/Warehouse]
| Example name | Why it works |
|---|---|
RSR - Vendor Warehouse - US | Supplier, connection type, and region all visible at a glance in routing rules |
Keystone - Dropship - East | Distinguishes from a potential West warehouse without ambiguity |
ACME - CSV Feed - Daily | Feed type and frequency help identify why the source updates differently from API sources |
Internal WH - Chicago - IL | Makes clear this is not a dropship supplier - routing rules can target it separately |
Sources are not deleted from within Flxpoint. If you no longer need one, email support@flxpoint.com with the source name and the Flxpoint team will remove it for you.
Before you ask, disable the source's scheduled operations (Get Inventory, Sync) and take it out of any Routing Groups, so no new orders are routed to it in the meantime. If you only need to stop inventory updates for a while, pausing the operations is enough: deletion is permanent and removes the source's inventory from your account.
Deactivating a source
To mark a source inactive, navigate to the source settings and toggle the status to Inactive. This stops Flxpoint from running scheduled jobs for this source and prevents new orders from routing to it. However, marking a source inactive does not automatically delist or remove products from connected sales channels like Shopify. Whether a listing is hidden or removed depends on your specific Channel listing workflow configuration.
When a source is deactivated, Flxpoint can archive the affected items and set their quantity to 0. If the same product is supplied by other active sources, those sources will continue to contribute inventory to the listing based on your routing and aggregation rules. To fully remove a source from your account, you must still contact support after deactivating its operations.
Get Inventory runs successfully but no inventory appears in Source Inventory
Inventory quantities completely wrong or all showing as 0
Source integration suddenly failing after working correctly
SKUs or MPNs changed unexpectedly after a Get Inventory run
Orders routing to this source but supplier says they're not receiving them
Inventory on channels is higher than the supplier's actual available stock
Failed to send Fulfillment Request: Unable to connect to SFTP?
How do I check the status of inventory sync jobs for a source?
How do I check the status of inventory sync jobs for a source?
What do the job statuses mean?
When should I use Get Inventory Primary vs Secondary?
Can I add the same supplier as multiple sources?
What happens when a supplier like Sports South or RSR goes down?
What's the right inventory buffer size?
Is vendor assignment required when adding a source?
How do I handle overlapping products when adding a new supplier?
When multiple suppliers provide the same product, Flxpoint identifies them by SKU. To ensure a new supplier's inventory contributes to an existing listing, map the new source's SKU to match the existing SKU in your Master Catalog. Flxpoint will then aggregate the quantities or apply your routing priorities to determine which source fulfills the order.
How is inventory prioritized across multiple sources?
Inventory quantities are combined or prioritized based on your Routing Group settings. You can configure Flxpoint to sum the total available stock across all sources for a single listing, or set a priority order (e.g., Source A first, then Source B) to control which supplier's stock is reflected and utilized first.
Can I change how a source sends me data without deleting the source?
Yes. Open the integration on the source's Integrations tab and use Change Integration to pick a different integration type and connection. You do not need to delete and recreate the source.
What do I enter to connect an inventory feed over FTP or SFTP?
Fill in the host, port, username and password (or key file for SFTP), the protocol, the folder to read from and the file name. For SFTP the file name can include * as a wildcard to pick the matching file.
How can I see which feed file my source last imported?
Open the source's integration and check its recent notifications, then use View Logs on the latest run. The log lists the file name it downloaded and the time of the run.
How do I import product images that are stored on my supplier's FTP server?
Add the Get Inventory Images integration to the source and map the image field in the mapping template to the image file name or path. Each image is matched against the files on the FTP server and downloaded; a zip of images can also be supplied.
How do I get my supplier's custom API connected?
When adding a source, use 'Not Listed? Request a custom integration', which opens the contact page, and send the vendor's API documentation, endpoints and credentials. The integrations team reviews the request.
Can Flxpoint read my supplier's website for cost?
No. Pricing rules work from values that come in through the supplier's feed, file or API, so the cost must be in that data. A web login connection can only download a file the supplier provides behind a login, not read prices from web pages.
Where can I see which suppliers Flxpoint already integrates with?
When you add a source in Flxpoint, choose the FLX Supplier Directory option to browse and connect to integrated suppliers. Choose the manual option instead if your supplier is not in the directory.
Default source type
When you create a new source in Flxpoint, the system now automatically defaults the Source Type field to Vendor Warehouse. This applies to all creation workflows, ensuring that new inventory origins are pre-configured for standard supplier and warehouse operations by default.
Creation workflows
The Vendor Warehouse default is applied across the following areas of the platform:
Individual Creation: Going to Sources, clicking the + button and choosing Configure Single Source.
Bulk Creation: Going to Sources, clicking the + button, choosing Create Multiple Sources and adding a row for each source.
Note: While Vendor Warehouse is the standard default, you can choose a different Source Type while you create the source: Internal Warehouse, External Warehouse or Product Data Source. After the source exists, only Flxpoint support can change its type, so contact support if a source needs a different one.
FAQs
Does this change existing sources?
No. This default only applies to new sources created after the update. Existing sources will retain their currently assigned source types.
Can I change the type after the source is created?
Not on your own. The Source Type is set when the source is created, and it shows as read-only in the source's Basic Info. If a source has the wrong type, contact Flxpoint support and they can change it.
What it does
Flxpoint allows you to enable multiple Fulfillment Request (FR) integrations on a single source simultaneously. When multiple integrations are active, Flxpoint sends the order data through every enabled integration in parallel. This is most commonly used when transitioning a vendor from one method to another, such as moving from manual email PDFs to automated CSV exports, ensuring no orders are missed during the switch.
How to connect a second integration
- Navigate to Sources and select the specific source you want to modify.
- Click the Integrations tab and locate the Fulfillment Requests section.
- Click Add Integration to choose a second connection type (e.g., if you already have Email PDF, you might add CSV via SFTP).
- Configure the connection settings for the new integration, including credentials and mapping templates.
- Ensure the Status toggle is set to Enabled for both the old and new integrations.
Expected behavior
When an order is routed to a source with multiple active FR integrations, Flxpoint performs the following actions:
- Generates a Fulfillment Request for the source as usual.
- Triggers all enabled FR integrations at the scheduled time or upon manual execution.
- Sends the order data to all endpoints (e.g., one copy goes to the vendor's email, and another is uploaded to their SFTP server).
Transitioning between methods
To safely migrate a vendor to a new fulfillment method, follow this recommended workflow:
- Parallel Run: Enable the new integration alongside the existing one. Monitor both for 2 to 3 days to ensure the new data format (CSV/EDI) is accurate and successfully received.
- Verification: Confirm with the vendor that the new automated method contains all necessary fields and matches the legacy PDF or email format.
- Deactivation: Once the new method is confirmed stable, navigate back to the source integrations and toggle the old integration to Disabled.
Common issues
Vendor fulfills the order twice?
This occurs because both integrations are active. Flxpoint sends the request to all enabled endpoints. Always notify your vendor before enabling a second integration so they can ignore the duplicate during the testing period.
Integration types that cannot coexist?
While most standard integrations (Email, CSV, SFTP, HTTP) can run together, avoid running multiple API-based integrations that pull their own status updates, as they may conflict when trying to write back fulfillment data to the same Fulfillment Request in Flxpoint.