Opening an online store is less about launching a website and more about publishing a set of promises: what you sell, how much it costs, when it arrives, and what happens if it goes wrong. Most complaints trace back to one of those promises being vague. Use this checklist as a working document, not a formality.
Business and product basics
Confirm your legal business name, address and contact routes are consistent everywhere, and that your policies describe what you will actually do. For each product, check the name, description, specifications, price, weight and dimensions, because shipping charges are calculated from weight or volume. Confirm every product has at least one usable image, and that the image belongs to you or is properly licensed for commercial use.
Stock and variants
Decide how stock is tracked before you import anything. If the same item exists in several sizes or colours, model them as variants of one product rather than as separate products, because that keeps reviews and reporting together. If an item is made to order, mark it so the store does not promise immediate dispatch. Import a test batch, check the counts, then do a full import rather than testing on live data.
Payment setup
Complete merchant onboarding with your payment provider early, since it involves documentation and verification that can take time. Confirm which payment methods you actually want to accept and what each one costs you. Place a real order, watch it come through, then refund it and confirm the money returns correctly. Check that failed payments produce a sensible message rather than an error page, and that no card details are stored anywhere on your own systems.
Shipping, tax and delivery promises
Set up shipping zones that match the pin codes you can genuinely serve, and give a realistic dispatch and delivery estimate. Check what happens for a customer in an unsupported pin code: it should be a clear message, not a silent failure at checkout. Confirm whether tax is shown as included or added at checkout, and make sure that matches your pricing decision. Nobody should discover a surprise charge on the payment screen.
Content, policies and trust
Write the delivery, returns, refund, privacy and terms pages for your business rather than copying a template unchanged. Put contact details where a customer can actually reach a person, and add a way to ask a question before buying. Check that product descriptions answer the question a buyer asks just before committing, such as dimensions, materials, care instructions and what is included in the box.
Test the whole journey on a phone
Place a real order on a small screen, using a card you control. Follow it through to the confirmation email and check that the email arrives, is readable on a phone and contains the right order reference. Then test the account area, the wishlist if you offer one, and a return request. Finally, walk the site with the shipping, returns and privacy pages open in another tab, because that is how a cautious customer reads it.
After launch, keep watching
Keep a short weekly list for the first month: errors in the payment report, unexpected questions from customers, pages with no visits, products with no sales, and stock counts that disagree with reality. Most early problems are found this way rather than by a customer reporting them. A short written record of what changed and when makes any later debugging dramatically faster.
Accessibility and device checks
Check that images carry descriptive alternative text, that form fields have visible labels, that colour is not the only way information is conveyed, and that buttons and links can be operated by keyboard. Check the product page and checkout on an older phone, not only a new one, because low-end Android devices are still common among buyers. Payloads also matter: oversized images and unnecessary scripts are a common cause of a slow checkout on mobile data, and a slow checkout loses orders.
Confirm emails actually arrive
Test the order confirmation, the dispatch notice, the delivery update and the password reset from a real mailbox, and check where each one lands. Configure the sending domain properly so messages come from your own business address rather than a shared one, and authenticate them using whatever mechanism your platform supports. Add the sending domain to your own documentation, because an email that fails silently is the hardest kind of store problem to notice.
Keep the accounts organised
Write down where every account lives: domain registrar, hosting or platform, payment gateway merchant account, analytics, search console, courier accounts and email sending. Register them in your business name with an email address you control, not with a developer's. Ask for credentials and documentation at handover, enable two-factor authentication on each, and store the record somewhere your team can reach without asking one person.
More of the reasoning is in our e-commerce guides. If you would rather have the catalogue, payment and shipping setup handled as part of a build, our e-commerce development work starts at INR 35,000 per project, with hosting, platform subscription, payment gateway charges, shipping and ad spend billed separately by their own providers, and you can tell us what you sell for a scoped plan.
Common questions
How long before launch should this checklist be started?
Start with the operational answers rather than the technical ones, because the platform decisions depend on them. Give yourself enough time to collect product data, imagery, shipping rates and policy text, and to complete merchant onboarding with your payment provider. Merchant verification in particular can take longer than the website build itself, so begin that early.
What is usually forgotten on launch day?
The small things: a test order that was never refunded, a shipping rate that does not cover a served pin code, a confirmation email landing in spam, a size chart missing on two products, and a returns page describing a different policy from the one in the footer. Walk the purchase as a customer on a phone, then walk the refund too.
Do I need professional help for a small store?
A short catalogue with simple variants can often be set up competently by an in-house person, and that is a reasonable use of budget. Bring in help when the catalogue is large, when several systems must connect, when tax and shipping rules are complicated, or when the store has to survive real traffic. Ask any provider to scope the work in writing so you know exactly what you are buying.