Integration Partners: Connect What You Already Run

Shopify merchants do not sit around hoping for another logo wall.

They sit in admin and wonder why the apps they already pay for never show up at the same time.

That is what people actually write in public. On r/shopifyDev the top answer to "what are merchants struggling with in 2026" was messy integrations and too many apps doing half-jobs. The line that got voted up: merchants do not want more tools. They want ones that work together.

On r/shopify_growth an operator walked through an 18-app store. Each app solved one small issue. Together they slowed the storefront and made the backend confusing. The fix was not a nineteenth install.

This post is about one feature. Integration partners. The cards on the ShopGuide integrations page. What you get when you connect the ones you already run, and how ShopGuide itself is wired so those cards are not decoration.

The feature: integration partners ride the same conversation

ShopGuide is an on-page agent. You install it from the Shopify App Store. You add the ShopGuide Chat section in the theme editor. The dashboard lives in the Shopify admin sidebar.

During chat the agent looks up products on the Shopify Catalog API. Stock, variants, and price come from the live store. Not from a CSV you uploaded last month.

Integration partners attach to that same thread. They do not get a second bubble.

The current set is the list on the ShopGuide integrations page. Same six cards as integrations.yourshopguide.com/shopify. No coming soon row.

That is the merchant value. Not a new stack. The stack you kept, used at the moment the shopper hesitates.

Connect the ones you run. Leave the rest alone.

Deep dives already exist if you only need one pairing: Klaviyo, Judge.me and Rivyo, Smile.io, Slack.

Earlier maps of the same surface: how ShopGuide is wired, partners on the existing stack, and the partner page as merchants would read it. This post is the connect-or-skip decision.

How ShopGuide is integrated so partners have somewhere to land

Integration partners only work because ShopGuide is already inside Shopify. Three connections. That is the product.

1. Theme block. You add the ShopGuide Chat section in the theme editor. Launch messages, visibility, and styling live in the app admin. One storefront surface. Not a new script for every partner.

2. Shopify Admin. Home, Dashboard, Test your Guide, Integrations, Settings. Chat-attributed revenue shows up there. Review-app tokens live on the Integrations screen. You do not leave Shopify to see if a conversation sold anything.

3. Live Catalog API. The agent queries Shopify for the products in play. Sold-out SKUs should not get recommended as available. Dirty titles still produce thin answers. Live stock is the part the API can keep honest. Details are in the live Catalog API post.

Most pairings activate when both apps are installed. Slack is the exception. That one needs an incoming webhook URL in ShopGuide settings.

There is a second Klaviyo path that is easy to miss if you only look at storefront chat. Path Explorer can sync reachable segments into a Klaviyo list with cohort properties. Cart abandoners and chat-assisted buyers can land in a flow you already run. That is documented. It is not a promise that every anonymous browser becomes a profile.

A store on Judge.me and Klaviyo does not need Rivyo or Alia for the agent to be useful.

Why merchants care about integration partners

High-SKU operators already run a lean version of the same kit. Email. Reviews. Loyalty. A channel for the team. Maybe a popup tool.

The complaint is not "I hate apps." It is paying for tools that never share context when a shopper stalls on a 10,000-SKU catalog.

Popup in one corner. Stars below the fold. Points in a widget. A ticket that starts from zero.

Integration partners do not ask you to rip Klaviyo out. They ask the agent to use Klaviyo. Same for reviews and points.

The useful test is boring. Can the shopper hear the thing you already paid for without opening another tab?

That is why the partner page is short. Six names. The catalog underneath them.

Honest limits

Say this before you flip switches.

ShopGuide does not replace Klaviyo, Judge.me, Rivyo, Smile.io, Alia, or Slack. If the partner app is missing or the token is wrong, there is nothing to read.

Reviews in chat are only as good as the reviews you collected.

Smile.io only helps once the shopper is identified. A first-time anonymous visitor has no points to surface.

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 conversation from Slack replies.

Klaviyo does not invent a list. Popup recovery needs Klaviyo actually on the store. Path Explorer sync only pushes reachable people, the ones with an email or a Shopify customer id.

The agent cannot invent metafields that live only inside another app and never in Shopify. The Catalog API keeps stock current. It does not write your descriptions.

Integration partners are context in the path. They are not a new operating system for the store.

That is the climax, and it is not a ShopGuide slogan. It is how Shopify is describing the channel.

ShopGuide's job on your store is smaller than that vision. Put the agent on the page. Read the catalog. Bring in the partner facts you already paid for. Hand off to a human with the transcript when the agent is stuck.

Connect the ones you run. Leave the rest alone.

Install ShopGuide and connect your stack

Frequently Asked Questions