Latch AI Ops

Playbook · Shopify product bundle / bundle builder / frequently bought together widget missing on PDP

Shopify bundle builder or frequently bought together not showing on the product page.

Written for a Shopify DTC owner whose product bundle builder, frequently bought together offer, or bundle widget never appears on the product page — bundle / FBT apps unpublished on Current, theme blocks missing from this product template, or cart transform Functions that never surface a storefront card. DIY-first: prove apps vs theme blocks vs cart transform Functions; repair the live product template; retest on the live storefront. Distinct from quantity breaks / volume discount not showing, selling plans / subscriptions not showing on PDP, recently viewed not showing, wishlist button missing, product recommendations / related products alone, and Bundles app product not showing / wrong inventory. No earnings claims, no invented case studies.

Nico at Latch AI Ops · Sep 8, 2026 · ~12 minute read

Buy the 72-hour install — $997Bundles inventoryQuantity breaksMerchant FAQ

01

Bundle builder / FBT missing — not quantity breaks, selling plans, recently viewed, wishlist, or recommendations.

Several PDP widgets can look alike. They do not share a settings panel. This page is only when a product bundle builder, frequently bought together offer, or product-bundle widget never renders on the PDP (bundle / FBT apps, theme blocks, cart transform Functions). Quantity break / volume tiers missing is shopify-quantity-breaks-not-showing. Selling plans / subscriptions missing is shopify-selling-plan-not-showing. Recently viewed blank is shopify-recently-viewed-not-showing. Wishlist button missing is shopify-wishlist-button-missing. Native Search & Discovery / theme “You may also like” recommendations alone are not this playbook. A Shopify Bundles app parent product unpublished or wrong inventory is shopify-bundles-not-showing.

If the buyer should see a bundle builder, FBT card, or “complete the set” widget on the PDP and they do not, you are on the right page. If the Bundles parent product itself 404s or stocks wrong, leave this playbook.

02

Prove apps vs theme blocks vs cart transform Functions on the live PDP.

Open a live PDP in a logged-out window (not only Theme editor preview). Capture four facts before you change anything:

  1. On the PDP: does any Bundle builder / Frequently bought together / Product bundles / Complete the set card appear below the buy box or in the product template?
  2. Theme settings → App embeds: is exactly one intended bundle / FBT / product-bundles app enabled on Current (not a draft theme)?
  3. Customize → product template this SKU uses: is a Bundle builder / FBT / Product bundles block present and visible? Wrong template (Default vs alternate) is a common miss.
  4. If the offer depends on a cart transform Function: is the Function published? Do product / collection rules include this SKU? Console / network: do app scripts inject, or are two bundle widgets fighting?

Write those four answers down. Guessing “the theme is broken” without checking Current app embeds and the product template wastes hours.

03

Bundle / FBT apps, theme blocks, or app embeds off / draft-only / fighting on Current.

Most PDP bundle / FBT UIs come from an app or a theme block — not from Discounts alone. On Current:

  • Theme settings → App embeds: enable exactly one intended Bundle builder / FBT / Product bundles app; disable duplicates.
  • Product template: add / enable the Bundle builder / Frequently bought together / Product bundles block on the template this product uses. Save.
  • App admin: product / collection selection includes this SKU; offer Active; display style set to show on storefront; preview matches live.
  • Publish to Current — draft theme previews that look fine never ship to buyers.
  • If scripts never inject, fix app embeds first. If the block is on the wrong template, move it. Retest logged-out after save.

04

Cart transform Functions published without storefront widget UI (or rules miss this SKU).

Some bundle offers use a cart transform Function to expand / price lines at cart. Common misses:

  • Function app installed but not published to the live shop, or draft-only configuration.
  • Product / collection / market rules leave this SKU out — buyer never qualifies, so the app hides the PDP card.
  • Function runs at cart but the storefront still needs the app embed / theme block to draw the builder / FBT card on the PDP. Fixing Functions alone will not paint the widget.
  • Two apps both claim cart transform + PDP widget — half configured each → blank UI. Keep one stack.

Publish the Function, match product scope, then confirm the matching PDP block / app embed is on Current. Retest add-to-cart from the widget.

05

You tested quantity breaks, selling plans, recently viewed, wishlist, recommendations, or Bundles inventory instead.

Do not “fix bundle builder / FBT” by editing those surfaces:

06

When to stay DIY vs pay $997.

Stay DIY if Current app embed + the right product template block + (when needed) a published cart transform Function get your bundle builder / FBT widget working on a logged-out PDP. Pay $997 when you want Latch AI Ops to install lead capture + ops alerts + a checkout-ready workflow on the stack you already pay for in 72 hours — not a rebuild of your bundle app, and not an earnings claim.

Nico ships the install. You keep your theme, your Functions, and your apps. No invented case studies.

Buy the 72-hour install — $997Merchant FAQAll playbooks