Flxpoint Knowledge Base

What pricing & quantity rules do

Automate pricing

Apply markups, discounts, MAP enforcement, .99 decimals, and MSRP overrides without touching each listing manually.

Protect margins

Add dropship fees or shipping costs into the list price so those costs aren't absorbed at fulfillment.

Prevent oversells

Zero out quantity before stock runs dry, and delist products automatically as stock approaches zero.

Auto-relist on restock

Automatically queue a Publish action when quantity recovers above a threshold - bringing delisted products back live.

Global vs channel-specific - where to configure

Scope	Navigation path	Use when	Override behaviour
Global	`Settings → Products → Pricing/Quantity → Add Rule → Update Workflow`	The rule should apply to all channels (e.g. always set decimal to .99, always add dropship fee)	Applies as the base layer. Channel-specific rules run on top of global rules for that channel's listings.
Channel-specific	`Channels → ⚙ → Pricing/Quantity → Add Rule → Update`	The rule should only affect one channel (e.g. Amazon gets a 5% markup, Shopify gets MAP pricing)	Runs after global rules. Use this to override or add to global behaviour for a specific channel.

Non-obvious behaviours - read before adding rules

Rules evaluate top-to-bottom - order matters

Rules in a workflow are evaluated in sequence from top to bottom. If Rule 1 sets Default List Price to MSRP and Rule 2 then adds 10%, the result is MSRP + 10%. If you reverse them - add 10% first, then set to MSRP - the final price is just MSRP. Always sequence rules to produce the intended cumulative result, and use the workflow test tool to verify before saving.

Click Update Workflow or prices/quantities won't change

Adding a rule and clicking OK creates it, but it doesn't activate until you click Update Workflow (global) or Update (channel-specific). This is the most common reason rules appear saved but aren't affecting any listings - the workflow was never updated after the last rule change.

Global rules run before channel rules - not instead of them

Channel-specific rules don't replace global rules - they stack on top. If your global workflow adds 10% and your Amazon channel workflow adds another 5%, the listed price on Amazon will be +15% over base cost. When a channel listing isn't pricing as expected, check both the global workflow and the channel workflow together, not just one of them.

Delist and Relist rules must be paired

If you create a rule to delist products when quantity falls below 5, you also need a paired rule to re-queue Publish when quantity rises above a threshold. Without the paired rule, products delist but never automatically come back - even after restocking. Both rules shown in the examples below should be used together.

Rule examples - ready to use

Quantity protection & listing control

Zero out quantity before selling out

Prevents oversells when supplier feeds lag - show 0 before you actually hit 0.

IFQuantity < X (e.g. 3)

THENSet Quantity to 0

Delist as stock approaches zero

Removes the listing from the channel entirely before stock runs out, avoiding a "sold out" display.

IFQuantity < 5 AND Parent Listing Status = Published AND Variant Listing Status = Published

THENSet Parent Queued Action to Delist AND Set Variant Queued Action to Delist

Re-publish when quantity is replenished

Paired with the Delist rule - automatically brings delisted products back once stock recovers.

IFQuantity > 5 AND Parent Listing Status = Delisted AND Variant Listing Status = Delisted

THENSet Parent Queued Action to Publish AND Set Variant Queued Action to Publish

Price formatting

Set all prices to .99 decimal

Psychological pricing - makes every item end in .99 regardless of base cost.

IFAlways Run

THENSet Default List Price → Set Decimal = 99

Set price to MSRP

Use when Default List Price is missing or when you want to sell at the supplier's recommended price.

IFAlways Run

THENSet Default List Price → Set To Field: MSRP

Set price to MSRP then raise by X%

Use MSRP as the base but add a margin buffer before publishing.

IFAlways Run

THENSet Default List Price → Set To Field: MSRP, modify by +X% before setting

Enforce MAP pricing

Replaces list price with the MAP field value whenever MAP exists - ensures channel compliance.

IFMAP Exists

THENSet Default List Price → Set To Field: MAP

Margin protection

Add dropship fee to list price

Passes the supplier's dropship fee on to the customer price so it doesn't erode your margin.

IFEstimated Dropship Fee Exists

THENSet Default List Price → Add Field: Estimated Dropship Fee

Add shipping cost to list price

Rolls shipping cost into the product price - useful for free-shipping channels where shipping can't be charged separately.

IFAlways Run

THENSet Default List Price → Add Field: Estimated Shipping Cost

Selective markups & discounts

