Web Design

GeekVape Store

An ecommerce experience for a hardware brand with a deep product catalogue, designed in Figma as a reusable system and built to fit how Shopify actually works.

Role
UX/UI DesignerDesign SystemsUser Research
Client
GeekVape
Deliverables
  • UX Research
  • Information Architecture
  • UI Design
  • Design System
  • Usability Testing
Tools
  • Figma
  • Shopify
The GeekVape storefront shown on a laptop, with the nicotine warning bar above the site navigation and a device on the homepage banner
Objective

Make a large hardware catalogue easy to shop. Series, devices, pods, tanks and coils all have to stay findable, and a shopper must be able to tell which parts fit the device they already own before they reach the cart.

The Challenge

Compatibility is the whole problem. Coils, cartridges and pods only work with certain devices, so the usual product grid quietly pushes people toward the wrong purchase. The structure had to carry that relationship, rather than leaving it buried in a specifications table.

Research

I reviewed how people move through the catalogue and where they stall, then tested the navigation and product pages with a small group of buyers: both first-time shoppers and returning owners restocking consumables. The two groups want different things from the same pages: one needs orientation, the other needs speed.

Designing in Figma

Every page was designed in Figma (home, collection, product, cart and checkout) across desktop and mobile. Rather than drawing one-off screens, I built them from a component library: product cards, variant pickers, compatibility callouts, filters, and the merchandising blocks that repeat down the home and collection pages.

Built for Shopify

The system was designed around how Shopify is actually assembled. Figma components map to theme sections and product templates, variants follow Shopify's own option model, and anything the platform owns (the checkout, cart behaviour, product metafields) was designed within those limits instead of around them. Merchandising stays editable in the admin, so the team can reorder a homepage or launch a collection without a designer.

Testing

The compatibility pattern was the thing worth testing. Pairing each device with the consumables it takes, and surfacing that on the product page rather than a separate chart, was what most reduced hesitation before adding to cart.

From research to a store the team can run

A system-first approach: understand the catalogue, give it a structure, design it once in Figma, then hand over something Shopify can carry.

  1. 01

    Research

    • Catalogue and competitor review
    • Sessions with new and returning buyers
    • Mapped where compatibility confusion starts
  2. 02

    Structure

    • Series-led product architecture
    • Filters built around real buying questions
    • Consumables tied back to their devices
  3. 03

    Design system

    • Figma library of components and tokens
    • Product, collection and cart patterns
    • Desktop and mobile from one set of rules
  4. 04

    Shopify handoff

    • Components mapped to theme sections
    • Variants following Shopify's option model
    • Merchandising left editable in the admin
Information Architecture

How the store is organised

  • GeekVape
    • Products
      • New Arrivals
      • Pod
      • Pod Mod
      • Box Mod
      • Tank & Coil
      • All Products
    • About Us
      • Our Brand
      • VPU Technology
    • Info Center
      • News & Events
      • Blog
    • Support
      • FAQ
      • Warranty
      • Contact Us
      • Downloads
      • Verify Product
    • Compliance
User Personas

Who I designed for

Placeholder photo for the Marco Ruiz persona
Starting out

Marco Ruiz

29 · Warehouse Supervisor, switching from cigarettes

Needs

A starter device he can buy with confidence, described in words he already understands rather than wattage and ohm ratings.

Goals

Leave with one kit that works out of the box, plus the refills it takes, and know roughly what it costs him each month.

Challenges

The catalogue assumes knowledge he does not have yet, and every product sounds equally advanced, so he stalls before choosing.

Placeholder photo for the Hannah Lowe persona
Restocking

Hannah Lowe

34 · Nurse, Aegis owner for two years

Needs

Certainty that the coils and pods she adds to the cart actually fit the device sitting in her bag.

Goals

Reorder consumables in under a minute, ideally straight from the product page of the device she already owns.

Challenges

Coil families look nearly identical, and a wrong order means a week without the thing she bought it for.

