Selection without dead ends
Categories, search and specifications help people find the right product.
BIG FISH / Online store development
We create online stores with a considered catalogue, product pages, basket and checkout, connecting the storefront to payment, delivery and back-office systems within the agreed scope.
from RUB 320 000 · scoped around your project
DESIGN × DEVELOPMENT × BUSINESS
Categories, search and specifications help people find the right product.
Customers can understand what they are buying, its cost and the next step.
We plan prices, stock, statuses and integration error handling.
EXPLORE THE JOURNEY
Switch options to see how the solution changes. This demonstrates the approach using fictional data.
Select an item and examine its properties.
How the work is estimated ↘Review quantities and contents before checkout.
How the work is estimated ↘Demonstration products and values.
Receive confirmation and a clear next step.
How the work is estimated ↘In a real project, this would show the reference, contents and next step.
A CLEAR PROCESS
Discuss the business, audience, content and constraints. Define the first release goal.
Agree architecture, key journeys and visual direction before full implementation.
Implement the agreed scope, connect data and review progress in stages.
Check working journeys, hand over access and agree ongoing support.
WEBSITE PRICING
The starting price is a discussion guide. The final quote depends on unique page types, workflows, source materials and integrations. Work scope and additional expenses are recorded in the proposal before the project starts.
A precise quote follows a discussion of your project.
Unique templates and content volume
Selection, forms, roles and states
CRM, payments, back office and migration
IN DETAIL / 01
We define categories, specifications, variants and filter rules, checking what exists in the back-office system and what must be prepared manually.
A sound product model supports search and reduces repetitive editorial entry.
IN DETAIL / 02
Product pages answer questions about the item, availability and terms. The basket retains selections and checkout collects the necessary details.
Testing includes quantity changes, unavailable variants, payment errors and returning to an order.
IN DETAIL / 03
Each integration has defined data ownership and exchange direction. Payment status is confirmed by the system, and repeated messages must not create duplicate orders.
Licence and provider charges are separate from development. Capabilities are checked against documentation and a test workflow.
IN DETAIL / 04
We plan category and product URLs, metadata, filter behaviour and internal links, then connect the agreed funnel events.
After launch, we examine where people abandon the journey. Store development follows data, the range and the company’s operational capacity.
FAQ
If 1C manages products, stock and orders, integration may reduce manual entry. The synchronisation scope depends on your configuration.
Volume is assessed alongside variants, specifications, filters and traffic. Product count alone is not enough to choose the architecture.
Yes. The site can accept orders or quote requests, with payment added later once the workflow is agreed.
BIG FISH / DEVELOPMENT
NEXT STEP
Start with an idea, your current website or a list of things you want to change. We will help define the next step and project scope.
Your enquiry has been sent. We will contact you to discuss the project.