Every screen in the admin

49 screens from one seeded store — 64 products, 260 orders across 150 days, five locations — captured at 1440×900 in both colour schemes. Each caption is the screen’s own heading and first sentence, read from the panel as it was photographed.

Home 1 screen

Home: Home — Welcome back, admin@example.com. — **Home** Welcome back, admin@example.com. Open the file ↗

Orders 5 screens

Orders: Orders — **Orders** Open the file ↗

An order: Orders — **An order** Open the file ↗

Abandoned carts: Carts — **Abandoned carts** Open the file ↗

Invoices: Invoices — **Invoices** Open the file ↗

Payouts: Orders — What each payment method charged over the window, what went back out through it, and what it is still owed. A sale here means the same as on Reports: an order whose stock has left the shelf. — **Payouts** What each payment method charged over the window, what went back out through it, and what it is still owed. A sale here means the same as on Reports: an order whose stock has left the shelf. Open the file ↗

Products 8 screens

Products: Products — **Products** Open the file ↗

A product: Products — **A product** Open the file ↗

Collections: Collections — **Collections** Open the file ↗

Categories: Categories — **Categories** Open the file ↗

Inventory: Inventory — Available is on hand minus what is reserved for orders in flight. Stock moves as a delta or an absolute count, never as a blind overwrite — so a sale that lands mid-edit cannot be lost. Without a location chosen, the thr — **Inventory** Available is on hand minus what is reserved for orders in flight. Stock moves as a delta or an absolute count, never as a blind overwrite — so a sale that lands mid-edit cannot be lost. Without a location chosen, the thr Open the file ↗

Price lists: Price lists — **Price lists** Open the file ↗

Reviews: Reviews — **Reviews** Open the file ↗

Vendors: Vendors — **Vendors** Open the file ↗

Customers 6 screens

Customers: Customers — A cancelled order is still an order but not a sale, and money only counts once it has arrived — so the two figures rarely match. — **Customers** A cancelled order is still an order but not a sale, and money only counts once it has arrived — so the two figures rarely match. Open the file ↗

Groups: Customers — A shopper joins a group on their customer record; the price lists that aim at it are under Products. — **Groups** A shopper joins a group on their customer record; the price lists that aim at it are under Products. Open the file ↗

Accounts: Accounts — **Accounts** Open the file ↗

Contact inbox: Contact — **Contact inbox** Open the file ↗

Wishlists: Customers — **Wishlists** Open the file ↗

Discounts 1 screen

Discounts: Discounts — **Discounts** Open the file ↗

Notifications 3 screens

Notifications: Notification History — **Notifications** Open the file ↗

Setup Email: Notifications — Who carries the store's emails. Activate a provider and type its key; until one is active every message is written to the log and nobody receives it. — **Setup Email** Who carries the store's emails. Activate a provider and type its key; until one is active every message is written to the log and nobody receives it. Open the file ↗

Setup SMS: Notifications — Who carries the store's texts. Activate a provider and type its key; until one is active every message is written to the log and nobody receives it. — **Setup SMS** Who carries the store's texts. Activate a provider and type its key; until one is active every message is written to the log and nobody receives it. Open the file ↗

Content 6 screens

Files: Media — Drag and drop images, videos, 3D models, and files — **Files** Drag and drop images, videos, 3D models, and files Open the file ↗

Pages: Pages — **Pages** Open the file ↗

Menus: Menus — Pick a menu on the left, or create one. A storefront reads a menu from /x/navigation/menus/<handle>. — **Menus** Pick a menu on the left, or create one. A storefront reads a menu from /x/navigation/menus/<handle>. Open the file ↗

Product feeds: Content — Both files are generated when they are fetched, from the catalogue as it stands at that moment. There is no build to schedule and nothing to regenerate. — **Product feeds** Both files are generated when they are fetched, from the catalogue as it stands at that moment. There is no build to schedule and nothing to regenerate. Open the file ↗

Sitemap: Content — Read by fetching the files themselves, the way a crawler would. Each is generated at the moment it is asked for, so what is counted here is exactly what a crawler would have got a second ago. — **Sitemap** Read by fetching the files themselves, the way a crawler would. Each is generated at the moment it is asked for, so what is counted here is exactly what a crawler would have got a second ago. Open the file ↗

