Practical guide
Explain a bundle price without confusing unit prices
Explain a bundle price without confusing unit prices: a practical process, a clearly illustrated example and checks to use before the next live session.
A practical process
- Name the number and identity of items included in the package.
- State the total package price first, then explain any calculated per-unit comparison clearly.
- Check whether mixed sizes or included extras make a simple unit comparison misleading.
Worked example
In a hypothetical three-cloth pack priced RM24, RM8 is a calculated average per cloth, not necessarily the price for buying one separately. Say both parts explicitly. If the cloth sizes differ, compare the package contents rather than calling every item identical value.
Before the next session
Use the current Aseacast product overview to check which parts of this workflow fit your setup.