You are here:
Configure PDP Layout for Product Bundle in Point of Sale CMS
Map a dedicated product page layout to bundle child products so the POS app shows style choices, availability, and price for the bundle.
When an associate taps a child product from a bundle, the point of sale app sets a BundleID product attribute on it. Add a PDP mapping rule that recognizes this attribute so the child opens on a layout for the bundle experience. Without this rule, the child opens on the store's default product page, missing the availability section and bundle-specific price layout.
- In CMS, go to and edit a configuration. Go to UI | PDP Layouts and edit PDP Mappings.
-
Add a rule to PDP mappings with these values.
Setting Value Attribute Type PRODUCT_ATTRIBUTE Attribute Name BundleID (spelled and cased exactly as shown) Attribute Value ^(\s|\S)(\S)+(\s|\S)$—matches a product with any non-empty BundleID value Layout ID The ID of the bundle child layout you build in the next step -
Move the new rule above any broader rule that a bundle child product would also match.
The app uses the first matching rule in the list. A broader rule above this one prevents bundle children from reaching their dedicated layout.
-
Build and publish the PDP layout that the rule's Layout ID points to.
Include style selectors, the stock availability section, and price (including any discounted or struck-through price). Arrange, show, or hide sections however you want the bundle experience to read. Don't add a quantity selector, a fulfillment selector, or a bottom action button to this layout. The bundle (parent) page owns the quantity and fulfillment for every item in the bundle. The app adds the Confirm and Next or Add to Cart button automatically.
Open a bundle and tap a child product to confirm the setup. The page shows your configured style choices, the availability section, and the child's price. The app's button appears at the bottom.
If the child opens on the default product page instead, the availability section and the bundle-specific price layout are missing. Check that:
- The rule's attribute name and value pattern match exactly what's shown in this task.
- The rule sits above any conflicting rule.
- The layout publishes.
