Q: 12
Universal Containers is beginning the process of SKU rationalization as part of their Revenue Cloud project. They have been advised that rationalizing their product catalog will reduce complexity and increase flexibility. Which three areas can they look to consolidate products?
Options
Discussion
Its B D E. C is a trap since bulk discounts use price books, not extra SKUs. Agree or see it different?
I get why people mention C, but for SKU rationalization and flexibility, it's really B, D, and E. Those all relate to product attributes that can be consolidated without making the catalog a mess. I'm pretty sure that's the logic here, but correct me if I'm missing something!
B D, E. SKU rationalization focuses on attribute values, bundles, and term lengths rather than price variations handled in price books.
Feels like B, D, and E. Rationalization here means cutting down duplicate products that only differ by attributes or term, not pricing. Bulk discounts (C) are usually handled in the price book. Pretty sure about this but open to counterpoints.
B D, E tbh. If attribute value or term is the only difference, that's classic rationalization territory.
If the main goal is to reduce catalog complexity and not just pricing tweaks, then B, D, and E make sense. Price breaks (C) usually stay as price book entries, not extra SKUs. Attribute values and term lengths often clutter catalogs way more. Anyone run into Revenue Cloud client projects where C actually was rationalized too?
Its B, D, E. Bulk discounts (C) are more about pricing config than SKU catalog cleanup imo.
C/D? I see a lot of folks going for B, D, E, but I'd put C in there too since having different bulk discount levels could bloat the SKU count. Maybe that's a trap option, but it feels plausible to me.
C imo, since bulk discount levels could create unnecessary duplicates in some catalogs too. Saw something like this on a practice test.
Its B, D, E for SKU rationalization. Those three are where duplicate SKUs get created in practice during Revenue Cloud projects.
Be respectful. No spam.