As product data moves through Flxpoint, pricing lives at three stages — the inventory imported from your suppliers (via Get Inventory Primary & Secondary, or GIP/GIS), your central Product Catalog, and the Channel Listings shown to customers. Each stage has its own pricing fields, and a price set at one stage feeds the next.
| 1 · Source Inventory (GIP / GIS) | 2 · Product Catalog | 3 · Channel Listings |
|---|---|---|
|
Imported from your supplier Cost · MAP · MSRP · Source List Price |
Your master record Estimated Cost · Default List Price |
What customers see & pay List Price |
The key idea: the prices imported from your supplier (Cost, MAP, MSRP, Source List Price) are reference values — none of them is automatically your selling price. Your selling price is the List Price on the channel listing, which you set (directly or with pricing rules) using those reference values as inputs.
Key Concepts
Four distinctions worth getting right before reading the field lists.
Cost vs. the other supplier prices. Cost is what you pay the supplier. MAP and MSRP are the advertising floor and suggested retail. Source List Price is the supplier's own retail price. None of these is your selling price — that's set downstream.
Cost vs. Estimated Cost. Cost is the supplier's item price. Estimated Cost is your approximate total cost to fulfill the item — Cost plus estimated shipping and dropship/handling fees — so your margins reflect the real cost to deliver.
Default List Price vs. List Price. Default List Price is the starting price held on the product in your catalog. List Price is the final price on a specific channel listing — what the customer sees. The Default List Price seeds the channel List Price, which rules can then adjust per channel.
Which price do customers pay? The List Price on the Channel Listing. Everything upstream (Cost, MAP, MSRP, Default List Price) is an input you use to arrive at it — manually or through pricing rules.
Source Inventory Pricing Fields (GIP / GIS)
These fields are populated when Flxpoint imports inventory from a source through your Get Inventory Primary (GIP) or Get Inventory Secondary (GIS) jobs. They reflect the pricing data your supplier provides. The lightweight Secondary sync keeps the ✓ fields refreshed between full imports.
| Field | Type | What it is | Secondary sync |
|---|---|---|---|
| Cost | Number | The actual cost incurred by your business to acquire a product. It is the base price that you pay to your supplier before any markup or additional costs are applied. | ✓ |
|
MAP Minimum Advertised Price |
Number | The lowest price that a retailer can advertise a product for sale. It is set by manufacturers to maintain brand value and ensure fair competition among retailers. You can create rules in Flxpoint to enforce MAP pricing if it exists. | ✓ |
|
MSRP Mfr. Suggested Retail Price |
Number | The price that manufacturers recommend retailers charge for their products. It serves as a guideline for pricing but does not have to be followed strictly. Similar to MAP, you can create rules in Flxpoint to adjust prices based on MSRP. | ✓ |
| Source List Price | Number | The price provided by the supplier or source from which you are acquiring the product. It may vary from your internal cost and can be used as a reference point for setting your own prices. | ✓ |
Related supplier costs: sources may also provide Shipping Cost and a per-order Dropship Fee. These aren't prices customers see, but Flxpoint can fold them into your Estimated Cost so margins reflect the true landed cost.
Product Catalog Pricing Fields
Your Product Catalog is the master record for each product. This is where your working cost and starting price are established before they reach your channels.
| Field | Type | What it is | Typically from |
|---|---|---|---|
| Estimated Cost | Number | An approximation of what it will cost you to sell a product, including potential additional expenses like shipping or handling fees. It helps in calculating profit margins and setting competitive prices. | Cost + est. shipping & dropship fees |
| Default List Price | Number | The initial price assigned to a product when it is listed in your system. It typically starts as the product's estimated cost but can be adjusted based on other pricing rules, such as mapping it to MSRP or MAP. | Estimated Cost, then rules |
Channel Listings Pricing Fields
Channel Listings hold the prices actually published to your sales channels and shown to customers.
| Field | Type | What it is |
|---|---|---|
| List Price | Number | The final price at which a product is offered for sale to customers. This price may be influenced by various factors, including cost, MAP, MSRP, and any additional markup or discounts applied. |
How Prices Transform Between Stages
You rarely sell at cost. Pricing & Quantity Rules are how the reference values above become your live List Price.
- Map a field — base your price on a supplier value (e.g. set Default List Price from MSRP).
- Apply a markup — add a percentage or fixed amount on top of Cost or Estimated Cost.
- Enforce MAP — never advertise below the Minimum Advertised Price when the supplier provides one.
- Adjust per channel — different markups or rounding for each sales channel.
Where to set this up: see Pricing & Quantity Rules for catalog-level pricing, and Channel Pricing & Quantity for per-channel adjustments.
Quick Answers
- "Which price do customers actually pay?" — The List Price on the channel listing. Everything else is an input used to set it.
- "What's the difference between Cost and Estimated Cost?" — Cost is the supplier's item price; Estimated Cost adds estimated shipping and dropship fees for your true landed cost.
- "Why is my Default List Price the same as my cost?" — It defaults to the Estimated Cost until you apply a pricing rule (for example, map it to MSRP or add a markup).
- "Does the hourly Secondary sync update prices?" — Yes. Cost, MAP, MSRP and Source List Price refresh on the Secondary (GIS) sync, matched by SKU. Catalog and channel prices you've 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.
Good to know: the fields shown on your actual screens in Flxpoint are always the source of truth and can vary slightly by supplier or channel integration.