An online store in Uzbekistan: planning the budget and launch stages

A store’s budget follows the order journey, not just the number of product pages. Customers choose a variant, check availability, see delivery terms and pay; staff confirm, prepare and resolve exceptions. Describing only the storefront leaves inventory, refunds and manual handling to appear after the quote is agreed. Start with one complete order and name an owner for each step. This makes proposals comparable by outcome rather than by the name of a package or the appearance of a homepage.

1. Define the first release through tasks

Describe the assortment, delivery regions, languages, order methods and content owner. Separate required functions from later stages. Ordering without a customer account can be enough initially if a manager can confirm requests manually. Agree that choice explicitly: who receives orders, during which hours and how the customer learns the result. Do not describe a manual process as automation. Include out-of-stock items, incorrect addresses and payment failure in the brief so the quote covers more than the successful route.

2. Prepare the catalogue before estimating integrations

Supply real examples: a simple product, a size or colour variant, and an item made to order. Each needs an identifier, price, stock, images and selection rules. Name the authoritative system for price and availability. If records sit in separate spreadsheets, agree cleaning and matching first. Import work depends on data quality as well as row count. Photography, descriptions, translation and correction of the source catalogue need their own owner and deadline; they do not become development tasks automatically.

3. Build the estimate around deliverables

Development cost consists of agreed work, estimated effort and the work rate, plus separate licences and services. This is a calculation structure, not an agency price list. Request assumptions, included corrections and dependencies on your materials. Equal totals can cover different deliverables: one quote includes import and training, another only layouts. Compare payment stages and scope-change rules too. Do not automatically add the starting price of every function to a package that may already include some of them.

4. Treat payment and delivery as processes

Choosing Click, Payme or another method does not establish merchant-account readiness. Check requirements and access with the provider before fixing the date. Define when an order becomes paid and how repeated notifications, cancellation and refunds are handled. Delivery needs zones, schedules, address responsibility and a fallback when a courier is unavailable. Fees, agreements and logistics belong in the operating budget. Building a button does not complete these external arrangements, and an available test connection is not proof of production approval.

5. Use stages with a verifiable exit

1. Brief: approve workflows, catalogue, owners and exclusions.
2. Prototype: walk through product selection, ordering and error states.
3. Development: demonstrate a working order using agreed samples.
4. Integrations: test data exchange and an external-service failure.
5. Acceptance: let a staff member process an ordinary order independently.
6. Launch: check notifications, analytics, backups and access.

Name a business approver for each stage. An assortment or delivery-rule change after prototype approval needs an estimate of its effect on cost and date. Duration also depends on content and provider approvals; a calendar omitting these dependencies is incomplete. Discuss the project at https://samsa.agency/en/solutions/ecommerce or start with https://samsa.agency/en/services/web-development.

6. Accept an order journey, not a set of screens

Test on a phone: the correct variant, a quantity change, unavailable stock, an address outside the delivery area and failed payment. The order must preserve its agreed items and total, avoid duplication on repeated actions and reach the responsible employee. Staff should update its state without a developer. Check role permissions, recovery and order export separately. If search preparation is included, agree accessible category and product links, metadata and inspection of important URLs. These deliverables do not promise search positions.

7. Separate launch from ongoing ownership

List hosting, domain, paid modules, fees, catalogue entry, advertising and support separately. Loyalty schemes, complex stock rules and multiple legal sellers are not automatically part of the first release. After handover the business needs account owners, instructions and an incident contact. Request a first-year operating estimate alongside development. The launch decision then reflects both the storefront and the team’s ability to handle real orders every day, including the work that remains outside the software.

Official sources checked on 14 October 2026: Google’s store URL guidance — https://developers.google.com/search/docs/specialty/ecommerce/designing-a-url-structure-for-ecommerce-sites ; category and product navigation — https://developers.google.com/search/docs/specialty/ecommerce/help-google-understand-your-ecommerce-site-structure . The stages and acceptance criteria above are a project-preparation method, not search-engine rules for pricing.