Map the trading process
Document the source of products, prices and stock; discount rules; payment and delivery regions; order states; returns and staff roles. These decisions shape the architecture more than card styling.
Map price, stock, discount, payment, fulfilment, delivery and return rules before selecting screens or estimating catalogue work.
Scope the complete product
A useful build covers catalogue navigation, filters, product availability, resilient checkout, payment callbacks, delivery, notifications, administration, analytics and integration error logs.
Treat the ERP or inventory system as the source of truth and define conflict handling instead of allowing two systems to overwrite each other.
Understand the estimate
Our basic stores start at ₽180,000. Projects with up to 300 products, filters, promotions, reviews and ERP or warehouse exchange start at ₽350,000; complex catalogues and wholesale workflows start at ₽600,000.
Test failed payments, duplicate callbacks, expired prices, unavailable delivery and partial refunds as carefully as a successful purchase.
Test failure paths
Before launch, test changed stock, failed and repeated payments, unavailable delivery, returns and external downtime. Assign catalogue ownership, monitoring and backup duties before the first order.
Operational acceptance includes staff tools, status notifications, reconciliation and recovery, because checkout is only the customer-facing portion.
Plan search and advertising before build
Category, filter and product URLs should reflect real demand without creating indexable duplicates. Define product feeds and analytics events from product view through payment failure and success before launch.
Campaign landing pages, product feeds and funnel events need stable catalogue data and URLs, so postponing them until after launch creates avoidable rework.