Shundor.me

Shundor.me is a Bangladeshi retailer running on the ReformedTech commerce stack. Rather than a bespoke build, Shundor uses our productized platform: DokanePOS for in-store sales, inventory, and back-office operations, and our multi-template Next.js storefront for the online channel — sharing a single product catalog, customer database, and order pipeline across both.

This is the model we recommend for Bangladeshi retailers ready to expand from a physical shop into omnichannel commerce: skip the rebuild-from-scratch path, deploy a configured instance of our platform, and brand it through our multi-template system. Shundor is one of the customers we run this playbook for.

What Shundor uses

• DokanePOS — our point-of-sale product for retail and food-service operators in Bangladesh. Inventory, sales, returns, staff management, and back-office reporting feed the same database the storefront reads from.
• Storefront on our Next.js multi-template platform — a fully-featured ecommerce experience: product catalog with filtering and pagination, cart, wishlist, account / login, order tracking, and a returns and refund flow.
• Branded theming via our template system — Shundor's brand identity (logo, colors, typography, header/footer variants) is plugged in via our env-driven template selector, with template-specific asset overrides falling back gracefully to platform defaults.

What's under the hood

• Storefront: Next.js 14 (App Router), React 18, Redux Toolkit + React Redux for cart, auth, and product state, Bootstrap 5 layout primitives blended with Tailwind CSS 4 utilities, SASS pipeline, Swiper carousels, React Toastify notifications, React Paginate, React Rating.
• Auth: JWT tokens persisted in localStorage, automatic Authorization header injection via Axios interceptors, init-time auth re-hydration via a checkAuthState thunk.
• Multi-template engine: a pluggable system in lib/ — template config + validation, dynamic component loading with fallback, env-resolved asset paths, template-aware error boundaries, and dynamic CSS loading. Switching a merchant's brand is a config change, not a fork.
• Service layer: dedicated services for products (including configurable variants), categories, orders, users, and slider/banner content, all routed through a centralized Axios instance with consistent error handling.
• POS: DokanePOS handles the in-store side — sales, inventory adjustments, staff roles, returns — feeding the same product and order records the storefront reads.

Why this engagement matters

Shundor.me is the kind of customer our productized stack was built for: a local Bangladeshi retailer who needs both a real POS and a real online store, doesn't want to wait for a six-month bespoke build, and benefits from the steady stream of platform improvements we ship to every merchant on the system. They're a long-term local partner — and a proof point that combining DokanePOS with our ecommerce template is a working playbook for omnichannel commerce in Bangladesh.