We’re pleased to share the latest updates and enhancements on MS!

Enhancements

Prioritize Store SKU Depth Override over Max SKU Depth

Updated the distribution depth logic so that when Store SKU Depth Override is uploaded for a store–SKU combination, the system treats it as the single source of truth and uses only the uploaded override depth for that combination.

What problem this solves

Previously, the system still applied other constraints even when an override was provided (it effectively did final depth override = max(max sku depth, store sku depth override)). This could prevent the uploaded override depth from being honored exactly as intended for the override-uploaded combinations.

Key capabilities

• Override-first depth calculation: For combinations present in the override upload, final depth override = store sku depth override.
• Constraint bypass for override combinations: Other constraints are not applied for override-uploaded combinations, including ROS*cover, Max SKU Depth, pack size, and style depth override.
• Improved control and predictability: Ensures distribution decisions for override-uploaded store–SKU pairs match the uploaded depth precisely.

Notes / Caution

• Uploading an override depth of 0 for a pivotal size can impact size continuity and overall style dispatch. Please upload such combinations carefully.