Custom nopCommerce Development
Business rules, admin workflows and storefront experiences that match how you sell.
Storefronts, B2B ordering and back-office integrations, built around your business. We develop for and support nopCommerce 4.50 to 5.00, the current release.
concept-supply.example
Concept Supply
Catalog / Safety & PPE
Safety & PPE
Vented safety helmet
HLM-120
Nitrile work gloves
GLV-210
Compact cordless drill
DRL-480
Stackable storage bin
BIN-330
Nitrile work gloves
Box of 100 · GLV-210
Size
Volume pricing
Order review
3 itemsTrade order approval
Example flowWhat we build
Storefronts, plugins, B2B workflows and integrations, built with nopCommerce and .NET to match how your business sells.
Business rules, admin workflows and storefront experiences that match how you sell.
Self-contained plugins for payments, shipping, pricing and widgets that upgrade cleanly.
ERP, CRM, payment and logistics connections with logging, retries and clear data ownership.
Contract pricing, company accounts, approval flows and quick ordering for trade buyers.
Vendor onboarding, moderation, commission rules and split fulfilment on nopCommerce.
Version upgrades, platform migrations and performance work planned around your data.
Our products
We build and sell our own nopCommerce themes and plugins, the same way we build client work. Shop the live demo as a customer would, or see every product in our store.
Live demo
A working electronics store on nopCommerce 4.90, running our TechOrbit theme and Advanced Search. Browse categories, search and open product pages as a shopper would.
Store
Themes and plugins we build and maintain for nopCommerce. Each one lists the version it supports and its licence. Online checkout for paid products opens soon, or download free ones straight from their page.
Engineering expertise
Standard storefronts handle standard businesses. When your pricing, workflows or system landscape are more involved, the platform needs to be engineered around them.
Pricing & catalog
Negotiated prices, tiered discounts and configurable products rarely fit a standard catalog. We model them inside nopCommerce so every customer sees the right product at the right price.
Built on nopCommerce customer roles, tier pricing and ACL, extended where your rules go further.
Price resolution · Trade account
sample data| Product | List | Customer price |
|---|---|---|
| Ball valve, 2″ brassVLV-1042 | 84.00 | 71.40Contract |
| Filter cartridge, 12 pkFLT-2210 | 126.00 | 113.40Tier 10+ |
| Inline pump, 0.5 HPPMP-3301 | 412.00 | 412.00Catalog |
Contract prices and price lists by customer, company or role.
Attribute matrices, configurable products and restricted assortments.
Import and maintenance tools for large or frequently changing catalogs.
Workflows & stores
Approval routing, purchase orders, delivery rules and store-specific behaviour belong in the platform, not in email threads. We build the workflow once and let nopCommerce enforce it.
Custom steps are added through plugins and events, keeping the core checkout upgradeable.
Checkout workflow · Trade store
example flowCart reviewed (complete)
14 lines · validated against minimum order quantities
Purchase order (complete)
PO reference and cost centre captured
Approval required (in progress)
Order value exceeds the buyer’s limit — routed to purchasing manager
Payment on account (pending)
Invoice terms applied for this company
Order released to ERP (pending)
Sent for fulfilment once approved
Approvals, PO numbers, validation and delivery scheduling.
Separate brands or regions with shared catalog and admin.
Behaviour that changes by customer group, store or order value.
Integrations
Stock, prices, customers and orders should move between nopCommerce and your back office without re-keying. We design integrations that are observable, retry safely and make data ownership explicit.
REST APIs, webhooks, scheduled tasks and message queues — chosen per data flow.
erp-inventory-sync
job logProducts, stock, prices and orders synchronised with your ERP.
Payment, shipping, CRM, PIM and marketing platforms.
Logged sync runs with clear errors and safe re-runs.
Why nopCommerce
nopCommerce is an open-source commerce platform built on ASP.NET Core. Its architecture makes it a strong foundation when a project needs deep customisation rather than configuration alone.
Built on Microsoft’s cross-platform framework, with a familiar C# codebase and dependency injection throughout.
Payments, shipping, tax, widgets and integrations are added as plugins rather than edits to the core.
Customer roles, tier pricing and access control lists provide a solid base for trade commerce.
Run several storefronts from one installation, each with its own catalog, pricing and theme.
Built-in vendor accounts give marketplace projects a starting point to extend from.
Open source code and extension points let you connect external systems through plugins, APIs and scheduled tasks.
How we work
A structured, transparent process — so you always know what is being built, why, and what comes next.
We map your business rules, existing systems and constraints, and agree what success looks like.
We design the solution — plugins, data flows, integrations — and plan delivery in milestones.
We build in short iterations with regular demos and a staging environment you can review.
Functional, integration and regression testing against the agreed scenarios before release.
We plan the release with you, monitor after go-live and support the platform as it evolves.
Selected work
Recent client projects on nopCommerce and .NET. Client names and brands are left out.
Technology
A focused Microsoft and .NET stack for commerce back ends, with modern Vue tooling where a decoupled front end makes sense.
Product names and logos are trademarks of their respective owners and are shown to identify technologies we use.
Engagement models
Every project is scoped individually. Choose the model that matches how your roadmap is likely to evolve — we will recommend one after discovery.
For businesses needing a custom implementation with a defined scope.
Best for
New builds, major features, integrations and migrations.
Key deliverables
For long-term engineering partnerships with an evolving roadmap.
Best for
Ongoing product development and roadmaps that change.
Key deliverables
For maintenance, upgrades and continuous improvements to a live store.
Best for
Live stores that need a dependable technical partner.
Key deliverables
Estimates follow a discovery conversation, so pricing reflects your actual scope rather than a fixed package.
Questions
Straight answers to what teams usually ask before starting a nopCommerce project.
Something else on your mind? Ask us directly.
We design and build storefronts, business rules, ordering workflows and integrations to your requirements. Our specialization is nopCommerce and .NET, so the platform choice, extensions and delivery scope are discussed during discovery rather than assuming every business needs the same solution.
We work across the platform: custom business logic, admin extensions, storefront themes, checkout changes, pricing rules, multi-store configuration and data model extensions. Where possible we implement changes as plugins rather than edits to the core, which keeps the store easier to upgrade.
Yes. We build payment, shipping, tax, widget, discount and integration plugins following nopCommerce conventions, and we can also update or extend existing plugins. You receive the source code along with installation and configuration notes.
In most cases, yes — provided the system offers an API, database access or file-based exchange. We start by reviewing the system’s integration options and data ownership, then agree field mappings, sync direction and error handling before building.
Yes. We assess your current version, plugins and customisations, recommend an upgrade path and flag anything that needs rework. Upgrades are rehearsed on a staging environment before the production cut-over.
We develop for and support nopCommerce 4.50 to 5.00, the current release. New projects start on 5.00 on .NET 10. If your store runs an older version, we can upgrade it first and then continue with the work you need.
Yes. We are based in Dhaka, Bangladesh, and work remotely with clients in other countries. We agree communication channels, meeting times and delivery milestones at the start of each engagement so remote collaboration fits your project.
Estimates are based on a discovery of your requirements and existing systems. For well-defined scope we provide a milestone-based estimate; for evolving work a dedicated-team model is usually a better fit. We explain assumptions and risks alongside every estimate.
Yes. Support engagements cover bug fixes, small enhancements, version and security updates, and performance reviews. Scope and response process are agreed in advance so you know what to expect.
Engineering insights
Upgrades, catalog transfers and ERP workflows, with implementation details and the limits to plan around.
Feed guide
Google replaced the Content API for Shopping with the Merchant API. Calls to the old API now fail more and more often until it shuts down in early 2027. How to check whether your store’s feed or plugin is affected, what changes in the new API, and how to move.
Read the guide: Google Merchant API: What the Content API Shutdown Means for Your StoreFeed guide
Product identifiers decide whether Google can match your product to the same item sold elsewhere. What GTIN, UPC, EAN, ISBN and MPN mean, which ones Google requires, where to find or buy them, and how to handle own-brand and handmade products.
Read the guide: GTIN, MPN and Brand for Google Shopping: What They Are and What to Do Without ThemFeed guide
Google sorts every product into its own category list, the product taxonomy. How the list is built, when Google needs you to set the category yourself, how product_type differs, and a practical way to map a whole store’s categories at once.
Read the guide: Google Product Category: How to Choose and Map It for Merchant CenterTell us about your storefront, ordering workflows or integrations by email, phone or WhatsApp. An outline is enough to start.