Skip to content

Vertical pack · Neutral

The neutral pack is the smaller claim.

A store lands here in one of two situations: its catalogue is still being read, or it was read and every vertical stayed under the three gates. The console names which of the two you are in, and both keep the same product. Refik declines to guess your trade and answers from your own catalogue on the words your own catalogue uses.

14 fields, nine of them empty 0 rules of its own, 16 from the base set Zero survey questions, zero roles, zero needs
  • Products
  • Variants & options
  • Prices
  • Live stock
  • Collections
  • Order status
  • Returns
  • Store policies
  • Answers you write
  • A code you choose
Refik’s console, Overview screen: conversations used against the plan, a bar per day, what happened in them, unanswered questions, and orders Refik took part in.
Product screenshot, sample data. The numbers are made up, not a customer’s result. Once installed, every figure here is counted from your own store.

A pack changes what Refik asks; it leaves the ten sources an answer is built from exactly where they were. Every store reads the same ten, placed or unplaced — what Refik reads.

What changes

What narrows, and what holds.

Two things, and only one of them is a loss. The neutral pack drops every sentence that would pretend to know your trade, and keeps every rule that any store could get wrong.

It answers the question it was asked

The survey object in this file has three blank members: the intro line, the question list and the sentence template. The profile field list is blank as well, so the tool that remembers a returning shopper stays closed — a tool with an empty schema would have to invent what to save. Refik introduces itself as a general product advisor, a sentence the file carries in English and Turkish, with English standing in for Spanish.

It still refuses

Sixteen claim rules and nine handover patterns, in English, Turkish and Spanish. The rules cover eight families: a treatment claim, a product standing in for a medicine, disease prevention, proof language, a promise of a fixed outcome, absolute safety, a legal or tax assurance, and lifting an age check. This set was added after the file was read, because a store we had placed carried more rules than a store we had merely accepted.

Counted, not written

A file with nine empty collections in it.

Fourteen top-level fields, and nine of them are empty on purpose. The tenth is a survey object whose three members are all blank. Four more fields the beauty pack carries are absent here — they exist for a pack that has something industry-specific to say.

0

questions it asks a shopper before answering. It answers the question it was actually asked.

0

fallback names for your product roles. Where your catalogue names a tag, that name is the only one there is.

16

claim rules it still carries, every one of them from the base set that every store gets whatever it sells.

Your own tags do the matching

Roles, needs and alternative spellings are three blank collections here. A shopper’s word goes straight at your own tags, titles and collections, so a catalogue written in one language is answered in that catalogue’s own words.

Three switches, all three closed

Shade matching, a remembered profile, a replenishment reminder. A closed tool is absent from the list the model is handed, so the model can only offer what the pack opened. The third is a list of reminder candidates; with the switch closed it comes back empty.

Your generic storefront wording stays

The greeting, the example questions and the entry cards keep the wording they shipped with. If a pack with a storefront block is confirmed later, its text is written to app-owned metadata and the same write clears the wording it replaces.

The plan price is the same under every pack: the billing and quota code reads your plan and your usage, and a pack name appears nowhere in it. Refik still answers from your catalogue, your stock and your policies, still refuses to assert an absence, and all five of the storefront surfaces work.

What this page is a picture of

Refik card for Vertical pack · Neutral: the sentence this page turns on, and the store data it reads.
Drawn from this page’s own data — the sentence and the sources shown are the ones shipped, not an illustration of them. Regenerated by scripts/sektor-maket-yaz.py.

Counted

Four counts a store on this pack can check.

Each of these four comes out of the pack file or the code that reads it, so each of them is something you can be shown in your own console.

  • Eight families, three languages

    The sixteen base rules split eight written for English, five for Turkish and three for Spanish, because a phrase is forbidden in the language it is written in. A rule carries the language it belongs to, so a Turkish answer is read against the Turkish rules.

  • Nine patterns, seven question families

    Pregnancy and breastfeeding, an allergy, a chronic condition, a prescription or a current medication, the shopper’s own doctor, safety for a baby or a child, and recent surgery. Those go to you with the conversation attached.

  • One persona sentence, two languages

    “General product advisor” is in the file for English and Turkish; Spanish reads the English one. English is the language a pack always fills, because every blank falls back to it.

  • One audit row per change

    Moving off this pack writes a dikey_degistir row to your account audit record in the same database batch as the change itself. The update is conditional on the pack you had on screen, so a second open tab is told the value moved instead of overwriting it.

Unchanged

What stays yours, under every pack.

These three are the same on every vertical page on this site, and that is the point: they describe the part of Refik that your store decides and a pack only reads.

You choose it, and the server measures again

Refik counts how many of your products carry any of a pack’s words and shows you the count, the ranked score, up to eight of the words it matched and up to three example products for each. A pack is only suggested when the share clears a threshold, at least three different words matched and at least five products matched. You confirm it, and the server runs the measurement again on its own before it writes anything. How a pack gets chosen.

Your catalogue supplies the products

A pack supplies names; your catalogue supplies the products. Every option Refik offers has passed two gates in your own store — sellable, and in stock — so the products a shopper sees are the ones you carry today. A pack tag that matches zero products in your catalogue is counted and shown in the console, with the number it matched.

The base set stays merged in

Sixteen claim rules and nine handover patterns are merged in when any pack loads, in English, Turkish and Spanish, and they sit behind the pack’s own rules so the pack’s rule is still the first one reported. A base rule that would report the same words twice stays quiet. An empty set makes the app refuse the pack outright. The base set.

Two situations bring a store here and the console names which one: the catalogue is still being read, or it was read and every pack stayed under the three gates. If you sell hair care, makeup, skin care, beard and shaving care or fragrance there is a file for you — the beauty pack, counted.