Store planning guide · published 8 Oct 2026
Ecommerce website requirements checklist: decide the operation before the platform
A useful ecommerce brief describes products, money, delivery, exceptions and staff work. It does not begin and end with “Shopify or WooCommerce”. Use this checklist before you request quotes.
Quick answer
An ecommerce website requirements document should define the selling model, products and variants, catalogue data, prices and approved tax inputs, customer accounts, payment methods, success and failure states, shipping zones and rates, COD rules, order notifications, cancellation and return process, inventory ownership, integrations, staff roles, reports, security and privacy responsibilities, acceptance tests, migration, training and ongoing costs.
Choose Shopify, WooCommerce or a custom build only after these requirements are clear, because the operation—not the home-page design—determines the platform and quote.
The business and its professional advisers remain responsible for product, tax, invoice, policy and regulatory decisions. The website implements the approved rules.
1. Define the selling model
“Online store” can describe four different systems.
- Catalogue and enquiry: customers browse but request a quote or continue on WhatsApp.
- Direct checkout: fixed prices, cart, payment and a defined delivery process.
- B2B ordering: account-specific prices, minimum quantities, RFQs or approval before fulfilment.
- Marketplace: multiple sellers, commissions, onboarding, moderation and settlement logic.
Write which model applies now and which one is only a future idea. A catalogue does not need to carry checkout complexity. A marketplace cannot be estimated as a normal single-seller store.
2. Prepare the product and catalogue requirements
Use ten real products to expose the structure.
List product name, SKU, description, category, images, price, approved tax input, stock, weight or dimensions, variants, attributes, related products and any downloadable files. State which fields are required, who supplies them and how they will be imported.
Use representative examples: one simple product, one with multiple sizes or colours, one heavy item, one out-of-stock item and one item with special delivery rules. If those records cannot fit a clean spreadsheet, the catalogue model is not ready for development.
Also decide search, filters, sorting, category navigation, product comparison and what the customer sees when a combination is unavailable.
3. Map the cart, checkout and payment states
The failed-payment path matters as much as the successful one.
- Guest checkout, account checkout or both.
- Required customer and address fields.
- UPI, cards, net banking, wallets, COD or approved payment links.
- Payment pending, failed, abandoned, duplicated, refunded and cancelled states.
- Coupon, gift card, store credit and minimum-order rules if needed.
- Invoice responsibility and approved tax configuration supplied by the business.
- Customer and staff notifications at each order state.
The payment provider approves the account and controls its current fees, settlement and supported methods. The build should name the selected provider, integration method, testing account and webhook or return-flow responsibility.
4. Write shipping and COD rules as examples
Exceptions create most fulfilment complexity.
Define serviceable countries, states or postcodes; pickup options; rate calculation; free-shipping thresholds; packaging assumptions; delivery estimates; split shipments; tracking; and what happens to an unserviceable cart.
For COD, state eligible locations, order-value limits, extra charges, verification steps, risky-order handling and return-to-origin responsibility. Do not write only “COD required”. Write sample orders and the exact result expected for each.
5. Define cancellation, return and refund operations
A policy page is not the workflow.
Record who can cancel, until which order state, whether partial cancellation is allowed, how returns are requested, which products are excluded, who approves a return, how pickup works and when a refund is triggered. The business supplies and approves the policy; the store must make the agreed steps possible.
Include damaged delivery, wrong item, failed delivery, exchange, partial refund and chargeback scenarios where relevant. Decide which steps are automatic and which remain manual for staff.
6. Describe the staff and administration workflow
The store must be operable after the developer leaves.
- Who creates products, changes prices and approves promotions?
- Where does stock come from, and which system is authoritative?
- Who sees new orders and which order statuses do staff use?
- Which exports, reports or reconciliation files are required?
- Which roles can view customers, issue refunds or change settings?
- How are support requests connected to an order?
- What training and written handover are included?
Use the smallest role and permission model that matches the real team. Shared administrator passwords are not an operating plan.
7. List integrations and their owners
Every connection has two systems, two accounts and failure states.
Possible connections include payment gateway, shipping aggregator, accounting or invoicing system, ERP, inventory system, CRM, email or messaging provider, marketplace, reviews and analytics. For each one, record the provider, business-owned account, data sent, data received, timing, error behaviour, recurring charge and who supports each side.
If the provider has not been chosen or access is unavailable, label the integration as an assumption or a later phase. Hiding an unknown inside a fixed quote creates avoidable disputes.
8. Use platform selection criteria, not preference
Shopify and WooCommerce are means, not requirements.
| Criterion | Question to answer |
|---|---|
| Editing | Who maintains products and pages, and how technical are they? |
| Checkout | Which payment, shipping, tax and COD rules must be supported? |
| Integrations | Which providers already support the platform reliably? |
| Ownership | What data, design and code can be exported or moved? |
| Operating cost | Which platform, app, plugin, hosting and support charges recur? |
| Maintenance | Who handles updates, backups, incidents and compatibility? |
| Growth | Which confirmed next-stage requirements must the platform accommodate? |
Then compare Shopify and WooCommerce against those answers instead of choosing from popularity.
9. Turn requirements into acceptance tests
A store is complete when the agreed scenarios work.
Write test cases before development ends: browse and filter on a phone; add each representative product; apply and reject a coupon; calculate shipping; place prepaid and COD test orders; simulate payment failure; verify notifications; change an order state; cancel; refund; update stock; export an order; and check access with each staff role.
Include performance, keyboard use, form labels, broken links, HTTPS, privacy choices, analytics consent where used, backups and a launch rollback plan. The visual review is only one part of acceptance.
The one-page brief to send with every quote request
Copy these headings and answer what is known.
- Business, audience and selling model
- Product and variant counts with sample data
- Countries or service areas
- Payments, currencies and COD rules
- Shipping, pickup and delivery logic
- Approved tax, invoice, return and privacy inputs
- Customer accounts and staff roles
- Required integrations and business-owned accounts
- Content, photography and data responsibility
- Migration, testing, training, launch and support
- Known recurring-cost limit
- Future ideas explicitly excluded from phase one
This is enough for a useful discovery call. The ecommerce development service turns the agreed answers into a page, feature and testing scope.
Questions
Ecommerce requirements questions
What are the basic requirements for an ecommerce website?
Should I choose Shopify or WooCommerce first?
What product information should I prepare?
Is a payment gateway enough to launch a store?
Who is responsible for tax and policy rules?
How much does an ecommerce website cost?
Next step
Bring the requirements, not a platform guess.
Send the product examples, payments, shipping rules and current workflow. Ashish will turn them into a written phase-one scope and fixed quote.