Puribazar

Project Overview

Puribazar is a multi-vendor e-commerce marketplace that brings the rich culinary and craft heritage of Odisha onto a single, scalable platform. From Puri's legendary Khaja and Nrusingha Sweets to traditional Pattachitra artifacts, the client envisioned a digital Bazar where independent local sellers could open their own storefronts, manage inventory on their own terms, and ship authentic regional products across India without depending on generic marketplace giants.

My role was to architect that vision from the ground up. A WordPress build powered by WooCommerce , Dokan , Elementor , and a fully tested payment gateway flow, engineered for performance, vendor autonomy, and SEO-ready discoverability.

The Brief

The client approached me with a clear ambition but a complex problem. They needed a regional marketplace that could:

• Onboard multiple vendors with their own branded storefronts and dashboards.
• Handle physical goods with variants, including different weights, packaging, and flavours of regional sweets.
• Process secure online payments across UPI, cards, net banking and cash on delivery.
• Stay editable by a non-technical team after handover, with zero developer dependency for daily content updates.
• Rank for niche searches like "Odisha sweets online" and "Puri Khaja delivery" without paid acquisition.

In short, the feature depth of Amazon, the autonomy of Etsy, and the editability of a WordPress blog, all on a budget that respected a regional startup's reality.

Strategy & Approach

Building a marketplace is not the same as building a store. A store has one voice; a marketplace has many. The architecture had to host dozens of independent sellers without letting the storefront feel fragmented to the customer. I broke the build into four working layers: commerce, vendor management, design system, and trust infrastructure. Each layer was made modular so the client could grow without rebuilding.

The decision to choose WordPress with the WooCommerce and Dokan stack came from a deliberate trade-off study. Custom platforms offered control but burned timelines. SaaS marketplaces offered speed but locked the client into rental economics. WordPress sat at the intersection. It is open-source, infinitely extensible, and supported by a plugin ecosystem mature enough to handle real commerce at regional scale.

Tech Stack & Architecture

Each tool in the stack was chosen to solve a specific problem, not because it was familiar.

WordPress & Elementor

WordPress served as the content backbone, giving the client full ownership of pages, blogs, and landing routes. Elementor was layered on top for visual building, letting the marketing team edit the homepage, vendor showcase blocks, and seasonal campaign banners without touching code. Every section was built as a reusable template, so a new vendor spotlight or festival sale could go live in minutes. This editability-first approach is a pattern I have refined across other WordPress builds in my portfolio .

WooCommerce

WooCommerce powers the core commerce engine, handling product catalogues, cart logic, tax rules, order states, and inventory. I configured product variations specifically for the food vertical, where a single Khaja product can ship in three weights and two packaging types, each with its own SKU and shipping weight.

Dokan Multi-Vendor

The Dokan plugin transformed the WooCommerce store into a true marketplace. It gave every vendor a frontend dashboard to upload products, manage orders, view earnings, and customise their store page, all without admin access. I configured commission structures, vendor verification flows, and product approval queues so the marketplace owner retains editorial control while vendors retain operational freedom.

Payment Gateway Integration

I integrated a payment gateway with full multi-vendor split logic. When a customer buys from multiple vendors in a single cart, the payment automatically settles into the right vendor accounts after the platform commission is deducted. The flow was hardened with secure checkout, refund handling, and order state synchronisation between Dokan and the gateway.

Key Features Delivered

• Vendor Onboarding Flow: Custom registration form with KYC fields, store setup wizard, and automatic store-page generation.
• Frontend Vendor Dashboard: Sellers manage products, orders, coupons, withdrawals and analytics without touching WordPress admin.
• Multi-Vendor Cart and Checkout: Customers buy from multiple vendors in one transaction with unified shipping and split settlement.
• Variable Product Support: Critical for regional sweets sold in multiple weights, packaging and combo formats.
• Secure Payment Gateway: UPI, cards, net banking, wallets and cash on delivery, all routed through a PCI-compliant flow.
• SEO-Ready Architecture: Clean URL structure, schema markup, optimised meta tags per product, and image lazy loading for Core Web Vitals.
• Elementor-Powered Pages: Editable homepage, vendor directory, category collections and campaign landing pages.
• Responsive Storefront: Mobile-first layout tuned for the Indian buyer, where most marketplace traffic arrives on phones.

Challenges & Solutions

Three problems demanded the most thought during the build.

1. Vendor Independence vs. Brand Consistency

Vendors needed creative freedom on their store pages, but the marketplace had to feel like one cohesive brand. I solved this by locking the global header, footer, and product card design at the theme level, while opening the vendor banner and store description for full customisation. The result is that every vendor page feels personal, but the marketplace feels unified.

2. Multi-Vendor Cart Settlement

A standard WooCommerce payment gateway sends the entire payment to one account. For a marketplace, this is broken by design. I configured the gateway with Dokan's vendor wallet system so commissions and vendor payouts are calculated automatically on every order, removing all manual reconciliation from the client's workflow.

3. Editability After Handover

The client team is not technical. I built every page in Elementor with named, reusable sections and recorded a handover walkthrough so the team can publish a new vendor highlight, change banner copy, or launch a festival sale without opening a support ticket.

Outcome

Puribazar launched as a fully operational multi-vendor marketplace where independent Odisha-based sellers, including sweet shops, snack makers, and traditional artisans, could reach customers across India through one searchable, mobile-first storefront. The client gained a platform they could grow without ongoing development costs, vendors gained autonomy, and customers gained access to regional products that were previously locked behind local geography.

The build proves a quiet thesis I keep returning to. WordPress, when architected with intent, can hold its own against custom marketplace builds at a fraction of the cost and timeline , especially for regional commerce where flexibility and editability matter more than scale. You can see a similar editorial-first WordPress approach in my Monalisa Mandal portfolio build , and broader e-commerce thinking in The House of Abigail case work.

Reflections

Every marketplace is, at its core, a trust engine. The code only matters because it carries that trust between three parties: the platform, the vendor, and the customer. Building Puribazar was less about choosing plugins and more about choreographing how those three parties hand work to each other, every minute, without friction.

The most satisfying part of the project was not the launch itself but the first time a vendor uploaded a product, set a price, fulfilled an order, and received their payout, all without contacting me. That is when a marketplace stops being a website and starts being an ecosystem.