Ecommerce Website Development in Pune: A Pre-Launch Testing Checklist for Your Shopify or WooCommerce Store — Test Orders, Devices, Emails and Tracking Before You Go Live

Ecommerce Website Development in Pune: A Pre-Launch Testing Checklist for Your Shopify or WooCommerce Store — Test Orders, Devices, Emails and Tracking Before You Go Live

Before launching an online store, you should place real test orders through every payment and delivery option, check the store on actual phones, confirm every customer email arrives, verify that sales tracking records one order once, and remove anything that tells search engines to stay away. A professional ecommerce website development team in Pune will run this as a written test plan, not as a quick look around, because the most expensive bugs are the ones customers find first. This guide gives you that plan in the order we would run it, with what to check, what "pass" looks like and what is commonly forgotten.

It is written for the store owner or marketing lead who will sign off the launch, so you do not need to read code. If your developer says "it's all working", this is how you verify it. We cover Shopify and WooCommerce because they are the two platforms most Pune businesses use; the same logic applies to custom builds.

Why a launch test plan is worth the day it takes

A store that goes live with a broken checkout loses sales silently, because shoppers rarely report errors; they just leave. Launch day is also when you are spending money on ads, announcing to your list and attracting your most curious visitors, so a defect costs more then than at any other time.

The tests below fall into eight groups. Run them on the staging or preview version first where possible, then repeat the essentials on the live store immediately after launch. For the staging step itself, see our guide to website staging before launch.

Before you start: set up the test environment

Prepare these so your testing is repeatable:

• A test log: a spreadsheet with columns for test, device, result, screenshot link, owner and date fixed.
• Test accounts: two or three customer email addresses you control, and one test phone number.
• Payment test mode: each payment gateway provides test credentials or a test mode. Shopify offers a test mode and a "Bogus Gateway" for development stores; WooCommerce gateways usually include a sandbox or test-mode switch. Ask your developer which applies, and never use real card details in a test mode that is not clearly marked as such.
• A short product sample: at least one simple product, one with variants, one out-of-stock item, one discounted item and, if relevant, a product with a pincode restriction.
• Real devices: your own phone and, if possible, one older or lower-end Android phone, since many Indian shoppers use mid-range Android handsets.

Group 1: The buying journey

Walk through the store as a first-time customer would, on a phone first.

Navigation and discovery

• The home page loads, shows the correct logo and links, and the menu opens and closes on a phone.
• Category pages show the right products and filters, and the filters can be cleared.
• Site search returns sensible results for a typo, a product code and a common synonym. See our notes on site search and category navigation.
• Product pages show the correct price, images, variants, stock status and delivery information.
• The "Add to cart" button works for each variant, and the cart counter updates.

The cart

• Quantities can be increased, decreased and removed.
• Prices and totals recalculate correctly, including discounts and bundles.
• A discount code works, an invalid code shows a clear message and a code cannot be combined where it should not be.
• Cart contents persist if you close the tab and come back later on the same device.

Group 2: Checkout and payment

This is the group where the most revenue is at risk, so be thorough.

Checkout form

• Required fields are marked, errors are specific, and the form is usable one-handed on a phone.
• The keyboard type is right: a number pad for phone and pincode, an email keyboard for email.
• Address and pincode fields accept real Indian addresses, including those with long flat names or landmark text.
• Guest checkout works if you offer it, and account creation works if you require it. We cover this in checkout forms and guest checkout.
• Shipping options and charges match your intended rules for each pincode or order value.
• If you charge GST, check that the tax shown at checkout and on the order matches what your accountant expects for a few typical baskets. Ask your accountant to sign off on the invoice format.

Payment methods

Test every method you intend to offer, successful and failed:

For each, verify:

• The customer lands on a clear confirmation page after success.
• A failed or abandoned payment leaves the cart intact and offers a retry.
• The order appears in the admin with the correct status (paid, pending or cancelled).
• The customer is not charged twice if they click the button twice or press back.

Our guide to the order confirmation page explains what that page should contain.

Refunds and cancellations

Place a test order and cancel it from the admin. Check the status, the stock level and the email the customer receives. Where your gateway supports test refunds, run one to verify the status updates.

Group 3: Customer emails, SMS and WhatsApp messages

