Skip to content
CodeWave Systems
Selected project

Case study · Sportswear retail

JerseyWorld

Custom ecommerce, from the first shirt to the final delivery.

Visit jerseyworldstore.co.ke
Category
Ecommerce platform
Industry
Sportswear retail
Platforms
Online storefront · Staff administration portal
Technology
Laravel · Vue · Inertia · MySQL · Redis

01 · Project overview

What was built, and for whom.

JerseyWorld is a custom ecommerce project built by CodeWave for Jersey World Store. Designed to replace a WordPress and WooCommerce storefront, it combines a customer-facing shop with the tools staff need to manage products, local inventory, personalised printing, payments and delivery. The platform supports online shoppers and staff-created orders through the same back office.

Built for
Jersey World Store, a Kenyan sportswear retailer
Website
jerseyworldstore.co.ke (opens in a new tab)
Type
Selected project
Platforms
Online storefront, Staff administration portal
Focus
ecommerce payments web

02 · Business challenge

The problem, as the business experienced it.

Selling personalised jerseys requires more than a product catalogue: shirt variations, printing instructions, stock, payment and delivery all need to stay attached to the same order.

A jersey can have a size, a player name, a number, a badge and special printing instructions. Those choices need to reach the printing and packing teams accurately while the customer checks out with the right delivery charge and payment method.

  • Product variations and personalisation must remain linked to each order line
  • Stock availability needs to inform both storefront and staff orders
  • Payment confirmation must stay connected to the order
  • Printing, packing and delivery need clear processing stages

03 · Our approach

How we got from the problem to the system.

CodeWave built a custom Laravel and Vue ecommerce platform connecting product discovery and personalisation to checkout, payment collection, printing, packing and dispatch.

  1. 01

    Model the catalogue

    Organised categories, product variations, stock and personalisation options around how jerseys are selected and prepared.

  2. 02

    Build the shopping experience

    Built browsing, search, filters, customer accounts, wishlists and a basket that preserves each shirt's selected options.

  3. 03

    Connect checkout and payments

    Connected delivery areas and rates to checkout, with M-Pesa and Pesapal payment flows tied to the order record.

  4. 04

    Carry the order through operations

    Added staff order creation, printing and packing stages, dispatch tracking, delivery receipts and customer notifications.

04 · Solution architecture

Layers of the system.

Clients at the top, the core application in the middle, integrations and data underneath. Green marks the integration layer where the system meets the outside world.

05 · Key features

What the system does.

Product catalogue & variations

Categories, search and filters help shoppers find the right jersey and size.

Jersey personalisation

Names, numbers, badges and printing instructions travel with each order line.

Inventory & staff orders

Local stock management and staff-created orders share the same catalogue.

M-Pesa & Pesapal checkout

Customers can pay through integrated payment flows associated with their order.

Printing, packing & dispatch

Processing stages give each department a view of the work that needs its attention.

Delivery receipts & notifications

Dispatch and delivery records sit alongside customer communication and order history.

06 · Technology

The stack behind it.

Chosen for the job — mature, supportable and straightforward to host and staff for in Kenya.

Backend
PHP Laravel
Frontend
Vue Inertia Tailwind CSS
Data
MySQL / MariaDB Redis
Integrations
M-Pesa Daraja Pesapal SMS Email

07 · Business impact

What changed for the business.

Outcomes are described qualitatively. Figures are published only when verified by the client and approved for release.

  1. 01

    Personalisation details remain attached to the items being prepared

  2. 02

    Online and staff-created orders use a shared operational workflow

  3. 03

    Payment, printing, packing and delivery records are connected

  4. 04

    Staff can manage the catalogue and storefront content from the back office

08 · Screens

Interface illustration.

A representative illustration of the interface, not a live screenshot — no client data is shown.

Similar problem?

Have a process that looks like this one?

Tell us how it runs today. We will tell you what a system built for your operation would involve.

Start a Conversation
info@codewavesystems.com +254 708 604 940