Quick answer
KitForge JavaScript on product pages calls the app proxy at /apps/kitforge/offers with the current product context. The response returns eligible fixed kit, FBT, and quantity break offers after priority sorting and coexistence filtering.
- /apps/kitforge/offers is the storefront source of truth for widget data.
- Empty responses are usually configuration, not infrastructure failures.
- Network tab debugging is faster than guessing theme conflicts.
- App embed must be active for the runtime to fetch offers.
App proxy vs admin API
The storefront never calls KitForge admin APIs directly. The app proxy is Shopify's supported pattern for theme extensions to fetch app data with shop context — keeping credentials server-side.
KitForge's theme app extension mount point triggers a fetch on PDP load; widgets render from the response without merchant theme edits.
Performance considerations
Offers are fetched per product page load. Keep offer count manageable per shop — priority and coexistence reduce multiple widgets competing on one PDP.
Final recommendation
The KitForge app proxy powers all product-page widgets. Verify offers JSON on the PDP before debugging discount or placement issues deeper in the stack.
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
Does the app proxy work on non-product pages?
KitForge auto embed targets product pages. Manual app blocks can place widgets elsewhere with explicit bundle IDs.
Can I cache the offers response?
The KitForge runtime handles fetching. Theme-level caching of proxy responses can serve stale offers — avoid aggressive CDN caching on PDP HTML.