Feature · Sell
Launch a branded store in minutes. Run all of them from one list.
A Brikl store is a branded on-demand storefront with its own address, its own catalogs and its own sign-in — live without developers. The part that matters once you have twenty of them is the list: status, URL, products, orders, revenue, customer and owner, on every store, on one screen.
Every storefront, and how each one is doing
One store is easy to keep in your head. Thirty is not. Every column here exists because it answers a question you would otherwise open the store to ask.
Status
Draft or live. A store being built and a store taking orders look different from across the room, which matters when you are running dozens.
URL
The real web address, as a link you can open and a button that copies it. The address a client asks for is on the row, not two screens in.
Products
How many products the storefront is actually selling — the fastest way to spot a store that was created and never stocked.
Orders (30d)
Orders over the last thirty days, so a program that has gone quiet is visible without opening a report.
Revenue (30d)
The same window in money. Two stores with similar order counts and very different revenue is a conversation worth having.
Customer
The account the store belongs to — or a dash, which is how an internal store identifies itself.
Owner
The person on your team responsible for it. In a 100-rep network this is the difference between a list and a directory.
Modified
Relative and exact: “Today” with the date beneath it, because both questions get asked.
Scope it to one account
A scope selector sits above the list. Narrow to the customers you are working on and the whole screen — stores, counts, revenue — is about them.
Search, filter, sort, page
The usual controls sit above the table, and the count is always stated in full — which page of how many, and how many stores in total.
Adding one takes a name. A web address is reserved from it and the store is created as a draft — see Create from anywhere.
The record
Open a store without losing the list
Click a store and its record opens beside the list rather than replacing it. The row stays highlighted, the table stays readable, and a pager at the top of the panel steps through every store in the list without going back.
Reviewing a portfolio is one arrow, pressed repeatedly — not a list, a detail page and a back button, thirty times over.
Everything on the record is about one store: what it sells, where it lives, who can sign in, who owns it, and what has happened to it.
One button into the storefront itself
The record answers questions about the store. Changing how it looks is one press away.
Edit this store is the first thing on the Overview tab and opens the store editor — theme, pages and navigation, edited on the storefront itself rather than in a theme file with a preview beside it.
Under it sit the two things that decide whether anyone can shop: the status, and the opening mode.
Always open, or a window
A pop-up store goes live automatically at its open date and closes at its close date. Outside the window shoppers see a coming-soon or closed page — not a store with nothing in it. It is the same store either way, so a seasonal program is a setting rather than a rebuild each year.
Pop-up stores →Eight tabs, one storefront
Everything a live store needs that isn’t design work — what it sells, where it’s served, who gets in, who owns it, and what has happened to it.
Overview
Identity, status, and when it's open.
The name, an internal description never shown to customers, and the status. Below them, the opening mode: always open, or a pop-up window with an open and a close date — outside which shoppers see a coming-soon or closed page rather than a broken store. And above all of it, one button into the store editor.
Catalogs
What the storefront sells.
Link several catalogs at once, unlink one from its row, or open a catalog's record with the arrow. Each linked catalog shows whether it is live and carries its own reference. Changes hit the live storefront straight away — there is no separate publish step to forget.
Domain
Where the storefront is served.
A free Brikl subdomain, a domain you already own, or one bought through Brikl. The connected address shows its SSL state, and HTTPS is issued automatically — nothing to upload and nothing to renew.
Sign-in
How shoppers get in.
Switch on the methods this storefront should offer: a passwordless email link, social sign-in, or enterprise SSO over SAML. The list is your organization's own identity providers, read live, so adding one makes it available here.
Integration
What the store is wired to.
Where the storefront connects outward — including running the shop front on a site you already have while the products, pricing and orders stay in Brikl.
People
Who it's for, and who owns it.
The customer the store is assigned to — or Unassigned, which marks it as an internal store — and the owner on your team, with their role and contact. Both are labelled Customer or Team member, so an external contact is never mistaken for an internal one.
Settings
Taking it down, and bringing it back.
Archive the store: the storefront goes down and the row leaves the list, but its web address stays reserved so the same URL is there when it comes back. Nothing is deleted.
Activity
What changed, and who changed it.
A timeline grouped into Today and Earlier — details edited, status changed, store created — each entry carrying the person and the time.
A store doesn’t own its products
It links to catalogs. Link several at once, unlink one from its row, or open a catalog’s record with the arrow. Changes hit the live storefront straight away.
That separation is why running many stores is possible at all. Price a range once and every storefront that links to it sells the same products at the same numbers. Change the range and every store changes with it — instead of twenty storefronts quietly drifting apart.
Each linked catalog shows whether it is live yet, so a store that looks finished but is publishing a draft range says so on the tab.
Domain
Three ways to serve a storefront
A free Brikl subdomain to start, the client’s own domain when the program is real, or one bought in the panel. HTTPS is automatic in all three — nothing to upload, nothing to renew.
A Brikl subdomain
Free, instant, and SSL is handled. It follows the store's name, so renaming the store moves the address with it.
A domain you already own
Point it at Brikl with a CNAME first, then connect it — the record is checked at that moment, so a domain that isn't pointed yet is rejected with the exact target to add rather than failing silently later.
A domain bought through Brikl
Buy it in the panel and DNS and SSL are handled for you — for the client who wants their own address and has no interest in a registrar.
Good to know
- A domain serves one store at a time — connecting it elsewhere means releasing it from the store that holds it.
- Point the domain at Brikl with a CNAME before connecting it; the record is checked at that moment, and a domain that isn't pointed yet is rejected with the exact target to add.
- Your Brikl address follows the store's name, so renaming the store moves it.
- Certificates issue automatically once a domain is connected.
- Paste just the domain — an https:// prefix or a path is stripped for you.
Sign-in
Who gets in, decided per store
A public fan shop and a locked internal uniform store are the same product with different switches. Each method is a toggle on the storefront that needs it, and the list reads your organization’s own identity providers live.
Passwordless email link
A shopper enters their address and gets a link. Turn it off and they sign in with a password instead — the choice is per store, not per platform.
Social sign-in
Offer the accounts your shoppers already have. Each provider is a switch, so a consumer-facing fan shop and an internal uniform store don't have to offer the same set.
Enterprise SSO over SAML
Connect Okta, Microsoft Entra ID, OneLogin or any SAML 2.0 provider, and members of the organization sign in with their work account — which is usually what a corporate client's IT department wants to hear before a store goes live.
How a store gets built
By hand in minutes, or assembled for you in about ten seconds. Either way you end up with the same record, and the same list.
Assembled in ten seconds
Turbo Store takes three picks — industry, quality tier, logo — and builds the catalog, the pricing, the artwork and the storefront.
Turbo Store →2Designed by clicking on it
The store editor changes theme, pages and navigation on the storefront itself. No theme files and no separate preview.
Store Editor →3What the buyer sees
The storefront itself: a product page where they pick a color, place their decorations and mix sizes, with the price building as they go.
The storefront →Frequently asked questions
What is a Brikl store?
How long does it take to launch a store?
Can I run many stores at once?
Can I use my client's own domain?
How do shoppers sign in?
Can a store open and close on a schedule?
Do changes to a catalog reach the live store?
What happens when I archive a store?
Can I run the storefront on a site I already have?
Launch your first store today
No credit card, no subscription. 3.5% when you make a sale.