What happened
BigCommerce moved cascading price lists from closed beta to open beta, opening the feature up to more stores.
The mechanics: a new "layer fallback pricing" field on a price list defines which list resolves a shopper's price when the primary list has no record for that product. Instead of a missing record dropping the shopper straight to the base catalog price, the fallback list answers first.
The audience is obvious: B2B stores, tiered pricing programs, and wholesale operations — anyone running per-account or per-group price lists layered over a base catalog. If your setup is one retail price for everyone, this release changes nothing for you. The more lists you maintain, the more it changes.
Why this matters
The failure this removes is quiet and expensive. Before layering, a price list missing one SKU dropped that product straight to catalog price. For a wholesale account, that means a customer who negotiated a rate suddenly sees retail — mid-quote, mid-reorder, with no error anywhere. Nobody catches it until the customer does, and customers who catch it stop trusting your quotes.
There's a maintenance win too. Without fallback, the defensive move was duplicating your entire catalog into every account list so no record could ever be missing. With layering, an account list can be a thin overlay — just the negotiated exceptions — sitting on a shared wholesale base list. Fewer records to maintain, fewer places for stale prices to hide.
The caution: this is a beta, and pricing is the worst possible place to discover beta behavior. Fallback resolution touches every price render on the storefront, and a surprise in that chain shows up as a wrong number in front of a paying customer, not as an error in a log. Interactions with customer groups, currencies, and promotions all deserve deliberate testing before any of this touches a live quote.
What to do about it
Inventory your price lists first
Before layering anything, map what you have: how many lists, which customer groups they serve, and how much of each list is duplicated catalog padding rather than genuine negotiated pricing. That padding is what fallback layering exists to delete — and the map tells you what your base layer should be. Most B2B stores that have run price lists for a few years find more padding than pricing.
Build a deliberate failure test
On a sandbox store with a copy of real pricing, pick a SKU you know is missing from an account list, set the layer-fallback-pricing field, and confirm which price renders on the product page, in the cart, and in any quote flow. The whole feature is about what happens when a record is absent — so test the absence on purpose.
Keep it off production until the math checks out
Open beta etiquette applies: trial on staging with realistic data, not on live customer pricing. Compare resolved prices for a sample of real accounts against what your current lists produce, and only promote the setup once the two agree everywhere they should.