Setup
Refik installs as a Shopify app plus a theme app extension. Setup runs as a wizard in your admin; these are its screens, in order, with the names you will read on them.
Refik reads your own catalogue and proposes a starting point: what kind of store this is and how it should introduce itself. It shows you the evidence it used, and you accept that or change it.
Your click is the only write path: the detection code returns a proposal, and the wizard applies it when you say so. Where a catalogue gives it little to go on it proposes the neutral pack, marks its confidence low, and names the reason.
The rules Refik is allowed to state to a shopper — return window, who pays return shipping, where you ship, how long it takes. Your own policy pages arrive as a draft in the form, so most of this step is confirming your own words.
Preparation time and transit time are pulled apart, each carrying the sentence it came from. A figure whose sentence is ambiguous reaches you marked “unclear” and you place it. A field you leave empty makes Refik say it will check with you and offer to pass the question on.
Ask it your own questions while the storefront is still quiet. This runs against your real catalogue and your real rules, so what you read here is what a shopper would get.
Every side effect in the app travels through one interface, and this step hands that interface a stand-in. So the step lists what it would have done live: the return it would have opened, the note it would have written.
Open the theme editor, turn on “Refik chat” under App embeds, save, then come back and check again. Refik never edits your theme files — the switch is yours, in Shopify’s own editor.
The check reads the setting Shopify reports. Where Shopify stays quiet the wizard calls the result inconclusive and holds the step open until it reads active.
Refik is answering on your storefront, and the console shows you what it was asked, what it answered, and where it handed a conversation over.
Refik is not listed on the Shopify App Store yet, so today this page is the map. These are the steps the wizard runs the day the listing goes live.
Setup lives in your Shopify admin. Your Shopify login is the login, and every switch you touch is one Shopify already gives you.
Access is asked for once, at install, and the list is short enough to read in full: six scopes. Two of the six carry a write verb, and each of those writes exactly one kind of record.
refik/profil, holding the preferences a shopper stated about themselves, with a timestampYour theme stays yours: the storefront surfaces arrive as a theme app extension, so a theme update leaves the interface standing and each surface keeps its own switch in Shopify’s editor.
The full list of scopes, with what each one is for and where it stops, is on the security page — and the build compares that list, name by name, against the app’s own configuration file.
These are the names to look for once setup is done. The first is an app embed and appears on every page; the other four are section blocks you place where you want them, so each one stays a decision you make per template.
App embeds → the chat bubble, on every page of the storefront. Turning this on is step four of setup, and the accent colour set here is the one the other four surfaces inherit.
A section block for the product template: the questions shoppers actually ask about that product, answered from its own fields and from your rules.
A section block for the search results template. It speaks up when it adds something — a barcode, a synonym match, a product that has run out, or a query that wants information rather than a product.
A section block that puts suggested questions in front of a shopper, so the first move is already written for them.
A section block that builds a short routine around the product on the page, using only options your store can sell right now.
All five ship with their own wording in every storefront language the extension carries, so a shopper reads the interface in the language your theme is already serving. What each one says, in full, is on the surfaces page.
Setup is a wizard you click through; the work behind it is a pipeline with three stages. It runs on a schedule so a long catalogue finishes on its own time, and it keeps running after setup is done.
Stage one
Products, variants, options, prices, stock and collections come in over Shopify’s Admin API, page by page. Three counters guard the pull: the product count Shopify reports against the products received, each product’s variant count against the variants received, and the collection count against the collections received.
A mismatch stops the pull with a named error. A page limit that drops rows quietly is the one way a catalogue read can go wrong and still look healthy, so all three are hard stops.
Stage two
The raw pull becomes the file Refik answers from: what each product is for, which products complete each other, which ones form a routine, and which options a shopper can buy today.
The interpreting pass is batched and runs on the hourly job rather than inside your click, so a long catalogue finishes as a handful of scheduled passes and your request closes in a second.
Stage three
Two Shopify webhooks keep the file in step with your store: one fires when a product changes, one when a product is removed. Both arrive at the same endpoint, and the decision comes from what the Admin API answers rather than from the header on the webhook.
So a price edit, a stock change, a product switched to draft and a product deleted all reach the knowledge base by the same route, on the next hourly pass.
While that pipeline is running the wizard keeps its own record of each pass, and the console shows you the time of the last one — so a store that is waiting reads differently from a store that is stuck.
Four answers, each of them something the code already does. The trial, the billing ceiling and the removal path all have their own pages, linked where they come up.