What's included
OutsourcingVN is operated by Netbase JSC, and this page describes Netbase's own e-commerce service: a project that builds a new storefront, extends an existing one, or replatforms a store from one engine to another, each scoped as its own milestone rather than one open-ended commitment. A catalogue and checkout, a chosen integration set, and a migration path when an existing store moves, are scoped in discovery before a contract is agreed.
-
New build
A catalogue, cart, checkout and the integrations a launch needs, built from a blank store on the chosen platform.
-
Extension
A module, integration or workflow added to a store that is otherwise staying put.
-
Replatform or migrate
Moving an existing store to a new engine or a new major version, with data, catalogue and extensions carried across and checked rather than assumed to transfer unchanged.
-
Post-launch support
A defined window of fixes, monitoring and the first round of operational issues a new or migrated store surfaces.
Every Netbase offer, including this one, is listed on the services hub.
Which platform fits: Magento, WooCommerce or headless?
Magento, WooCommerce and a headless, API-first architecture are different starting points, not different qualities of work. Magento suits a catalogue running into the thousands of SKUs or B2B pricing rules; WooCommerce suits a smaller catalogue already living on WordPress, or a print business adding an online design tool; a headless build, commonly rendered in Next.js, suits a store that needs several channels or an independent release cycle. The Magento vs WooCommerce guide compares the first two platforms head to head, and headless vs traditional e-commerce covers the architecture decision once a platform is chosen, or nearly so. An existing store deciding whether a move is worth making at all starts with the e-commerce platform modernization checklist.
Is this the right project for your store?
Good fit
- A new storefront, a platform migration or a bounded extension with a scope that can be named
- The catalogue, checkout and integration list can be described before work starts
- A migration carries data, extensions and customer accounts that need parity evidence against the old store
- A print or personalisation business needs an online design tool bolted onto checkout — see web-to-print platforms
Another route fits better
- An existing store only needs a security fix, an extension upgrade or a single integration — legacy application modernization is usually the cheaper path
- Nobody can yet say what the store needs to do, and the honest first step is a discovery engagement on its own
- The build is really a companion mobile app on top of a store that already works — see mobile commerce apps
- The workflow has little to do with catalogue and checkout, and a different service fits better
Delivery modules
-
Catalogue and checkout
Products, variants, pricing rules, cart and checkout, built fresh or carried over from the previous platform.
-
Integrations
Payment gateways, ERP or stock feeds, marketing and loyalty systems, connected through the platform's own API or a custom layer where none exists.
-
Migration
For a replatform, data, catalogue, customer accounts and extensions are moved and checked against the old store rather than assumed to carry over.
-
Post-launch support
A defined window of fixes and monitoring once the store is live, scoped as its own line in the proposal.
For custom development, the client owns the IP created for it; Netbase's own productized modules, where a build reuses them, are licensed rather than transferred. Reusing those modules can cut development time by up to 60%.
How the project runs
-
Choose the platform and scope the migration
Confirm Magento, WooCommerce or a headless build, and for an existing store, list every extension, integration and data set that has to move.
-
Build or migrate behind the storefront
Catalogue, checkout and integrations are built or carried across, with the old store still live until the new path is checked.
-
Test and reconcile
Orders, payment routes and migrated data are checked against the old store, or against the agreed specification for a new build, before cutover.
-
Launch and support
The store goes live in a planned window, with a defined post-launch support period covering fixes and monitoring.
Where AI fits on a commerce store, and where it runs
The clearest AI wins on a commerce store are catalogue search, product-attribute enrichment and a support assistant that answers order-status questions before a ticket opens; none of it replaces the checkout and pricing engine the platform already owns. Netbase engineers and operates cloud environments on AWS, Google Cloud, DigitalOcean and Cloudflare, choosing the provider per workload.
What Netbase has already delivered
For Netztech, Netbase delivered a Magento 1 to Magento 2 Commerce migration in 35 working days, migrating 11 extensions with installation, configuration, customization and data transfer; see the Netztech migration record. For an existing client store, Netbase separately scoped a three-phase recovery of a compromised Magento site — investigation and a damage assessment, cleaning and system recovery, then file restore and hardening — typically 6 to 13 days depending on the damage; see the Magento recovery and hardening record.
For a Dubai-based loyalty and rewards technology company that is not named, Netbase delivered a headless multi-store reward shop platform on Magento 2 Open Source with a Next.js front end: individually branded reward shops per client programme, a hybrid points-plus-cash checkout, a multi-vendor module with fulfilment routing, Arabic and English, and mobile SDK interface components for client apps, delivered in four phases over 3.5 to 4.5 months; see the loyalty reward shop record.
For 4over4, Netbase delivered a product recommendation engine that suggests products from browsing history and previous purchases, plus an automated workflow that converts uploaded Adobe Illustrator files into editable SVG templates; see the 4over4 conversion record. The published case for that store reports revenue up 82% within six months, conversion up 48%, average order value up 35%, production time down 40%, 200+ templates added within three months and fulfilment time down 50%, figures from that one store and not a benchmark for another buyer.
PrintLeo, an e-commerce and advertising company, runs the CMSmart WordPress Printshop package with its online design plugin, delivered by Netbase. For a large-format inkjet printer in Singapore that is not named, Netbase redeveloped most of the store's own system on a WordPress print-store feature set over several phases and more than a year. Netbase has delivered 50+ custom web-to-print platforms across apparel, packaging, signage, promotional merchandise and corporate B2B portals, building web-to-print platforms since 2012. Representative Magento stores with companion Android and iOS apps serve a women's fashion retailer in the Netherlands, an omnichannel fashion retailer in Nigeria and a parts and equipment seller.
Which questions should you ask a commerce development vendor?
- Which platform fits your catalogue size, B2B needs and team skills, and why that one over the alternatives?
- For a migration, how will every extension and data set be checked against the old store before cutover?
- What does the post-launch support window cover, and for how long after launch?
- Who owns the code, and any licensed module, once the store ships?
- How does AI fit the catalogue or support workflow on this store, and where does it stop?
What goes wrong in an e-commerce build or migration?
-
Platform chosen before the catalogue is understood
Choosing Magento for a hundred SKUs, or WooCommerce for a multi-store B2B catalogue, moves the cost somewhere else rather than removing it.
-
Extensions assumed to carry over
Each one has to be reinstalled, reconfigured and checked on the new platform or version, not copied across unchanged.
-
Checkout tested with one payment route
A secondary gateway or a tax rule fails in the first week live, after the team has stopped watching closely.
-
Post-launch support left unscoped
The coverage and length of the support window need agreeing before launch, not after the first issue arrives.
Frequently asked questions
Yes. Platform choice is usually the first milestone, scoped against your catalogue, B2B needs and team skills before any build work starts.
Yes. A migration carries data, catalogue, customer accounts and extensions from the old platform to the new one, checked for parity rather than assumed to transfer unchanged.
Each one is listed, reinstalled or replaced, and reconfigured on the target platform or version; an extension with no supported version for the target becomes its own small piece of work.
Not by default. A companion shopping app built on your store's API is scoped separately; see mobile commerce apps for that workflow.
The length and coverage are agreed in the proposal and vary by project; it is scoped as its own line item, not assumed.
You do, for the custom development created for you. Any licensed Netbase module is identified in the proposal before you accept it.
Ready to scope your store?
Bring your current platform, your catalogue and the integrations you depend on to a brief. Submit a project and a person will reply with the platform fit and what discovery would check first. OutsourcingVN is Netbase's own outsourcing-services platform.