What you sell, and for how much

What the price list shows

Catalog & pricing is one row per package you can source, with the cost you pay beside the price you charge. Packages arrive here when a provider’s catalog is imported; until then the screen reads "No packages to price yet" and points you at Connections.

Under the table, Rows sets how many packages a page holds — 25, 50, 100 or 200 — beside the range you are looking at and numbered pages to jump between. Every column with a figure in it sorts: click Cost, Provider RRP, Your price, Margin or Sold 30d to order the whole filtered catalog by it, click again to reverse it.

The validity in a package row is a number of days, and those days start when the eSIM first connects to a network — not when the customer pays. A 7-day package bought a month before a trip is still a full 7 days on landing. Price it as 7 days of travel.

Finding the packages you mean

A shop sourcing four thousand packages does not read the list, it asks it questions. Every control above the table narrows the whole catalog, not the page, and each one writes itself into the address bar — so a filtered price list is a link you can bookmark, send to somebody, or come back to with the back button.

• The search box takes a country name in your own language, a coverage code, or part of a package title. Type "Japan" and it finds JP; type "Kore" in Turkish and it offers you Güney Kore.
• Destination is a searchable list of every destination you can source, named in your language, with the number of packages behind each. Tick as many as you like.
• Coverage narrows to countries, regions or global tiers.
• Price narrows by what the price is doing: follow rule, overridden, set by hand, hidden, below cost, no margin, or unpriceable.
• The last two selects appear only when they have something to choose between: a provider filter when more than one connection carries your catalog, and a top-up filter when your catalog has top-ups in it.

Everything you narrowed stays visible as a chip under the controls, and Clear filters removes the lot. When a filter leaves nothing, the screen says so in those words — "No package matches those filters" — rather than showing you an empty catalog.

Country names are matched in the language you are reading the panel in. A colleague using the panel in English will find the same package by typing "Greece" where you typed "Yunanistan"; the link you send them carries the code, so it works for both of you.

Prices are public the moment you save

There is no draft, no staging copy and no publish step for prices. The header of the screen says so: "Price changes go live immediately." The moment a price saves, that is what the next customer pays.

This covers every control on the screen, not just the price field. A typed price, the Visible toggle and Apply to all each reach your live store as soon as they save.

The store markup

The Default markup rule card holds one number: a percentage added on top of provider cost. It governs every package without a price of its own — which, straight after an import, is all of them.

Every margin figure on this screen is sale price minus provider cost. Your payment provider’s fee is charged inside your own gateway account and never reaches Esimbit, so it is in none of these numbers — set your markup knowing your real margin is a little lower than the column says.

Below the field the panel does the sum on a real cost taken from your own catalog, in the form "A $4.20 cost becomes $5.88.", and recalculates it as you type. Use it to check the rule against a package you know before you commit to it.

Typing a new percentage changes nothing on its own. It takes effect when you press Apply to all.

Apply to all

Apply to all puts the percentage in the field into force across the store. Two things survive it, and the confirmation names them: "Fixed prices and hidden packages were kept." A price you typed into the table stays as you typed it, and a package you hid stays hidden.

Everything else moves onto the new percentage, and its price changes on your storefront at once. There is no confirmation dialog before it runs and no way to put the old prices back except by typing them.

The catalog step in setup has a button labelled "Save and continue" that runs this exact operation. Going back through setup months later to adjust your markup is not a gentler act than pressing Apply to all — it is the same press. If you only want to change one package, do it in the table instead.

Repricing many packages at once

Every row carries a tick box, and the one in the header takes the page. Once anything is ticked, a bar appears along the bottom with the number selected and what can be done to it. When your filters match more packages than fit on the page, the bar offers to select all of them — "Select all 700 matching" — so a decision about a destination, or about every below-cost package, is one press rather than twenty-eight pages of clicking.

Nothing runs on the first press. Each action asks once, naming the number it is about to change, and only then does it run. When some packages could not take the action, the confirmation afterwards says how many and why — "Repriced 640 packages. Left alone, the suggestion is under cost: 60." A count of nothing is reported as nothing changed, not as a success.

There is no undo, and the storefront changes as soon as the bar reports back. Read the number in the question before you press Apply: with all matching selected it is the size of your filter, not the size of the page.

Setting one package’s price by hand

Click the price in the Your price column and it becomes a text field, filled with the current price in whole currency: type 14.90, not 1490. Enter saves it. Esc closes the field and leaves the price alone.

While you type, the hint under the field shows the margin that price would give you against the cost in the same row, so you can aim at a margin without doing the arithmetic yourself.

