With EOMS BD, the final instalment for your website is paid only after the admin panel is complete and you have tested the whole store on a demo link. You check every feature in the written quote, from checkout and stock to payments, shipping, staff permissions and reports, and anything that does not work as described is fixed first. After the final payment the store goes live and the source code, database and credentials are handed to you.
- Your line-by-line quote doubles as the acceptance checklist
- Five test scenarios cover orders, payments, cancellations, returns and staff access
- Bugs are fixed before payment; new features are scoped and agreed separately
- Full handover after the final payment, with no vendor lock-in
- Six months of free support and one year of free bug fixing after launch
What "pay after the demo" means
It means the last payment for your website is released only after you have used the finished store yourself, on a demo link, and confirmed that it does what the quote says it will do. You test first and pay second.
At EOMS BD every project is paid in three milestone instalments: an advance, a payment after the homepage design is approved, and a final payment once the admin panel is complete. Each stage is shown on a demo link, but the last review is the one that matters most. It is the point where you stop looking at pages and start running the store as a business would, from a customer placing an order to a staff member dispatching it. The full payment structure is explained in website development in milestone payments.
In software this step is called acceptance testing. Done properly, it protects you from paying for features that do not work, and it protects the launch from problems that would otherwise surface in front of real customers.
What counts as "done": your quote is the test plan
The feature list in your written quote defines what "done" means. If a listed feature works as described, it passes; if it does not, it is fixed before the final payment. Anything that was never in the quote is a new request, not a defect.
That is why the quote is written line by line. A vague promise such as "complete online store" cannot be tested; a line such as "stock reduces automatically when an order is placed, with a low-stock alert" can. Before you accept a quote from any developer, read the feature list as if it were the checklist you will test against later, because that is exactly what it becomes.
- Each feature is described in terms of what it does, not just its name.
- Integrations are named: which payment methods, which courier services.
- Staff roles and what each role can and cannot do are stated.
- Reports are listed individually, such as sales, orders, customers and profit and loss.
- Ownership and handover items are listed alongside the features.
Acceptance testing checklist
Work through the store in five areas: the storefront, the admin panel, payments and shipping, staff and reporting, and mobile and tracking. You do not need technical skills, only the patience to behave like both a customer and a shop owner.
Storefront and checkout
- Navigation, categories and product pages load correctly and link where they should.
- Search returns the products you expect.
- Variants such as size and colour can be selected, and the cart updates correctly.
- Checkout accepts a real-looking order and shows a clear confirmation.
- Customer accounts can be created, and past orders appear in them.
Admin panel and inventory
- Products can be added, edited and hidden, with images uploaded.
- Stock reduces when an order is placed, and low-stock alerts fire.
- Order statuses move cleanly from new to confirmed, shipped, delivered, cancelled or returned.
Payments and shipping
- Every payment method in the quote completes a transaction or, where live approval is pending, a test transaction.
- For Bangladesh stores, cash on delivery, bKash, Nagad, Rocket and optional SSLCommerz behave as specified, and parcels can be booked with Steadfast, Pathao or RedX from the admin panel.
- For other markets, the gateway you chose is tested end to end.
Staff, reports and security
- Staff accounts see only what their role permits, and the activity log records who did what.
- Reports reflect exactly the test orders you placed.
- SSL is active and the admin area requires a login.
Mobile, speed and tracking
- The whole journey works on your own phone, not just on a desktop.
- Pages load quickly and images display properly.
- If the store is bilingual, both languages read correctly.
Live payments usually depend on approval from the payment provider, and in Bangladesh bKash, Nagad and Rocket all require merchant approval. Apply as early as possible. Until approval arrives, the rest of the flow is normally verified with test mode and cash on delivery.
How to run the test: five scenarios
Rather than clicking around at random, run a handful of realistic scenarios from start to finish. Together they exercise almost every part of the store.
| Scenario | What to do | Expected result |
|---|---|---|
| Standard order | Order two products on your phone and pay with cash on delivery | Order appears in admin, stock reduces, courier booking works |
| Online payment | Place an order using an online payment method | Payment status recorded against the order |
| Cancellation | Place an order, then cancel it from admin | Stock returns, reports exclude the sale |
| Return | Mark a delivered order as returned | Status and stock update; reports reflect the return |
| Restricted staff | Log in as a staff member with limited permissions | Restricted areas are hidden, and actions appear in the activity log |
- Set aside time to complete the scenarios in one or two sittings.
- Record every issue with the page link, a screenshot, what you expected and what happened.
- Send one consolidated list rather than separate messages.
- Re-test the fixes on the demo link once they are reported as resolved.
- Release the final instalment when every quoted feature passes.
Ask the person who will actually process orders day to day to run the scenarios too. People who will use the admin panel every day spot workflow problems that owners often miss.
Bugs, adjustments and new features
A defect in a quoted feature is fixed before you pay. A new idea is scoped and priced separately, and only started once you agree. Keeping the two apart keeps the project on time and the final payment fair.
| Type | Example | How it is handled |
|---|---|---|
| Bug | Orders fail at checkout; stock does not update; a report total is wrong | Fixed and shown again on the demo link; covered by free bug fixing for a year after launch |
| Adjustment within scope | Text, images or menu order; a page that does not match the approved design | Corrected from your feedback list |
| New feature | An extra report, another payment method, an AI chatbot, multi-vendor selling | Scoped and priced in writing, agreed before work, timeline confirmed |
New ideas during testing are a good sign: they mean you are thinking about how the store will run. A practical approach is to launch the agreed scope first, start selling, and add the new features as a second phase.
Handover after the final payment
Once the final instalment is paid, the store is launched on your domain and hosting and everything needed to run it is handed to you. The domain and hosting are in your name from the start; the handover completes your control.
- Live store on the domain registered to your name and email, on hosting in your own account.
- Top-level admin access to the full admin panel.
- Complete source code: the Laravel backend and the Next.js/React frontend.
- The MySQL database and every credential the system uses.
- Search Console, Google Analytics and Meta Pixel on your own accounts.
- Free lifetime SSL and daily backups in place.
There is no vendor lock-in: you can move the store to another developer or server whenever you choose. Our page on full source code and data ownership explains what a complete handover should include.
Support after launch
After launch you receive six months of free support and one year of free bug fixing, where a bug is a problem in an existing feature. Real customers sometimes find paths that testing missed, which is why the bug-fixing period starts at launch rather than at the end of testing.
Optional yearly maintenance is available if you want EOMS BD to manage the server, but the store runs without it. New features are always scoped and priced in writing before work begins. If you are hiring from abroad, see how the wider engagement works in offshore e-commerce development for USA and UK businesses, or start with our overview of custom e-commerce website development in Bangladesh.
How EOMS BD handles acceptance: 15 years in e-commerce, 13 years as Head of IT in Saudi Arabia, clients in the USA, UK and Malaysia, and more than 150 e-commerce sites running in Bangladesh. Each stage is delivered on a demo link, the final instalment follows your own testing of the admin panel, and the code, data and credentials are handed over in full. See the client videos below, then contact us on WhatsApp at +880 1784-222255 or at info@eomsbd.com for a written, line-by-line quote.
See our work and hear from our clients
Frequently asked questions
Do I need technical knowledge to test my website?
No. Acceptance testing means using the store the way a customer and a shop owner would: placing orders, processing them in the admin panel, and checking stock and reports. The checklist and scenarios on this page are enough to guide you.
What if I find problems during testing?
Send them as one list with screenshots and page links. Anything that does not work as described in the quote is fixed and shown again on the demo link, and you re-test before releasing the final instalment.
Can I add new features while I am testing?
Yes, but features that were not in the quote are treated as new work. They are scoped and priced in writing and started only after you agree. Many clients launch the agreed scope first and add new features as a second phase.
What if payment-provider approval has not arrived by the time I test?
Live payments depend on the provider approving your merchant account, which can take time, so it is best to apply early. Until approval arrives, the rest of the order flow is normally verified using test mode and cash on delivery.
What do I receive after the final payment?
The store goes live on your domain and hosting, and you receive top-level admin access, the complete Laravel and Next.js/React source code, the MySQL database and all credentials. Search Console, Google Analytics and Meta Pixel are set up on your own accounts.
Is this process available to clients outside Bangladesh?
Yes. Demo links can be reviewed from anywhere, and we work with clients in the USA, UK and Malaysia through WhatsApp and email. The acceptance process and handover are the same wherever you are based.