A shopper who does not receive a confirmation will contact you, doubt you, or dispute the charge.

• Order confirmation, shipping confirmation, cancellation, refund and account emails are all delivered to Gmail, Outlook and a Yahoo or company address, and not to spam.
• The sender name and reply-to address are correct and professional.
• The email design renders properly on a phone, and the logo, links and unsubscribe notice work.
• Order numbers, amounts, addresses and product names are accurate and match the order.
• If you use WhatsApp or SMS for order updates, confirm the templates are approved, the numbers are formatted correctly and a customer who has not opted in does not receive marketing messages.
• Your sending domain has SPF, DKIM and DMARC records set up, otherwise your emails may be filtered. Our guide to email authentication explains how to check.

Group 4: Mobile and browser testing

Most Indian ecommerce traffic arrives on phones, so test there first, not last.

• Test on at least one recent iPhone, one recent Android and, if available, one older budget Android phone.
• Test in Chrome, Safari and one more browser such as Samsung Internet or Firefox.
• Check portrait and landscape orientation, and that nothing is cut off at the edges.
• Check that pop-ups, cookie banners and chat widgets do not cover the add-to-cart or pay buttons. See pop-ups and cookie banners that do not hurt mobile visibility.
• Test on a slow connection. Your browser's developer tools can throttle the network, and your own phone on a weak signal is an honest test.
• Check tap targets are large enough to press without zooming.
• Confirm accessibility basics: images have descriptions, form fields have labels and the site can be used with the keyboard alone.

Group 5: Speed and stability

Use Google's PageSpeed Insights on your home page, a category page, a product page and the cart. Google's Core Web Vitals guidance gives target values that count as "good": Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds and Cumulative Layout Shift below 0.1. Treat these as goals, and use the report to find what to fix rather than chasing a score. Pre-launch data may be limited because real-user data builds up only after launch.

Look for:

• Oversized images, especially hero banners and product galleries.
• Third-party apps and scripts that block rendering. Our guide to auditing third-party scripts can help.
• Layout shifts when images, fonts or banners load.

For a deeper treatment, see store speed and Core Web Vitals.

Group 6: Tracking and analytics

Tracking is where launch checklists most often fail, and mistakes are invisible until you try to measure ad performance.

• Analytics: confirm that GA4 receives page views, product views, add-to-cart, begin-checkout and purchase events. Use the debug view while you test.
• Purchase counted once: place one test order and confirm exactly one purchase event with the correct value, currency and transaction ID. Refreshing the confirmation page must not create a second one.
• Ad platform pixels and tags: confirm that the Meta pixel or Conversions API and Google Ads conversion tag fire on the right events and carry the right value.
• Consent: if you use a consent banner, check that tags respect the choice, and that declining actually stops the relevant tags.
• Internal traffic: exclude your team's visits so test orders do not pollute reports. Refund or cancel test orders and mark them clearly.
• UTM parameters: click a tagged link and confirm the source and medium appear in reports. See UTM tracking and campaign naming.

If the setup is new, our GA4 setup checklist for Indian ecommerce covers the configuration itself.

Group 7: Search visibility and technical SEO

Launching a store with search engines blocked is shockingly common.

• On WordPress and WooCommerce, check that Settings > Reading > "Discourage search engines from indexing this site" is unticked at launch. Many staging sites tick it on purpose and forget to clear it.
• On Shopify, remove the storefront password when you are ready to open, and check that unpublished or draft products are not exposed.
• Check the robots.txt file, and view the page source of a few pages for stray "noindex" tags.
• Make sure there is one canonical version of the domain (with or without www, HTTPS only) and that the other versions redirect to it.
• Submit the XML sitemap in Google Search Console and confirm it lists real product and category URLs, not staging addresses.
• Check that titles and meta descriptions are unique on key pages and not left as defaults such as "Home" or "My Store".
• Check product structured data with Google's Rich Results Test. See product schema for Shopify and WooCommerce.
• If you are replacing an old site, test the redirect map from every important old URL to its new equivalent, as described in website migration without SEO loss.

Group 8: Legal pages, trust signals and security

