E-commerce storefront

Objects for the quiet hours

A small-catalogue homewares store built end to end: a filterable collection, product pages that answer the questions a buyer actually has, a moderated review system, a GST-inclusive cart, and an inventory console whose edits land on the storefront while you watch.

E-commerceStorefront + consoleAustralian retail
Vesper Home product screen

Sector

  • Homewares and interiors
  • Direct-to-consumer retail

Product surface

  • Storefront and admin console
  • 12 products, 4 collections

What we did

  • Product modelling
  • UX and UI design
  • Design system
  • Front-end engineering

Retail detail

  • GST-inclusive AUD pricing
  • Free-shipping threshold
The product

What is Vesper Home?

A store for a brand that sells twelve things rather than twelve thousand. That constraint changes the whole design: with a small catalogue, every product page has to do the work a category page does elsewhere, and the operator running it needs stock and reviews on one screen rather than a warehouse system.

A small catalogue is a different problem to a large one

A small catalogue is a different problem to a large one

Search matters less; the reasons to buy matter more. So the storefront leans on collection browsing, honest availability, and product pages carrying dimensions, materials, shipping and owner reviews - the things that stop someone leaving to look them up.

Filters people actually useCollection, price band, in-stock-only and a rating floor, combined live with five sort orders and a clear-all - and a written empty state for when a combination returns nothing.
Reviews with a moderation pathRatings break down by star, sort four ways and mark verified purchases. Submitted reviews queue for approval in the console rather than publishing straight to the page.
Stock that is true on both surfacesThe console and the storefront share state, so a stock edit shows as "Only 3 left" or "Out of stock" on the shop grid immediately, with an activity feed recording what changed.
The problem

Why do small-catalogue stores lose the sale?

Rarely on price. They lose it on unanswered questions - how big is it, what is it made of, when will it arrive, does the brass base feel cheap - and on stock that says one thing on the grid and another at checkout. Both are fixable in the build.

The product page stops at a photoReviews are decoration or absentStock is a spreadsheet somewhere else
The momentA templated storeHow Vesper Home does it
Browsing the rangeA grid and a search boxFour collections plus price, availability and rating filters with five sort orders
Judging a piecePhotos and a paragraphDimensions, materials, bulb and cord spec, shipping window and returns on the page
Reading reviewsA star averageA clickable rating histogram, verified-purchase badges and four sort orders
Low stockDiscovered at checkout"Only 3 left" and "Out of stock" on the grid, driven by the same value the console edits
Understanding the priceTax added at the endGST-inclusive AUD throughout, with the GST component itemised in the cart
Shipping costRevealed at checkoutA free-shipping threshold shown on the product page and unlocked visibly in the cart
Publishing a reviewStraight to the page, or neverA moderation queue in the console with publish and hide on every entry
The whole store

What did we build?

Eight screens covering both surfaces: the storefront a customer moves through, and the console the person running the shop lives in.

Catalogue

12 products, 4 collections

Linen and bedding, ceramics, lighting and objects, each product carrying a SKU, category, price, sale price, rating, review count and a live stock state.

  • SKU per product
  • Bestseller and new flags
  • Sale pricing

Browse and filter

4 filter groups

Collection, price band, availability and rating, combined live against five sort orders with a written empty state.

  • 5 sort orders
  • Clear all

Product page

Spec + shipping

Dimensions, materials, what is included, the shipping window, returns, and a related-products rail that stays inside the collection logic.

  • Details panel
  • Goes-well-with rail

Reviews

Rate, sort, moderate

A clickable rating histogram, verified-purchase badges, helpful counts, four sort orders, a submission form, and an approval queue in the console behind it.

  • Verified purchase
  • Moderation queue
  • Helpful votes

Cart and pricing

GST-inclusive AUD

Quantity controls, an itemised GST component, a free-shipping threshold shown as unlocked, and a persistent cart count in the header.

  • Tax itemised
  • Free-shipping unlock

Inventory console

2 tabs, 4 KPIs

Stock and reviews on one screen, with units on hand, low stock, out of stock and orders today above an editable product table.

  • Editable stock
  • Activity feed
How we worked

How did we build it?

