What planning grain? SKU level vs product category

Started by Priya Ramaswamy · 1 year, 3 months ago · 3 replies · 2 views
Priya Ramaswamy Participant
1 year, 3 months ago

We have 4,000 SKUs. Planning at SKU level would be unmanageable. But planning at category level loses granularity. What's the best practice on planning grain?

3 Replies
Accepted answer
Director of Enterprise Analytics · Stellar Manufacturing · 1 year, 1 month ago
Best Answer

Classic top-down vs bottom-up debate. Our recommendation: plan at category level for the budget, but maintain the ability to allocate down to SKU using prior year mix. Manageable planning with granular reporting.

Senior BI Architect · Peak Logistics Europe · 1 year, 1 month ago

The semantic model handles this elegantly. Plan at category, and when you need to report at SKU level, the allocation from category to SKU is driven by actuals mix. No one has to plan at SKU level.

Head of Financial Planning & Analysis · Nexa Retail Group · 1 year, 1 month ago

We moved from SKU-level to category-level planning two years ago. Our budget cycle went from 8 weeks to 3 weeks. The category-to-SKU allocation in the Intelligence dashboard gives the commercial team the granularity they need.

Viewing 3 replies - 1 through 3 (of 3 total)

Enterprise planning, Integrated with PowerTable and Intelligence, native to Microsoft Fabric. Co Engineered with Lumel.
BUILT ON