Skip to content
Shola Japheth

Client build · Storefront & company site

One site for a tech-talent and events company, with a shop that cannot be tricked on price.

The company site and branded-merchandise storefront for Innovotio, a Lagos company that supplies tech talent, runs tech events and sells branded merchandise. I rebuilt it as one app with an admin the team runs themselves.

Role
Design & full-stack build
When
Oct 2026 — present
Status
Live
  • 1

    domain for company pages and shop

  • 66

    products managed in the admin

  • Guest

    checkout, no customer accounts

The problem

Innovotio sold through a marketing site and a separate shop subdomain, with a product catalogue that lived in slides. The team needed one place to show their services, take merchandise orders in naira with per-product minimums, and manage products, promotions and careers without a developer. Anything touching money had to be safe against a customer editing the page.

What I owned

  • Rebuild of the company pages and the storefront as a single app
  • Catalogue, cart, checkout and payment integration
  • Admin for products, promotions, careers and team access
  • Security, test suite and the cutover from the old site

The system

How an order is priced and paid
  1. Cart

    client totals are a preview

  2. Re-price on the server

    catalogue, options, minimums

  3. Order created

  4. Hosted payment

    Paystack

  5. Verified server-side

    not by redirect

  6. Confirmation email

    or

    Quote-only items

    a request-a-quote flow instead of the cart

The browser only shows totals. The server prices every order itself and trusts nothing the client sends about money.

Key decisions

  1. 01

    The database is the catalogue

    Products, options, promotions and careers live in Postgres and are edited in the admin. Seed data only bootstraps it. The team changes the shop without a deploy, and cached pages refresh when they save.

  2. 02

    Never trust the client on price

    Money is stored as integers, every line is re-priced on the server, and payment state is confirmed by verifying with the payment provider, not by a redirect or a request body. Minimum order quantities are enforced again when the order is created.

  3. 03

    One enquiry system for every service

    Recruitment, events, consultancy, talent and training all share one enquiry flow, so a new service is a configuration change rather than a new form.

  4. 04

    Guests, not accounts

    Customers check out as guests and look up past orders with an emailed one-time code. Only staff have accounts, invited by email with a single-use link, so there are no customer passwords to protect.

  5. 05

    Move the old site without losing it

    The previous marketing URLs and the old shop subdomain redirect permanently to their new pages, so existing links and search results keep working after the switch.

What I shipped

Storefront
Search, category browsing, variants generated from options, minimums across a product's total, and URL-driven filters you can share.
Admin
Product and category management, banners and campaigns, an admin team with invite and reset flows, and an audit log.
Company site
Services, programs, about and careers, in the client's brand system with a dark home page they asked for.
Quality
Unit and integration tests run against a real Postgres rather than mocks, with Playwright for the main journeys. Security controls get tests that fail when the control is removed.

Outcome

  • Live

    on innovotio.com

  • 1

    app replacing a site and a shop subdomain

  • Self-serve

    catalogue, promotions and careers run by the team

  • 301s

    old URLs carried across

Next.jsTypeScriptTailwindPostgres + DrizzlePaystackResendPlaywright

esc
↑↓ to move · ↵ to run