One product, many price lists
The same product can carry different prices in different catalogs, so retail, wholesale and partner audiences stay separate without duplicate records.
Build an assortment once, then give each audience the products and prices that belong to it.
The same product can carry different prices in different catalogs, so retail, wholesale and partner audiences stay separate without duplicate records.
Assign a product to any number of catalogs and categories, then publish only the relevant catalog to each storefront.
Price and product updates can be staged, validated and applied in bulk rather than edited one item at a time.
A single list price rarely survives contact with real trading. Contract pricing, regional differences, currency rounding and promotional overlays all need somewhere to live. WebStore separates the product record from the price list so each commercial conversation can have its own terms.
Because the catalog is also the assortment boundary, it becomes a useful permission and publishing unit. A partner storefront can receive one catalog while the public site receives another.
Name catalogs after the audience they serve, not after the person who created them. Document which catalog drives which storefront and who may change prices. A small amount of naming discipline prevents most pricing incidents.
Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.
The useful test is a real assortment, a real market and a real order. Bring those to a conversation rather than a generic feature list.