Quick answer
After installing KitForge, invisible offers usually mean the app embed is off, bundles are still draft, or the product you are testing is not a trigger, component, or eligible SKU.
- Test the product configured in the bundle editor, not an arbitrary PDP.
- Draft and scheduled states do not render on the storefront.
- Coexistence defaults hide overlapping offer types on one page.
- Use admin live preview before assuming the storefront is broken.
First hour after install
Complete onboarding: enable embed, then create one bundle type you understand (fixed kit is often simplest). Use live preview in admin before toggling storefront activation.
Test on the exact product configured in the editor — not a random bestseller unless it is a trigger product.
Product eligibility by type
Fixed kit standalone: visit the bundle product page. Inline: visit a component product page. FBT: visit a trigger product page. Quantity breaks: visit an eligible variant's PDP.
- Fixed kit standalone → bundle product URL
- Fixed kit inline → component PDP
- FBT → trigger PDP
- Quantity break → eligible SKU PDP
Launch checklist
Reproduce bundle offers not visible after installing kitforge on a known product with a clean browser session after confirming the app embed is active.
Confirm variant coverage, mobile layout, and that the discount only applies through the intended path so shoppers are not surprised at checkout.
- Preview the offer on a real product page and on mobile.
- Place a test order that exercises the discount and inventory path.
- Brief support on what is included and what is not.
- Document the success metric before you scale the offer.
Mistakes that quietly kill conversion
Debugging discounts before confirming the widget mounts wastes time. Network responses from the Kitforge offers proxy should be the first technical check.
For “Bundle offers not visible after installing KitForge,” keep the page focused on one primary next step. Extra widgets, stacked badges, and unclear exclusions increase bounce more often than they increase AOV.
- Do not hide eligibility rules until checkout.
- Do not bundle unrelated leftovers without a customer story.
- Do not skip mobile QA on choice-heavy widgets.
- Do not launch without a rollback plan for the discount.
How to measure whether it worked
A fix is complete only when the storefront, cart line properties, and checkout total all match the intended offer.
If the metric moves but support volume rises, fix presentation or inventory rules before cloning the offer across more SKUs.
- Attach rate on treated product pages
- AOV and contribution margin after discounts
- Refund or fulfillment exception rate
- Time for a teammate to edit the offer safely
Final recommendation
Treat post-install visibility as a ordered checklist: embed, status, product, coexistence. Most tickets resolve at step one or two.
If you want this kind of offer to feel native to the buying journey, Kitforge Bundles is built around that exact problem: turning related Shopify products into clearer bundle offers before the shopper reaches checkout.
FAQ
How long until offers appear after activation?
Immediately after theme save and bundle activation, subject to CDN cache. Hard-refresh or use a private window to verify.
What should I do before publishing changes related to Bundle offers not visible after installing KitForge?
Preview on mobile, place a test order, and confirm inventory and discount behavior match the storefront promise. Only then activate for all traffic.
When is Kitforge Bundles the wrong tool?
If you only need a simple Buy X Get Y or free-gift discount with no product-page merchandising, native Shopify discounts may be enough. Kitforge is built for fixed kits, FBT, and quantity-break widgets with inventory validation.
How long should I wait before judging the offer?
Give the offer at least one to two weeks of normal traffic, or enough orders to see attach rate stabilize. Seasonal spikes can distort a shorter window.