Development buildDesigned for global selling

Fashion ecommerce and dropshipping

Sheaker - Custom Ecommerce Platform

A development-stage Django commerce platform joining customer experience, supplier data, pricing, fulfilment and growth operations.

Sheaker Development build

Commerce operations

01Supplier dataImport and audit
02Clean catalogueVariants and media
03Protected pricingRules and margin
Customer journeyDiscover → buy → track
OperationsOrders → fulfilment
Growth layerSEO → retention

System map based on verified development scope — not a production analytics screenshot.

Client
Sheaker
Build
Custom ecommerce and operations platform
My role
Product architecture, UX/UI and full-stack development
Engagement
End-to-end commerce platform engineering
Evidence, not theatre.

Evidence basis: the local source repository was inspected across its models, routes, services and templates. The product is explicitly presented as a development build; no live launch, revenue, conversion rate or customer-volume claim is made.

Project context

Building for the buying decision and the work behind it.

Sheaker is a custom commerce system designed to give a growing ecommerce operation more control than a collection of disconnected storefront plugins. The build covers the buyer journey, product and supplier operations, pricing, fulfilment, customer accounts, marketing and reporting within one Django application.

01

The challenge

What the product needed to make easier.

A supplier-led catalogue introduces operational problems that a conventional storefront does not solve by itself: inconsistent product data, external image ownership, changing costs, variant and inventory complexity, fulfilment synchronisation and margin protection. The business also needed different staff roles to manage products, orders, customers, content and campaigns without relying on terminal access.

02

The approach

One connected experience, not isolated features.

I architected a role-based Django platform around three connected layers. The customer layer includes discovery, product variants, wishlist, cart, multi-step Stripe checkout, order tracking and return/refund requests. The operations layer handles supplier imports, data cleaning, image processing, pricing rules, catalogue management, order status and reporting. The growth layer includes technical SEO, editorial content, currency handling, analytics settings, loyalty, gift cards, affiliate journeys and email integration points.

03

Verified scope

Capabilities implemented around the real workflow.

Product categories, brands, variants, media, attributes, inventory and size guides

Supplier import, duplicate detection, data cleaning and catalogue audit trails

Configurable pricing logic designed to protect operating margin

Search, recommendations, wishlist, cart and multi-step checkout journeys

Stripe checkout, order detail, tracking, returns and refund requests

Customer accounts, saved addresses, notifications and quick reorder actions

Role-based product, order, customer, reporting and content dashboards

Blog, sitemaps, product feeds, analytics, loyalty, gift card and affiliate foundations

04

The demonstrated outcome

What can be said responsibly.

The repository contains a substantial development build with the major commerce and operations workflows represented in models, routes, services and dashboard interfaces. It is not currently live, so this case study does not claim production sales, conversion uplift or customer adoption. The strongest demonstrated outcome is the consolidation of complex commerce requirements into a maintainable custom product architecture.

A useful next step

Have a customer journey or internal workflow that has outgrown generic tools?

I’ll help you identify the smallest credible version that can create value.