Collection performance

Connect a collection catalogue to dated sales records. Compare collections and launches, then inspect the products behind them. Keep source coverage and unmatched rows beside the result.

Match before comparing

Use stable product references. Read the full relevant source range and locate the actual header rather than assuming it never moves. A missing catalogue or a failed join should stop publication, not produce an empty dashboard that looks successful.

Keep negative movements distinct and preserve the signed net result. Do not allocate an unmatched row to a product by guessing. Align the reporting periods before comparing collections.

After the source repair, a separate control reconciled the published totals with the original sheets. The published comparison, product drawer and mobile layout were tested again on 16 October 2026. Refresh time and the last sale present in the source are displayed separately.

This is a built and tested workspace. Recent routine use of this interface has not been independently confirmed. It does not provide live inventory, purchasing automation or predicted performance.

Explore collection performance. All public collection names, products and states are fictional. No private catalogue, sales figure or product image is copied.

Applying the method elsewhere

Test moved headers, growing tables, empty catalogues and partial matches. Compare published totals with an independent source calculation. Keep aliases pointing to the same underlying workspace instead of counting them as new products.