Learn how to set up bundles and configurators that automatically track inventory — and connect your store to Claude.
Get up and running in two steps — the app block install takes about 2 minutes, then Auto-Create handles the rest in 30 seconds.
You must do this before creating any configurations. The app block is what displays your configurators and bundles to customers — and what triggers inventory deductions at checkout.
⚠️ Without the block installed, customers won't see your options and inventory won't be tracked. This is a one-time setup.
Once verified, Auto-Create appears on your dashboard and you're ready to build.
The fastest way to configure a product. After the app block is installed, an Auto-Create bar appears on your dashboard.
You have "The Hidden Snowboard" with 3 variants: Small, Medium, Large.
What Auto-Create builds:
Use this when your product is a fixed package — customers buy exactly what's in it, no choices.
A "Complete Snowboard Package" that includes a board, bindings, and boots — all pre-selected.
What customers see: just your main product page. Components are tracked silently behind the scenes.
What happens on purchase: Assemblage atomically deducts each component from inventory the moment an order comes in.
Use this when customers choose their own options — size, colour, add-ons, etc.
Customers pick their board size (150cm, 158cm, 165cm) and binding colour.
What customers see: dropdown menus and colour swatches on the product page, powered by the app block.
What happens on purchase: the exact variants the customer chose are deducted from inventory automatically.
An Assembly is a reusable template — like a recipe that defines:
Build it once, assign it to as many products as you need.
Your control centre showing which products have configurations assigned.
Assemblage uses an event-driven architecture — no pulling of historical order data on page load.
Traditional Shopify: you sell a "Snowboard Package". Shopify tracks that product but has no idea it contains a board, bindings, and boots. Component inventory is never touched.
With Assemblage: when a customer checks out, Shopify fires an order webhook. Assemblage intercepts it, reads the selected variant GIDs from the line item properties, and fires an atomic GraphQL mutation to deduct stock from every component simultaneously — all or nothing. No partial oversells, even under simultaneous purchases.
This means the inventory numbers your team sees in Shopify are always accurate at the component level.
Items that ship with every order but customers don't choose — packaging, manuals, sticker packs. Stock is still deducted, invisibly.
Every snowboard includes a safety manual and sticker pack. Customers never see these, but you need to track how many you have left.
Now every order — regardless of which configuration the customer chose — deducts those components automatically.
One assembly can power hundreds of product pages. Same option structure, each product linked to its own inventory.
You built "Custom Snowboard Builder" for Burton boards. Now deploy it to Lib Tech and Ride boards too — same size/colour dropdowns, different inventory variants per brand.
If a product shows "Needs Configuration" in Product Manager after deployment, it just means the variant links for that product haven't been set yet. Click the product and complete the picker.
Assemblage calculates exactly how many complete kits you can build from your current component stock — across every location.
The calculation works by looking at every required component and option choice in the assembly, then finding the binding constraint — whichever component has the lowest buildable quantity given your current stock levels. That number is your maximum buildable kit count.
Your Grooming Kit needs: Matte Clay (45 in stock), Beard Oil (12 in stock), Comb (89 in stock). The binding constraint is Beard Oil — so you can build a maximum of 12 complete kits before you need to reorder.
Reorder alerts fire automatically when a component crosses your threshold, so you're notified before you run out — not after.
Assemblage tracks order data via an event-driven counter system — meaning analytics reads are near-instant (typically under 50ms) and never hit Shopify's order API rate limits.
What's tracked:
All of this data is also queryable via the Claude integration in plain language — see Section 4.
Assemblage connects to Claude via MCP (Model Context Protocol) — a direct, secure link between Claude and your live store data. Instead of opening a dashboard, you can ask questions and get instant answers in plain language.
Read-only queries are available on every plan. Write-actions that update your store are available on Advanced and Plus plans.
Assemblage exposes an MCP server that Claude connects to via a secure OAuth 2.0 + PKCE flow. The whole setup takes under two minutes.
Make sure Assemblage is installed and active
You'll need an active Assemblage subscription. Any plan gives you read-only Claude access. Advanced and Plus plans unlock write-actions.
Open Claude.ai and go to Settings → Integrations
In the left sidebar, click your profile → Settings → Integrations. Click Add integration.
Search for Assemblage and connect
Search for Assemblage in the integrations list. Click Connect and follow the OAuth prompts. You'll be asked to authorise your Shopify store — Claude will receive a short-lived token scoped only to your shop.
Start a new conversation and ask away
Open a new Claude conversation. Assemblage tools are now available — Claude can query your assemblies, inventory, and analytics in plain language without you opening a dashboard.
⚠️ Privacy: Claude's access is scoped to your shop domain only. The token is short-lived and stored securely. Assemblage does not share your store data with any third party. Claude cannot access another merchant's store.
These are read-only — Claude queries your live data and returns a plain-language answer. No changes are made to your store.
Paste a customer question and get an instant, accurate answer from your live assembly data.
"Does the Pro Kit include titanium screws?"
Uses: get_assembly_detail
Query revenue, order counts, and top-performing assemblies without opening a report.
"What's my best-selling configuration this month?"
Uses: get_analytics_summary
Ask Claude to audit all assemblies for broken SKU links, unlinked choices, and missing components.
"Which of my configurators have broken links?"
Uses: find_broken_assemblies
Find out which option pairings customers buy together most — useful for bundle ideas and stock planning.
"What are my most popular component combinations?"
Uses: get_combination_trends
These actions make changes to your store on your behalf. Each requires your confirmation before executing.
Claude reviews your production forecasts, identifies components at risk of stocking out, and drafts a purchase order — ready for your approval.
"Draft a PO for anything running out in the next 7 days."
Claude finds your most popular component combinations from real order data and creates a fixed bundle product — ready to promote.
"Turn my top combo into a bundle for the homepage."
When Claude finds broken SKU links, it searches your Shopify inventory for the closest matching variants and patches the configurator automatically.
"Find and fix the broken links in my Summer Kit."
These are the MCP tools Assemblage currently exposes to Claude. All tools are scoped to your shop — Claude cannot access another merchant's data.
| Tool | What it does | Plan |
|---|---|---|
| list_assemblies | Lists all assemblies with name, type, product count, and deployment count | All |
| get_assembly_detail | Full config for one assembly: options, choices, components, assigned products | All |
| find_broken_assemblies | Surfaces unlinked choices, empty option groups, missing components | All |
| get_shop_status | Current plan, trial status, theme block installation state | All |
| get_analytics_summary | Total revenue, orders, top assemblies, most popular options and combinations | Adv+ |
| get_assembly_performance | Order count and revenue for a specific assembly | Adv+ |
| get_option_trends | Ranked list of individual choices by order frequency | Adv+ |
| get_combination_trends | Ranked list of option pairings customers select together | Adv+ |
| get_deployment_history | When an assembly was published to the storefront over time | Adv+ |