Brand upcharge

Mark up items from premium brands (Apple, Nike, etc.) that carry higher demand and justify higher prices.

IFBrand Contains [Brand Name]

THENSet Default List Price → % Change: +X%

Category upcharge

Apply a consistent markup to an entire product category without touching individual items.

IFCategory 1/2/3 Contains [Category Name]

THENSet Default List Price → % Change: +X%

Discount items on sale

Target a specific list of SKUs (maintained as a Flxpoint List) for percentage discount campaigns.

IFMaster SKU in List [Sale Items list name]

THENSet Default List Price → % Change: -X%

Common issues

Rules are saved but prices aren't changing on the channel

▾

Two most common causes: (1) Update Workflow wasn't clicked after adding or editing rules - the rule is saved but inactive. Go back to the workflow, confirm the rules look correct, and click Update Workflow (global) or Update (channel). (2) The Sync Listings integration hasn't run yet since the workflow was updated. Rules are evaluated when Sync Listings executes. Trigger a manual Sync Listings run on the channel to apply the updated rules immediately.

A rule is applying to listings I didn't expect it to affect

▾

Check whether the rule was added to the global workflow instead of a channel-specific one. Global rules apply to all channels - if you only meant to affect one channel, move the rule to that channel's Pricing/Quantity workflow at Channels → ⚙ → Pricing/Quantity. Also confirm the IF condition is precise enough - Brand Contains Apple matches any brand containing the word "apple", including brands like "Appleton" or "Pineapple Co." Use Brand Equals for exact matching.

Price is higher or lower than expected - rules seem to be stacking incorrectly

▾

Rules run top-to-bottom and each one operates on the result of the previous rule, not the original source cost. If you have both a global and a channel workflow, the channel rules also run on top of the already-modified global result. Open both workflows side by side and trace the price transformation step by step: start from the source cost, apply each global rule in order, then each channel rule in order. The final value is what gets synced. Reorder or remove rules until the sequence produces the expected price.

Delisted products are not coming back when stock is replenished

▾

The Delist rule doesn't have a paired Relist rule. When quantity drops below the threshold and the listing is delisted, it stays delisted until a separate rule queues a Publish action. Add a rule: IF Quantity > X AND Listing Status = Delisted → THEN Queued Action = Publish. Set X to whatever quantity level you consider "safe to sell" - typically the same threshold used in your Delist rule, or slightly higher to avoid rapid delist/relist cycling.

MAP rule isn't applying to some listings even though MAP exists

▾

The MAP Exists condition checks whether the MAP field on that specific listing's source inventory record is populated. If MAP is empty on the source inventory record (because the supplier feed doesn't include it), the condition evaluates false and the rule is skipped. Verify the MAP field is populated at Products → Source Inventory → [variant]. If the supplier provides MAP in their feed, confirm the MAP field is mapped correctly in your source's import mapping template.

FAQs

When exactly do pricing and quantity rules apply?

Rules are evaluated each time a Sync Listings or Publish Listings job runs for that channel. They're not applied in real time as you add them - the workflow runs on the next scheduled or manually triggered integration run. For global rules, they apply on every channel's next sync. For channel-specific rules, they apply only when that channel syncs.

Can I use a pricing rule to set different prices on different channels for the same product?

Yes - that's the primary use of channel-specific rules. Set a base price globally (or no global price rule), then add separate pricing rules per channel. For example: Amazon channel adds 8%, Shopify channel uses MAP, Walmart channel adds 5%. Each channel's workflow evaluates independently so the same product can show different prices on different platforms.

What is a "Flxpoint List" and how do I use it in discount rules?

A List is a named set of values - SKUs, brands, categories - that you maintain in Flxpoint and reference in rule conditions. For the discount rule, you'd create a List called "Sale Items" containing all the Master SKUs you want discounted, then use IF Master SKU in List [Sale Items] as the condition. To run a sale campaign, add SKUs to the list - the discount rule applies automatically on the next sync. To end the campaign, remove SKUs from the list.

Will adding a shipping cost to the list price affect what the customer is charged for shipping separately?

No - the Add Shipping Cost to List Price rule only modifies the product's Default List Price field in Flxpoint, which becomes the displayed item price on the channel. It doesn't configure or modify your channel's actual shipping settings. The rule is most useful on channels where you offer free shipping - by baking the estimated shipping cost into the item price, you recover that cost through the higher product price rather than losing it at fulfillment.