Ecommerce Provider After Launch Checklist
The store is live. These are the checks for day 1, week 1 and day 30, the handover pack to collect from your provider, how the bug-fix period works and which old logins to remove.
An ecommerce after launch checklist covers the 30 days after a new store, a redesign or a platform move goes live. That window matters because most launch faults stay invisible on the first afternoon: a payout that does not arrive, an order email that lands in spam, old links that now show an error page, a tracking tag that counts every sale twice. It is also a sensible length for a provider’s bug-fix period, and anything found after that period ends costs extra.
The checks below are grouped by when to run them and who runs them. Use them for a store built by an agency, a freelancer or yourself. If the provider built it, the development agency guide explains the phases that should lead up to this point.
What do you check on launch day?
Launch day is about one question: can a customer buy, pay and hear back from you? Run these checks within the first two hours, on a phone as well as a computer.
| Check | How | Pass when |
|---|---|---|
| Real test order | Buy a low-priced product with a real card, then refund it | Order appears in the admin, payment is captured, refund goes through |
| Every payment method | One small order per method (card, wallet, pay later, bank transfer) | Each completes and shows the right status |
| Order emails | Check the customer confirmation and the shop notification | Both arrive, in the inbox, with correct shop name, address and reply address |
| Delivery and pickup options | Enter a postcode from each delivery zone and one outside | Right fees, right options, a clear message outside the zones |
| Tax on an order | Compare a sample order’s tax line with what your accountant expects | Rate and wording match |
| Discount codes | Apply one live code | The discount and the order total are right |
| Top old URLs | Open your 20 most visited old addresses | Each lands on the right new page |
| Forms | Send the contact form and any back-in-stock form | Messages arrive |
| Purchase tracking | Check your analytics real-time view during the test order | One purchase recorded per order, with the order number |
For the tracking check, Google’s Analytics ecommerce documentation shows the purchase event carrying a transaction_id, and refunds are measured by sending a refund event with the same transaction ID. If your test order shows up without that ID, or twice, tell the provider now; reports built on broken tracking mislead you for months.
What do you check during week 1?
Week 1 is when money and search traffic show whether the launch really worked.
Payouts
Check that the first payout from your payment provider reaches your bank account, then reconcile it with the orders. Example with invented figures: 42 orders worth $3,150, one refund of $85, and payment fees of $96 according to your provider’s statement. Expected payout: $3,150 minus $85 minus $96 = $2,969. A payout far from your own figure points to missing orders, a wrong fee plan or a refund you did not authorise.
Broken links and redirects
Google Search Console’s Page indexing report shows the indexing status of the URLs Google knows about on your site, and lists 404 errors from the past month. Google advises fixing the 404 errors you link to yourself or list in a sitemap; ignore old junk URLs nobody links to. Submit the new sitemap in Search Console in the same session.
Speed
Test the home page, one category page and one product page. Google’s Search Central page on Web Vitals gives these targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1. A new store that misses them in week 1 will not get faster on its own once more apps and images are added.
Backups and stock
Ask the provider to show you a restored backup, or restore one to staging yourself. Then compare the online stock count of ten fast-selling products with the shelf. A mismatch in week 1 tells you the stock sync needs fixing before a busy weekend proves it.
What do you check on day 30?
Day 30 closes the launch. By now you have a month of real orders to compare with the month before.
- Orders and revenue against the previous 30 days and the same period last year, if you have it.
- Checkout completion: the share of started checkouts that end in an order. A drop points at a fault in the new checkout steps.
- Analytics against the admin: the number of purchases in analytics should be close to the number of orders in your store. A big gap means tracking is still broken.
- Refunds and returns recorded in both places.
- Redirects still in place. Google’s site move guidance says to keep redirects for as long as possible, generally at least one year. Nobody should remove them during a clean-up.
- Bug log: every item fixed, or moved to a paid change list with your agreement.
- Warranty end date confirmed in writing.
- Old access removed (see the access section below).
Write a one-page summary of the numbers and the open items. It is the document you will want in six months when someone asks what changed at launch.
What goes into the handover pack?
The handover pack lets anyone (you, a new freelancer, a different agency) run and change the store without the original builder. Ask for it before the final payment, and check every line.
- Account list: every system the store uses, the owner of each account and who has access today.
- Theme and code: theme name and version, where custom code lives, how to deploy a change.
- Apps or plugins: each one, what it does, its monthly cost and who pays for it.
- Connections: till, stock, accounting, couriers; what syncs, on what schedule and what to do when it stops.
- Redirect list: the full old-to-new URL map used at launch.
- Settings that matter: tax, delivery zones and fees, pickup locations, payment methods, order emails.
- Backups: where they are, their schedule and how to restore one.
- Known issues: anything left unfixed with the reason.
- A short how-to for the tasks you will do yourself: adding a product, changing a banner, editing a delivery fee.
Store the pack where you control it. A shared folder in the provider’s account disappears the day the relationship ends.
How does the bug-fix period work?
A build contract should include a warranty or bug-fix period after launch, during which faults in the agreed work are fixed at no charge. Three things make it work:
- A written definition of a bug: the store does not do what the agreed acceptance criteria say. Anything working as agreed that you now want different is a change, and changes are paid.
- A start and end date, written down, starting from launch day.
- A shared bug log that both sides can see, so nothing gets lost in email.
A simple bug log is enough:
| # | Found on | Page or step | What happens | What should happen | Screenshot | Status |
|---|---|---|---|---|---|---|
| 1 | Day 2 | Cart, mobile | Delivery fee shows $0 for zone B | $6 for zone B | link | Fixed day 3 |
| 2 | Day 5 | Order email | Pickup address missing | Shop address and opening hours | link | Open |
Report bugs as you find them, with a screenshot and the steps to repeat them. A list of 15 bugs sent on day 29 leaves the provider one day to fix them inside the warranty, and you will argue about which ones count. The difference between a bug and a change is set by the acceptance criteria in the statement of work; the development agency guide explains how those are written.
How do you remove old access after launch?
A launch leaves logins behind: the agency’s developers, a freelancer who helped with the import, an old provider from the previous store. Each one is a door you no longer need open. Go through this list at the end of the warranty period:
| Where | What to check | Action |
|---|---|---|
| Shopify admin | Staff and collaborator accounts | Remove or limit anyone whose work is done. Shopify’s client transfer store documentation notes that the partner keeps collaborator access by default after the transfer. |
| WordPress and WooCommerce | Users with Administrator or Shop Manager roles | Remove, or downgrade to the role the remaining work needs (WooCommerce roles) |
| Hosting account | Extra users, SSH or FTP logins | Remove provider users and change shared passwords |
| Domain registrar and DNS | Who can change where the domain points | Only you, plus your current provider if needed |
| Payment provider | Team members and connected apps | Remove anyone who does not handle money |
| Analytics, Search Console, ad and merchant accounts | User lists | Remove or set to read-only |
| Apps and plugins | Accounts registered under the provider’s email | Move them to your email, or replace |
| API tokens and connected apps | Tokens created for the build | Revoke the ones no longer in use |
Do it in one sitting with the account list from the handover pack, and write the date next to each line. It takes under an hour for a small store.
Who does what in the first 30 days?
Split the work before launch day, so nobody assumes the other side is watching.
| Task | Owner | Provider |
|---|---|---|
| Test orders and refunds | Runs them | On standby to fix |
| Order emails and wording | Checks | Fixes faults |
| Payout reconciliation | Does it | None |
| Redirects and 404s | Reports what they find | Fixes and adds redirects |
| Tracking and analytics | Compares numbers | Fixes the tags |
| Speed tests | Runs a monthly check | Fixes anything below target in the warranty |
| Bug log | Adds items | Updates status |
| Handover pack | Checks every line | Writes it |
| Access removal | Does it | Confirms nothing breaks |
If you plan ongoing help after the warranty ends, decide now between a monthly arrangement and paying per job; retainer vs one-time help compares the two.
What if sales drop after launch?
A dip in the first weeks has a short list of usual suspects. Check them in this order, from quickest to slowest:
- Checkout. Place a real order on a phone. If it fails, nothing else matters yet.
- Tracking. Compare orders in the admin with purchases in analytics. Sales that look lower in reports and normal in the admin are a tracking fault, and the shop is fine.
- Payment methods. A missing wallet or pay-later option shows up as fewer orders from mobile.
- Redirects and 404s. Old product URLs from search results or other sites landing on error pages.
- Speed. Product pages slower than before, especially on mobile.
- Delivery fees and options. A changed fee or a missing pickup option at checkout.
- Real demand. Only after the first six are clean: season, prices, stock, competitors.
Search traffic after a platform move with URL changes can take time to settle while Google recrawls the new addresses. The store migration checklist covers the move itself; this list helps you separate launch faults from that settling period.
FAQ
How long should the bug-fix period be after an ecommerce launch?
Thirty days from launch is a sensible minimum for a small store, because it covers a full monthly cycle of orders, payouts and reports. Agree the length and the start date in the contract, and ask for it to start on the real launch day if the launch moves.
Should I place test orders on the live store?
Yes. Use a real card on a low-priced product and refund it the same day. Test modes on staging do not prove that live payment settings, emails and payouts work.
What if my provider will not hand over a full handover pack?
Withhold the final payment until it arrives, if your contract ties payment to handover. If it does not, list the missing items in writing and ask for a date. Without the pack, your next provider spends paid hours finding out what the last one built.
How regularly should I check for 404 errors after launch?
Weekly in the first month, then monthly. The Page indexing report in Search Console lists 404 errors seen in the past month, so a monthly look catches new ones.
When can I remove the old provider’s access?
At the end of the warranty period, once every bug in the log is closed or moved to a paid change list. Remove it the same day the warranty ends, using the account list from the handover pack.
Do these checks apply to a redesign without a platform move?
Most of them do. A redesign changes templates, checkout steps and tracking tags just like a new build. Skip the payout checks if the payment set-up did not change, and keep the redirect checks if any URLs moved.
Who should fix a fault found after the warranty ends?
Whoever you hire for ongoing work, at their normal rate. Faults that trace back to the original build are worth raising with the old provider anyway; some will fix them as goodwill, especially with a clear bug report.
What should you do next?
Copy the three checkpoint lists into your calendar now: launch day, day 7 and day 30, with the owner of each check. Ask your provider for the handover pack contents in writing before launch, so the final payment and the pack arrive together.
If you want a second pair of eyes on your launch plan or handover pack, send a short description through the MarketPulse contact form.