Case study · Electronics retail
RANI Gadgets
A second storefront, with its own look, on the engine built for JerseyWorld.
- Ecommerce platform
- Electronics retail
- Online storefront · Shared administration portal
- Laravel · Vue · Inertia · MySQL · Redis
01 · Project overview
What was built, and for whom.
RANI Gadgets is an electronics storefront built by CodeWave on the commerce platform first developed for JerseyWorld. The platform now serves each domain as its own shop: RANI has its own header, product cards, palette and font, its own twelve categories and fifty-eight sub-categories, and its own menus, pages and homepage. Products, payments and fulfilment run through the same back office, so staff manage both shops from one place.
- RANI Gadgets, a Kenyan electronics and technology retailer
- Selected project
- Online storefront, Shared administration portal
- ecommerce payments web
02 · Business challenge
The problem, as the business experienced it.
RANI Gadgets sells everything from powerbanks and phones to robotic arms and electric vehicles. It needed a premium electronics storefront of its own, and some of what it sells is priced by quotation, not added to a basket.
A second shop could have meant a second codebase to host, secure and update. The aim was a store that looks and reads entirely like RANI while reusing the proven checkout, payment and order workflow underneath.
- A premium electronics look, distinct from a sportswear shop
- Each shop showing only its own products, categories, menus and pages
- Industrial products, machinery and vehicles sold by quotation, not online checkout
- One back office for catalogue, orders and payments across both shops
03 · Our approach
How we got from the problem to the system.
CodeWave extended the JerseyWorld commerce platform to run more than one storefront, then gave RANI its own skin, category tree, menus, pages and homepage, plus quote-only products, while checkout, payments and fulfilment stay shared.
-
01
One engine, several shops
Made storefronts domain-based, each with its own name, contacts, logo, display currency and catalogue rules, choosing which product groups every shop sells.
-
02
Give RANI its own skin
Built a RANI header with a wide search and a category bar, a RANI product card, and a navy and neon-green palette with its own font and storefront wording.
-
03
Organise the catalogue
Imported RANI's approved category tree and gave each shop its own menus, pages, blog and sitemap, with a homepage made of sections staff edit.
-
04
Sell by quotation
Added quote-only products: shoppers request a quote instead of checking out, staff are alerted, and the request becomes an order once the price is agreed.
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.
Storefronts
- RANI Gadgets
- Jersey World Store
- Shared administration
Per shop
- Skin & palette
- Categories & menus
- Pages & blog
- Homepage sections
- Catalogue rules
- Quote requests
Shared commerce
- Products & stock
- Checkout
- M-Pesa & Pesapal
- Orders & delivery
Application & data
- Laravel
- Vue & Inertia
- MySQL / MariaDB
- Redis queues
05 · Key features
What the system does.
Its own storefront design
A RANI header, category bar and product card, with the palette, font and wording RANI chose.
Category tree & menus
Twelve categories and fifty-eight sub-categories, with menus and pages that belong to the shop.
Request a quote
Robotic arms, machinery and vehicles show Request a quote; staff turn the request into an order.
Shared checkout
M-Pesa prompt, Pesapal and pay on delivery, with prices shown in KES, USD, GBP or EUR.
Catalogue rules per shop
Choose which product groups each shop sells; anything left out never appears there.
WhatsApp enquiries
Shoppers can chat with the shop, and enquiries land in the same back office as orders.
06 · Technology
The stack behind it.
Chosen for the job — mature, supportable and straightforward to host and staff for in Kenya.
- PHP Laravel
- Vue Inertia Tailwind CSS
- MySQL / MariaDB Redis
- M-Pesa Daraja Pesapal WhatsApp 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.
-
01
RANI has a storefront that reads as its own brand, not a copy of another shop
-
02
Checkout, payments and fulfilment are reused, not rebuilt
-
03
Quote-only products reach staff as enquiries they can turn into orders
-
04
Both shops are managed from one back office
08 · Screens
Inside the system.
Screens from the delivered system.
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.