FAQ: Content — The questions this shop is asked often, grouped into the sections you name and in the order you put them. A draft is invisible to shoppers. The storefront reads the published ones from /x/faq. — **FAQ** The questions this shop is asked often, grouped into the sections you name and in the order you put them. A draft is invisible to shoppers. The storefront reads the published ones from /x/faq. Open the file ↗

Reports 1 screen

Reports: Reports — Sales — what the store sold, by period, with its best sellers — is on the dashboard. This is for the questions only this shop has, written as SQL once and run by whoever needs the answer. — **Reports** Sales — what the store sold, by period, with its best sellers — is on the dashboard. This is for the questions only this shop has, written as SQL once and run by whoever needs the answer. Open the file ↗

Jobs 1 screen

Jobs: Jobs — The full outbox, with every event's history, is under Settings › Event log. — **Jobs** The full outbox, with every event's history, is under Settings › Event log. Open the file ↗

Settings 17 screens

Store: Settings — **Store** Open the file ↗

Team: Settings — **Team** Open the file ↗

Your account: Settings — **Your account** Open the file ↗

Payment methods: Settings — How shoppers pay. A gateway that is active and set up is offered at checkout; an idle one is listed here and nowhere else. Cash on delivery is built in. — **Payment methods** How shoppers pay. A gateway that is active and set up is offered at checkout; an idle one is listed here and nowhere else. Cash on delivery is built in. Open the file ↗

Shipping and delivery: Settings — The most specific zone wins: a zone naming a state beats one naming only its country, which beats the zone that names nowhere in particular. — **Shipping and delivery** The most specific zone wins: a zone naming a state beats one naming only its country, which beats the zone that names nowhere in particular. Open the file ↗

Shipping providers: Shipping — Who carries the parcels. An aggregator that is active and set up is offered on the ship dialog; an idle one is listed here and nowhere else. Manual fulfilment is built in. — **Shipping providers** Who carries the parcels. An aggregator that is active and set up is offered on the ship dialog; an idle one is listed here and nowhere else. Manual fulfilment is built in. Open the file ↗

Taxes: Tax rates — **Taxes** Open the file ↗

Locations: Locations — **Locations** Open the file ↗

Channels: Channels — **Channels** Open the file ↗

Attribute dictionary: Settings — **Attribute dictionary** Open the file ↗

Diagnostics: Settings — Nothing has failed, but 3 checks of 15 are worth a look. — **Diagnostics** Nothing has failed, but 3 checks of 15 are worth a look. Open the file ↗

Event log: Settings — **Event log** Open the file ↗

API keys: Settings — A key is held to its role exactly as a person is, so give it the smallest one that does the job. Owner includes making more keys. — **API keys** A key is held to its role exactly as a person is, so give it the smallest one that does the job. Owner includes making more keys. Open the file ↗

Webhooks: Settings — Where this store POSTs the events an endpoint names. Each delivery is signed, and a failed one is retried on a backoff until it is delivered or given up on. — **Webhooks** Where this store POSTs the events an endpoint names. Each delivery is signed, and a failed one is retried on a backoff until it is delivered or given up on. Open the file ↗

Audit trail: Settings — **Audit trail** Open the file ↗

Export: Settings — **Export** Open the file ↗

Import: Settings — A dry run validates the whole file and rolls back, reporting what it would have done. Worth doing first, always. — **Import** A dry run validates the whole file and rolls back, reporting what it would have done. Worth doing first, always. Open the file ↗

FAQ

About these captures

Are these real screenshots?

Yes. Each is a Playwright capture of the admin at 1440×900, in both colour schemes, from a GoCommerce instance run from the repository and filled by its own seed script. Nothing is mocked up, and the captions are the screens’ own headings and first sentences, read at capture time.

Why does the data look invented?

Because it is: the seed script generates a fixed catalogue, customers and orders from a fixed random seed so the same store can be photographed twice. No real customer appears on any screen.

Is every screen here?

Every screen the panel’s own navigation lists when every module is installed — 49 in this capture — plus one order and one product opened from their lists. Drawers, dialogs and per-row editors are not photographed; the list screens show where they open from.

Can I click around a live one?

The home page links a live instance at admin.kitcommerce.store. What it lets you do depends on how that instance is configured on the day; this page is the complete, stable tour.

The same admin, on your server, in one command

It is compiled into the GoCommerce binary — no separate deployment, no second server.

Deploy in minutes Explore GoCommerce 44 modules