Separate the range reset from the last date an item can sell

Name the events hidden behind the reset date

List the affected products and sites, then separate the final order opportunity, intended delivery, new display installation and approved selling period. Identify which dates are commercial decisions and which are system controls. A merchandising presentation may describe the visual reset while a supplier calendar describes dispatch. Neither alone establishes the receiving or selling rules the store must follow.

Include outstanding orders and physical residual stock in the transition review. Record the exact product identities and units, but do not assume a range change requires a new identifier. Keep the old and new ranges distinguishable when they coexist. Ask the responsible owners to identify any regulatory, contractual or operational restrictions that limit disposition rather than creating a clearance plan from marketing convenience.

Map dates to the actual system meanings

SAP’s Managing Assortments guidance separates procurement periods governed by assortment assignment from sales periods in product master data. It also describes a listing-condition check against the planned delivery date. These are scoped SAP behaviors, not a claim that every retailer uses identical controls.

Have the retailer’s system owner map each business date to the actual field or process used locally. Check the configured meaning of an end date and the relevant time boundary. Ask what happens to an order already placed when its delivery moves across that boundary. Do not copy a date into several systems merely because the labels sound similar. Preserve unresolved mappings as a readiness issue rather than forcing the calendar to look complete.

Rehearse the cases that cross the boundary

Build a small set of fictional or safely de-identified transition cases with the owners: an early new-range delivery, a delayed old-range order, remaining units after reset and a branch that installs the layout later. For each, identify whether ordering, receipt, display and sale are permitted under the approved rules. The answer may differ at each stage, which is precisely what the exercise should expose.

Route conflicts to the owner of the affected decision. A supplier’s dispatch confirmation does not authorize a store to override receiving controls. A new layout does not itself authorize destruction or return of old stock. Record approved handling for residual units and who communicates it to stores. Where a plan depends on a future decision, make that dependency visible before publishing a universal launch or availability claim.

Accept the transition with exceptions still visible

Before the change, reconcile the calendar with the latest outstanding orders and store readiness evidence. Confirm who owns each unresolved branch or product case. After the boundary, verify the actual state through the approved retailer records: intended arrivals, eligible selling paths and executed layout. Do not infer all stores switched because headquarters changed a central date.

Preserve original dates, approved revisions and the reason for each exception. This lets the team explain why a late delivery was rerouted or residual stock remained available without rewriting the plan after the fact. Keep public availability messages consistent with the verified selling situation. The completed calendar should make the transition understandable across buying, receiving, merchandising and service while leaving consequential stock and commercial actions with authorized owners.

Make the reasoning concrete.

A fictional homeware chain resets its seasonal display on Monday. A previously ordered old-range delivery is delayed until Tuesday, while some shops still hold approved saleable units. The team proposes using Monday as the end date for every range-related field.

The chain chooses the separate calendar. It does not assume that a visual reset either permits an otherwise blocked receipt or prohibits every sale of remaining stock.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Events

   Which order, delivery, display and selling dates are distinct?

2. System meaning

   Which local controls implement each approved period?

3. Crossings

   Which outstanding orders or residual units cross a boundary?

4. Disposition

   Who decides the permitted handling of each exception?

5. Verification

   What proves the actual store transition matches the approved calendar?

Watch for the wrong conclusion.

• Using the visual reset date as every system cutoff.
• Ignoring a changed delivery date after an order is placed.
• Treating residual-stock disposition as a creative-team decision.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis. Sources support only specifically attributed principles. Platform guidance can change; legal requirements depend on jurisdiction and context. No measured results or named human reviewer are claimed.

• SAP S/4HANA Cloud public edition Retail: Managing Assortments (3I5) →Primary product-specific training, accessed 7 November 2026 · Supports: Supports the distinction between procurement/listing and sales periods and the planned-delivery-date check in the named SAP course context.