The short answer

Choose one restrained visual system before styling pages. Assign every color a role, define a type scale, and use a short spacing scale instead of choosing gaps by eye. Then apply those rules to the homepage, categories, product cards, product pages, and cart. Check important text and interface color pairs with a contrast tool. In Setka, most of this is deciding rather than implementing: you supply the colors, font, and references, Setka applies them across the store, and you check the result against your rules.

Start with brand inputs, not swatches

A visual system can’t repair an unclear brand direction. Before you open a color picker, collect the few inputs that should constrain the design:

  • approved logo files and any size or clear-space rules;
  • existing colors, your font by name, the weights you use, and fallbacks;
  • representative product and lifestyle photography;
  • two or three annotated visual references;
  • practical adjectives with opposites, such as “warm, not rustic”;
  • the audience, price position, product character, and main shopping task.

Without formal brand guidelines, write a one-page working brief. “Quiet, tactile, and warm; photography leads; no glossy gradients” gives more direction than “premium and modern.” The brand-asset preparation guide explains how to organize source files and usage rights.

Separate brand recognition from interface function. A packaging color may be tiring as body text; a pale signature color may fail as a button label. Give each ingredient a job it can perform.

Give every color a functional role

Start with neutral page, surface, text, and border colors. Add one main action color and only the status colors the store needs. Names such as “forest” and “oat” are helpful in conversation; role names such as text-primary and action-primary prevent misuse in implementation.

The following palette is illustrative, not a recommendation for every brand. Its values show how to document roles and permitted combinations.

RoleExample tokenIllustrative valueIntended usePairing rule
Page backgroundcanvas#FAFAF7Main page fieldUse with primary or secondary text
Surfacesurface#FFFFFFCards, cart summary, panelsUse with primary text
Primary texttext-primary#222222Body, names, pricesUse on canvas or surface
Secondary texttext-secondary#59615DSupporting copy and metadataDo not use below the chosen body size without checking
Primary actionaction-primary#1F5B45Main buttons and active controlsUse with white text
Accentaccent-warm#D97745Small highlights and selected decorationDo not assume it works for small white text
Borderborder-subtle#CBD1CDDividers and nonessential card edgesNot the only cue for an input or state
Errorstatus-error#A12D2DError text and indicatorsPair with text, icon, or explicit label—not color alone

Color must not be the sole carrier of information. Pair an invalid field with an error message and an icon or other visible cue; pair a sale state with words and a price treatment. WCAG 2.2’s Use of Color criterion explains why color alone is insufficient for conveying information or prompting a response.

Check contrast as a recorded decision

For WCAG 2.2 Level AA, the Contrast (Minimum) criterion sets a contrast ratio of at least 4.5:1 for ordinary text and 3:1 for large-scale text, with stated exceptions. The Non-text Contrast criterion addresses visual information needed to identify interface components and states, generally at 3:1 against adjacent colors.

Keep a record like this beside the palette. The ratios below are illustrative calculations for the example values.

ForegroundBackgroundIntended useRatioThreshold usedRecord
#222222#FAFAF7Ordinary body text15.21:14.5:1Pass for this contrast check
#59615D#FAFAF7Ordinary supporting text6.10:14.5:1Pass for this contrast check
#FFFFFF#1F5B45Button label7.95:14.5:1Pass for this contrast check
#FFFFFF#D97745Small accent label3.15:14.5:1Fail for ordinary text; change the pair
#CBD1CD#FFFFFFEssential control boundary1.55:13:1Fail if the boundary is required to identify the control

Record the component, state, font size and weight, colors, ratio, checker, date, and decision. Test hover, focus, selected, disabled, error, sale, and image-overlay states too. Keyboard access, focus order, names, semantics, zoom, motion, and error handling need separate review.

Build a type hierarchy from content jobs

Choose type by reading conditions, not by how impressive a specimen looks. A useful body face stays clear at small sizes and includes the weights you will serve. One family with careful scale and weight is often enough.

