E-commerce Website Development:Features, Payments and Planning
The features, payment options, product data and day-to-day operations to plan before building an online store, plus the mistakes that most often cost e-commerce sales.
Table of Contents
- 1. Product catalogue
- 2. Payments
- 3. Delivery and returns
- 4. Checkout
- 5. Operations behind the store
- 6. Integrations
- 7. Choosing the platform
- 8. Hosting, security and performance
- Example product data template
- Phasing a store project
- Common mistakes
- Pre-launch test list
- Frequently Asked Questions
- Related reading
- Sources
Building an e-commerce website means more than adding a shopping cart to a site. Before development starts, plan the product catalogue and its data, how customers will pay, how orders are delivered and returned, what the checkout asks for, who processes orders, and which systems the store must connect to. These decisions shape the platform choice and the budget more than the design does.
1. Product catalogue
- How many products, and how many variations (size, colour)?
- What information each product needs: price, stock, SKU, weight, dimensions, images, specifications.
- Categories and filters customers will use to browse.
- Who will enter and maintain product data, and in what format (spreadsheet imports help for large catalogues)?
Good product data (accurate descriptions, real photos, clear prices) sells more than any design feature.
2. Payments
Decide which methods your customers expect. In Bangladesh that commonly includes mobile financial services, cards through a payment gateway, and cash on delivery. For each method, check:
- merchant account requirements and documents;
- fees and settlement times;
- how refunds work;
- whether the payment page is hosted by the provider (which keeps sensitive payment data off your site).
See accepting online payments in Bangladesh.
3. Delivery and returns
- Delivery areas, charges and how they are calculated (flat rate, by weight, by area).
- Courier integration or manual dispatch.
- Order tracking and status emails.
- A clear return and refund policy, published on the site.
4. Checkout
The checkout is where stores lose the most customers. Keep it short:
- allow guest checkout;
- ask only for information you need;
- show the total, including delivery, before the last step;
- make phone and address fields work for local formats;
- test on a phone.
5. Operations behind the store
- Who receives order notifications and processes them?
- How is stock updated when items sell in a physical shop too?
- How are invoices produced?
- What reports does the business need?
6. Integrations
Common integrations: payment gateways, couriers, SMS notifications, accounting software, inventory or POS systems, and marketing tools. Each adds development and maintenance work; list them early. See what is an API.
7. Choosing the platform
- WooCommerce on WordPress suits most small and medium stores and offers full ownership; see WooCommerce hosting requirements.
- Hosted e-commerce platforms are quick to start, with monthly fees and less control.
- Custom development suits unusual business rules, marketplaces or deep integration needs.
8. Hosting, security and performance
- A store needs reliable hosting with enough resources for uncached cart and checkout traffic.
- HTTPS everywhere, 2FA for admin accounts, and prompt updates.
- Regular backups, because the database changes with every order.
- Fast product pages; see how to speed up WooCommerce.
Example product data template
Preparing product data in a spreadsheet before development speeds up the build and makes imports reliable. A useful set of columns:
| Column | Example |
|---|---|
| SKU | TSH-BLU-M |
| Product name | Cotton T-shirt, blue |
| Category | Men > T-shirts |
| Variation attributes | Colour: Blue; Size: M |
| Regular price | 650 |
| Sale price | 550 |
| Stock quantity | 24 |
| Weight (for delivery) | 0.25 kg |
| Short description | Soft 100% cotton, regular fit |
| Full description | Fabric, care instructions, fit notes |
| Image file names | tsh-blu-front.jpg; tsh-blu-back.jpg |
Consistent SKUs and attribute names (always "Colour", never sometimes "Color") prevent duplicate filters and broken variations later.
Phasing a store project
- Phase 1, launch: catalogue, cart, checkout with the main payment methods, delivery rules, order emails, policies.
- Phase 2, growth: customer accounts and order history, discount codes, reviews, abandoned-cart emails.
- Phase 3, efficiency: courier and accounting integrations, stock sync with the physical shop, reporting.
Each phase can go live on its own, which spreads cost and gets the store selling sooner.
Common mistakes
- Launching before payments, emails and delivery charges are tested end to end.
- Missing or unclear return and delivery policies.
- Poor product photos and thin descriptions.
- Forcing account creation before checkout.
- No plan for who processes orders at busy times.
Pre-launch test list
- Place test orders with every payment method
- Check order emails reach customers and staff
- Test delivery charges for different areas
- Process a refund
- Check stock reduces correctly
- Test on mobile devices
- Confirm legal pages are published
Frequently Asked Questions
How long does it take to build an online store?
A small store with a standard platform can launch in weeks; complex catalogues and integrations take longer. Product data preparation is often the slowest part.
Do I need a developer to run an online store?
To run day-to-day sales, usually not. For setup, integrations, performance and security, professional help reduces risk.
What does an e-commerce website cost?
It depends on catalogue size, integrations, design and platform. See how much does a business website cost for the factors.
Related reading
Plan the whole project with how to plan a website project, and read how to start an online store for the business side. For a store built for you, see ServerNeed e-commerce development.
Sources
Featured image: “The Packages” by bfishadow, licensed under CC BY 2.0.
Last updated 7 October 2026