A price you type into the table is a fixed price, never a margin. It survives Apply to all, and it does not move when your provider’s cost moves. A cost rise eats a fixed price’s margin silently, and a large enough one pushes the package below cost and out of your store.

Putting a package back on the markup

A package with a price of its own is drawn with a dashed border, so you can see at a glance which rows have left the store rule. Beside that price is a ↺ button — hover it and it reads "Use the store markup again". Press it and the package’s own price is dropped; the panel confirms with "Back to the store markup".

That button is the only way to undo a hand-set price. Typing the old number back in leaves a fixed price in place — it will look right today and will not follow the store markup the next time you change it.

Never below provider cost

You cannot sell a package for less than it costs you, and it is refused twice. Type a price under the cost in the same row and the field turns red, the tick button disables, and the hint reads "Below provider cost — you would lose money on every sale." If a below-cost price gets past the field, the save is refused again on its way through, and that refusal is shown to you word for word.

The rule also applies after the fact. If your provider raises a cost above a price you set months ago, that package is pulled from your store until you fix it — the row turns red and the Impact preview counts it under "below cost". Raise the price above the new cost and it goes back on sale.

Nothing announces this. A package can leave sale quietly because a cost moved somewhere upstream, and the only place that says so is this screen. Check the below-cost count after every catalog import.

Hiding a package

The Visible toggle at the end of each row takes a package off sale and puts it back. A hidden package stays in this list, dimmed; it disappears from your storefront. Use it for packages you can source but would rather not sell.

A package hidden because it is below cost is a different case. That one is not your toggle — hover it and it explains itself as "Hidden because the price is below cost", and fixing the price is what brings the package back.

Un-hiding forgets the price. Hiding writes a setting on the package; un-hiding removes that setting altogether, so a package you priced by hand, then hid, then un-hid comes back on the store markup with the price you set gone. Set it again after you un-hide.

The Impact preview

The Impact preview card counts your whole catalog by what each price is doing, so you can see the shape of your pricing without reading the table. Every figure is also a filter: press one and the table below shows exactly the packages it counted.

• follow rule — priced by the store markup.
• overridden — carrying a price of their own.
• hidden — taken off sale by you.
• below cost — priced under what you pay, and off sale until fixed.
• no margin — the provider’s own suggested price does not clear its cost.
• unpriceable — no route to a provider, or quoted in a currency your store does not sell in. Shown only when there are any.

The below-cost figure turns amber when it is not zero, and an amber band appears under it: "Priced under provider cost: 3. They are hidden from your store until you fix them." Beside the band is a Review button that filters the table down to the offending rows, and a Show all that puts it back.

Review filters your whole catalog, not the page, so the rows it shows and the number beside it always agree. Press it again — or press Show all — to put the table back.

The provider’s suggested price

Provider RRP is what your provider suggests you sell the package for. Your markup is still calculated over cost and nothing is applied from the suggestion on its own — but when you want it, the small arrow beside the figure sells that package at it in one press, and Match provider RRP does the same to everything you have selected. Opening the price for editing offers it too, as a value to fill in, so you see the margin it implies before you save.

Where that suggestion does not clear the provider’s own cost, the row is tinted amber and the number carries a "no margin" tag, explained on hover: "The provider’s suggested price does not cover its own cost — selling at it would lose money." Suggested prices are written for the provider’s business, not yours.

Cost and Provider RRP are shown in the currency your provider bills you in. Your price is shown in your store’s currency. When the two differ, reading across the row compares two currencies — check the Margin column, which does the comparison properly.

Top-up packages

Some rows carry a top-up tag. A top-up is not a new eSIM: it loads more data onto one a customer already holds. It sits in the same list as everything else, takes the same store markup, and can be given a fixed price or hidden in exactly the same way.

You do not sell a top-up from the panel. The customer buys it themselves from their own order page, so the price you set here is the price they meet there, unannounced and without you in the conversation.

A top-up adds data and nothing else. It does not move the eSIM’s expiry date and it does not issue a new QR code. Do not price one as though it extends the plan.

Who can change a price

Moving a price is an Admin job. A Support member can open Catalog & pricing and read the whole list, because customers ask about prices — but the markup field, Apply to all and every price cell are disabled for them, with the reason on screen: "Support can read the price list but not change it. Ask an Admin to move a price."

Roles are set on the Team screen. Nothing on this screen changes them, and controls locked by a role are shown with their reason rather than hidden, so you can see what you would be able to do with a different one.