Check the font’s character set and weights against your real product names and prices, including any accented letters your catalog uses, and look at its fallback too: line breaks, button widths, prices, and card heights can change. In Setka you name the font and Setka uses it, with no font file or license to supply.

Here is an illustrative type specimen and scale. Values are starting points, not universal requirements.

RoleExample styleSample contentUse
Display48px / 52px, 600Stoneware for daily ritualsOne short homepage statement
H140px / 44px, 600Mugs and cupsOne page title
H228px / 34px, 600Made for smaller kitchensMajor section heading
H320px / 26px, 600Stackable collectionCard-group or subsection heading
Body16px / 25px, 400Glazed by hand in small batches.Descriptions and policies
Small14px / 20px, 400Ships in 2–3 business daysSupporting information, not essential copy squeezed smaller
Label14px / 18px, 600Add to cartButtons and concise controls

Test the scale with real product names, prices, delivery lines, and unusually long content. Position, weight, spacing, and wording should reinforce size. On mobile, reduce display sizes while preserving the role order. The mobile e-commerce checklist includes text-resize and real-device checks.

Use a spacing scale, then allow deliberate exceptions

Spacing explains which elements belong together. Random gaps make a store feel inconsistent even when its colors and fonts match. Choose a base unit and a short scale, then attach common uses to it.

The following illustrative spacing sheet uses a 4px base:

TokenValueTypical use
space-14pxIcon-to-label adjustment
space-28pxClosely related metadata
space-312pxProduct name to price
space-416pxCard padding on compact layouts
space-624pxRelated content groups or mobile page gutter
space-832pxComponent separation
space-1248pxSection padding on smaller screens
space-1664pxMajor desktop section separation
space-2496pxRare, high-level desktop breathing room

Use optical judgment after applying the scale. A logo may need more apparent space than its box suggests. Exceptions should be named and rare, not silent one-off values. Test narrow screens before compressing gaps around controls.

If you don’t write the CSS yourself, the scale is still useful as a review standard. When gaps on a page look random against it, that is a concrete change to ask for.

Apply the system across the shopping path

A visual rule matters only when it survives real content and states.

Homepage. Use the display style sparingly, keep one dominant action treatment, and let spacing reveal the intended order. The homepage design guide helps determine that hierarchy before visual polish.

Category and product cards. Keep image ratios, name styles, price emphasis, gaps, and card padding consistent enough to compare products. Test the longest name and widest price. Accent treatments must not outrank the product itself. Use the detailed product-card design guide when defining the listing component.

Product page. Preserve the same text and action roles while allowing more room for product detail. Keep specifications and delivery notes clearly related to the purchase action.

Cart. Familiarity matters more than novelty. The primary checkout action should look like the same class of action used elsewhere. Product identity, quantity, price, subtotal, errors, and removal controls should remain distinct without depending on color alone. Test empty, long-name, error, and discount states that the store actually supports.

Review screenshots of all four surfaces side by side. Circle unexplained changes in button color, heading role, card padding, borders, or spacing. Make them consistent or document why the exception helps.

Where Setka takes over

On a theme, every rule above becomes your implementation work: theme settings, custom CSS, and checking that each template and each app’s widget follows them. In Setka, your colors, font, logo, references, tone, and catalog context become one store-wide creative and structural direction. Setka builds the homepage, category pages, product pages, navigation, and cart from that direction, so the same rules reach each of those pages without you applying them one by one. Your approved photos go into the store’s image slots.

You keep the decisions: the brand rules, the contrast standard, and the review. When a page breaks a rule, open it, describe what should change and where, edit exact wording directly when you know it, and preview the next version before publishing. Every version is saved, so you can go back to an earlier one. There is no theme code for you to maintain while you do this.

Write down the palette roles, the font, and two or three references, then build your store in Setka and review the homepage, a category, a product page, and the cart against your rules before you publish.