Supported Channels and Compatibility
BundlesIQ is a post-checkout bundle engine. It does not change the checkout experience. Instead, it transforms orders and draft orders after they are created.
This page explains what that means across Shopify channels, where it’s “works by design,” and where it becomes connector-dependent.
What “Supported” Means in BundlesIQ
BundlesIQ can process any transaction that meets all of the following:
- It results in a Shopify Order or Shopify Draft Order (visible in Shopify Admin), and
- The record is eligible for post-checkout edits, and
- The order contains a BundlesIQ bundle variant (ghost SKU variant), and
- No third-party system immediately locks, rewrites, or rejects post-checkout changes.
Practical rule of thumb: If it shows up as an order/draft order in Shopify Admin, BundlesIQ can usually process it.
The main exceptions are third-party marketplace/connector workflows that re-sync or constrain edits.
Compatibility Levels
To avoid overpromising, channels are described using these levels:
- Works by design: The channel creates standard Shopify Orders/Draft Orders and typically doesn’t interfere with post-checkout edits.
- Works, but has channel UX limitations: BundlesIQ can transform the resulting Shopify order, but the channel UI (receipt, confirmation, etc.) may show the ghost SKU before transformation.
- Conditional (connector-dependent): The order may be created in Shopify, but a connector/marketplace may re-sync, lock, or override edits. Requires testing.
- Not applicable: BundlesIQ does not transform at checkout time (no cart/checkout transformation).
Channel Compatibility
| Channel / Source | Compatibility | What to expect |
|---|---|---|
| Online Store | Works by design | The most common case. Customers purchase the ghost SKU variant; BundlesIQ transforms after the order is created. |
| Draft Orders | Works by design | Fully supported. Common for B2B and wholesale workflows. |
| Shopify B2B | Works by design | Supported as long as the flow creates standard Orders/Draft Orders. Test if your B2B setup uses specialized integrations. |
| Shop App | Works by design | Produces standard Shopify orders; BundlesIQ processes post-checkout. |
| Buy Button | Works by design | Produces standard Shopify orders; BundlesIQ processes post-checkout. |
| Headless / Hydrogen / Storefront API | Works by design | Supported as long as checkout completion results in standard Shopify orders. |
| Facebook / Instagram (Meta) | Conditional (connector-dependent) | Often works, but some channel/connector setups may re-sync inventory or order data. Test before relying on it. |
| Google Shopping | Conditional (connector-dependent) | Often works, but connector behavior varies. Test before going live. |
| TikTok Shop | Conditional (connector-dependent) | Frequently connector-dependent. Some setups have strict fulfillment/inventory expectations that can conflict with post-checkout edits. Test. |
| Amazon / eBay (via marketplace connectors) | Conditional (connector-dependent) | If the connector creates Shopify orders, BundlesIQ can process them — but some connectors overwrite edits after sync. Test with your specific connector. |
| Shopify POS | Works, but has channel UX limitations | BundlesIQ can transform the resulting order after sale completion, but POS UI/receipt typically reflects the pre-transformation ghost SKU. BundlesIQ does not provide a POS extension yet. |
Important: Post-Checkout Processing (What BundlesIQ Does and Doesn’t Do)
BundlesIQ transforms:
- Orders using Shopify’s post-checkout order editing capabilities
- Draft orders using draft-order updates
BundlesIQ does not:
- Transform bundles at checkout time
- Provide a POS-specific component-scanning interface (yet)
Implications:
- Order confirmation emails typically send before BundlesIQ completes transformation, so customers may see the ghost SKU in the initial email.
- Channel UIs that print or display receipts at time-of-sale (like POS) will typically show the ghost SKU, not the expanded components.
Why Parent-Only (BOM) Mode Is the Safest Multi-Channel Option
If you sell through connectors/marketplaces that may resist post-checkout edits, Parent-Only (BOM) has a unique advantage:
- Parent-Only mode does not expand the order into component line items
- That means there is no risk of line-item re-sync conflicts or “connector overwrote my edits”
- Inventory/cost behavior can still be managed via BundlesIQ settings (depending on your workflow)
Parent-Only is often the best fit when you need cross-channel consistency and want to minimize risk from connector behavior.
Subscription Apps (Recharge, Skio, Bold, etc.)
BundlesIQ can process subscription orders when those orders appear as standard Shopify orders or draft orders.
Because subscription apps vary, consider them works by design with a simple requirement:
- Test at least one subscription checkout and one renewal flow, and confirm:
- Order still transforms after the subscription app finishes its own updates
- Line item properties (if used) are preserved
- Renewals continue to transform reliably
POS-Specific Notes
BundlesIQ works after the POS sale is completed and the order exists in Shopify.
What BundlesIQ can do:
- Transform the Shopify order created by POS (post-sale)
- Keep Shopify Admin accurate for ops/accounting
What BundlesIQ does not do today:
- Show components inside the POS cart before checkout
- Provide POS staff a “bundle breakdown” UI within POS
- Change the printed receipt to show components
If POS staff need to see component breakdown before completing the sale, recommend one of:
- Staff reference the bundle configuration in BundlesIQ, or
- Use Parent-Only mode for POS-heavy workflows, or
- Treat POS component visibility as a future enhancement (POS extension)
How to Validate a Channel Before Going Live
If you rely on a non-core channel (marketplaces/connectors), run a quick validation:
- Place an order through the target channel
- Confirm BundlesIQ detected the bundle and processed successfully (Health dashboard)
- Confirm the transformed order in Shopify Admin matches your handling mode expectations
- If you use fulfillment automation/3PL:
- Confirm holds/tags behave correctly
- Confirm the external system imports only after processing
- If you use inventory sync on the ghost SKU:
- Confirm availability behaves correctly across channels
Known Limitations
| Limitation | Detail |
|---|---|
| No checkout-time transformation | BundlesIQ expands bundles after order creation, not during checkout. |
| Confirmation emails may show ghost SKU | Processing occurs after order creation; initial emails/receipts may reflect pre-transform content. |
| Connector conflicts possible | Some marketplaces/connectors re-sync or overwrite order edits. Test your exact setup. |
| No channel-specific handling mode | Handling mode is global or per bundle, not per channel. |