Ecommerce website development

An online store built around the way you sell

Help customers in Vietnam browse products and place orders in the languages your store supports, with a clear process for your team to confirm and fulfil them.

AT A GLANCE

Connect product selection, checkout and order handling in one agreed workflow.

Start with
Product examples, delivery choices, payment needs and your order handling process.
Deliverable
The agreed catalogue, checkout, order states and administration with operating guidance.
Agree first
Data entry, external integrations and recurring fees are defined before implementation.

STARTING BUDGET

Online store

From8,000,000 VND/ project · one time
Get a scoped quote

What this starting fee covers

  • One language, VND and up to 20 simple products from prepared data.
  • Catalogue, cart, order requests, cash on delivery and one delivery-fee rule.
  • Basic product and order administration, statuses and handover guidance.

Separate costs / conditions: Payment gateways, carrier APIs, inventory/ERP sync, complex variants and large imports are separate.

Compare service prices →

Cost depends on the amount and complexity of the work. A smaller scope may reduce the total; we confirm this after reviewing your requirements. Work fees exclude any applicable taxes; domains, hosting, paid tools/APIs and advertising are separate. The final quote confirms scope, total, taxes and timing before work begins.

Catalogue

A catalogue that helps customers choose

Structure the site around real products and how customers choose them. A catalogue website and a store accepting orders may need different scopes.

Products and categories

Define categories, attributes, variants and the information each product page needs. Include filters, search and comparison where the data and customer needs support them.

Prices, images and availability

Agree who supplies, checks and updates product codes, descriptions, prices, images and availability. For products with variants, clarify pricing and quantities for each option.

Source data

Enter products from prepared data within the base scope’s stated quantity. Data cleaning, large imports and system connections are assessed and quoted separately when needed.

TRY A SHOPPING FLOW

From a selection.
To a demo order.

Add items, change quantities, choose fulfilment and create a sample confirmation. This example helps us discuss how a store should work; it is not a client project.

Illustrative catalogue and prices.

No purchase, payment or data submission. Everything runs in this open page; reloading or switching language resets the sample cart. Maximum 9 units per item; the illustrative delivery fee is 30,000 VND.

01 / Choose sample products

Sample ceramic cup

Sample item A · Not for sale

120,000 VND

Sample canvas bag

Sample item B · Not for sale

180,000 VND

Sample notebook

Sample item C · Not for sale

65,000 VND

02 / Demo cart

0 items

Your cart is empty. Add a sample product above to begin.

Increase, decrease or remove each item. The limit of 9 units per item applies to this demonstration only.

03 / Review and confirm

Illustrative payment method: on receipt. No money is collected and no name, address or contact details are requested.

Subtotal
0 VND
Sample delivery fee
0 VND
Demo total
0 VND

Add a product to try the flow.

Checkout

From a reviewed cart to a received order

Clarify the cart, charges and order statuses before customers confirm.

A clear cart

Customers can review products, change quantities and remove items. Agree totals, delivery charges, any discounts and how price changes or unavailable stock are handled before confirmation.

Checkout and payment methods

Define required fields, delivery areas, collection and payment methods. A payment gateway integration needs suitable accounts, technical documentation and a test environment before implementation.

Confirmation and order status

Distinguish received, confirmed, paid, dispatched and completed orders according to the agreed workflow. Check retries, uncertain payment outcomes and failed updates so customers and staff know the next step.

Administration

A store your team can operate

Define administration, data and handover alongside the buying journey. Connections to inventory, accounting or delivery systems require their own assessment.

Roles and permissions

Agree who edits products, changes prices, views orders and updates statuses. Limit access by role and identify the management screens, notifications and change history the team needs.

Check the full journey

Use sample products and orders to check mobile layouts, carts, charges and statuses. Where external connections are included, test them in an approved test environment against agreed scenarios.

Handover and running costs

Hand over accounts, source code and assets covered by the agreement, with guidance for managing products and orders. Separate the build fee from hosting, licences, external service fees and maintenance, and explain the delivered system's limits.

HOW WE WORK

Clarity at every step.

  1. Understand the sales process

    Review products, data, order intake, fulfilment, payments and responsibility for each step.

  2. Agree the structure and scope

    Approve pages, management screens, data fields, statuses and the integrations to implement.

  3. Build and test with sample orders

    Develop the components, import the agreed data and check successful flows, errors and retries.

  4. Launch and hand over

    Review the checks and prepare access, operating guidance and support arrangements before launch.

FAQ

Before we begin.

A few useful answers to help define the right scope.

Can we start with a catalogue and order requests?

Yes. If you do not yet need online payments or complex inventory management, we can scope a catalogue, cart and order requests for staff to confirm. The page must make the order stage clear and cannot describe an order as paid without confirmation.

Which payment method does the base scope include?

The base scope uses cash on delivery (COD). Online payment gateways are quoted separately after reviewing account requirements, technical documentation, fees and transaction handling.

Can it connect to our inventory or existing software?

We review the system, data and connection options before confirming an approach. The proposal defines the main data source, sync direction, update timing and error handling.

Can my team update products and handle orders?

The base scope includes product and order administration and basic statuses. We agree user permissions and provide operating guidance. Additional management screens, permissions or workflows are assessed separately.

What determines the cost?

The published starting price covers the stated base store scope. Page templates, product types and variants, data entry, languages, order management and external integrations determine the actual workload. The final quote separates development, data preparation and recurring costs.

What should I prepare?

Share product groups, examples of existing data, intended delivery and payment methods, who handles orders and the systems you use. Do not send real customer details or passwords; suitable test data is enough to define the initial requirements.

LET’S DEFINE THE REQUIREMENTS

Define how your online store should work.

Share your products and the delivery and payment options you need. We will clarify the catalogue, order flow and systems that need to connect.

Discuss your online store