WeezShop commerce platform
- Client
- WeezLab — in-house commerce product
- Live site
- shop.weezlab.com
- Scope
- Product strategy
- Storefront & admin UX
- Full-stack platform engineering
- Courier & payment integrations
- Timeline
- 2026 — v1 through v2.2, ongoing
Plugins break. Shared hosting can’t run the fix.
A small shop in Bangladesh gets sold WordPress and a stack of plugins, then discovers the real cost: a checkout that depends on an extension somebody stopped maintaining, courier booking done by copy-pasting addresses into a separate portal, and annual licences for features that should have shipped in the box.
The hosting makes it worse. Shared cPanel accounts mean no shell, no Composer, no Docker, no background workers—so most modern ecommerce stacks are simply not deployable, and the ones that are tend to break the first time nobody updates them for a year.
Upload a folder. Everything else is already in the box.
We built WeezShop as a single PHP and MySQL codebase that installs by uploading a folder. It has no Composer manifest, no vendor directory, and no build step—even SMTP is a dependency-free client we wrote, so an unmaintained install keeps sending order confirmations years later.
Everything a merchant needs is core, not an add-on: Pathao and Steadfast booked from the order page, bKash and PortPos hosted checkout confirmed server to server, cash on delivery and manual wallet transfers, inventory, coupons, reviews, expenses and profit reporting, SEO and Meta Pixel—governed by a set of longevity rules that make the database schema, the theme contract, and the provider interfaces additive-only, forever.
Platform highlights. Four decisions that shaped the build.
One admin panel, nothing to bolt on
Twenty-four modules in a single panel—orders and manual order entry, products and variants, inventory, customers, coupons, reviews, expenses and profit reporting, storefront analytics, an admin activity log, content and homepage editors, subscribers, and one-click backup and restore. Nothing here is licensed separately, because nothing here is an add-on.
Couriers booked from the order
Pathao and Steadfast behind one provider contract: book a shipment from the order page against the courier's own city and zone lists, then pull delivery status back. A flaky courier API surfaces an error, never a half-written order.
The payments this market runs on
Cash on delivery and manual bKash, Nagad and Rocket transfers with admin verification, plus API-backed bKash and PortPos checkout captured server to server. Totals, shipping and coupons are always recomputed on the server—the browser is never trusted with money.
Engineered to outlive its own maintenance
Nineteen versioned migrations that only ever add, a theme contract where templates display prepared data and never touch business logic, prepared statements and row-locked stock so two checkouts cannot oversell the last item, and audited access control across every admin page and background action.
What it delivers. Everything in the box, nothing to license.
- Admin modules in one panel
- 24
- Courier & payment integrations built in
- 4
- Composer packages or build steps to deploy
- 0
I've watched too many small shops lose a weekend because a plugin update broke their checkout. So while building WeezShop, I kept asking myself one thing: if nobody touches this store for two years, will it still take orders? That's why couriers, payments and backups live inside the platform, not in plugins someone might stop maintaining.
An editorial store for a Dhaka accessories brand: about 200 handpicked products in browsable categories, fabric sold by the yard, and courier booking with cash-on-delivery checks built into every order.
