- Published on
Shopify Integration Partners: Detect the Stack You Already Run
TL;DR
Shopify merchants do not want another dashboard. They want the apps they already pay for to show up in the same conversation. ShopGuide scans the theme for those apps, then reads them from the on-page agent once you paste the tokens that actually unlock the data.
- Authors

- Name
- Isaac Lewin
- Shopify Architect
- @iliveoffgrid
Merchants keep saying the same thing in public.
Not "give me more apps."
Give me fewer half-jobs.
On r/shopifyDev in early 2026, a thread asked what merchants were actually struggling with. The top answer was not search. It was the stack:
"Honestly, it’s the small daily stuff: messy integrations, tracking mismatches, clunky returns, and too many apps doing half-jobs. Merchants don’t want more tools they want ones that actually work together."
That is the whole brief for Shopify integration partners.
ShopGuide does not replace Klaviyo, Judge.me, Rivyo, Smile.io, Alia, or Slack. It sits on the storefront, reads the Shopify catalog live, and pulls partner context into the same conversation when those apps are installed and connected.
One feature in this post. Automatic app detection, and what those partners are worth once the wiring is live.
The feature: ShopGuide looks for the apps you already run
Open ShopGuide → Settings → Integrations.
The app scans your published theme and storefront assets for embeds it already knows. Klaviyo onsite scripts. Judge.me review widgets. Smile.io loyalty launchers. Detected apps move to the top under "Looks like you use these" with an On your store badge.
That scan is not the integration. It is the map.
Detection tells you what is already on the theme. The partner still needs a key for ShopGuide to read live data:
- Smile.io: API token from Smile admin, pasted into the Smile card.
- Judge.me or Rivyo: public API token from that review app, pasted into the matching card.
- Klaviyo: private API key with Profiles: Write, Events: Write, and Lists: Write.
- Slack: incoming webhook URL. This one is not auto-detected the same way. You paste it.
Alia is on the public partner page as personalized incentives. If you do not run it, skip it.
You do not connect six partners to make the agent useful. Connect the ones you already pay for.
How ShopGuide itself is wired into Shopify
Three connections. That is the product surface.
1. Theme block.
ShopGuide Chat is a theme app section. You add it in the theme editor. Launch messages, visibility, and styling live in the ShopGuide admin. Partners do not get a second chat window.
2. Shopify Admin.
The app sits in the admin sidebar. Home, dashboard, Test your Guide, chats, Path Explorer, Appearance, Integrations, Settings. Revenue attributed to chat sessions shows up there. You do not leave Shopify to see if a conversation produced an order.
3. Live Catalog API.
During chat the agent looks up products from Shopify. Stock, variants, and price come from the store, not from a file you uploaded last week. A sold-out SKU should not get recommended as available.
Partners attach to that same conversation. Reviews, points, events, and handoffs ride along. They do not become a new pixel farm.
The public list lives on the integrations page. Partner how-tos if you only need one pairing: Klaviyo, Judge.me and Rivyo, Smile.io, Slack.
What each partner is worth to the merchant
High-SKU stores already run a lean version of the same kit. Email. Reviews. Loyalty. A channel for humans. The shopper still has to hunt for each one.
Popup in one corner. Stars below the fold. Points in a widget they never open. Support that starts from a blank ticket.
The useful test is not "how many Shopify integration partners." It is whether the shopper hears the fact you paid for at the moment they hesitate.
| Partner | What detection finds | What you still paste | What the shopper gets |
|---|---|---|---|
| Shopify catalog | Native. Always on. | Nothing extra. | Live stock, variants, and price in the reply |
| Klaviyo | Onsite script in the theme | Private API key | Chat events and profile fields in Klaviyo, plus list capture when the shopper gives an email |
| Judge.me | Review widget embed | Public API token | A matching review in the recommendation, not only under the fold |
| Rivyo | Review / UGC embed | Public API token | Same job if Rivyo is your review app |
| Smile.io | Loyalty launcher embed | API token | Live points and VIP tier in the sentence that closes the sale |
| Alia | Listed on the partner page | Use it if you run Alia | Incentive stays in the conversation after a popup is gone |
| Slack | Not a theme embed | Incoming webhook URL | Cart, path, and transcript posted to a channel when a handoff fires |
Klaviyo write-back is specific. ShopGuide can send ShopGuide Chat Engaged, ShopGuide Order Attributed, and ShopGuide NPS Submitted. Profiles can carry journey archetype, last chat intent, and the hesitation the shopper actually said. That only happens after the private key is in Settings.
Smile only answers "how many points do I have" once the shopper is identified and the token works. A first-time anonymous visitor has no balance to read.
Why this is the post merchants say they want to read
Forums do not ask for another AI wrap-up.
They ask why two tools in the same category fight. Why a subscriber return still bills. Why loyalty treats subscriptions as an afterthought. Why ten apps each do a half-job.
Shopify Community threads on app sprawl say the same thing in plainer words. Every basic job seems to need another $9 app. Scripts stack. Speed drops. Uninstall leftovers stay in the theme.
A scrape of 10,000 Shopify stores that made the rounds on r/shopify_geeks put numbers on the speed part. Stores with 10+ apps averaged much worse mobile scores than stores with none. Klaviyo and Smile.io were in that script-cost list. The point is not "delete Klaviyo." The point is stop installing a second copy of the same job.
ShopGuide is one theme block. It does not install a second Judge.me. It reads the one you have.
On a 200-SKU boutique that is polite. On a 10,000-SKU catalog it is how "does this run large" stops becoming a ticket.
Honest limits
Say this before you paste any keys.
Detection is a theme scan. If the partner app is installed but the embed is off, ShopGuide may not badge it as "On your store." You can still paste the token.
No token, no live partner data. An empty Judge.me catalog means empty social proof in chat. A Smile program with no identified customer means no points line.
Slack is one-way. ShopGuide posts context into a channel. Your team still resolves in Shopify or the ShopGuide admin. You do not run the whole thread from Slack replies.
Klaviyo does not invent a list. Events and profile fields only write if the key has the right scopes and the shopper actually engages or shares an email.
WhatsApp handoff exists in the docs as a high-touch path. It is not on the public partner page next to Rivyo and Smile. Treat it as optional, not as a listed partner in that grid.
The agent cannot invent metafields that live only inside another app and never in Shopify. Dirty product data still produces thin answers. The Catalog API keeps stock honest. It does not write your descriptions.
That is the deal. Native wiring. Partner context when the token works. Not a new operating system.
We’re going to begin to use these agentic applications as these kinds of personal shoppers.
Tobi Lütke put the same idea in one line when Shopify shipped Checkout Kit, Catalog, and Universal Cart: agents will become a common way people shop, and commerce should plug into the conversation instead of opening another tab.
ShopGuide's job on your store is smaller than that vision. Put the agent on the page. Read the catalog. Detect the stack you already run. Bring in the partner facts you already paid for. Hand the transcript to a human when the agent is stuck.
Connect the ones you run. Leave the rest alone.
Install ShopGuide and connect your stack
Frequently Asked Questions
What are ShopGuide's Shopify integration partners?
The public list is Klaviyo, Judge.me, Rivyo, Smile.io, Alia, and Slack, plus the native Shopify Catalog API. See the integrations page.
How is ShopGuide integrated into Shopify?
Three places. A theme block on the storefront. A native app in the Shopify admin for analytics and settings. Direct catalog reads during chat. Partners attach to that same conversation.
What does automatic app detection actually scan?
Published theme embeds and storefront assets. Detected apps show under "Looks like you use these" with an On your store badge. The badge is not the same thing as a live data connection.
Do I have to replace Klaviyo or Judge.me?
No. Keep the apps that already work. ShopGuide reads them. It does not ask you to rip them out.
How do I turn a partner on?
Install both apps. Then paste the token or webhook the partner needs in ShopGuide → Settings → Integrations. Slack always needs a webhook URL.
Will this add more scripts and slow the storefront?
ShopGuide is one theme block. It does not install a second copy of Klaviyo or Judge.me. Partner apps keep their own scripts. The integration is the agent reading those systems.
What if I only use some of the partners?
Use the ones you have. A store on Judge.me and Klaviyo does not need Rivyo or Alia for the agent to be useful.
Does Slack let my team reply inside Slack?
No. Slack gets a structured alert with context and a link to the transcript. Resolution stays in Shopify or the ShopGuide admin so history lives in one place.
Master Agentic Commerce
Join Shopify founders receiving weekly insights on AI agents and autonomous growth.
Trusted by top Shopify Plus brands
