Overview
Importing Source Inventory allows you to retrieve rich product data, pricing, quantity and/or status information from your source(s).
After Source Inventory is imported, you can build your Product Catalog and Channel Listings.
Before You Get Started
-
Before importing source inventory, you must complete the following:
Instructions
How to Import Source Inventory
Importing source inventory is done by executing the Get Inventory [Primary] integration on a Source.
How to Execute the Get Inventory [Primary] Integration |
---|
|
Important Considerations:
- Variant SKU is required and must be unique in Flxpoint. If a duplicate variant SKU is found, Flxpoint will only import one of these variants.
- Parent SKU allows you to group variants together to form variations. It is also recommended to map in options while creating variants. This will allow you to specify the options that distinguish one variant from another (i.e. size, color, etc.). To learn more about parents and variants, see auto$.
As Source Inventory variants are imported, they go through an import workflow which determines whether a variant is imported into the system.
Bin Location
The primary use for this is the ability for Internal Warehouses to be able to track where the inventory is located through the SKU. Located under the Identifiers field, it can be populated by pulling the data in from the GI-P (Get Inventory [Primary]).
If the Source is an Internal Warehouse, you will have the ability to manually edit Bin Location.
Removing Parent-to-Variant SKU Relationships
There are use-cases where you may want to deconstruct the parent and variant(s) relationship. The traditional parent and variant relationship allows for a group of variant options to be listed under a single list.
Deconstructing the parent and variant relationship will allow each variant to exist on a channel as its own listing.
How to Deconstruct the Parent and Variant Relationship |
---|
|
Parent-to-Variant SKU Relationship vs Variant-to-Variant SKU Relationship |
Imagine you have a Parent SKU that represents a baseball hat, with multiple Variants SKUs representing the various colors of that baseball hat. Let's see the two ways you can structure your Source Inventory. When creating a "Parent-to-Variant" SKU Relationship, you will set:
Your inventory will import in this structure: Parent SKU = 111 / Title = Baseball Hat
To create a "Variant-to-Variant" SKU relationship, you will set:
To further illustrate this, let's assume you also set:
Your inventory will import in this structure: Parent SKU = 123 / Title = Blue Baseball Hat
Parent SKU = 456/ Title = Red Baseball Hat
Parent SKU = 789 / Title = Green Baseball Hat
|
Source Inventory Import Workflow
The Source Inventory import workflow allows you to apply conditional rules to filter out undesirable inventory variants before they are imported into the system. This can be configured on the Get Inventory [Primary] integration page.
To learn more about what you can do with workflows, see Workflows.