A real shop online, built for how Bangladesh buys.

Everything a shop actually needs to run, rather than everything that demos well.

• Products that behave like products

  Sizes, colours, and any other option you sell by, each with its own price, code and stock count. Group them into collections. Add photos. Nothing is a workaround.

• Stock the database defends

  When two customers reach for the last piece at the same moment, the database settles it — one sale succeeds and one is refused. It is not decided by your shop guessing, and it is not decided by whoever's connection was faster.

• Search that only ever sees your shop

  Your catalogue has its own search index, separate from every other shop on the platform. Saving a product sends it for indexing without you asking; our test for that path asserts it is findable in under two seconds.

• Staff, with keys that fit their job

  Three kinds of login — owner, admin and staff — so the person who updates prices is not the person who can remove your domain. Owners and admins must set up a second factor. There is a grace period when you start; after it, the only thing an un-enrolled account can still do is finish setting it up.

• Bulk work without retyping

  Load a catalogue from a spreadsheet instead of entering four hundred products by hand. The import runs in the background, and it is all or nothing — if row 312 is wrong, nothing is written and you fix it and run it again.

• A record of who did what

  Consequential changes are written to a log that cannot be edited or deleted afterwards — not by your staff, not by us. That is enforced by the database's own permissions and by a trigger, not by a policy.

Checkout supports the ways your customers actually pay: bKash (বিকাশ), Nagad (নগদ), SSLCommerz for cards and bank channels at home, and Stripe for customers paying from abroad.

• Your customer's browser never names a price

  It can say which product, how many, and which discount code. It can never say what that costs. Prices, discounts, shipping and the total are recalculated on our server from your database every single time.

• A request that tries to set a price is refused

  Not quietly ignored — refused, with an error. Ignoring and honouring look identical from the outside, and only one of them tells you somebody tried.

• A payment can only be counted once

  Gateway callbacks are checked for a valid signature, matched against the amount and currency we expected, and rejected if that transaction has been seen before. A replayed callback does not become a second free order.

• Money is stored as whole units

  Never as a decimal that quietly loses a poisha. An order keeps a frozen copy of exactly what was bought at the price it was bought for — change a product tomorrow and yesterday's order does not change with it.

A shop that looks like everyone else's is a shop nobody remembers. Themes here are files you or your designer control, not a settings panel we decided the shape of.

• Upload a theme, keep the versions

  Every version you have ever published is kept, permanently. Publishing a new one does not throw the old one away. Drafts you never published are tidied up after the most recent twenty.

• Look before you publish

  Preview a theme on your real shop, with your real products, while your customers still see the current one.

• One click back

  A theme that broke your shop at nine on a Friday evening is undone by choosing the previous version. No re-upload, no support ticket.

• You choose the currency

  Your shop sets what it sells in — ৳ if that is what your customers pay in. Prices are the ones you typed; there is no exchange rate quietly converting anything behind your back, because there is no conversion at all.

• Your own web address

  Point your domain at your shop and prove it is yours with a DNS record we give you. Until then your shop lives at its own address on prime-bot.live. The HTTPS certificate for a custom domain is not being issued yet — that one is honestly unfinished.

• Other people's tools, at arm's length

  Apps connect over a standard authorisation flow with scopes you approve and signed notifications they must prove came from us — they do not get a folder of code on our servers, and an app found misbehaving can be cut off everywhere at once.

Every item below is enforced by something other than our good intentions, and every one has a test that fails the build the moment the protection is removed.

• Another shop cannot read yours

  Separation is enforced inside PostgreSQL itself — on nineteen tables today, as well as in our code — so a mistake in our application is not by itself enough to hand your catalogue to somebody else's shop. The tables not yet covered are listed and argued for in the codebase, with a name and a date against each.

• A missing shop is an error, not a guess

  If our code ever asks the database a question without knowing whose shop it is about, that request fails outright. It never quietly returns everybody's rows.

• Your history cannot be rewritten

  The audit log accepts new entries and nothing else. Update and delete are revoked from the account our application runs as, and a database trigger refuses them as well.

• Uploads are inspected, not trusted

  Every image goes through sixteen checks in a fixed order before it is stored, each with one named reason for refusing. A file is not safe because it ends in .jpg.

• Signing in is not a guessing game

  Repeated failures lock the attempt out, second-factor codes cannot be replayed, and a wrong email and a wrong password take the same time to refuse — so nobody can use our timing to find out who banks here.

• Backups are restored, not just taken

  A backup nobody has ever restored is a rumour. Ours are restored as a drill, and the drill reports what it could not bring back.

Prices are per month and are billed in US dollars, which is the currency the platform settles in — your own shop can price and sell in whatever currency you like. Basic, Standard and Advanced each start with a 14-day trial (১৪ দিন).

Products, staff logins and domains are the three limits the platform actually counts and enforces. Nothing else on this page is rationed by plan. When a trial runs out without a subscription behind it, your allowances fall back to the trial's — one login, no domain of your own — the moment the clock passes, not whenever some nightly job happens to notice.

This is a young platform and it would be easy to leave this section out. Here is what you would be signing up to, in full.

• No payment gateway has been run live yet. Every driver is written to the published documentation and tested against simulated gateways. None has processed a real taka. Nagad is the furthest behind: starting a session and issuing a refund through it currently refuse outright rather than run cryptography nobody has verified.
• Custom-domain certificates are not being issued yet. You can add your domain and prove it is yours today. The machinery that obtains the HTTPS certificate is built but has no certificate authority connected, so a domain waits rather than completing.
• Uploaded files are not covered by our database backups. Product photos and theme archives live in object storage and are protected by that storage's own versioning, not by our restore drill. A restore can leave a picture missing, and it tells you so.
• Your storefront is not in Bengali yet. The theme format has translation files, and there are Bengali drafts in the tree — including money written the way Bangladesh actually writes it, ১২,৩৪,৫৬৭ rather than 1,234,567. But the part that picks a language still only reads the English file, so those drafts do not load. This page is in two languages; your shop is not, yet.
• Shoppers cannot have accounts. Checkout is guest-only. Your customers can buy, but they cannot sign in, save an address, or look up what they ordered last month.
• There is no theme marketplace. You bring a theme or you have one built. There is no gallery to browse, no library of designs, and no mobile app for running your store.
• The theme editor in the admin is a placeholder. Uploading, versioning, previewing and rolling back all work. Editing a theme's settings from a nice screen does not exist yet.
• A product scheduled to go live does not reach search on its own. It appears on your shop at the time you set, but will not turn up in search results until something saves it again.
• You would be among the first. There are no merchants trading on this platform yet, so there is no uptime record, no support history and nobody to ask about us. We are not going to invent any of those.