If you buy or produce point-of-purchase displays, your year is not organized by quarters. It’s organized by resets: the fixed windows when a retailer tears down a category and rebuilds it to a new planogram. The reset calendar is set by the retailer, published to vendors, and enforced by a simple mechanism — the display that isn’t in the distribution center by the compliance date doesn’t go on the floor. It waits for the next reset, which may be months away, while the product it was built to sell launches without it.
That makes reset dates a different species of deadline from most of what moves through a fabrication shop. A launch event can slip a week. A showroom refresh can phase in. A reset cannot. Planning display production around one is therefore less about working fast and more about working backward — and about being honest, early, over which scheduling commitments actually fit a date that has no grace period.
The rhythm: majors, category windows, and the decision that lands a season early
Most retailers run major resets in the spring and fall, with category-specific windows scattered between them — cosmetics on one cycle, electronics on another, seasonal aisles on their own clock. The dates vary by retailer and by year, so the only calendar that matters is the one in your vendor portal or your buyer’s last email.
What doesn’t vary is the lead structure in front of the date. Work backward from a reset and the chain is longer than it looks: the floor date is preceded by the DC compliance date, which is preceded by freight transit, which is preceded by the manufacturing completion date, which is preceded by fabrication, which is preceded by proof approvals, which are preceded by the quote, the files, and the design. By the time a reset window opens, every production decision behind it was made a season or more earlier. If you’re reading this with a confirmed planogram in hand, you are already in the decision window for it — the same backward-planning logic we walk through in designing POP for volume runs and the broader retail display guide.
A reset date is a completion-date problem — name it that way
In Production Scheduling terms, a reset deadline is a specific completion date that cannot move. That maps onto the tiers precisely:
- Production Schedule — the standard tier — builds the schedule in the order projects come in and are paid for. It’s the honest choice for a program that can slide to the next window without damage.
- Accelerated Production moves a project up the queue where the schedule has visibility — the most opportunistic completion date available, with no guarantee. Right for “sooner is better,” wrong for “this date or nothing.”
- Reserved Production is the tier built for exactly this shape of problem: dedicated capacity purchased for a guaranteed manufacturing completion date, priced as its own line on the quote — and accepted only when the schedule can actually support it. A reset with no second chance is the textbook Reserved case.
The distinction that trips buyers: Reserved guarantees the completion date — the day the work comes off our floor. Freight transit and DC appointment windows sit on your side of that date, so the number to hand the fabricator is not the floor date — it’s the completion date you computed after subtracting transit and the DC’s receiving rules. The full tier mechanics are in the tiers explainer.
DC versus direct-to-store changes more than the address
A multi-door rollout adds a consolidation step that quietly rewrites the fabrication spec. Shipping to a retailer DC usually means the retailer’s routing guide governs carton sizes, labeling, pallet configuration, and appointment booking — and those requirements belong in the quote, not discovered after it. Direct-to-store flips the problem: more destinations, smaller shipments, and pack-out that has to survive more handling per unit. Either way, the pack-out and labeling are part of what’s being fabricated, and the date that actually matters (DC compliance date versus per-store delivery window) should be written on the purchase order in those words. Programs that treat compliance requirements as a fabrication input, the way retail-ready display programs do, don’t get surprised by them.
The quiet win: resets recur, so build for the reorder
A reset program is rarely a one-time build — the same retailer resets the same category again, and the brand that won the space wants to hold it. That makes the second reset the cheapest one you’ll ever buy, if the first one was built like a program: files, specs, and pack-out requirements on record, so the next window starts with a purchase order instead of a project. For programs that are built to repeat, we keep a fuller record — which is exactly what turns “can you do it again by the spring window” into a yes with a date on it.
Resets also stack with the rest of the retail calendar — if your program’s next window lands near the new-year transition, the new-year reset post and the spring reset timing post cover how those windows interact with the production calendar.
If you have a planogram, a door count, and a compliance date, that’s enough to start the backward plan — send them over and the first thing you’ll get back is whether the date is comfortable, tight, or a Reserved conversation.