Three passes took a homewares brand from a product list to a store with a working back office.

Model the catalogueBuild the buying pathGive it a back office
Transferable

What does a small-catalogue store need?

Six things that decide whether a twelve-product store converts. They are cheap while the store is being built and expensive to add once it is selling.

  1. Put the specification on the page. Dimensions, materials, what is in the box and the shipping window are the reasons a considered purchase completes. Behind a support email, they are the reason it does not.
  2. Make availability one value. Grid, product page and console must read the same number, or the first person to find the discrepancy is a customer at checkout.
  3. Give reviews structure and a gate. A distribution, sorting and verified-purchase marks make reviews persuasive; a moderation queue keeps them trustworthy.
  4. Show tax and shipping the way the market expects. An Australian store quotes GST-inclusive prices and itemises the component - getting this wrong reads as a foreign store, whatever the domain says.
  5. Design the empty and low states. No results, out of stock, only three left, an empty cart. These are seen constantly and are usually the least designed screens in a store.
  6. Build the console alongside the shop. Whoever runs the store edits stock and approves reviews daily. If that needs a developer, the store is not finished.
Visual language

Why does it look like this?

Homewares sold on restraint should not be sold in a loud interface. The palette is a deep indigo ink with a single brass accent for anything premium or promotional, on white and a cool off-white. Instrument Serif carries the headlines with the poise of a print catalogue; Albert Sans keeps prices, specifications and filters plain.

Aa

Primary typeface

Instrument Serif

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

a b c d e f g h i j k l m n o p q r s t u v w x y z

0 1 2 3 4 5 6 7 8 9 & ? ! £ $ €

Instrument Serif 400Page titles and the wordmark
Albert Sans 600Product names, prices and buttons
Albert Sans 500Filters, badges and table headers
Albert Sans 400Body copy, specifications and reviews
44pxObjects for the quiet hoursDisplay
30pxYour cartH1
20pxHalo Table LampH3
18px$249.00Price
15pxBody copy, specifications and review textBody
12pxIN STOCK - ONLY 3 LEFT - BESTSELLERBadge

The palette is authored in OKLCH in the store's own token file and converted to hex here. Only two colours ever carry meaning: indigo for the action you are meant to take, brass for anything premium or urgent - which is what lets a low-stock badge register instantly on a page of neutrals. Instrument Serif and Albert Sans are open-licence typefaces; the specimen above falls back to the nearest available face if they are not installed on your device.

Under the hood

What is it built with?

A dependency-free front end over a single product model, with the storefront and the console sharing one state layer and one token file.

FAQ

Building an e-commerce store

What retail founders ask us before committing to a custom build.

Ask us yours
How much does an e-commerce website cost to build?

It depends far more on the operational surface than on the shop. A storefront over a small catalogue is predictable work; the cost sits in inventory, review moderation, tax and shipping rules, and whatever integrations your fulfilment already uses. Shanti Infosoft scopes it on a short call and returns a fixed quote within 48 hours.

Should we use Shopify or build a custom store?

Use a platform when your requirements are ordinary and your differentiation is the product. Build custom when the buying experience itself is the differentiator, when you need an operational console shaped around how your team actually works, or when platform fees on your volume outrun the build cost.

Why do product reviews need moderation?

Because unmoderated reviews are the fastest way to lose trust in both directions - spam on the page, or genuine reviews silently rejected by a filter. A queue with publish and hide on every entry keeps the trust layer of the store owned by a person, and it takes minutes a day rather than a policy.

How do you handle GST on an Australian store?

Quote GST-inclusive prices everywhere and itemise the component in the cart. Australian shoppers expect the number on the product page to be the number they pay, and a store that adds tax at checkout reads as foreign. The same principle applies to the free-shipping threshold: show it before checkout, not at it.

What does an inventory console need on day one?

Stock you can edit in one place, low-stock and out-of-stock visible at a glance, a review queue, and a record of what changed. Everything else can wait. The test is whether the person running the shop can do a normal day's work without asking a developer for anything.

Planning a store of your own?

Tell us how your business actually works and we will tell you honestly what it takes to build. See more of our work or what we do.

Book a 15-minute call