Skip to content

Industry · B2B and wholesale

A trade supplier runs on the neutral pack.

No dedicated pack is built for this sector yet, so a shop selling to other businesses — case quantities, a catalogue keyed by part number, a buyer who is rarely the account holder — lands on the neutral one. That is the smaller claim rather than the broken one: twelve tools exist in the code, nine of them are handed to the model from the first conversation, and the base rule set every store gets is merged in whatever the shop sells. This page counts what runs on day one, the one axis of a trade question the base rules genuinely hold, and the axis they do not hold at all.

Nine of twelve tools, from day one Guest orders need number and e-mail Zero roles, zero reorder intervals
  • 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. A trade catalogue reads the same ten as a placed one — what Refik reads.

What runs

Nine tools, handed over on the first day.

Ten of the twelve tools are present under every pack; a pack only decides whether shade matching and a remembered profile are offered, and both are shut here. The ordered-routine tool is the third one that stays shut, and it is shut by your catalogue rather than by the pack: it is offered once at least one chain carries a product role, and roles are the thing a pack supplies. What is left is the whole order and policy axis, which is most of what a trade account asks for. Order status for a signed-in buyer, a guest order lookup, the return request, the shipping and returns lookup, the stock-back e-mail and the handover to your team all work from the first conversation — and the shipping answer comes out of your own policy pages rather than out of memory, as two legs plus a total, because quoting the transit leg alone shortens the wait a buyer is told by about a week.

A part number is a search, not a lookup table

The search tool runs before any recommendation and reads what the buyer actually typed: it resolves barcodes. That leg is code and the same under every pack; the Spanish and Turkish words — and the misspellings — it maps are hand-written entries in the pack’s synonym dictionary, which here is an empty object. Nothing is corrected by algorithm: matching is substring-based, so a word merely cut short still lands and a transposed one does not. It is called before a product name or a price is ever stated, and an item that is out of stock never appears in what it returns — so a line ordered in cases is not quoted and then found missing. What it matches is whatever your own titles, tags, barcodes and collections already carry. A superseded code, or a code your supplier uses and you do not, matches nothing today: the dictionary that would map one onto the other is the field a pack fills, and under the neutral pack it is an empty object.

The person chasing the delivery is often not the account holder

A signed-in buyer gets their own orders and a tracking link where one exists, and a guest gets nothing from that tool at all. For the guest there is a second one, and it asks for the order number and the e-mail together — both are required, and it is never called with one of them. That is the ordinary case in this trade: the person asking where the pallet is works in receiving, not in finance. When there is no match the tool’s own answer is relayed rather than explained, because a guess about why an order cannot be found is a guess about someone else’s account.

Counted, not written

The base rules hold the tax side of this trade, and only that side.

Sixteen claim rules merge into every pack, and two of them — one written in English, one in Turkish — are the pair this trade runs into. Between them they cover a store saying there is no customs or import duty, that you will not pay import tax, that something is tax or VAT deductible or exempt, that a return on an investment is assured, that you can claim it on your taxes or from insurance, and, in the Turkish rule, that you are legally entitled or legally obliged. Measured against the sixteen patterns with a boundary on both sides of each word: tax, vat and customs are all there. The commercial half of the same conversation is not. invoice, bulk, wholesale, moq and the Turkish word for payment terms appear in none of the sixteen, and neither do credit, duty or tariff on their own.

16

claim rules in the base set, merged in whatever the shop sells; two of them are about tax and legal assurance.

3

words on the tax axis — tax, VAT and customs — that those patterns do carry.

5

words on the commercial axis — invoice, bulk, wholesale, MOQ and the Turkish word for terms — that appear in none of them.

What the two rules actually catch

Both are about an assurance a shop is not in a position to give: a customs or import figure, a deduction or an exemption, a certain return, a claim against insurance, and — in the Turkish rule only — a statement about what the law requires of the buyer. They fire on the wording rather than on the topic, so they catch the sentence that promises, not the sentence that explains your own published policy.

What nothing stops today

Thirty-day terms, a credit limit, a price that applies from five hundred units, a minimum order quantity: no rule in the base set holds any of them, and there is no tool that reads them out of your store either. The partial mitigation is narrow and worth naming exactly — the policy tool forbids answering delivery time, the return window or a shipping threshold from memory and hands back the policy page itself. That is shipping and returns. It is not commercial terms, and writing it up as though it were would be the leak this page exists to avoid.

So a terms question is a handover

The handover tool is for complaints, damaged goods, a return dispute, an angry buyer, a medical question, and anything that cannot be answered — and today a question about terms, a credit account or a tiered price is squarely the last of those. An e-mail address is required so your team can reply: for a signed-in buyer it is taken automatically, and for a guest it is asked for first, along with the order number when an order is involved.

A rule written for payment terms, a minimum order quantity or a trade price is a pack’s job, and a pack is what this sector has yet to get — what the base set carries.

What this page is a picture of

Refik card for Industry · B2B and wholesale: 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.

From the schema

Four things a pack for this trade would add.

A pack is a file of named fields, and the schema says which of them a pack has to carry. These four are the ones this trade would fill, in the order of what they unlock.

  • A dictionary from the buyer’s code to yours

    One field maps the customer’s word onto the catalogue’s word, and it exists for typos and other languages. In this trade it is the field that would carry a superseded part number, a supplier’s own name for the same item, and the long alphanumeric a buyer copies out of their last order with one character wrong. Under the neutral pack that dictionary is an empty object, so a code matches only when your own titles, tags or barcodes already spell it.

  • Product roles, and an ordered set

    A role dictionary maps your products onto the parts of a routine, and it is the precondition for the one tool that writes to the table a shopper sees. With no roles the chain is empty, that tool is kept out of the list the model is handed, and the pairing tool switches to a description that promises pairing alone instead of pointing at a tool the model cannot see. Here the same field is what a standing supply set would be built from — the consumable, the part it fits and the thing that wears out next to it.

  • Reorder intervals

    A role maps to a lifetime in days, and a reminder candidate is only produced between twenty-one and two hundred and forty days after the order. Of the twelve sectors this is the one where that switch is easiest to defend: a consumable bought on a cycle is arithmetic rather than a guess, and a buyer who reorders the same line every quarter is the ordinary case. Under the neutral pack the candidate list comes back empty for two independent reasons — the switch is shut, and the role-to-days table is where a pack would put the days.

  • Claim rules for commercial terms

    A pack carries its own claim rules and they sit in front of the base ones, so a pack for this trade is where terms, a minimum order quantity and a tiered price would be named. The base sixteen stay merged in underneath, and a pack rule is still the first one reported when both would fire. A rule can also be scoped to a market, though the only market a rule is allowed to name today is Turkey — any other value is refused when the pack loads. A statement that is routine in one country and a promise in another is told apart that far, and no further.

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.

A pack arrives for this trade the day a catalogue in it is measured, and until then the neutral file is the honest one — the neutral pack, counted. The industries page lists the packs that exist and the three gates a store has to clear for one of them; this sector sits among the stores those gates leave unplaced — how a pack gets chosen.