When we say an ecommerce website handover is complete, we mean the store actually takes orders, records payments correctly, and you can run it without the developer. So before you sign the acceptance record and make the final payment, put the purchase flow, payments, stock, shipping, access and backups through specific tests. Record each result with evidence, meaning a screenshot or log that shows exactly what you saw. That way every defect has a clear owner and a fix date.
How is an ecommerce website handover different from finishing the visual design?
Finishing the design means the pages look the way you approved them. Handover means the store works in practice. Say you love how the store looks, but an order a customer has already paid for doesn't show up in the admin panel. However good it looks, that store hasn't passed acceptance testing.
That's why you should define the acceptance criteria for an ecommerce site as outcomes you can see and that both sides have agreed on. “The gateway is active” is not a criterion. This one is: “A test order was paid for with the correct amount and appeared in the panel with the status Paid.” Anyone who looks will see the same thing.
So I've written this ecommerce website handover checklist as tick-box items. Each item has three parts: why you check it, how you test it, and what counts as a pass. If you can't write down one of those three, the item isn't ready for testing yet.
This article covers store acceptance only. It assumes the features and the contract are already settled. If you haven't chosen your features yet, our guide to ecommerce website design before you order will help. For the order of work and who does what, see the ecommerce website design process from contract to handover.
A note on money: your contract sets the payment schedule, not this checklist. The list gives you evidence and a shared language. It doesn't replace the financial clauses in your contract.
What should you test during an ecommerce website handover?
In short, test every path that money or an order passes through. The core list covers browsing through to a placed order, successful and failed payments, duplicate returns from the gateway, and simultaneous orders. After that, check stock, shipping, discounts, returns, mobile display, admin access and backup restoration. Record each result with evidence and a named owner for the fix. In the acceptance meeting, a test nobody recorded might as well never have happened.
Before the first test, have these ready:
A defined version of the site: The version under test should have a number or a date, and nobody should change it without telling you until testing is done. Otherwise you can't tell which version a result belongs to.
Test data: A few simple products, some products with variants, a discount code, and several sample addresses in different cities.
A customer account and an admin account: Keep these separate from the developer's personal accounts so you test access under real conditions.
Contract criteria and permission to test: Keep the list of criteria at hand. For payment tests, get permission in writing.
Every check ends in one of four states: pass, fail, not run, or out of scope. Never count “not run” as a pass. A test you didn't run hasn't proved anything.
In handover meetings, I go to the “not run” items first, because the surprises that turn up after launch are usually hiding there.
How do you test a complete purchase scenario?
Take one realistic purchase and follow it step by step, from searching for a product to seeing the order in the panel. Say your store sells clothing and has a T-shirt in three colors and four sizes. The test buyer searches for it, picks green in large and sets the quantity to two. Then they open the cart, enter an address and continue to payment.
Run this scenario first, because every other handover test builds on it. Along the way, tick off the following:
Guest and member checkout: If both are in scope, test them separately. Add the item to the cart, then log in or come back to the cart from another page. Pass: color, size and quantity stay exactly as they were.
Amount reconciliation: Add up the item price, discount, tax where it applies, and shipping by hand, and compare your total with the final total on the site. Also check the currency unit in the cart, at the gateway and in notifications. Where two units are in use (rials and tomans in Iran, for example), a mismatch means an amount ten times too low or too high.
Order number and status: Match the order number and status across the customer account, the admin panel and the notification message. An SMS on its own doesn't prove the order was recorded correctly. Sometimes the message goes out while the order stays incomplete.
Separation of customer data: Log in with two test accounts. Open customer one's order page URL in customer two's browser, or change the order number in the URL. Pass: the page shows no one else's order or personal details. This test takes a few minutes, and a failure here means a data leak.
Clean-up: Mark test orders with a clear label. Then, together with the store manager, remove their effect on stock, the shipping queue and financial reports so your first month's numbers stay clean.
How should successful, failed and duplicate-return payments be checked?
In an ecommerce website handover, test payment in five states. Always take the result from the store server's confirmation, not from the page the customer sees. (The server is the computer the site runs on.) An ecommerce payment testing checklist needs at least these rows:
State | How to test | Pass condition |
|---|---|---|
Successful payment | A full purchase in the gateway's test environment, with no real money moving | One order with the correct amount and the status Paid |
Canceled by customer | Clicking Cancel on the gateway page | The order stays unpaid and the customer can try again |
Payment failure | Using failing test data | A clear error message, and stock released according to policy |
Lost connection | Closing the browser before returning from the gateway | The order isn't lost and its status can still be traced |
Unknown status | Simulated together with the tech team | The order doesn't enter the shipping queue until there's valid confirmation |
The most important point is this: a customer coming back from the gateway is not the same as a confirmed payment. The browser shows the success page. What proves the money arrived is the store server verifying the payment with the gateway. Ask the developer to show you what the server checks during that verification: the amount, the currency, the order ID and the transaction ID.
When you take screenshots of these steps, mask card numbers and gateway keys, the credentials that connect the store to the gateway. Evidence files usually pass through several people, so they shouldn't carry sensitive data with them.
A green message on the customer's screen isn't a receipt. The real receipt is the server's verification with the gateway.
A duplicate return means the result of one payment reaches the store twice, for instance because the customer refreshes the page or the gateway resends its message. The test is simple: after a successful payment, open the return URL once more. Pass: still one order, one stock deduction and one notification.
Test retries too. A customer fails once and pays again, and sometimes both transactions turn out to be successful. Any overpayment has to be identifiable in the panel so you can follow up on the refund.
Sometimes money has left the customer's account but the payment status is unclear. For this case, test the verification and reconciliation path. The order must not be released for shipping without valid confirmation, even if the customer sends you a bank receipt.
The order of work matters here. Finish testing in the gateway's test environment first. Then, if needed, run one small live transaction with sign-off from whoever is responsible for finance. Record its financial effect and the refund plan, because this time real money has moved.
Switching from test gateway keys to live ones is one of the most common breaking points in an ecommerce website handover. So every time the final gateway settings change, repeat the core payment tests. I suggest logging that repeat run as a separate entry on the form, so it's clear which settings it was run against.
How do you test stock, variants and simultaneous orders?
Inventory bugs mostly show up in two places: at the level of each variant, and at the moment two customers compete for the same item. So that's exactly where you should test stock. A reservation means temporarily setting stock aside for a customer who's in the middle of paying. Before testing, agree three things with the developer: when the reservation starts, how long it lasts, and when stock is permanently deducted.
There's no single right answer for every store. A store selling expensive items in small quantities usually needs a different policy from one selling cheap, fast-moving products. So during handover, the stock test should check your own approved policy rather than some generic pattern.
Each combination has its own data: For every color and size combination, check the price, image and stock against the panel. A common bug: the blue option shows the red image, or picks up the main variant's price.
The last unit: Suppose there's only one large green T-shirt left. Two customers on two devices go through to payment at the same time. Pass: the outcome matches your policy for selling stock.
Releasing stock: Cancellation, payment failure and an expired reservation should all release stock according to the approved policy. A returned item, though, should only go back into sellable stock once the warehouse has decided what to do with it. A damaged item shouldn't reappear in the store automatically.
Late payment: With the tech team, simulate a customer who completes payment after their reservation has been released. Pass: there's a clear way to handle the shortage, such as a phone call, a substitute offer or a refund.
Pre-orders and overselling: If these are allowed, the customer message and the order status have to say so plainly. Don't flag negative stock as a defect without checking the business policy first. Sometimes it's exactly what you asked for.
What tests do shipping, discounts and returns need?
Test these three with edge cases: carts close to a threshold, unusual addresses and multi-item orders. Many of the defects customers report after an ecommerce website handover come from here, because two rules end up applying to the same cart at once.
For shipping, check the following:
Addresses inside and outside the service area: The site shows only the shipping methods allowed for that address.
A cart right at the free-shipping line: Build one cart slightly below the threshold and one exactly at it. For example, if shipping is free from 1,000,000 tomans, make one cart at 980,000 and one at exactly 1,000,000. Then apply a discount code and see whether the site checks the threshold before or after the discount.
Heavy items or items with special conditions: The cost and shipping method follow the rule you defined.
Changing the address at the last step: The system recalculates the cost and the method, and no longer-valid method stays selected.
For discounts, test expired codes, minimum spend, usage limits, product restrictions and combined discounts, according to the features you agreed on. Also shrink the cart once after applying a code. If the total drops below the minimum spend, the discount shouldn't stay.
Returns are more delicate. Test them with a hypothetical three-item order that used a discount code. Return one item and see how the panel shows that item's share of the discount, the shipping cost and the refundable amount. It passes when the store manager can explain that exact number to the customer.
Recording a return isn't the same thing as a bank refund. If refunds are paid out manually, define who handles them, what proof of transfer is kept, and a status in the panel you can track. Finally, test canceling a single item; it mustn't cancel the whole order by mistake. The customer notification also has to match the status in the panel.
How should mobile, speed and searchable pages be checked?
Repeat the purchase flow on a real phone, not just in the mobile view of a desktop browser. Then measure speed under consistent conditions and check whether pages are indexed, meaning the search engine has added them to its index. In most stores a large share of purchases happen on phones, so don't rush this part of the ecommerce website handover.
Buying on a phone: Go through the full flow on a real phone and in the browsers you agreed on. A page loading isn't enough. Choosing a variant, the cart and the pay button all need to work comfortably with a finger.
Local and Latin digits: Enter the phone number and postal code once with local-script digits (Persian, in Iran) and once with Latin digits, because many phone keyboards send local digits. Pass: the form accepts the input or shows a clear error, and fixing the error doesn't wipe the rest of the form.
Accessibility of the purchase flow: Everyone, including someone who uses only a keyboard, should be able to complete a purchase. Fill in the form with the keyboard alone, read every field label, and judge payment errors from an ordinary customer's point of view. “Error 102” means nothing to a customer.
Speed: Measure product, category and cart pages with the same device, connection and data so the numbers can be compared. To understand the metrics, this guide to web user experience metrics is a good reference. Just don't treat one tool's score as a guarantee of speed or sales.
Searchable pages: Public product and category pages must not carry an unintended noindex directive, which tells search engines not to index a page. This sometimes gets left over from the staging version after handover. The sitemap, the file that gives search engines the list of your pages, should also be reachable.
Account and payment pages: These need access control, meaning only the customer themselves can see them. Hiding them from search engines is no substitute for security.
No checklist can guarantee rankings or when pages will appear in results. Your job at this stage is only to remove obstacles. For technical details on each directive, see Google's technical documentation on how pages appear in Search.
How should the domain, access and backups be handed over?
In an ecommerce website handover, consider these three done only when you can log into each one and use it yourself, without the developer's help. The first question I usually ask at this stage is: if you lost contact with the developer tomorrow, who would renew the domain? If you don't have a clear answer, the domain hasn't really been handed over.
Domain and hosting: Check ownership of the domain (or your contractual control over it), the hosting account (the server the site runs on), the renewal process and the recovery email. The recovery email must not be the personal address of someone on the developer's team. And remember that access to the site's admin panel is not the same as owning the domain.
Admin panel handover: The store manager logs in with their own account and does something real, such as changing a price or confirming an order. Test the roles as well. A warehouse or support user shouldn't have full rights without a good reason.
Connected services: Get a list of every account, from the gateway and SMS service to the shipping service. Agree how passwords will be transferred securely, that they'll be changed after handover, and that the developer's temporary access will be removed.
Backup restoration: Restore a backup that includes the database (where orders and product data are stored) and the essential files into a separate environment. Simply receiving a zip file doesn't count as a pass.
Checks after restoration: Compare the number of orders, a few sample orders, images and settings with the live store. In this environment, SMS and live payments must stay switched off so customers don't get strange messages.
Until you've restored a backup at least once, you're only hoping it will work.
Before signing, agree on two numbers with the developer. The first is how much data you can accept losing, for example the last few hours of orders. The second is how long the store can take to come back up after a failure. Without these two numbers, the backup part of the handover is only half done. For upkeep after handover, see our guide to scheduling regular backups.
What should training, documentation and support responsibility deliver?
The goal here is simple. After an ecommerce website handover, your team should be able to run the store without the developer, and when something goes wrong, they should know who to contact. So the handover documents should include at least:
a guide to day-to-day tasks, such as adding products, changing stock and handling orders;
a list of key settings, from the gateway and shipping methods to message templates;
dependencies and licenses, meaning plugins, themes and services that need a subscription or license, with their renewal dates;
known limitations that haven't been fixed yet;
the code and the code repository (where versions of the code are kept), as specified in the contract.
A training test could look like this: the store manager adds a product and changes its stock without any help from the developer, then takes an order all the way to ready-to-ship. During this test I usually just watch and note every place they pause. Those pauses show you where the guide falls short.
The training material also has to match the exact version you're receiving. A recording of the training session isn't proof that anyone learned anything, especially if the panel screens have changed since it was made.
For support, separate three types of request: fixes for contractual defects, new features and routine maintenance. Each one needs a way to log requests and a person responsible for replying. Write response time and fix time down separately, because a quick reply is not a quick fix. A “same-day response” commitment only means someone has seen your message, not that the problem is solved.
Some outages are outside the developer's control, such as the payment gateway or the shipping service going down. For these, ask for a clear escalation path rather than a promise of a fix. You'll find more questions about what to expect from a developer in key questions to ask web design companies.
How do you fill in the online store test form?
Log each test on the form the moment you run it, not from memory and not at the end of the day. A few hours later, details like the version or the browser have usually slipped your mind. You can copy the structure below into a spreadsheet and print from there. The form header has these fields: test ID, site version, environment, date, tester, precondition and related contract criterion. In an ecommerce website handover, this form is the main attachment to the acceptance record.
Then fill in these fields for each test. The example below is entirely hypothetical:
Field | Hypothetical example |
|---|---|
Test ID | PAY-04 |
Input and steps | Successful payment in the test environment, then reopening the return URL from the gateway |
Expected result | One order, one stock deduction, one notification |
Actual result | Two orders with different test numbers |
Evidence | Panel screenshot and technical log, with IDs and sensitive keys masked |
Severity | Blocker |
Fix owner | Developer's tech team |
Retest status | Awaiting fix |
Set severity by impact, not by how easy the fix looks. Changing one line of code may be simple, but a bug in that same line can record money incorrectly. Three levels are enough:
Blocker: any financial defect or data exposure. The store can't be accepted while it's open.
Major: a serious problem that has a temporary workaround. Going ahead with it open needs a written decision.
Minor: a cosmetic or wording issue that stays on the defect list until it's fixed.
The most dangerous defects are intermittent: they happen sometimes and not at other times. Honestly, these are the ones that worry me most. For a bug like this, write down the number of attempts and the conditions it appeared under, such as the device and the time. A bug not showing up on one attempt doesn't mean it's fixed. The defect list should also record, for each item, an owner, an agreed deadline, the result of the fix and evidence from the retest.
نمونهکارهای ما در همین زمینه
Store launch
Prices exclude payment-gateway fees, domain and hosting. Product count and variants are priced in during the consultation.
How should the acceptance record and the payment decision be set up?
The last document in an ecommerce website handover is the acceptance record. It has to show exactly what was accepted, which version was accepted, and which defects were still open. Copy the template below and fill in the blanks:
Parties: Client ………… / Developer …………
Version and scope of handover: …………
Meeting date: ……/……/……
Test attachments: test form no. …………
Documents received: …………
Items not run, and why: …………
Acceptance status: Accepted / Conditionally accepted / Not accepted
Open defects: ID, impact, owner, agreed deadline, retest condition
Signatures of authorized persons: …………
State the acceptance status explicitly, using only one of those three options. A blocker shouldn't hide behind a vague line like “handover completed”. With conditional acceptance, taking on the risk isn't something just anyone can decide, so the person who signs should have the authority to do so.
On money, the financial clause in the record should simply refer to the terms of the contract and whatever the parties have agreed in writing. This isn't legal advice, and it doesn't suggest withholding payment on your own. If you're unsure about your financial obligations, talk to your own legal adviser.
After each defect is fixed, rerun that test along with the paths connected to it. A payment fix, for example, may affect stock deduction and the shipping queue. Retesting means more than ticking the same single row again.
Here are your next steps:
Compare this list with the criteria in your contract and mark anything that's out of scope.
Complete the test form with the store manager and a representative from the developer, in one or more sessions.
Make a clear decision for each open item: fix before acceptance, conditional acceptance, or out of scope.
Sign the record with the form attached, and handle payment according to the contract.
If you haven't started the project yet, the best time to write these criteria is before the contract, when both sides have more room to negotiate. When you talk to the Niasa ecommerce website design team, ask for the feature scope and the acceptance criteria for each part to be put in writing before work begins.
Tell us about your products, the integrations you need and how your store runs day to day, so the scope is clear. Then the ecommerce website handover happens against this list, not against each side's impressions. Time and cost estimates depend on how complex the integrations are, how varied your product range is and how much needs testing. So don't ask for a fixed figure until those are clear.
فهرست امکانات و اتصالهای موردنیازتان را برای نیاسا بفرستید تا درباره دامنه طراحی فروشگاه و معیارهای پذیرش آن گفتوگو کنیم.
Frequently asked
5Is one successful payment enough to sign off on a store handover?
No. One successful payment covers only one path. You also need to know what happens to the money, the order and the stock when the connection drops, when the customer retries, or when the gateway sends its result twice.
If we find defects at handover, what happens to the final payment?
How a defect affects acceptance and payment depends on your contract and on what both sides agree in writing. Log the defect with evidence and a severity level. Then record the acceptance status, who owns the fix and the retest condition in the acceptance record.
Who should run the store's acceptance tests?
The business owner should confirm that day-to-day operations work, and the tech team should provide evidence for the specialist tests. For sensitive cases such as simultaneous payments, it helps to have both sides present so the technical result can be checked against store policy.
Do we need to make a real purchase to test the payment gateway?
You can cover many scenarios in the gateway's test environment, but the final connection may need a controlled live test. Run it with approval, a small amount and a clear plan for its effect on finances, stock and the refund.
Is getting the admin password and a backup file enough for handover?
No. You need to be able to recover the accounts and run the store on your own. A backup only counts as reliable evidence once it has been restored and tested in a separate environment.








