Sellino — Multi-Vendor Ecommerce Platform
A Laravel commerce platform with seller operations, POS, inventory, delivery, wallets, returns, and a versioned REST API.
v10
API version
6+
core domains
2
customer interfaces
The brief.
-
problem
Commerce workflows span storefronts, inventory, orders, delivery, payments, and support.
-
overview
Built as a core product, a modular Laravel ecommerce platform covering both public shopping journeys and seller-side operations.
-
solution
Built a modular Laravel application with API v10 endpoints, role-based seller features, and connected operational modules.
-
role note
I focused on full-stack features across ecommerce operations, seller workflows, inventory, delivery, and API-connected functionality.
-
business goal
Give merchants one system for catalog, sales, fulfilment, finance, and customer operations.
Modules I worked on
Stack
Laravel PHP MySQL REST APICase study.
Personal project — built as a core product. The notes below describe the product and what I built.
Project Overview
Sellino is a modular Laravel ecommerce platform built around real operational workflows, not just the storefront. It includes catalog and seller tools, order management, inventory, delivery, payment records, customer accounts, returns, and POS support.
What I Built
I built full-stack features across ecommerce operations, seller workflows, inventory, delivery, finance, and API-connected functionality as a core product.
Architecture
The platform exposes a versioned API v10 alongside its Laravel web application. This supports the customer web experience and allows a dedicated Next.js frontend to consume the same product, customer, checkout, and account domains.
Key Modules
Work spans catalog and seller management, warehouses and inventory, shipping partners, delivery charges, order shipments, returns and replacements, wallets, financial records, customer support chat, and CMS-managed site sections — all built as a core product.
Engineering Focus
The implementation favours clear domain boundaries, role-aware seller features, and incremental schema changes so that operational features can evolve without disconnecting the shopping experience from the back office.
Implementation notes
Seller-facing features run behind a role-aware policy layer, so the same controller surface serves different capabilities per account type. Cart and pricing rules live in dedicated service classes with queue-backed side effects (order confirmations, invoice records, wallet movements), keeping request cycles short even on heavy checkout paths. Multi-warehouse inventory is resolved at quote time: stock reservations are scoped per location, delivery-charge rules are cached per zone, and returns re-enter the same state machine as fresh orders so the fulfilment flow has exactly one source of truth.
On the data side, schema changes ship as expand-contract migrations so deploys never block on long ALTERs: new columns fill in the background, readers switch behind a feature flag, and the old column is dropped a release later. Search and catalog endpoints are cache-tagged per category and vendor, which makes invalidation surgical after price or stock updates. The API v10 layer mirrors the web controllers' form requests and resources, so the Next.js storefront and the server-rendered app consume byte-identical payloads from one codebase.