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.

The table shows 25 packages at a time, with Prev and Next underneath. The search box above it searches your whole catalog by country code or package, not only the page you are looking at.

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.

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.

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 four ways, so you can see the shape of your pricing without reading the table.

• 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.

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 the page you are looking at, while the count beside it covers your whole catalog. On a catalog longer than 25 packages, Review can show fewer rows than the number that prompted it, or none at all. Trust the count, and use search to find the rest.

The provider’s suggested price

Provider RRP is what your provider suggests you sell the package for. Nothing is applied from it: your markup is calculated over cost, and the column exists so you can see where you sit against the provider’s own retail idea.

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.