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.
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.
in/, out/, or root folder).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.
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. |
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 |