Integrations
Shopify here is the product itself. Every other connection is listed in the state it is actually in, and where one leg is still open, that leg is named at the same size as the rest.
Working shipping in the app today
Partly built one leg is missing, and it is named
Decided, not built a record exists, the blocker is named
Four connection points a store owner can use today. Refik is the only install, and every switch lives in Shopify’s own theme editor.
Refik is a Shopify app and a theme app extension. Setup and the console are screens in your Shopify admin; the storefront surfaces are theme blocks you switch on in Shopify’s own theme editor. Shopper requests reach Refik through Shopify’s app proxy, and each one is signature-checked before Refik answers it.
What Refik reads, and the two things it writes, are listed step by step on the setup page.
When you edit, unpublish or delete a product, Shopify tells Refik and the knowledge it answers from follows your catalogue instead of a nightly copy. Deletions are subscribed separately, because an update webhook fires only for a product that still exists.
Uninstalling the app, and Shopify’s mandatory data-request and deletion notices, arrive as webhooks too — each on its own route.
The routine suggestion block on a product page is built from Shopify’s own complementary-products data. The model is out of this loop entirely: the block reads the metafield and renders in Liquid, and it checks stock once more before it shows a product.
Where that data is empty for a product the block stays closed, so every pairing a shopper sees is one you set in Shopify.
When a shopper asks about something that is out of stock, Refik can take their email and write it to Klaviyo twice: a sign-up at the moment they ask, and a second event when that exact variant is back. It waits for the exact variant, so the note goes out for the colour they asked about.
Back in Stock is the event your flow listens for, and Back in Stock Request is the sign-up. Your public site ID is the whole configuration; saving it records that ID, and the email itself goes out when a live flow in your own Klaviyo account is triggered by the event. An empty field leaves sign-ups off.
Built, wired and usable, with one leg still open. That leg is written out below, at the same size as the rest of the row.
When Refik hands a conversation to your team, it can also open a ticket in your helpdesk with the shopper’s contact details and the conversation itself. It looks for new handoffs about once an hour, sends each one with its own reference so a handoff opens exactly one ticket, keeps your key encrypted, and sends the shopper’s side of the conversation. The window is the last seven days, so connecting it today leaves older handoffs where they already are.
Where the ticket fails to open, the handoff stays in the Refik inbox exactly as it would have anyway, and the inbox names the step that failed. The ticket is the second copy; the inbox is the first.
Both of these were decided and written down, and both wait on something outside the code. That is why each row carries a state where a date would otherwise go.
Refik answers on your storefront. The web is the one channel wired today, so a question asked in WhatsApp, Instagram DM or Messenger waits for you to answer it.
The groundwork is already in: every conversation Refik stores carries the channel it arrived on, and the web is one adapter among however many come later — so adding a channel is wiring. What it waits on sits outside the code: business verification and app review on the platform’s side, and a number to send from.
Today the console inbox is where a waiting handoff, a half-finished setup and a quota warning appear, and the console is where you read them.
The triggers are written and tested and the sending provider is chosen. Sending stays switched off until its domain is verified, and while it is off the queue stays empty — so switching it on sends the next event, and only that one.
The boundary is worth as much as the list, so here is the other half: the four paths in, and everything your storefront carries because of Refik.
Two things are worth saying plainly beyond that list: the only thing we read from a review, loyalty or subscription app is Shopify’s own product-rating metafield, whichever app writes it, and only once a product has at least five ratings — anything beyond that star figure has to come from the answers you write; and the conversation-to-order figure is a server-side read of Shopify’s own record, which is why it holds up when a browser blocks scripts. What leaves our own system to reach a provider is listed row by row on the security page.