Some retail items are sold as kits or bundles built on top of an Assembly BOM. An item used as a kit is not itself a stocked physical item; instead, when it is sold, its components are consumed from inventory.
For Product Level Blocking (PLB), the Australian localization treats an Assembly BOM kit as restricted whenever any child component is restricted. This prevents the kit from being used to indirectly sell restricted items together with non-restricted items under a single, unrestricted SKU.
Detection order on the POS
When an item is added to a POS line, the POS determines whether it is a PLB item using the following rules, in order. The first rule that matches wins:
- The item itself has the PLB Item check box enabled. See PLB Retail Item.
- The item is an Assembly BOM kit and at least one of its components is a PLB item (evaluated recursively through nested BOMs).
- The item's Item Category has the PLB Category check box enabled. See PLB Item Category.
- The item's Retail Product Group has the PLB Group check box enabled. See PLB Product Group.
How the recursive BOM check works
- Each BOM Component child item is inspected.
- If any child is itself marked as a PLB item, the parent kit is treated as restricted.
- If a child is also an Assembly BOM (sub-assembly), its components are inspected the same way, all the way down the tree.
- The first restricted component found stops the search; the kit is marked as a PLB item on the POS line.
Implications for product design
- To sell a mixed-content kit at a non-CDC store, the kit can include restricted components without being blocked at the POS, because PLB enforcement is per-store.
- At a CDC store, a kit containing any restricted component will be treated as restricted at the POS. Cashiers cannot bypass this by changing the parent item's PLB flag — the recursive BOM check overrides it.
- If the kit is incorrectly flagged for a specific transaction, a manager can use the override action. See Override PLB Item.
See also