GenVoid.

E-Commerce & Online Store Development.

We design and build online stores on the platform that actually fits the catalogue, the margins, and the team behind the counter. WooCommerce, Shopify, or a custom headless setup — picked after a look at the products, not before. Every store ships with the boring essentials working: fast PDPs, a checkout that doesn't shed users, and analytics wired so you know what's earning its keep.

How we do it
WooCommerce logoWooCommerce
Shopify logoShopify
WordPress logoWordPress
Astro logoAstro
Next.js logoNext.js
Stripe logoStripe
Cloudflare logoCloudflare
WooCommerce logoWooCommerce
Shopify logoShopify
WordPress logoWordPress
Astro logoAstro
Next.js logoNext.js
Stripe logoStripe
Cloudflare logoCloudflare
Pick a platform, honestly

WooCommerce, Shopify,
or custom.

Three shapes we ship regularly. Which one fits is a function of catalogue size, margin per order, who edits the store, and where integrations sit. Here's how we'd think about it before opening a template.

WooCommerce

Best when you want to own every layer, already run on WordPress, or need unusual product / checkout logic a SaaS won't bend to.

Shopify

Best when speed-to-launch matters, the team is small, and the catalogue fits a standard product model. Fewer moving parts to run.

Headless / custom

Best when the storefront, the CMS, and the backend are already pulling in different directions — or when design ambition outruns a theme.

Decision
WooCommerce
Shopify
Headless / custom
Custom design ambition
Theme + deep customisation. No hard ceiling, but you're paying in build time.
Theme-led. Fine-grained design tweaks possible, but the checkout is mostly Shopify's.
Anything you can draw. The storefront isn't tied to a theme at all.
Running cost at small scale
Hosting + licence for key plugins. Lowest and most predictable of the three.
Platform plan + app subscriptions. Creeps as the app list grows; easy to underestimate.
Hosting + CMS + APIs. Heaviest of the three; makes sense once revenue justifies it.
Team editing the store
WordPress admin. Familiar to marketing teams; more surfaces to learn.
Clean admin, solid app ecosystem. Easiest for a non-technical operator.
CMS you choose. As editor-friendly as you make it — needs design work.
Payments & checkout
Razorpay, Stripe, Paytm, CCAvenue, COD — all work, some need plugins.
Shopify Payments first-class; others via gateway apps. Checkout is locked down.
Anything with an API. You're building it — which cuts both ways.
Multi-currency / multi-region
Possible with plugins. Works, but you'll test edge cases carefully.
Built-in via Shopify Markets. The least-pain path for global selling.
Whatever your backend supports. You own the complexity.
Integrations with your stack
Thousands of plugins, but quality varies. We vet each one before shipping.
App store is cleaner; apps cost monthly. Covers most SaaS tools out of the box.
Direct API integrations. Cleanest, also the most code to maintain.
SEO control
Full. Rank Math / Yoast, clean URLs, schema, log files — all within reach.
Good but opinionated. URL structure, robots, and some schema are Shopify's call.
Full, because the storefront is yours.
Where it breaks down
If the team won't run WordPress, it becomes a liability after launch.
If the catalogue or checkout needs unusual logic, you'll hit a wall or a workaround-tax.
If revenue doesn't justify the build, the overhead is real.

The accent dot marks what we'd default to for that decision, not the winner overall. The right platform is usually whichever one scores the dots on the rows that matter most to your business.

What we actually ship

Stores that keep running
after launch day.

Most stores are built beautifully and then slowly fall apart — a theme update breaks the PDP, a pixel never fires, shipping tables quietly go stale. We build against those specific failures, not around them.

  • What usually happens

    A homepage designed for the pitch deck, then templated product pages nobody opened Figma for.

    What we do instead

    We design the PDP and cart first. Homepage is the last page we touch, not the first.

  • What usually happens

    Checkout 'works' but sheds users at address validation, coupon codes, or mystery shipping rates.

    What we do instead

    Checkout is wired end-to-end on staging with real cards, real addresses, real edge cases, before handover.

  • What usually happens

    Analytics is half-installed: GA4 fires, but add-to-cart and purchase events are missing or double-counted.

    What we do instead

    GA4 + Meta + Google Ads events are spec'd, implemented, and QA'd against GA DebugView before launch.

  • What usually happens

    Plugin-creep: 30 plugins, 6 admin notices, 2 that haven't updated in a year.

    What we do instead

    A vetted plugin list you sign off on. Replaced before we ship anything that hasn't updated in 12 months.

  • What usually happens

    Speed dies the moment you load product images or a review widget.

    What we do instead

    Core Web Vitals measured on real product pages, not just the homepage. Images served as WebP, reviews lazy-loaded.

  • What usually happens

    Theme updates break the layout, and nobody notices until a customer complains.

    What we do instead

    Child theme for all customisations. Staging mirror for updates. We check the checkout after every platform push.

What it looks like

How we work, start to finish.

  1. 01
    Catalogue audit

    We walk through your products, margins, shipping rules, and current pain points. Output: a one-page recommendation on platform, scope, and what to fix first — before any design work.

  2. 02
    Design the PDP

    Product page and cart designed against real products — images, descriptions, variants, stock states. This is where stores live or die; we give it the attention the homepage usually steals.

  3. 03
    Build & wire

    Store built on a staging URL you can test with real orders. Payments, shipping, tax, analytics, and transactional emails are all exercised end-to-end before go-live.

  4. 04
    Launch & monitor

    Go-live, DNS cutover, and two weeks of active monitoring. We watch for checkout errors, broken pixels, and the first-week support tickets — and fix them as part of the build.
What every store ships with

The baseline for every build.

Not a premium tier. Every store we ship meets these four baselines on day one, whether it's a single-SKU launch or a 2,000-SKU catalogue migration.

PDP
Designed, not templated
Product page is the hero, not an afterthought
E2E
Checkout QA
Real cards, real addresses, real edge cases
GA4
Events instrumented
Add-to-cart, purchase, refund, QA'd in DebugView
CWV
Performance baseline
Measured on PDPs, not just the homepage
Questions we hear

Before you
ask us.
Plan the build

Figure out the platform before you commit.

Tell us what you sell and who runs the store. You'll get a plain-English read on which platform fits, what the build would cost, and where the first wins are — before any contract.

or email hello@genvoid.com