Online stores built for the whole job, not just the checkout
eCommerce development builds the store: catalogue, cart, checkout, payments, shipping and the systems behind them. MBGDesk builds on Shopify, WooCommerce or a custom stack, choosing by what you sell and how you fulfil it rather than by platform preference.
An online store is mostly not the shop front. It is tax rules, shipping rates, stock counts that have to stay true across two systems, refunds, failed payments, and what happens when someone orders the last item twice. The storefront is the part clients look at and the part that causes the fewest problems.
Stores tend to fail operationally rather than visually. A catalogue structured for how the business thinks rather than how customers search produces category pages nobody finds. Stock lives in two systems that disagree. Shipping rules approximate reality and lose money on every heavy item. Variants are modelled as separate products, so the same shoe appears eleven times in search results and competes with itself.
When this work makes sense
Questions worth asking any supplier
How do your customers actually browse? The category structure should follow that, not your internal product hierarchy.
Where does stock live? If the store is not the source of truth, the synchronisation design is the project.
What are the real shipping rules? Weight bands, zones and free-shipping thresholds decide margin more than the theme does.
How are variants modelled? Getting this wrong creates duplicate content and cannibalised product pages.
What is the total platform cost at your volume? Transaction fees and app subscriptions often outweigh the build over three years.
Deliverables
A store on Shopify, WooCommerce or a custom stack, chosen against your catalogue and fulfilment
Catalogue and category structure designed around search demand and browsing behaviour
Product pages with correct variant handling and Product structured data
Payment integration — Razorpay, Stripe, PayPal or local providers as the market requires
Tax and shipping configured against your real rules, including GST or VAT where applicable
Integrations with inventory, accounting or fulfilment systems
Checkout tested on real devices, including the failure paths
Analytics with ecommerce tracking so you can see where orders are lost
Built with
Process
eCommerce projects start with the catalogue and the operations, not the design. We model products, variants, categories and the stock flow first, because those decisions constrain everything downstream and are painful to change once orders are flowing. A storefront can be restyled later; a catalogue restructure after launch means redirects for every product URL.
The standard nine stages — discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement, continuous improvement — apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Shopify, WooCommerce, or custom
Shopify
Fits: Most retail businesses — hosted, secure, reliable checkout, strong app ecosystem
Limits: Transaction fees, monthly cost, and checkout customisation is restricted below Plus
WooCommerce
Fits: Content-led stores and businesses already on WordPress wanting full control
Limits: You own hosting, security and updates; plugin conflicts are your problem
Custom / headless
Fits: Unusual product models, high volume, or commerce embedded in a larger application
Limits: Highest build cost and ongoing engineering commitment
Case studies
No published eCommerce case study yet. Revenue figures are the most commonly exaggerated numbers in this field; we will publish none until we can show a real one with permission.
MBGDesk operates from 4 offices — India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Shopify or WooCommerce?
It depends on who maintains it and what you sell. Shopify if you want the platform to handle hosting, security and PCI compliance and you can live with the fees. WooCommerce if content and SEO lead the business, you want no transaction fees, and you have someone to keep it updated. We pick based on your situation, not a preference.
Can you migrate our existing store?
Yes. The work is in the data and the URLs, not the design. Product data usually needs cleaning, and every old product and category URL needs a mapped redirect or you lose the search visibility the old store built up.
Do you handle payment gateways?
Yes — Razorpay and UPI for India, Stripe and PayPal internationally, and local providers where a market needs them. Which gateway suits you depends on your market, currencies and settlement requirements.
How do you handle GST or VAT?
Tax is configured against your actual obligations and, where appropriate, integrated with your accounting system. We will not guess at your tax position — that is a question for your accountant, and we build to what they specify.
Will the store be fast?
That is mostly a function of discipline rather than platform. Heavy themes, unoptimised images and a long tail of apps are what slow stores down. We set a performance budget at the start and check against it before launch.
Can you improve conversion on our existing store?
Often, and usually in the checkout and the product page rather than the homepage. We start by looking at where people actually drop out in your analytics, not by redesigning what looks oldest.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.