B9 Solution builds online stores as complete commerce systems: the storefront customers browse, the checkout and payments that take the order, and the inventory, shipping and business systems that fulfill it. We help you choose the right foundation, whether that is Shopify, WooCommerce or a custom build, and set it up so your team can run it day to day.
Every project is scoped and quoted individually, after a conversation about your store.
We build onShopifyWooCommerceCustom builds
yourstore.example/collections/home-kitchen
yourstoreShopCollectionsNew inSearch mugs
Everyday ceramics
Mugs, bowls and serveware
Shop the range
New
Stoneware mug
₹1,299
Trail sneaker
₹3,499
Table lamp
₹2,899
Linen tote
₹899
Stoneware mug
₹1,299incl. taxes
SL
In stock · delivery to 110001
Add to cart
UPI·Cards·COD
Order #1042Packed
Stoneware mug × 2Committed
Trail sneaker × 1Committed
PaymentConfirmed
Inventory updatedUPI payment received
Illustration · sample products and data · not a B9 client project
The whole commerce chain, not just the storefrontMost ecommerce problems sit between these parts, not inside any one of them.
StorefrontWhat customers see and use
Product discoveryNavigation, search, filters
CheckoutCart, address, shipping, tax
PaymentsGateways and local methods
InventoryStock states and sync
IntegrationsERP, CRM, accounting, logistics
FulfillmentPacking, shipping, returns
Reviews, Certifications & Partnerships
02Portfolio
Our Ecommerce Development Portfolio
Selected ecommerce projects will appear here, each with the platform it runs on, the scope of the build and what was developed beyond the platform's standard features: custom functionality, integrations and the storefront itself.
project-address.example
Desktop preview
Mobile
Featured project
Project name and one-line summary
Project type
To be supplied by B9New store, redesign or migration
Verified platform
To be supplied by B9Only a platform B9 built the project on
Development scope
To be supplied by B9What B9 built or changed
Custom functionality
To be supplied by B9Anything beyond standard platform features
Integration details
To be supplied by B9Systems the store was connected to
Case study
To be supplied by B9Link to an approved case study, if one exists
An approved case-study link appears here when one exists.
project-address.example
Storefront preview
Project two
Project type
To be supplied by B9
Verified platform
To be supplied by B9
Development scope
To be supplied by B9
Custom functionality
To be supplied by B9
Integration details
To be supplied by B9
project-address.example
Storefront preview
Project three
Project type
To be supplied by B9
Verified platform
To be supplied by B9
Development scope
To be supplied by B9
Custom functionality
To be supplied by B9
Integration details
To be supplied by B9
03Business models
Ecommerce Solutions for Different Business Models
Ecommerce is not one thing. A wholesale store, a subscription box and a multi-vendor marketplace each change how the catalog is structured, who sees which prices, how orders are billed and how stock is fulfilled. Choosing the model first stops a good build solving the wrong problem.
yourstore.example
yourstoreShopNew2
Stoneware mug
₹1,299
Trail sneaker
₹3,499
Linen tote
₹899
01
B2C Ecommerce
Selling to individual shoppers, usually across many products, with prices and stock visible to everyone.
An open catalog that search engines and ads can reach, with guest checkout and public prices.
The work is in discovery: category structure, filters, product pages and a short mobile path to payment.
Plan for Merchandising, mobile conversion paths and a clear returns policy.
yourbrand.example/build-a-set
Build your set3 of 4 chosen
Made in small batches. Pick four.
+
One timeDeliver every month
Add set to cart
02
Direct-to-Consumer (D2C)
A brand selling its own products straight to customers, so the store carries the brand as well as the transaction.
Storytelling, bundles and first-party customer data matter as much as the catalog.
The brand owns the relationship: accounts, reorders, lifecycle email or WhatsApp, and its own fulfillment or 3PL.
Plan for Bundles, reorder paths and retention content from the start.
trade.yourstore.example
Sample Trading Co.Distributor price list
SKUPackYour priceQty
MUG-S-1212₹84024
MUG-L-1212₹96012
TIN-066₹4100
Paste SKUs for quick orderRequest a quote
03
B2B Wholesale
Selling to businesses: repeat orders, negotiated prices and buying done by accounts, not individuals.
The catalog may be login-gated, with customer-specific price lists, tiers and minimum order quantities.
Buyers need quick order by SKU, reorder from history, purchase orders or credit terms, and GST invoices.
Plan for Which system owns price lists and credit terms, and how new trade accounts are approved.
yourstore.example/account/subscription
Monthly tea selectionActive
Active
Deliver every
2 weeksMonth2 months
Next delivery · Fri 12 Nov (sample)
SkipSwapPause
04
Subscription Commerce
Products delivered on a schedule and billed repeatedly, so the customer account becomes the product.
Plans and frequency are part of the product; customers manage skips, swaps, pauses and cancellation themselves.
Recurring billing needs payment-provider support, local recurring-payment rules and failed-payment recovery.
Plan for The billing provider's capabilities, before the platform is chosen.
market.example/vendor/dashboard
VendorProductsOrdersPayouts
Awaiting approval
Table lampApproveReject
Planter setApproveReject
Commission set per category · payouts on a schedule
05
Multi-Vendor Marketplaces
One store hosting many independent sellers, with the operator earning a commission.
Vendors onboard, upload their own catalogs and need approval workflows and moderation.
Payments split between operator and vendors, fulfillment and returns run per vendor, and vendors need their own dashboard.
Plan for The operating model and its obligations, before any software is chosen.
yourstore.example/products/table-lamp
Table lamp₹2,899
Store A · 2 kmIn stock
Store B · 6 kmLow stock
Store C · 11 kmOut of stock
Reserve in storeDeliver to me
06
Hybrid Retail and Omnichannel
Physical stores and online selling working from one view of stock, customers and orders.
Stock is visible per location, with click-and-collect and, where it makes sense, ship-from-store.
Point-of-sale and online orders reconcile, and a return can be accepted in whichever channel the customer chooses.
Plan for Which system owns inventory, and how the point-of-sale connects.
Illustrations with sample data; not B9 client projects.
How the six business models differ in practice
The same storefront technology behaves very differently depending on the model. These are the dimensions that change.
Ten services in three groups, from the first build to the years after launch. They sit within B9's wider web development and web design work. Choose a service to see what it covers, what has to be decided and which parts of the commerce chain it touches.
Service 01 of 10
Custom Ecommerce Website Development
A store built around your products, customers and operations, on the platform that suits them.
We start from the business, not the template. We define the catalog model, the buying journey, checkout rules and the systems the store must talk to, then choose between a standard platform, a customized platform or a custom build. The result is a store your team can manage day to day, with the technical decisions written down for whoever maintains it next.
What it covers
Requirements and catalog model
Platform choice and store architecture
Storefront design and development
Checkout, payment and shipping set-up
Testing and launch support
What gets decided
Standard, customized or custom build?
What must work on day one, and what can wait?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Storefront, Product discovery, Checkout, Payments, Inventory, Integrations, Fulfillment.
Service 02 of 10
Ecommerce Storefront Development
The customer-facing layer: themes, templates and interface components, fast on phones and editable by your team.
The storefront is where catalog structure becomes a buying experience: category and collection templates, product pages with variant logic, search and filter interfaces, the cart and mini-cart. On Shopify that means theme development, on WooCommerce theme and template work, on a custom build a purpose-built front end. We keep templates lean so pages stay fast and your team can update content without breaking layouts.
What it covers
Category, collection and product templates
Variant, size-guide and media components
Search, filter and sort interfaces
Mobile-first, keyboard-friendly layouts
Content blocks your team can edit
What gets decided
Which templates are unique, and which stay standard?
How much can the team edit without a developer?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Storefront, Product discovery, Checkout.
Service 03 of 10
Ecommerce Website Redesign
Improving an existing store's structure, templates and journeys without losing what already works.
A redesign begins by finding what the current store already does well: pages that earn traffic, templates people use, URLs that other sites link to. We then rework navigation, product and category templates and checkout where the evidence shows they hold customers back, and plan URL and tracking continuity so the redesign does not reset what the store has built.
What it covers
Review of analytics, search data and user paths
Navigation, category and product page redesign
Checkout and mobile experience improvements
URL, redirect and tracking continuity plan
Phased release where the store cannot pause
What gets decided
Redesign on the current platform, or move?
Which pages must not change address?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Storefront, Product discovery, Checkout, Integrations.
Service 04 of 10
Shopping Cart and Checkout Development
Cart rules, checkout flow, payment, tax and shipping logic that match how you actually sell.
Standard checkouts cover most stores. When yours does not, because of COD rules, B2B terms, order minimums, custom shipping logic or unusual product rules, the cart and checkout need design and development. We map the rules first, build second, and test the unhappy paths third: failed payments, address errors, stock running out in the middle of an order.
What it covers
Cart behavior, discounts and stacking rules
Checkout steps, guest and account flows
Payment gateway integration and failure handling
Shipping zones, rates and tax configuration
Order confirmation and notification flows
What gets decided
Which rules live in the platform, and which need custom code?
What happens when payment fails or stock runs out?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Checkout, Payments, Fulfillment.
Service 05 of 10
Product Catalog Development
Product, variant, attribute and collection structure, with your existing data cleaned and imported.
A catalog is a data model before it is a page. We design product types, variants and attribute sets, set up collections and navigation logic, and prepare a bulk import of your product data with validation, so filters, feeds and reports work from day one. For an existing store we clean and map the data rather than carrying its problems across.
What it covers
Product types, variants and attribute sets
Collections, categories and navigation logic
Bulk import and data validation
Image and media organization
Merchant editing workflow
What gets decided
Which attributes drive filtering, and which are display only?
Who maintains product data after launch?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Product discovery, Inventory.
Service 06 of 10
Ecommerce Integrations
Connecting the store to payment, shipping, inventory, CRM, email and analytics tools.
We connect the store to the systems the business already runs, using the platform's own functionality, an app, a configured connector or custom API development, whichever fits. Each integration is specified with a source of truth, a failure path and an owner, so it keeps working after launch and someone knows what to do when it does not.
What it covers
Payment gateways and shipping tools
Inventory and order data flows
CRM, email and marketing platforms
Analytics and ecommerce event tracking
Custom integration through REST or GraphQL APIs
What gets decided
App, configured connector or custom development?
Which system owns each kind of data?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Payments, Inventory, Integrations, Fulfillment.
Service 07 of 10
Ecommerce Portals
Account areas and portals for repeat customers, trade buyers or internal teams.
Where customers or trade buyers need more than a standard account page, such as reorders, order history, price lists, quotes or document downloads, a portal layer sits on top of the store. It may be a platform feature, an app or a custom-built application connected through APIs. The choice depends on how much logic sits in the portal and where the data lives.
What it covers
Customer and company accounts with roles
Order history, reorder and returns requests
Price lists, quotes and approval flows
Document and invoice downloads
Connection to ERP or CRM data
What gets decided
Platform feature, app or custom portal?
Where does price and account data live?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Storefront, Checkout, Integrations.
Service 08 of 10
Ecommerce Migration
Moving a store to a new platform, with data, URLs and integrations planned and checked.
A migration is a project in its own right: products, customers and orders are mapped to the new data model, URL redirects are planned, payment and shipping configuration is rebuilt, integrations are replaced or reconnected, and everything is tested before switching over. We plan for what can and cannot be moved cleanly and tell you before launch, not after.
What it covers
Platform evaluation and migration plan
Product, customer and order data mapping
URL mapping and redirect planning
Payment, shipping and integration rebuild
Pre-launch testing and launch validation
What gets decided
What history is moved, and what is archived?
What changes on the day, and what must stay as it is?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Storefront, Product discovery, Inventory, Integrations.
Service 09 of 10
Performance and Technical Improvements
Measured improvements to speed, mobile behavior and technical health, on your real templates.
We measure Core Web Vitals and page behavior on your real templates, find what slows them (oversized images, unused scripts, heavy apps, theme code) and fix the causes. We also review structured data, the crawlability of category and filter pages, and the accuracy of tracking. We do not promise a score, because results depend on the platform, the apps and the content.
What it covers
Core Web Vitals review on real templates
Image, script and app clean-up
Caching and delivery configuration where it applies
Product and category structured-data review
Analytics and ecommerce event audit
What gets decided
Which templates carry the most traffic and orders?
Which apps earn their weight?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Storefront, Product discovery, Checkout.
Service 10 of 10
Maintenance and Technical Support
Updates, fixes, minor changes and improvements after launch, agreed for each store.
After launch a store needs platform and plugin updates, bug fixes, small changes and sometimes new features. Ongoing maintenance is available, and its scope is agreed for your store: what it covers, who does what and how requests are handled. If your team would rather take over, we hand over the access and documentation they need.
What it covers
Platform, theme and plugin updates where they apply
Bug fixes and technical support
Minor changes and improvements
Integration monitoring where agreed
Handover documentation and access
What gets decided
Retainer, as-needed work or in-house?
What counts as a fix, and what as a new feature?
Parts of the commerce chain this service works on
Storefront
Product discovery
Checkout
Payments
Inventory
Integrations
Fulfillment
Works on: Storefront, Integrations.
05Platforms and technologies
Ecommerce Platforms & Technologies: Choosing the Right Foundation
There is no universally right platform, only the one that fits your products, your team, your running costs and where you plan to grow. Compare on fit, not on feature lists. This is an educational comparison: it does not mean B9 builds on every platform shown.
Shopify
Hosted platform (SaaS)
B9 builds on this
Suited toTeams that want to run a store without managing hosting, with a large app ecosystem and a standard checkout.
Merchant editing
Strong: an admin built for merchants, with section-based theme editing.
Customization
Theme and app level. Deeper checkout and back-end changes are limited by plan.
Integrations
A large app store plus APIs. Many integrations are paid subscriptions.
Technical complexity
Low to moderate, rising with custom apps and complex B2B needs.
Maintenance
The vendor handles hosting and core updates. Apps and themes still need review.
Subscription and licensing
Monthly plan, app subscriptions and transaction or gateway fees. Confirm current terms.
Migration implications
Import tools exist for common data. URL patterns are fixed by the platform, so redirects matter.
WooCommerce
Open-source plugin for WordPress
B9 builds on this
Suited toContent-led businesses already on WordPress, and stores with unusual product or checkout rules.
Merchant editing
Familiar WordPress editor. Store management is capable but depends on the extensions chosen.
Customization
High: open code, hooks and a large extension library. Every customization is yours to maintain.
Integrations
A wide range of extensions and APIs. Quality varies by extension.
Technical complexity
Moderate, growing with extensions, hosting needs and customization.
Maintenance
You own updates, security patches, backups and hosting performance, or contract them.
Subscription and licensing
The core is free. Hosting, premium extensions and payment fees apply.
Migration implications
URLs are flexible, which helps preserve them. Import tools exist, but product data quality varies.
Adobe Commerce Magento
Adobe Commerce (Magento)
Licensed or open-source platform, self-hosted or cloud-managed
Compared for reference
Suited toLarge catalogs, multi-store setups and complex B2B requirements, with the technical budget to match.
Merchant editing
Powerful but heavier admin. Merchants usually need training.
Customization
Very high, through extensions and custom modules.
Integrations
Extensive. ERP and enterprise integrations are common.
Technical complexity
High. Needs experienced developers and infrastructure.
Maintenance
Security patches and upgrades are significant ongoing work.
Subscription and licensing
The open-source edition is free to license, with hosting and development to pay for. Adobe Commerce is licensed by Adobe at a price Adobe sets, and what hosting includes depends on the package. Confirm current terms.
Migration implications
Large data volumes and extension dependencies make a move in or out a project of its own.
BigCommerce
Hosted platform (SaaS)
Compared for reference
Suited toGrowing stores that want hosted simplicity and built-in catalog tools. B2B features vary by plan and add-on, so confirm what each plan includes.
Merchant editing
A merchant-friendly admin with a theme editor.
Customization
Theme and API level. The platform sets the boundaries.
Integrations
Native features, apps and open APIs. Works with headless set-ups.
Technical complexity
Low to moderate.
Maintenance
The vendor maintains the platform. Apps and themes still need review.
Subscription and licensing
Plan-based pricing, which can depend on sales volume. Confirm current terms.
Migration implications
Import tools exist. URL patterns differ from other platforms and need redirects.
Custom ecommerce development
A bespoke store or application
B9 builds on this
Suited toBusiness models or workflows that standard platforms cannot express without heavy workarounds.
Merchant editing
Whatever is built. The merchant admin has to be designed and tested, not assumed.
Customization
Open-ended in principle. Every feature is built, tested and maintained.
Integrations
Built to your systems, but each connection is development work.
Technical complexity
High. Needs product ownership, QA and security practice.
Maintenance
You own the code and its upkeep, including security updates and developer continuity.
Subscription and licensing
No platform license, but build and running costs are higher and continuing.
Migration implications
Full control of URLs and data, with all migration work done by hand.
Headless commerce architectures
An architecture pattern, not a product
Compared for reference
Suited toTeams that need a bespoke front end, several channels, or performance control the platform's theme layer cannot give.
Merchant editing
Depends on the content tooling chosen. Editors may need a separate CMS.
Customization
Very high on the front end. Back-end rules stay those of the commerce platform.
Integrations
API-based. Flexible, but every integration is built and monitored.
Technical complexity
High. Two systems to build, host, secure and keep in step.
Maintenance
Front end and platform are maintained separately, with API versions to track.
Subscription and licensing
Commerce platform fees plus front-end hosting and development.
Migration implications
A front-end rebuild with URL mapping. The commerce back end may stay.
Platform marks identify the platforms for comparison only. They do not indicate partnership, certification or endorsement, and are shown in one neutral colour. No Adobe Commerce or Magento vector mark is available from the CC0 source used, so none is shown.
Choosing by situation
Tendencies, not rules. The right answer comes from a conversation about your products, team and running costs.
You want to sell soon and run the store yourself, with a standard checkoutA hosted platform such as Shopify
Your business already lives on WordPress, or checkout and product rules are unusualWooCommerce
A very large catalog, several stores or heavy ERP-led B2BAn enterprise-grade platform, or a custom build, once running costs are compared
Your selling model fits no platform without heavy workaroundsA custom build
You need a bespoke storefront, or several front ends on one commerce back endHeadless, after standard options have been ruled out
You are not sure yetA scoping conversation about products, team and running costs
Technologies B9's developers work with
The technologies below are the confirmed front-end, back-end, API and data stack behind custom ecommerce builds and integrations.
React
Vue.js
Node.js
PHP
Laravel
GraphQL
MySQL
PostgreSQL
Working with a technology is not a partner status or certification.
Few customers arrive on the product they end up buying. They land on a category, a search result or an ad, narrow the range, compare, and only then commit. A well-built storefront shortens that path and removes the doubts along it. The catalog behind it, the structure of products, variants and attributes, decides how much of that is possible at all.
1
Step 1: Category
Category and collection pages
yourstore.example/home-kitchen
yourstore
Home › Kitchen › Home & kitchen
Home & kitchenSort: Featured ▾
AllMugsLightingStoragePlanters
Stoneware mug
₹1,299
Table lamp
₹2,899
Planter set
₹1,099
Storage jar
₹749
Load more products
The first screen after an ad or a menu click. It has to show the range, not hide it behind decoration.
Category tree and collection rules, manual or rule-based
Breadcrumbs, short intro copy and featured slots
Mobile category navigation that works with one thumb
Clean category URLs designed with search in mind
2
Step 2: Search & filter
Search and filtering
yourstore.example/search?q=stoneware+mug
stoneware mug
Colour ▾Size ▾Price ▾✓ In stock
ColourSizeSLPrice₹800 to ₹2,000
4 results · most relevant first
Mug, Sand
₹1,299
Mug, Slate
₹1,299
Mug, Sage
₹1,349
Mug, Clay
₹1,349
Filters should follow how people actually choose, such as size, material or compatibility, not only the fields in the database.
Product search with relevant results and sensible empty states
Facets, sorting and filter state kept in the URL
Variant-aware results, so the colour that matched is the one shown
Behavior on slow mobile connections
3
Step 3: Product detail
The product page
yourstore.example/products/stoneware-mug
Home › Home & kitchen › Stoneware mug
Stoneware mug₹1,299incl. taxes
ColourSizeSmallLarge
Delivery PIN 110001Check
✓ Delivery available · COD available
Add to cartSave for later
Details and care+
Delivery and returns+
Where doubts get answered: images, options, specifications, delivery and return information.
Image gallery and zoom, with video where it helps
Variant selectors with clear stock and availability states
Structured descriptions, specifications and size guides
Delivery check by PIN code and return information
4
Step 4: Product selection
Choosing and adding to cart
yourstore.example/cart
Added to your cart
Stoneware mugSand / Large · Qty 1In stock
₹1,299
Complete the set
Tea tin
₹699
Honey jar
₹449
Subtotal₹1,299
ShippingCalculated at checkout
Continue shoppingGo to checkout
The moment of commitment. Confirm the choice, show what happens next and keep the way to checkout open.
Add-to-cart confirmation or a mini-cart
Variant and stock validation before the cart
Bundles, cross-sells and comparison where they help
Wishlist or save-for-later where the platform supports it
Illustrations of a fictional store. Sample products, prices and data; not a B9 client project.
Catalog design decides what the storefront can do
Filters, feeds, reports and merchandising all read from the catalog. Getting its structure right before data entry is cheaper than repairing it after launch.
Variants and options
Colour, size or material change the SKU, price, image and stock. Model them once, correctly, and every filter, feed and report downstream stays consistent.
Attributes and specifications
Attributes make filtering and comparison possible. A mug has capacity and material; a brake disc has diameter and vehicle fitment. Decide the attribute set before data entry begins.
Descriptions and content
Descriptions that answer purchase questions in a consistent structure your team can maintain. Not a wall of text, and not a copy of the supplier feed.
Images and media
Consistent aspect ratios, a sensible number of views per product, responsive image delivery and alt text that describes the product.
Mobile browsing
Most browsing happens on phones. Sticky filters, thumb-reachable controls, quick category scrolling and a product page that does not need pinch-zoom.
Merchandising pathways
Collections, "complete the set" and related-product logic that follow real buying relationships, and that a merchandiser can edit without a developer.
Comparison tables help when products differ on specifications, as with electronics and tools, and add clutter when they do not, as with most apparel. We add them where they shorten a decision.
One product, four sellable SKUs
A "Stoneware mug" in two colours and two sizes is one product page and four SKUs. Each SKU has its own stock level; price and images can differ.
Stoneware mugOne product page
ColourSandSlate
SizeSmallLarge
Sand / Smallown stock · own price
Sand / Largeown stock · own price
Slate / Smallown stock · own price
Slate / Largeown stock · own price
Illustrative catalog structure.
07Checkout and operations
Shopping Cart, Checkout, Payments & Order Fulfillment
Choosing a product is the easy part. What follows is a chain of rules and handoffs: totals, tax, shipping, payment, stock, notifications, packing, delivery and sometimes a return. Each link has to be designed and tested, because a store is judged by what happens after the customer clicks Pay.
Stage 01
Cart
Totals the customer can trust
Line items, quantities and variant stock checks
Coupon and discount rules, including stacking limits
Shipping and tax estimates before the checkout step
Cart persistence across sessions and devices where supported
Stage 02
Checkout
Fewest steps, clearest errors
Guest and account checkout paths
Address capture with PIN-code validation
GSTIN capture for business buyers, where tax invoices need it
Shipping method and delivery options by location
Stage 03
Payment
Money moves and state stays correct
Gateway integration and payment-method selection
UPI, cards, net banking, wallets, EMI and Cash on Delivery where the platform, plan and gateway allow
Failed-payment and retry handling, and payment confirmation callbacks
Saved-card and recurring-payment rules that follow current regulation
Stage 04
Order processing
The order becomes a record
Order creation, numbering and status
Inventory reserved, then committed or released
Confirmation by email and, where configured, SMS or WhatsApp
COD verification and fraud-screening rules where used
Stage 05
Fulfillment
From shelf to doorstep and back
Pick, pack and dispatch workflows
Courier or aggregator handoff, tracking and delivery updates
Returns, exchanges and refund handling
Stock restored when a return is accepted
Order summarySample data
Stoneware mug, Sand / Large× 2
Trail sneaker, UK 8× 1
Subtotal
From the cart
Discount
By rule
Shipping
By zone and weight
Tax lines
As configured
Total payableCalculated at checkout
The summary shows structure, not figures. Real totals come from the rules configured for the store.
Payment methods a store may offer
UPICommon in India; intent and merchant-collect flows differ by gateway
CardsDebit and credit; saved-card rules apply
Net bankingBank redirect, with failure handling
WalletsWhere the gateway supports them
EMISubject to issuer and gateway rules
Cash on DeliveryNeeds verification and a refusal policy
Availability depends on the platform, plan, payment gateway, product type and country. Nothing here implies that every method is available on every setup.
How stock moves through an order
AvailableCan be sold
ReservedHeld while a customer pays
CommittedOrder confirmed, stock allocated
ReleasedBack to available if payment fails, expires or the order is cancelled
RestockedReturned item accepted back into stock
Order statuses a customer and a warehouse can both read
Placed
Confirmed
Packed
Shipped
Delivered
If a return is raised
Return requested
Received
Refunded or exchanged
Checkout decisions that are specific to India
UPI placement and failure handling
UPI is a common way to pay in India, so where it sits in the payment list, and what happens when an app switch fails, deserves design attention.
Cash on Delivery
COD changes the economics. It needs verification steps, a refusal policy and often a different shipping rule. Decide whether to offer it, for which products and PIN codes, and at what fee.
GST and invoices
Tax lines and invoices should match how your accountant needs them: GSTIN capture for business buyers and invoice numbering that fits your filing. Confirm the rules with your accountant.
PIN-code serviceability
A delivery promise depends on whether a courier serves the PIN code, whether COD is available there and what it costs. Checking at the product page and the cart avoids surprises at payment.
Card and recurring-payment rules
Regulation on storing card details and on recurring card or UPI payments shapes saved cards and subscriptions. The payment provider's current rules decide what is possible.
Not every payment method, tax feature or checkout option exists on every platform or plan. During scoping we confirm what your chosen platform and gateway support before the design depends on it.
08Connected operations
Ecommerce Integrations & Connected Business Operations
A store that runs on re-keyed spreadsheets stops scaling long before its traffic does. Integrations decide which system is the source of truth for products, stock, customers and orders, and how every change travels between them.
Storefront
Commerce platformShopify, WooCommerce, custom or headless
CatalogCustomersOrdersCheckout
Native
Payment gateways
Third-party app
Marketplace connectors
Marketing automation
CRM
Inventory / WMS
Configured
Analytics
Accounting
Shipping & logistics
Custom development
Product information (PIM)
ERP
Order management
Native platform functionality
Works out of the box or through settings on your plan. Lowest effort to run, but limited to what the platform offers.
Ask Is it available on our plan, and in India?
Third-party application
An app or plugin from the platform's ecosystem. Quick to adopt; adds a subscription, an update dependency and another vendor.
Ask Who maintains it, and what happens if it is discontinued?
Configured integration
Two systems connected through their supported connectors, webhooks or automation tools, with mapping rules set up and tested.
Ask Which system is the source of truth for each field?
Custom integration development
Code written against the systems' APIs when no suitable connector exists. Fits unusual rules, costs more to build and must be maintained like any software.
Ask What are the failure and retry rules, and who monitors them?
One possible set-up. The real type of each link depends on the platform, the systems you already run and what suits them.
What connects to what, and how
Eleven business systems that connect to an ecommerce platform: what moves, in which direction, and the ways each is commonly connected
System
What moves
Direction
Commonly connected through
Marketplace connectors
Listings, stock and orders between the store and marketplaces
Two-way
Third-party appCustom development
Marketing automation
Customer, cart and order events to email, SMS or WhatsApp tools
Store to tool
Third-party appConfigured
CRM
Customers, orders and enquiries, so sales and support see one history
Store to CRM
Third-party appConfiguredCustom development
Analytics
Ecommerce events from storefront and checkout to GA4 through Tag Manager
Store to analytics
NativeConfigured
Payment gateways
Payment requests, confirmations, failures and refunds
Two-way
NativeConfiguredCustom development
Product information (PIM)
Master product data, attributes and media published to the storefront
PIM to store
Third-party appCustom development
ERP
Products, prices and stock from the ERP; confirmed orders back to it
Two-way
ConfiguredCustom development
Inventory / WMS
Stock per location; reservations and adjustments from orders and returns
Two-way
NativeThird-party appCustom development
Accounting
Invoices, payments, tax lines and refunds, so the books match the store
Store to accounting
Third-party appConfigured
Order management
Order routing, splits, status changes and exceptions across warehouses or stores
Two-way
Third-party appCustom development
Shipping & logistics
Rates, serviceability, labels, tracking numbers and delivery status
Two-way
Third-party appConfiguredCustom development
Name one source of truth
For products, prices, stock, customers and orders, exactly one system is authoritative. Most sync bugs are two systems that both believe they are.
Design for failure, not just success
What happens when an API is down, a webhook arrives twice or a stock update arrives late? Retries, queues, duplicate protection and alerts are part of the integration, not extras.
Keep access and ownership in your name
API keys, app subscriptions and vendor accounts belong to the business. Documentation and a proper handover keep the integration maintainable by whoever comes next.
Moving a store is when it is most likely to lose search visibility, order history or working integrations. Much of that loss is avoidable, but only if the move is run as a project: what moves, what is rebuilt, what is retired, and how you will know it worked.
MigrationSame store, new platform.
RedesignNew design, same platform.
ReplatformingA new platform and a rethought structure together.
Current storeExisting platform, apps and custom code
New storeChosen platform and architecture
Products and variantsis treated as: Map and importand becomes: Product data in the new catalog model
Categories and collectionsis treated as: Rebuildand becomes: Navigation and collection rules
Historical ordersis treated as: Import or archiveand becomes: Order history, or a readable archive
Content pages and blogis treated as: Move and reviewand becomes: Pages in the new templates
Page URLsis treated as: Map and 301 redirectand becomes: New URL structure with tested redirects
Payment and shipping set-upis treated as: Rebuild and testand becomes: Gateways, rates, zones, tax
Integrationsis treated as: Replace or reconnectand becomes: Connectors or API integrations
Tracking and analyticsis treated as: Re-implement, verifyand becomes: Ecommerce events and tags checked
Illustrative. The real list follows from an assessment of the current store.
1
Assess and plan
Existing platform evaluationWhat the store does today, which apps and custom code carry it, and which of those the new platform replaces.
Store architecture planningThe target data model, templates, URL structure and integration approach.
URL mappingEvery URL that earns traffic or links, matched to its new address.
Redirect planningWhich redirects are permanent, how they are tested, and how redirect chains are avoided.
2
Move and rebuild
Product and category dataMapping, cleaning and importing, with counts checked against the old store.
Customer recordsWhat can move, what needs consent or a password reset, and what is left behind.
Historical ordersImported for reference, or archived where the new platform cannot hold them.
Content migrationPages, posts and media moved and reviewed in the new templates.
Payment configurationGateways, methods and failure handling rebuilt and tested.
Shipping set-upZones, rates, serviceability and carrier connections.
Integration replacementsEach old connection replaced, reconnected or retired on purpose.
3
Validate and launch
Functional testingOrders through every payment method, emails, accounts, returns and edge cases on staging.
SEO migration considerationsRedirects, canonical tags, metadata, structured data, sitemaps and indexing checks before and after the switch.
Launch validationA launch checklist, live checks on checkout and tracking, and monitoring in the days after.
What a migration cannot honestly promise
No migration can guarantee zero downtime, zero data loss, preserved rankings or preserved revenue, and a company that promises them is guessing. What good planning can do is reduce avoidable loss.
Complete URL mapping and tested redirects
Data checked against the old store, with differences reported
Three broad approaches sit behind most ecommerce projects. Each trades flexibility against complexity, and the right one is the simplest that meets your real requirements, not the most impressive.
Approach 1
Standard platform implementation
An established ecommerce platform used within its supported capabilities: its themes, checkout, admin and approved apps.
Theme and templatesPlatform-supported
Platform coreCatalog · cart · checkout · admin
Apps and extensionsPayments · shipping · marketing
Approach 2
Custom storefront or platform customization
An existing platform adapted to more specific requirements: custom themes, modules, checkout rules or an added application.
Custom theme and templatesBuilt for your journeys
Platform core, extendedCustom modules · rules
Custom app and integrationsBuilt against APIs
Approach 3
Headless or bespoke commerce architecture
A separated storefront and commerce back end joined by APIs, or a fully bespoke build, where the requirement justifies it.
Custom front endWeb · app · other channels
APIsThe connection between the two
Commerce back endPlus CMS, search, payments, ERP as services
The three approaches compared on seven points
Point of comparison
Standard
Custom
Headless or bespoke
Flexibility
Within what the platform allows
High, inside the platform's model
Highest on the front end
Complexity
Low to moderate
Moderate to high
High
Integrations
Apps and supported connectors
Connectors plus custom code
Built through APIs, one by one
Merchant usability
Designed for merchants
Good if the admin is extended with care
Depends on the tooling built or chosen
Maintenance
Mostly vendor-managed (hosted)
Platform updates plus your customizations
Two systems, maintained separately
Development scope
Set-up, theme, catalog, testing
Set-up plus custom design and code
Front-end build, API layer, hosting, testing
Long-term implications
Tied to the platform's roadmap and plan limits
Upgrades must keep your customizations working
Freedom, with developer dependency and a larger running cost
A balanced decision guide
Choose standard when
Your products, checkout and operations fit what a mainstream platform does well. It is the fastest route to a working store and the cheapest to run.
Consider customization when
The platform is right but one or two requirements are not: a checkout rule, a pricing model, a distinctive product page. Customize those, not everything.
Consider headless or bespoke when
A specific requirement forces it: several front ends, a front end the theme layer cannot deliver, or a business model that no platform expresses.
A caution
Headless is not automatically better
There is more to build, host, secure and keep in step.
Editors can lose visual previews and built-in features that a theme layer provided.
Every integration becomes your responsibility to monitor.
It needs developers who stay available for the life of the store.
Start with the simplest architecture that meets your requirements, and move up only when a specific, written requirement forces it.
11Technical foundations
Ecommerce Performance, Technical SEO, Security & Analytics
A store that is slow, hard to crawl, careless with checkout data or blind to its own funnel will underperform however good the design is. These are the technical foundations a development project should settle before launch, not after.
Performance and mobile usability
Speed on a mid-range phone and a patchy connection is the test that matters.
LCP2.5 s or lessLargest Contentful Paint
INP200 ms or lessInteraction to Next Paint
CLS0.1 or lessCumulative Layout Shift
The thresholds Google publishes as "good". They are targets to measure against, not promises.
Core Web Vitals reviewed on real category, product and checkout templates
Responsive layouts that work with one thumb
Image optimization: sizes, formats, lazy loading
Caching and delivery configured where the platform allows
Search-ready structure
Technical SEO for a store is mostly about how many near-duplicate pages the catalog can generate.
/
/category/
/category/sub-category/
/products/product-name/
Category and product page architecture with clean, stable URLs
Canonical tags for variants and filtered views
XML sitemaps and crawl rules that fit the catalog
Structured data for products, offers and breadcrumbs, used only with accurate data
Checkout security and accessibility
Practices that lower risk and widen who can complete a purchase. They are practices, not certifications.
Card entry kept on the payment provider's pages to reduce card-data handling
HTTPS everywhere, with admin access limited by role and protected sign-in
Platform, theme and plugin updates and backups on a schedule
Labelled form fields, visible focus and sufficient contrast through checkout
Practices, not certifications. No security or compliance outcome is promised.
Analytics and conversion-path measurement
If the funnel is not measured step by step, nobody knows where it leaks.
view_item_list
select_item
view_item
add_to_cart
begin_checkout
add_payment_info
purchase
Event names from Google's recommended ecommerce events for Google Analytics 4.
Ecommerce events set up and checked in Google Analytics 4 through Tag Manager
Each step of the path measured, from list view to purchase
Consent-aware tracking configured to the rules that apply
Analytics orders reconciled against platform orders
Ongoing ecommerce search strategy is a separate discipline: see Ecommerce SEO. Conversion optimization is a separate service as well. This section covers what the build itself should get right.
What nobody can honestly guarantee
Results depend on the platform, the apps, the content, the traffic and the competition. A development project can remove technical causes of poor results. It cannot promise the results themselves.
PageSpeed scores
Search rankings
Revenue
Conversion increases
Security outcomes
Compliance certifications
12Pricing and project scope
Ecommerce Development Pricing & Project Scope
B9 quotes each ecommerce project individually. There are no fixed packages, because two stores with the same number of products can need very different work. This section shows what changes the scope, so you can prepare for the conversation and read any quote with the right questions.
Scope planner
Choose what applies. The indicator describes how involved a scope is. It does not produce a price or a timeline.
After launch. Handover, training where included, and ongoing maintenance are agreed separately and sit outside the build scope above.
Your scope profile
Not yet chosen
Choose an option in each group to see the profile.
Your choices
Questions the proposal should answer
This is a planning aid. It is not a quote, a price or a timeline, and no figure is calculated.
A fashion store and an automotive parts store share a platform and almost nothing else. The catalog, the checkout, the shipping and the returns all change with what is being sold. These are the requirements that usually shape ten categories of store.
01 Size, fit and returns
Fashion and Apparel
Variants
Size and colour grids with stock per size, and a size guide that cuts wrong-size orders.
Returns
Return reasons, size-swap exchanges and restocking rules.
Merchandising
Lookbooks, outfit sets and fast seasonal collection changes.
Imagery
Several angles and fit information per product.
02 Shades, ingredients and sets
Beauty and Personal Care
Variants
Shade swatches, sizes and refills, each with its own stock.
Product detail
Ingredients, usage and skin-type information that answers purchase doubts.
Bundles
Sets, samples and gift options.
Stock
Batch and expiry dates handled in inventory, and label information shown as required.
03 Specifications and compatibility
Electronics
Specifications
Attribute tables, filters by technical features and comparison where products differ.
Compatibility
Accessories linked to the devices they fit.
After sale
Warranty registration and serial-number handling.
Payment
High-value orders: risk checks and EMI options through the gateway.
04 Large items, considered buying
Furniture and Home
Options
Dimensions, materials, fabrics and finishes, with room imagery.
Shipping
Bulky-item freight, delivery scheduling and assembly information.
Consideration
Wishlists, saved carts and swatch requests for long decisions.
Catalog
Product sets and collections by room or style.
05 Perishables and repeat orders
Food and Beverage
Stock
Batch and expiry dates, with the oldest stock sold first.
Shipping
Delivery windows, PIN-code serviceability and temperature control where needed.
Information
Ingredients, allergens and nutrition shown clearly.
Repeat buying
Subscriptions and one-click reorder.
06 High value, careful handling
Jewelry and Accessories
Payment
Higher-value orders with payment checks and insured shipping.
Variants
Size, metal and stone options, and made-to-order lead times.
Imagery
Detailed zoom, with certification information only where it is genuine.
Gifting
Packaging, messages and gift wrap.
07 Claims discipline and refills
Health and Wellness
Claims
What a product page may say about benefits is constrained, so content needs a review step.
Product detail
Ingredients, dosage guidance, age restrictions and batch or expiry.
Repeat use
Subscriptions and refill reminders.
Data
Care with customer information and consent.
08 Fitment decides the sale
Automotive Parts
Fitment
Find parts by make, model, year and variant.
Compatibility
A check on the product page and again in the cart.
Part data
Part numbers, cross-references and supersessions.
Operations
Large catalogs, wrong-part returns, and trade and retail pricing.
09 Curation over breadth
Specialty Retail
Products
Made-to-order, personalization, limited editions or one-off items.
Storytelling
Curation and product stories carry more weight than range.
Catalog
Small ranges with complex options, or large ranges of single items.
Availability
Pre-orders, waitlists and low-stock handling.
10 Accounts, price lists and repeat orders
B2B Wholesale
Pricing
Account-based price lists, tiers and minimum order quantities.
Ordering
Quick order by SKU, bulk upload and reorder from history.
Payment
Credit terms, purchase orders and GST invoices.
Fulfillment
Partial shipments, backorders and ERP-led stock.
Listed for the commerce requirements typical of each category. It is not a statement about B9's client list or experience in each sector. Marketing for online sellers is covered on the ecommerce industry page.
15Process
Our Ecommerce Development Process
Six stages, each ending in a point where you approve before the next begins. Timelines are not listed because they depend on scope: your proposal contains one.
Discovery
Architecture
Storefront
Catalog & integrations
Checkout QA
Launch
01
Stage 1 of 6
Discovery & Commerce Requirements
We map what you sell, to whom and how orders are fulfilled today: the catalog, the buying journeys, payment and shipping rules, the systems involved, and what must work on day one versus later.
You provide
Product and order samples, access to the current store if there is one, operating rules and priorities.
Approval point
Scope and requirements confirmed
02
Stage 2 of 6
Platform & Store Architecture
We recommend a platform and architecture with reasons, including the running costs and skills each option needs. Store structure, data model, URL structure and the integration approach are planned.
You provide
The platform decision, the budget for subscriptions and apps, and who holds each account.
Approval point
Platform and architecture decided
03
Stage 3 of 6
Storefront UX & Development
The customer journey and the key templates (category, product, cart, checkout) are designed, then built in stages on a staging site you can review.
You provide
Feedback on each stage, plus brand assets and content.
Approval point
Templates and journeys approved
04
Stage 4 of 6
Catalog & Integration Setup
Product data is structured, cleaned and imported. Payments, shipping, tax and the agreed integrations are configured or built and connected to test accounts.
You provide
Product data and images, provider accounts and access to connected systems.
Approval point
Catalog and integrations signed off on staging
05
Stage 5 of 6
Checkout & Operational QA
We test real scenarios: orders by every payment method, failed payments, stock edge cases, shipping zones, tax, notifications, returns, devices and browsers, speed, redirects and tracking.
You provide
Place test orders and confirm that statuses and documents match how operations work.
Approval point
Pre-launch acceptance
06
Stage 6 of 6
Launch & Handover
We go live with analytics and Search Console in place, check checkout, tracking and redirects on the live site, then hand over documentation, a walkthrough and the agreed post-launch arrangements.
You provide
The go-live decision, domain and DNS access, and confirmation that accounts are in your name.
Approval point
Go-live and handover accepted
16Why B9
Why Choose B9 Solution for Ecommerce Development?
A store is built once and judged every day. These are the habits we bring to the build.
B9 Solution
B9 Solution is a digital marketing and technology agency founded in 2020.
B9 Solution is led by experienced digital marketing professionals, with leadership bringing 12+ years of experience in digital marketing and digital selling.
Our own developers write the code.
Team photography slotAuthorized B9 team or office photography will appear here. None has been supplied for this page.
01 Development and marketing in one agency
Developers and the search and paid-media team work in the same company, so a store is built with how it will be found and promoted in mind.
02 Business-first planning
We plan around how you sell and operate, then choose the technology. Platform comes after the requirements, not before.
03 SEO-aware architecture
Clean URLs, redirects, structured data and fast templates are settled during the build instead of being patched in afterwards.
04 Attention to the customer journey
The path from category to paid order is designed as one journey, including the unglamorous parts: errors, stock-outs and returns.
05 Integration and operational thinking
Every integration gets a source of truth, a failure path and an owner, so it keeps working after launch.
06 Practical store management
Admin screens, content blocks and workflows are set up for the people who will use them, not only for launch day.
07 Responsible migrations
URL mapping, redirects and checks are planned, and you are told what cannot be moved cleanly before launch.
08 A clear development scope
What is included, what is not, and who owns accounts and access are written down before work starts.
17After launch
Store Ownership, Maintenance & Post-Launch Support
A store launches once and is run for years. Here is what a business typically manages after launch, what B9 can support under a separate agreement, and what sits with third-party providers. Final terms are always set in your agreement.
What a handover should leave you holding
Handover checklist
Accounts and access
Platform account in the business's name
Domain registrar and DNS access
Hosting account, where there is one
Admin users and roles
Payment gateway and shipping accounts
List of app and plugin subscriptions, with renewal dates
Knowledge
A walkthrough of store management (training where included in the agreed scope)
Documentation of custom functionality and integrations
A list of third-party services the store depends on
Operations
Backup and update arrangements
A support route for questions and faults
How change requests are scoped
After launch: who handles what
After launch: who handles what
Area
Business
B9 (separately agreed)
Third party
Platform account ownershipThe account stays in the business's name.
Usually responsible
Not involved
Not involved
Domain and hostingRegistrar and host are third parties; B9 can configure where agreed.
Usually responsible
Can support, by agreement
Usually responsible
Administrator accessThe business decides who has access and removes it when it should end.
Usually responsible
Can support, by agreement
Not involved
Store management and ordersDay-to-day running; training where included.
Usually responsible
Can support, by agreement
Not involved
Product catalog updatesRoutine edits are the business's; structural changes may need a developer.
Usually responsible
Can support, by agreement
Not involved
Third-party subscriptionsBilled to the business by each vendor.
Usually responsible
Can support, by agreement
Usually responsible
Security updatesHosted platforms patch themselves; self-hosted and custom stores need a maintenance arrangement.
Can support, by agreement
Can support, by agreement
Usually responsible
Bug fixesTerms are set in the agreement.
Not involved
Can support, by agreement
Not involved
Feature changesScoped and quoted separately.
Not involved
Can support, by agreement
Not involved
Integration maintenanceThird-party API changes can need updates to the connection.
Not involved
Can support, by agreement
Usually responsible
Usually responsible
Can support, by agreement
Not involved
Separate agreement. These may need a separate commercial agreement: ongoing maintenance, feature work, integration monitoring and support arrangements.
Maintenance is not unlimited, and it is not included in every build. Its scope and how requests are handled are written into the agreement for each store.
18Questions
Ecommerce Development FAQs
18 questions, grouped by what you are trying to decide.
01
Planning and platform selection
Which ecommerce platform is right for my business?
It depends on what you sell, how you sell it and who will run the store. Shopify suits teams that want a hosted store with a standard checkout. WooCommerce suits businesses already on WordPress, or with unusual product and checkout rules. Larger platforms and custom builds suit complex catalogs or workflows. We recommend a platform after a scoping conversation and explain the reasoning, including the running costs and the skills each option needs.
How do Shopify and WooCommerce differ?
Shopify is a hosted platform: the vendor handles hosting, security patches and core updates, you pay a monthly plan plus app fees, and extra transaction fees with some third-party payment gateways, and customization happens through themes and apps within the platform's limits. WooCommerce is a plugin for WordPress that you host yourself. It is very flexible and the core is free, but you take on hosting, updates, security and performance. Shopify tends to be quicker to run; WooCommerce gives more control.
When should I consider a custom ecommerce system?
When your business model or workflow cannot be expressed on a standard platform without heavy workarounds: unusual pricing, complex product configuration, or deep operational integration. A custom system gives freedom, but you own the code, the security and the upkeep. Try a platform first, choose custom when a specific requirement forces it, and cost it over several years rather than just the build.
What is headless ecommerce?
Headless separates the storefront, which customers see, from the commerce back end that holds catalog, cart and orders, and joins them through APIs. It gives full control of the front end and lets one back end serve several channels. It also means two systems to build, host, secure and keep in step. It fits specific needs. It is not an upgrade every store should take.
02
Store functionality
Can my store support product variations?
Yes. Variants such as size, colour, material or pack size are standard on Shopify and WooCommerce, each with its own SKU, price, image and stock. Limits differ by platform, for example how many options a product may have and how stock behaves at variant level, so we check your catalog against the platform at the planning stage, before you commit.
Can you integrate payments and shipping?
Yes. We connect stores to payment gateways and shipping tools. Which gateway, which payment methods (UPI, cards, net banking, wallets, Cash on Delivery) and which couriers or aggregators are available depends on the platform, the plan and the provider's own terms, so we confirm those during scoping and test each path, including failed payments, before launch.
Can ecommerce connect to existing ERP or CRM systems?
Often, but how depends on the systems. Many CRMs and ERPs offer connectors, APIs or automation-tool integrations, and where they do not, a custom integration through APIs may be needed. We start by deciding which system is the source of truth for products, stock, customers and orders, then specify the data flows and what happens when a sync fails. ERP connections are scoped individually.
Can I manage products myself?
Yes. The admin screens on Shopify and WooCommerce let your team add and edit products, prices, stock and content without a developer. We set up product types, templates and content blocks so routine changes cannot break the layout, and hand over the access and guidance your team needs. Spreadsheet import covers bulk changes. Structural changes may still need a developer.
03
Migration and technical quality
Can I move my existing store to another platform?
Usually, yes. Products, categories, customers, orders and content can generally be moved, though not everything transfers cleanly: customer passwords often cannot be moved, order history may be imported or archived, and apps and custom functionality must be replaced or rebuilt. We assess the current store, plan what moves and what changes, and test before switching over.
What happens to my existing URLs?
Every important old URL is mapped to its new equivalent, and permanent (301) redirects are planned and tested before launch, so links, bookmarks and search engines reach the right page. Some platforms fix their own URL patterns, which means some addresses change and need a redirect. Redirects are designed to reduce avoidable loss of search visibility. No migration can guarantee that rankings are preserved.
How do you approach site speed and security?
For speed, we measure Core Web Vitals on real templates and remove what slows them, such as oversized images, unused scripts, heavy apps and theme code. On security, a well-built store keeps card entry on the payment provider's pages, limits admin access and keeps the platform and plugins updated. We do not promise speed scores or security outcomes, and security work beyond the build is scoped separately.
Is SEO considered during development?
Yes. Crawlable category and product pages, clean URLs, redirects, structured data and fast templates are handled during the build. Rankings still depend on content, authority and competition, which ongoing search work addresses. B9's SEO team can help with that separately: see Ecommerce SEO.
04
Pricing and ownership
What affects ecommerce development cost?
Scope. The main drivers are whether the store is new or existing, the platform approach, custom storefront layouts, the number and complexity of product types, checkout rules, integrations, migration and data volume, custom applications, testing, handover and maintenance. We quote each project individually once we understand these. The scope planner above shows how they add up.
Are subscription and payment fees included?
No. B9's fee covers the design and build work in the proposal. Platform subscriptions, app and plugin charges, payment processing fees and hosting are paid to the respective providers. We list the expected third-party costs during scoping so they are not a surprise, though exact amounts follow each provider's current pricing.
How long does an ecommerce project usually take?
It depends on scope. A standard store on a hosted platform and a store with custom checkout, ERP integration and migration are very different projects. You receive a timeline with the proposal, and we build in stages so you can review progress as it happens. We avoid quoting typical durations because they mislead more than they help.
Who owns the store after launch?
Generally, you do. The platform account, domain and hosting accounts stay in your name, and code access is handed over as set out in your agreement. It is good practice to create accounts in the business's name from the start, and we plan the project that way.
What happens after handover?
We hand over access, documentation of custom functionality and integrations, and a walkthrough of store management, with training where it is included in the agreed scope. After that your team runs the store day to day. Support is available as a separate arrangement, agreed for each store.
Is ongoing maintenance included?
Not automatically. Maintenance after launch is available, covering updates, fixes, minor changes, plugin and platform updates where they apply, technical support and improvements, but its scope is agreed for each store and is separate from the build. Hosted platforms handle some updates themselves, while self-hosted and custom stores need more. What is covered and how requests are handled is written into the agreement.
19Enquiry
Tell Us About Your Ecommerce Project
Share the basics and we will come back to you about your store. The more you tell us about your products, platform and systems, the more useful that conversation can be.
What happens next
We read your brief.
We get in touch to talk through platform, scope and sequence.
A proposal is scoped to your project.
Helpful to include
What you sell and who buys it
Your current platform, if any
Systems the store must connect to
Anything with a fixed date
Project details
Preview only. Nothing was sent. This form is a design preview and is not connected to any system.
This is how a confirmation would read
In the live page, this message would confirm that your request was received. Nothing has been sent from this preview.
Sections
Planning an ecommerce store?Scoped and quoted for your project.