Product Readiness vs Range Readiness: What Is the Difference?

A product can be ready while its range is not. A parent product can look complete while most of its variants are not ready to sell.

Those are different levels of readiness, and combining them into one percentage hides the part holding up the launch.

Variant readiness

A variant is the buyable version: this size, finish, fabric or orientation.

A variant is ready for a destination when it has the identity, commercial values, imagery and other information that destination needs.

The destination matters. A variant may be ready for an internal quote and not for a marketplace listing. Google's product-variant guidance, for example, expects variants to be connected to a parent product and supports specific properties for describing how they vary.

Useful questions include:

• Does every sellable configuration have an internal SKU?
• Is its price current?
• Can the buyer see the relevant finish or material?
• Is availability held at the right level?
• Can the destination represent the way this variant differs?

Product readiness

The product level contains the facts shared across its variants: name, category, construction, core dimensions, description and common assets.

A product is ready when that shared record is complete enough for the intended use and its required variants are connected correctly.

That last point matters. One polished product page and one hero image do not make every finish ready. Product readiness should never be used to conceal missing variant work.

Range readiness

A range is ready when the products and variants included in the intended launch clear the bar for a named destination.

This is why "the range is 90% ready" needs more explanation. It could mean:

• 90% of required fields are filled
• 90% of parent products are complete
• 90% of variants are publishable
• 90% of the planned assortment is already live

Those are not interchangeable.

Range readiness is better reported as a count with blockers:

184 of 220 planned variants are ready for Retailer A. Of the remaining 36, 24 need packaging dimensions and 12 need a finish-specific image.

That tells the team what can launch and what work remains.

Readiness always belongs to a destination

There is no universal "complete" product record.

Nebraska Furniture Mart's vendor guide asks for crated and uncrated dimensions. Google has announced that product images must be at least 500 × 500 pixels from January 31, 2027. Your own website, a printed price list and a trade proposal will have different requirements again.

Keep the base record stable, then define readiness rules for each destination. A channel-specific description or price should not overwrite the base value simply because that destination needs something different.

A practical reporting structure

Report readiness in three lines:

1. Variants ready: sellable configurations that clear the named destination's requirements.
2. Products ready: parent records with their required shared information and variant relationships.
3. Range ready: the planned launch set that can be sent or published, with blockers grouped by cause.

Avoid a blended score on its own. A high average can coexist with one missing field across every product or a complete bestseller range alongside hundreds of variants that cannot go live. Readiness reporting works best alongside the other product-content metrics a team tracks.

Furniture Connect can help teams structure products and variants, work across filtered product sets and maintain channel-specific values in a connected catalog. The business still defines the destination requirements and decides what must be present before use.

Readiness is not a description of how tidy the catalog looks. It is an answer to a specific question: can this product, variant or range be used here, now?