• Privacy policy, terms, shipping and returns policy, and contact details are present and linked from the footer and checkout. Ask your legal adviser to confirm the wording applies to your business.
• Your business name, address and contact details are visible, since shoppers look for them before paying.
• HTTPS works on every page with no mixed-content warnings, and the certificate renewal is automated. See domain, DNS and SSL renewals.
• Admin accounts use strong, unique passwords and two-factor authentication, and unused staff and developer accounts are removed.
• Test login attempts and the checkout against bot abuse. Our article on fake orders and bot checkouts describes the protections worth having.
• A backup exists and a restore has been tested. See website backups and disaster recovery.

The launch day sequence

When all groups pass on staging, a calm launch looks like this:

1. Freeze changes except for fixes to listed defects.
2. Take a full backup of the files and database.
3. Switch the store live: connect the domain, remove password protection or the search-blocking setting and enable live payment mode.
4. Run the live smoke test: place a real low-value order using each key payment method, then refund or cancel it, and confirm the emails, tracking and admin all behave as in testing.
5. Check Search Console and analytics for the new property, and submit the sitemap.
6. Watch the first 48 hours: monitor orders, failed payments, error logs, speed and customer messages. Have your developer on call.
7. Review at day seven: compare orders against sessions, check for abandoned-checkout patterns and fix the top three friction points.

Do not time the launch for the same day as a big ad campaign or festival sale unless you have already run the live smoke test. A soft launch to a small audience is a cheap way to find what testing missed.

Common mistakes to avoid

• Testing only as the admin, who sees a different experience from a customer.
• Using only one fast phone and one browser.
• Testing successful payments but never failed or abandoned ones.
• Forgetting to switch the gateway from test to live mode, or the reverse (leaving test mode on, so real customers "pay" nothing).
• Leaving the "discourage search engines" setting enabled.
• Launching with tracking not verified, then trying to reconstruct lost data.
• Not telling the team how to handle the first order, the first complaint and the first refund.
• Cancelling test orders without restoring stock, so inventory is wrong at launch.

What to ask your ecommerce development team

• Can we see the written test plan and results?
• Which devices and browsers did you test on?
• How did you test each payment method, including failures?
• How do we verify tracking, and who owns the analytics and ad accounts?
• What is the rollback plan if something breaks after launch?
• Who is on call for the first week, and what response time can we expect?

If you are comparing providers for ecommerce website development in Pune, ask to see a past launch checklist. A team that has one is telling you it has launched before.

Frequently Asked Questions

How do I test payments on my store without charging real money?

Use the test or sandbox mode that your payment gateway and platform provide, with the test card numbers or UPI test flows in their documentation. Confirm the mode is clearly marked, run successful and failed payments, and switch to live mode only when launching, followed by a small real order to confirm.

How many test orders should I place before launching?

Enough to cover every payment method, shipping option, discount type and failure case you support, which is often 15 to 30 orders for a typical store. Record each in a test log so you can show what was checked.

Why is my new store not showing up on Google?

New stores take time to be crawled, but a common cause is accidentally blocking search engines: the WordPress "discourage search engines" setting, a "noindex" tag, a robots.txt rule or a Shopify password page. Check those first, then submit your sitemap in Search Console.

Should I launch before a festival sale?

Only if you have finished testing, including a live smoke test, with enough time to fix problems. A soft launch a few weeks before the sale lets you find issues while traffic is light.

Who should sign off the launch?

The business owner or a delegated manager, using the written test log, with the developer confirming that every listed defect is fixed or accepted. Do not rely on a verbal "it works" from the team that built it.

Sources: Google Search Central: Get your website on Google (indexing basics), web.dev: Core Web Vitals thresholds, Shopify Help Centre: Testing orders, WooCommerce documentation: Payment gateways. Test-mode features differ by platform version and payment gateway; confirm the current options in each provider's documentation. The order counts above are a practical range, not a published standard.

Working with Govindani Infotech on store launches

Govindani Infotech is a Pune-based website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. We build and launch Shopify, WooCommerce and custom stores, and we run launches from a written test log like the one above, shared with the client for sign-off.

If you are within a few weeks of launching, send us the store link or staging address on WhatsApp at wa.me/919201958278 and we will tell you what a pre-launch review would cover. You can also read about our checkout system work or reach us through the contact page.

About the author: written by the Govindani Infotech ecommerce development team in Pune.