Channel Pricing & Quantity
Summary
Channel Pricing & Quantity defines how price and inventory are calculated for a channelβs listings, with channel-level rules setting the logic and listing-level values holding the final result. List Price Protection blocks risky listings from syncing until their pricing data meets minimum requirements.
Channel Pricing & Quantity defines how price and inventory are calculated for a channel’s listings. Channel-level rules set the logic applied before values are written; listing-level values show the final result and can be overridden or locked. List Price Protection stops risky listings from syncing.
- Channel rules — markup/markdown, MAP enforcement, and quantity buffers/caps applied before values reach listings.
- Listing values — the final calculated price and quantity per listing; review, override, or lock them.
- List Price Protection — blocks listings from syncing when pricing data is invalid; on by default for new channels.
- Locking — lock a listing’s price or quantity so workflows cannot overwrite it.
Two layers
- Channel Pricing & Quantity — defines the pricing and quantity logic and applies it at scale. Configure at Channels → Select Channel → Settings → Pricing & Quantity.
- Listing Pricing & Quantity — shows the final values on each listing, populated from the last workflow run. View at Channel Listings → Open Listing → Variant-level Pricing & Quantity.
How the layers relate
| Layer | Purpose | Workflow impact |
|---|---|---|
| Channel Pricing & Quantity | Defines pricing logic | Applies rules |
| Listing Pricing & Quantity | Displays final values | Receives output |
| Locked listing fields | Prevents updates | Overrides workflows |
| List Price Protection | Prevents risky listings from syncing | Blocks sync until corrected |
Channel pricing runs in three steps each time the workflow executes:
- Reset — listing values reset to the product variant defaults.
- Apply rules in order — channel pricing rules run top to bottom.
- Write final values — calculated price and quantity are written to the listing.
The reset step is what prevents markups or discounts from compounding across repeated workflow runs.
| Rule type | Example |
|---|---|
| Markup | Default List Price plus a fixed dollar or percentage markup produces the channel List Price. |
| MAP enforcement | IF MAP exists AND MAP is greater than the calculated List Price, THEN set List Price = MAP. Place these rules last so they override earlier calculations. |
| Quantity | Expose only part of inventory (for example 80%) or cap quantity (for example 5 per SKU). |
List Price Protection blocks a listing from syncing until its pricing data meets the minimum requirements. It is enabled by default on new channels and is not an error.
| Requirement |
|---|
| List Price must be greater than Estimated Cost. |
| Estimated Cost cannot be 0 or missing. |
| The listing must be linked to a product with at least one linked inventory item. |
Find affected listings at Channel Listings → Needs Attention → List Price Protection. Once all requirements are met, the listing is marked out of sync and becomes eligible for the next Sync Listings job.
Limited recent ticket data for this topic; the items below reflect documented behavior.
A listing shows a price protection message and will not sync
This is not an error. The listing meets one or more List Price Protection criteria: List Price at or below Estimated Cost, Estimated Cost missing or 0, or no linked inventory. Fix the pricing data; once all requirements are met the listing goes out of sync and syncs on the next job. The message cannot be dismissed manually.
A manual price or quantity change reverted
The field was not locked, so the next pricing workflow overwrote it. Lock the price or quantity on the listing variant to preserve a manual value.
Markups appear to be compounding
They should not: each workflow run resets listing values to the product variant defaults before applying rules. If values still look stacked, confirm you are not applying the same markup at both the channel and listing levels.
Why is my listing blocked from syncing?
Most likely List Price Protection. Check that List Price is greater than Estimated Cost, Estimated Cost is present and non-zero, and the listing is linked to a product with linked inventory.
How do I stop a value from being overwritten?
Lock it. Open the listing variant, click the padlock next to Price or Quantity, set the value, and save. Locked fields are skipped by pricing workflows.
Where should I set pricing rules?
At the channel level, in Pricing & Quantity. Place MAP and minimum-price enforcement rules last so they override earlier calculations.
Is the price protection message an error?
No. It indicates the listing does not yet meet minimum pricing requirements and is temporarily blocked from syncing until corrected.
