Product Pricing & Quantity
Summary
Product price and quantity can be derived dynamically by aggregating linked source inventory and applying workflow rules, or locked to static values. Prices move through three stages (source inventory, product catalog, and channel listing) and the customer pays the listing’s List Price.
Aggregation combines values from a variant’s linked sources into a single price and quantity; workflow rules then shape those values before they reach your channels.
- Aggregate: combine price and quantity from multiple linked sources: Lowest, Highest, Average, or Sum.
- Workflow rules: apply markups, MSRP or MAP mapping, and discounts on top of aggregated values.
- Three stages: source inventory to product catalog to channel listing, each with its own fields.
- Lock values: freeze price or quantity on a variant so source changes do not override it.
- Profit view: see estimated profit and margin from List Price and Estimated Cost.
The Best Source concept
The Best Source is the primary linked source designated to provide the authoritative data for a product or variant. While aggregation rules (like Lowest or Highest) handle numerical values like price and quantity, the Best Source determines which supplier or warehouse provides descriptive attributes and serves as the default priority for sourcing decisions. You can identify the Best Source by the star icon next to a source name in the variant inventory view. To change it, you can manually select a new Best Source on the variant level or configure source priority rules to automate the selection based on your preferred vendor hierarchy.
| Stage | Fields |
|---|---|
| 1: Source Inventory (GIP / GIS) | Cost, MAP, MSRP, Source List Price: imported from your supplier. |
| 2: Product Catalog | Estimated Cost, Default List Price: your master record. |
| 3: Channel Listing | List Price: what customers see and pay. |
| Field | What it is |
|---|---|
| Cost | What you pay the supplier for the item. |
| Estimated Cost | Cost plus estimated shipping and dropship fees: your approximate landed cost. |
| Default List Price | Starting price on the catalog product; seeds the channel List Price. |
| List Price | Final selling price on a channel listing. |
| MAP / MSRP | Advertising floor and suggested retail; reference inputs you can enforce or map with rules. |
| Field | Options |
|---|---|
| Pricing | Lowest, Highest, Average. |
| Quantity | Lowest, Highest, Average, Sum. |
| Out of Stock | Omit out-of-stock sources from the calculation. |
Default List Price in Flxpoint differs from the price shown on the channel
The channel List Price is separate from the catalog Default List Price. A channel-level Price/Quantity workflow or a price lock can override it. Check the channel’s Price/Quantity workflow and any MAP or lock on the variant.
A pricing rule (for example a percent increase) is not applied to some SKUs
Confirm the SKUs are in the target list and not blocked by a MAP rule or a price lock. Locked variants and MAP enforcement are skipped by markup rules.
Listings still show the old price after an update
A catalog update alone may not reprice listings. Run the channel’s price and quantity sync, or rebuild the listings, so the change flows to the channel.
Which price do customers actually pay?
The List Price on the channel listing. Everything upstream is an input used to set it.
What is the difference between Cost and Estimated Cost?
Cost is the supplier’s item price; Estimated Cost adds estimated shipping and dropship fees for your landed cost.
Does the hourly Secondary (GIS) sync update prices?
Yes. Cost, MAP, MSRP, and Source List Price refresh on the Secondary sync by SKU. Catalog and channel prices you set with rules are preserved.
How do I make sure I never advertise below MAP?
Use a pricing rule to enforce MAP wherever the supplier provides it.
How is profit margin calculated?
(List Price − Estimated Cost) / List Price. Profit with fees also subtracts estimated shipping and dropship fee.
What it does
When multiple sources provide the same product, Flxpoint can automatically aggregate their individual stock levels into a single total quantity. This allows you to represent your full selling potential on channels like Amazon or Shopify by summing the inventory available across your entire supplier network.
How matching works
Flxpoint identifies identical products across different sources using unique identifiers. To successfully merge quantities, the products must share a matching value in one of the following fields:
- UPC (Universal Product Code)
- GTIN (Global Trade Item Number)
- EAN (European Article Number)
- MPN (Manufacturer Part Number) + Brand
When the Build Master Catalog job runs, Flxpoint identifies these matches and creates a single Master Catalog record linked to multiple source inventory records.
Configuring quantity aggregation
- Navigate to Inventory and select your Master Catalog.
- Locate the product you wish to aggregate and ensure it is linked to all relevant sources (e.g., D&H and TD Synnex).
- Navigate to Channels and select the specific sales channel where you want to show the combined total.
- Open the Mapping Template for that channel and locate the Quantity field.
- Ensure the mapping logic is set to use the Estimated Quantity or Total Quantity across all linked sources.
- Save the template and run a Channel Sync to update the listing.
Calculation and updates
By default, Flxpoint calculates the aggregate quantity as the sum of all active, non-paused sources. If Source A has 10 units and Source B has 25 units, the Channel Listing will reflect a total of 35 units.
Note: If you have applied specific quantity rules (such as a "Maximum Quantity to Sync" or "Safety Stock" buffer) at the source level, these rules are applied before the quantities are summed for the channel.Common issues
Quantities are not merging?
Check the identifiers in the Source Inventory records. If Source A lists a UPC as a 12-digit number and Source B includes leading zeros, they may not match. Ensure your Mapping Templates for "Get Inventory" normalize these identifiers.
Total quantity is lower than expected?
Verify that all sources are currently enabled and not in a "Paused" status. Flxpoint excludes quantities from sources that are disabled or have failed their most recent inventory sync.