Placeholder photo for the Dejan Petrov persona
Enthusiast

Dejan Petrov

26 · Graphic Designer and vaping hobbyist

Needs

Full specifications in one place: output, airflow, battery, chipset, and how each series differs from the last.

Goals

Compare devices across the Aegis and Z ranges, then pick the one that suits the setup he is building.

Challenges

Specifications are scattered between tabs, images and marketing copy, so comparing two devices means opening several pages at once.

Placeholder photo for the Amina Farouk persona
Trade

Amina Farouk

41 · Owner of an independent vape shop

Needs

A clear view of the full range and what is in stock, so she can plan an order for her shelves rather than one device at a time.

Goals

Build a repeat order across several series quickly, and see new releases early enough to stock them on launch.

Challenges

A store designed for single purchases makes volume buying slow, and nothing tells her what is about to be discontinued.

Figma to Shopify

How the design reaches the storefront

Shopify builds pages out of sections, and a store is run by the people editing it long after launch. Designing to that shape, rather than drawing finished pages and hoping they survive the build, is what keeps the handoff short.

  1. 01

    Foundations

    Colour, type and spacing set up as Figma styles that mirror what the theme exposes as settings, so a token in the file has somewhere to live in Shopify. Desktop, tablet and mobile frames on a 12 column grid with a fixed max content width.

  2. 02

    Components

    Product cards, variant pickers, filters, quantity steppers and the cart drawer built once as components, with variants covering the states the catalogue will actually produce: sold out, low stock, on sale, long titles, missing images.

  3. 03

    Sections

    Pages assembled from blocks that match theme sections rather than one flat frame per page. Each section is annotated with the settings a merchant should control, such as heading, layout, items per row and background.

  4. 04

    Handoff and QA

    Specs for breakpoints, image ratios and which content comes from product fields or metafields, then a review in the theme editor on a staging store, where real data finds what a static frame hides.

Standards in the Figma file

  • Frames at 1440, 1024 and 375, on a 12 column grid with a 1200 max content width
  • Colour and type styles named after theme settings, not after their hex values
  • Every repeating element is a component with variants for its real states
  • Real product names, prices and images, never lorem text or perfect crops
  • Image placeholders drawn at the ratios the theme crops to, usually 1:1 or 4:5
  • Page frames named for the Shopify template they become: home, collection, product, cart

What Shopify decides, not the design

  • Sections and blocks are the unit of layout, so anything reusable is designed as one
  • Variant pickers follow Shopify's own option model, including combinations that cannot be bought
  • Specification tables come from metafields, so the layout has to tolerate uneven content
  • Checkout is Shopify's, and is themed rather than redesigned unless the store is on Plus
  • Apps inject their own markup, so leave room for review widgets and subscription pickers
  • Merchandising stays editable in the admin, which means no design that only works in one order
User Flow

End-to-end shopping flow

From the age gate through browsing, the compatibility check, checkout and the restock that brings people back: every branch and dead end the store has to handle. Click any node for its build notes.

States the store has to survive

A catalogue this size produces all of these every day. Each one needs a designed screen, not a generic error.

ConditionWhat the user seesEffect on flow
Age verification failsGate stays up with a retry and a plain explanation of why it is requiredHard stop
Coil chosen does not fit the deviceCompatibility callout on the product page, with the part that does fit offered in its placeCaught before the cart
Variant combination unavailableOption shown as unavailable rather than hidden, so the picker never changes silentlyBlocks add to cart
Out of stock in one variantBack in stock alert for that exact variant, with other pack sizes listed underneathHold
Shipping restricted in the regionExplained at the cart with the affected items named, before any payment detailsHard stop
Payment declinedReason in plain words, alternate methods first, cart kept intactRetry loop
Product discontinuedPage stays live and points to the device or coil that replaced itRedirect
Specification fields missingTable renders only the fields that exist, so a thin product does not look brokenDegrades quietly
Final Design

A storefront that holds a deep hardware catalogue without making anyone guess which part fits the device they own.