Unlimited in the table
The plan carries no included figure of its own. The number that applies is the one agreed for your account.
Enterprise
Not a card you click, and not a sales call either.
Past three thousand conversations a month the listed plans stop describing the arrangement, and the honest word for what replaces them is negotiated. This page is not a pitch for that. It is a description of what the Enterprise plan already is inside the product — which switches behave differently, what is deliberately absent, and the one mechanism that exists today for starting the conversation. Some of what follows is a gap rather than a feature, and the gaps are marked as gaps.
Where the line is
The threshold is the top listed plan’s included volume, not a judgement about your size.
There is no revenue test, no store count and no category. The line is arithmetic: the highest plan with a price on it includes three thousand conversations a month, so a store that needs materially more than that has run out of listed plans. A single store doing that volume and a group of twenty smaller ones arrive at the same place for the same reason, and neither of them is being sorted into a tier by anything other than the number.
What a conversation is
The unit the plans are counted in is defined on the pricing page rather than restated here, because a second definition is how two pages start disagreeing. If the number matters to you, that definition is the thing to read first.
Why there is no fourth card
A card implies a price, and a price we would have to publish before knowing what we were agreeing to. The App Store listing therefore carries three plans and a line saying what happens past the top one, which is less tidy than a fourth card and more accurate.
What changes in the product
Four switches behave differently, and one of them is a restriction.
Enterprise is a real plan in the quota system rather than a label on an invoice, so it is worth being specific about what it does. Three of the differences are what you would expect. The fourth is not: because the volume is agreed rather than metered, there is no overage to fall back on, which means the agreed ceiling is a hard one.
Set per account
A ceiling can be recorded against your account specifically. It is the only plan where a per-account figure is read at all.
No overage
There is no per-conversation charge past the ceiling, and therefore no grace band either. The ceiling is hard.
No free trial
The trial applies to the listed plans. An Enterprise arrangement starts when it is agreed, not after a countdown.
The warning threshold is the same as every other plan — you are told when the agreed volume is being approached rather than when it has been passed. A paid listed plan cannot be loosened account by account; the per-account ceiling exists for this plan alone, which is the reason it is the only one that can be negotiated in the first place.
How it starts
A form in your Shopify admin, and no email to anyone.
There is a request form on the plan screen inside your Shopify admin. Filling it in writes a numbered record that our side reviews; it does not send a message to us and it does not send a confirmation to you. That is unusual enough to state plainly rather than leave you waiting for something that is not coming: the request number on the screen is the receipt, and it is worth keeping.
Five fields, three of them optional
Your name and a contact email, then — if they help — the number of stores, an estimate of conversations per month, and a note. Nothing is asked that is not used to answer the question, and the two optional numbers are digits only, deliberately, so that a thousands separator cannot turn twenty thousand into twenty.
A store admin or owner
Staff with read-only access cannot send one, because a commercial request should come from somebody who can enter into it. A store already on Enterprise is told so instead of being allowed to ask twice.
A store can send three requests in twenty-four hours. Beyond that the form says how long to wait rather than silently discarding the fourth.
What happens to the request after you send it
It becomes a row with one of three states — new, reviewed, or closed — visible in our own admin panel, and every change of state is written to an audit record. That is the full extent of the machinery: there is no pipeline, no owner assignment and no automated follow-up.
We are not going to put a response time on this page. We have not measured one, there is no queue to measure yet, and a number invented for a page like this is the kind of promise that gets quoted back later.
Why the form is inside the admin and not here
Two reasons, and the second is the real one. The first is that a request from inside your admin arrives already knowing which store it is about, so nothing has to be matched up by hand. The second is that an Enterprise request has to be tied to a store record, and only the form in your admin can do that. The one form on this site, on the contact page, sends an e-mail and creates no request.
The consequence is a genuine gap and it is the next section.
What the form does not do
It does not change your plan, reserve capacity, start a trial or create an invoice. Nothing about your account moves because a request exists. The plan is assigned by hand afterwards, which is the same sentence as “negotiated” read from the other direction.
The gap, named
Before you install, the contact page.
The request form needs the app installed, because it lives in your admin. A store that wants to talk about terms before installing anything can write through the contact page: the message goes as an e-mail to [email protected], the inbox of Pirahas Türkiye, the company behind Refik.
Two things it is not. It is not an Enterprise request — that numbered record is still only made from inside your admin, after installing. And it carries no promised reply time, because none has been measured; the same applies to the pricing page’s wording about contacting us.
The limits of this page
Everything an enterprise buyer usually asks for, we do not have.
No service level agreement, no uptime commitment, no acceptable use policy, no security questionnaire already answered, no audit report and no certification. None of those is being prepared behind the scenes; they are things that do not exist, and a page that implied otherwise would be the easiest lie on this site to tell. What does exist is written down and checkable: the access the app asks for, where data is stored and for how long, the deletion paths, and a data processing addendum that applies from installation, with a countersigned copy on request.
Also absent, and for the same reason: a named reference customer, a case study, a volume discount schedule, a dedicated environment and single sign-on. The product is a Shopify app with one install and a per-account quota, and Enterprise is a plan inside it rather than a different product.