Checkout page: the fields, signals and steps that decide the sale
A checkout page is the most expensive page you own — everyone who reaches it already wanted to buy. Here is what to keep, what to cut, and where the drop-offs actually happen.
A product catalog is a navigation problem before it is a design problem. Get the categories, the attributes and the naming right and everything downstream — search, filters, feeds — starts working.
A product catalog is usually treated as a list of things to photograph. It is really a structure: how items are grouped, what attributes they carry, and what each one is called. Get that wrong and no amount of design fixes it — search returns nothing useful, filters do not narrow, and the same product appears under three names in three places.
The work is unglamorous and mostly happens in a spreadsheet before anything is published.
The test of a category tree: can a stranger place ten of your products into it without asking you a question? If not, the tree is describing your business's internal logic rather than how customers look for things.
Search and filters are built on the fields you filled in, not on the pictures. A catalogue where size lives in the description cannot filter by size, and no search box will rescue it. This is the single most common reason small shops feel unbrowsable at a few hundred items.
Keep attribute values controlled. "Blue", "blue", "navy blue" and "Blue (dark)" are four filter entries for one colour, and cleaning them up later means touching every product. Decide the allowed values once and put them in the sheet.
In Ettex Sites, store templates and 70+ sections cover the storefront itself, a live canvas edits it visually, themes control fonts, colours and spacing in one place, forms feed a built-in leads inbox, custom domains connect with certificates issued automatically, and SEO fields with an auto-generated sitemap are part of the builder rather than an add-on. Built-in analytics show visits, referrers and page stats, so you can see which category pages people actually reach. The builder works offline and publishes when you are ready.
Enough that no category holds more than about thirty items and none holds two. For most small shops that is five to twelve top-level categories, one level deep.
A product belongs to exactly one category — that is its place in the structure. Tags are cross-cutting labels like "sale" or "waterproof" and a product can carry many.
No. Group them under one parent so stock, reviews and search relevance stay together, and let the customer pick size or colour on the product page.
Long enough to answer what it is, what it fits or suits, and what is in the box. Two short paragraphs beats a page of copy nobody reads.
Everything, as CSV, keyed by SKU. Marketplaces, ad platforms and accounting all want a feed, and they all match on the stable ID.
A good product catalog is boring in the best way: predictable categories, controlled attributes, one ID per product that never changes. Do that and search, filters and feeds come almost for free.
A checkout page is the most expensive page you own — everyone who reaches it already wanted to buy. Here is what to keep, what to cut, and where the drop-offs actually happen.
Knowledge base software is easy to buy and hard to fill. The tool choice takes an afternoon; deciding what belongs in it, and who keeps it true, is the part that decides whether anyone uses it.
A CRM for startups solves a different problem than a CRM for sales teams. Early on you are learning who the customer is — and the tool should record that, not force a pipeline you have not earned yet.