Shopify

What the Shopify integration does today

This page is not a wall of logos. It is the list of what the Shopify connection does today, word for word, and the list of what it does not do. The second list is the one almost nobody publishes, and it is the one that saves you the awkward meeting in month three.

The important part first: with a connected store, Eva answers from your real catalog, checks stock at the moment it answers, sends the checkout link inside the conversation, builds a draft order and looks up an order's status. What it does not do today: it does not install in one click from the Shopify App Store, and it does not recover abandoned carts.

What it does today

Your catalog comes in whole. Store products are imported as the agent's catalog source, with their variants and their photos, and stay in sync through Shopify's product webhooks. A Shopify-sourced catalog is read-only inside Eva: it is edited in the store, and the store is in charge, which is how it should be once you already have a place where product truth lives.

Stock is checked at answer time, not at import time. When somebody asks about a product, Eva looks up live price, compare-at price, availability and inventory quantity; it can also check stock per location when you have more than one. If that live lookup fails, the answer is marked as cached data instead of pretending it is fresh.

Payment happens inside the conversation. Eva sends the Shopify checkout link with the products already on it, or builds a draft order when the sale needs adjusting before charging: odd quantities, a negotiated price, shipping that gets worked out separately.

After the purchase, Eva looks up the order and its shipping status in the same thread where the person asked. These tools touch buyer data, so they sit behind identity verification and depend on the protected customer data approval Shopify grants per store; until that approval exists, they stay off, and you will know it from setup rather than later.

Purchase history can feed the CRM, with explicit permission. It is opt-in: leave it off and nothing happens. Turn it on and each order is stored as history linked to the contact, with total spent, order count, last order date and most-bought categories recomputed, all deduplicated so re-importing never forks a person. How far back the history reaches depends on the permission your store grants: without the extended orders permission Shopify only returns the recent ones, and the window shrinks on its own rather than breaking.

How it connects: assisted, not one-click

Today the connection is assisted: we connect it with you during setup. It is not a button you press on a Sunday from the App Store, and we would rather say that here than let you find out after signing.

What we need from your side is store admin access with permission to authorise the connection, and a decision on which permissions you grant: products and inventory for catalog and stock, orders for lookup and tracking, and the extended orders permission only if you want older history in the CRM. Each permission you withhold turns off one specific capability rather than the whole connector.

In that same session we decide which agent the store is bound to, which product fields the customer can see and which stay internal, and whether purchase history goes into the CRM. It comes out connected and tested, not connected and waiting.

What it does NOT do yet

There is no one-click install from the Shopify App Store. The public-app code exists, but the app is paused on Shopify's side, and we are not going to sell you an install you cannot do today. The route that works is the assisted connection above.

It does not recover abandoned carts. This is not switched off and not waiting on a permission: the capability does not exist in the product. If that is what you are buying, the honest answer is that Eva is not your tool for it today.

It does not edit your catalog. A Shopify-sourced catalog is read-only in Eva: prices, descriptions and photos change in the store.

It does not take card payments outside Shopify. Paying inside the conversation means your store's checkout link, your gateway and your rules.

It does not connect to other online stores. Shopify is the commerce connector that exists today; any other platform is a custom integration on our primitives, subject to it having an API and documentation.

Who it is for

For a Shopify store already getting questions by message and answering them by hand: how much is it, do you have my size, is it in the other location, has my order shipped. That conversation arrives through WhatsApp, Instagram, Messenger, calls, email and your site, plus Instagram comments and TikTok ad comments, and what makes it useful is the agent seeing the same inventory your team sees.

For anyone selling products with variants and stock that moves. If your catalog is five products that never change, the connection adds less and there are simpler ways to start.

It is not for anyone buying cart recovery or an app-store install today. Neither exists in the product, and saying so before signing is cheaper for both of us.

Methodology

  • Have store admin access ready, with permission to authorise the connection.
  • Decide which permissions you grant: products and inventory, orders, and the extended orders permission if you want older history.
  • Decide which agent the store is bound to before connecting.
  • Mark which product fields the customer can see and which stay internal.
  • Decide whether purchase history goes into the CRM; it is off by default.
  • Get price and description right in Shopify: it is the source of truth and Eva does not edit them.
  • Test the whole conversation before opening it: product question, stock, checkout link and order lookup.

Put Eva to work.

Tell us what you sell and what people ask you by message, and we will say plainly what the Shopify connection covers and what it does not.

Message us on WhatsApp

Updated

Message us on WhatsApp