Importing Source Inventory

July 20, 2026

Summary

Importing pulls product data, pricing, quantity, and status into Source Inventory by running a source’s Get Inventory Primary integration, governed by Parent SKU / Variant SKU rules and the import workflow.

OVERVIEW

Importing pulls product data, pricing, quantity, and status from a source into Source Inventory by running that source’s Get Inventory Primary integration. You must create and integrate the source first; once imported, you can build your Product Catalog and Channel Listings.

Run Get Inventory Primary to import new items and updates.
Variant SKU is required and must be unique — duplicates import only once.
Parent SKU groups variants under a parent; map options to distinguish them.
Set Parent SKU equal to Variant SKU to make each variant list on its own.
Bin Location tracks internal-warehouse stock via the Identifiers field.
The import workflow filters out unwanted variants before they enter the system.

PARENT-TO-VARIANT VS VARIANT-TO-VARIANT

Set in the GI-P template	Result
Parent SKU = Parent SKU (default)	Variants group under one parent (for example, one Baseball Hat parent with Blue / Red / Green variants), listing as a single product with options
Parent SKU = Variant SKU	Each variant becomes its own parent, so it can list on a channel as its own standalone listing (optionally also set Parent Title = Variant Title)

IMPORTANT NOTES

Note: Variant SKU is required and must be unique in Flxpoint. If a duplicate Variant SKU is found, Flxpoint imports only one of those variants.

Note: Parent SKU groups variants into one product. Map options (size, color, etc.) too, or variants will not be distinguishable under the parent.

Note: The import workflow runs before import. Conditional rules on the Get Inventory Primary page filter out unwanted variants before they enter Source Inventory. An over-broad rule silently drops items.

Note: Bin Location is for internal warehouses. It is populated from the GI-P feed under the Identifiers field. If the source is an Internal Warehouse, you can also edit Bin Location manually.

COMMON ISSUES

Items that exist in the feed are not appearing in Flxpoint

Check that the Source Inventory import workflow is not filtering them out (an over-broad category or brand rule will silently exclude them), and confirm each Variant SKU is unique — duplicates import only once. This has been seen where an entire product category in the feed did not ingest.

The source creates separate products instead of one product with variants

Each variant imported as its own parent because they did not share a Parent SKU. Map a common Parent SKU to group them and map options so sizes/colors become variants of one product rather than separate product codes.

A known SKU is not available to build under Source Inventory

Confirm the Variant SKU is unique and actually mapped — a duplicate Variant SKU means only one copy imports — and that the import workflow is not excluding it. Then re-run Get Inventory Primary.

FAQS

How do I import Source Inventory?

Run the source’s Get Inventory Primary integration: Sources, the gear icon for the source, Integrations, Get Inventory Primary, then Run Integration.

What do I need before importing?

You must first create a source and integrate it. Importing runs against that configured source.

Is Variant SKU required, and does it need to be unique?

Yes to both. A missing Variant SKU will not import, and a duplicate Variant SKU imports only one of the matching variants.

How do I make each variant list on its own?

In the GI-P mapping template set Parent SKU equal to Variant SKU (and optionally Parent Title to Variant Title). This creates a variant-to-variant relationship so each item lists separately.

What is the import workflow?

A set of conditional rules on the Get Inventory Primary integration that filter out undesirable variants before they are imported into Source Inventory.

Back to Source Inventory