SellstampStorefront
A site you actually design,
on a domain you actually own.
Multi-page stores with a real section system, themes that differ in structure rather than in colour, and an editor that shows you the phone and edits the phone at the same time. A store with no products at all — a landing page, a local business site — is a valid store here.
yourstore.com
Sections, not a single long page. Nothing is live until you publish.
What you are actually editing
A schema-driven editor, not a page of text fields. Every control exists because a token or a field behind it changes the rendered store — a token with no consumer fails a test and cannot ship.
- Pages, not one long page
- A store is a set of pages with their own slugs, titles, ordering and SEO overrides, one of which is home. Your navigation is built from them, and so is the store's sitemap.
- Sections and blocks
- Every page is a list of typed sections, each with typed fields the editor draws a real control for. A section type is a shape rather than a topic — one feature grid does system requirements, what's included, technical specs and how-it-works, because all four are “a title and a detail, repeated”.
- The product page is a page
- Your listing template is a page too, with the eleven parts of a listing — media, title, price, proof, countdown, stock, terms, description, reviews, the buy form, delivery — as blocks you arrange. Four panel arrangements ship, and they are different skeletons rather than the same one recoloured.
- Per-device, honestly
- Padding and column counts hold separate phone, tablet and desktop values, and the editor's device tabs change both the preview width and which tier you are editing. It works because the storefront asks its container how wide it is, not the window — so a preview pane inside the dashboard answers correctly.
- Page shape
- A store's shell is a top bar or a left or right rail — a different document, not a restyled one — and each section claims its own measure: the column, wider than it, or edge to edge.
Design, as a closed set of decisions
Thirty-five controls across seven panels — typography with two independent faces, layout and density, colour roles, surfaces, buttons, the header, motion. Every one is a choice from a named list rather than a free number, which is what lets the editor draw a labelled picker instead of a box you can put anything in.
Seventeen themes
Each sets all four layers: a design document, its own home composition, its own product template and its own sections. They are compared against each other with every colour stripped out, so a theme that is another theme repainted cannot be added. Seven starter sites sit beside them in the picker.
Your logo, where it belongs
Brand as name, logo or both, with a height you set. Plus a header CTA, which is a property of a menu item rather than a second field, so one link is stored once.
Leave the theme alone
A token you have not set emits no CSS at all rather than a neutral value, so an unset heading weight falls back to each heading's own styling instead of flattening your hierarchy.
Or bring your own markup
You asked for Shopify's, Sellix's or Tebex's freedom. None of those runs arbitrary theme JavaScript either — so: HTML and CSS yes, through an allow-list; JavaScript no, in any form.
- A custom code section
- An ordinary section: it moves, duplicates, and goes on any page. Not a special mode you enter and cannot leave.
- Your CSS is scoped to it
- Wrapped so it applies to that section and nothing else. Unscoped “custom CSS” is how a stylesheet hides a price or restyles a checkout button.
- Upload a folder
- Point the picker at a folder of HTML and it becomes pages in your store — each one an editable section wrapped by your header and footer, replacing by slug rather than making about-2. It is not a file host. Images in the folder are skipped, visibly, rather than half-imported.
- It tells you what it removed
- Scripts, event handlers, frames and forms are stripped, and the import reports which, in a sentence saying why. “It just works” has to name the parts that did not.
- Export round-trips
- The export writes the same document the import reads — your published store, as a file you keep.
- And a marketplace
- Publish that same package as a listing other merchants can browse and install, one per shop. Installing writes to your draft, so trying a stranger's theme is reversible by Discard.
Nothing you do is a one-way door
- Draft and publish
- Everything you change lands on a draft. Your live store does not move until you publish, and Discard throws the draft away.
- Undo on the page you are looking at
- ⌘Z and ⇧⌘Z, twenty deep, scoped to the open page and cleared when you switch — an undo stack that could rewrite a page not on screen is worse than none.
- A version per publish
- Publishing writes the whole store to a version row inside the same transaction, so a version can never describe a state your store was not in. Thirty are kept, and restoring one restores it onto the draft.
- A half-applied restore is impossible
- A restored section list is validated whole and rejected whole. There is no state you never saw.
Your address, your languages
A store starts on a subdomain and moves to your own domain when you verify it. Storefronts speak Bosnian, Croatian, Serbian and English out of the box, and any other language you are willing to translate yourself.
Custom domains
Verified by a DNS record, after which the routing map your operator's proxy reads includes it. Sellstamp does not issue certificates and does not claim to — the proxy that terminates TLS decides that.
Import a language
Upload your own translations and the store serves them, alongside the four built in. The locale a customer gets is part of the URL, and the store's hreflang set follows it.
SEO you control
Per-store and per-listing title and description overrides, a sitemap and a robots.txt per store, and a switch that keeps your store out of search entirely if you want it out.
And what you sell on it
Five fulfilment types, and the commerce around them, all from one catalogue.
- Five kinds of product
- A file download, a serial key from a pool you imported, a licence key generated at purchase, a subscription, or a physical good that waits in awaiting-shipment until a human says they posted it.
- Bundles and options
- Variants with their own prices, quantity tiers, and bundles priced against the products they contain — membership is always written as a whole set, because a bundle price only means anything against its contents.
- A basket
- A cart page whose lines live in the customer's own browser and are re-priced against your live catalogue on every view, so an unpublished product reads as unavailable before an email address is typed.
- Gifts and store credit
- A purchase can name a recipient who is not the payer, and a credit you issue is spendable at your shop — one shop's liability, never a platform balance.
- Reviews, affiliates, support
- Verified-purchase reviews, an affiliate programme with its own referral links, and a support inbox, all on the same store.
Limits worth knowing before you build on it
What this does not do
- No JavaScript in a theme, uploaded or typed, in any form. That is the allow-list's whole point and it will not be widened.
- No storefront search. There is no control for one because there is nothing behind it.
- No TLS certificate issuance. A verified domain is a signal your operator's proxy acts on; nothing here speaks ACME.
- One theme per store and one marketplace listing per store. An agency selling five themes it does not run is a different model and is not built.
Open a store and try it.
Everything on this page is in the product today. Connect a provider in test mode and put a real order through it before you decide.