Gravity Group Logo

Webshop development: cost, timelines and what's included

Filip Ivanović

November 13, 2026

Filip Ivanović/Software Engineer

At Gravity Group, we quote webshop development according to project scope. Development usually takes around 10 days, with the final timeline depending on the complexity of the store, product preparation and the connections required.

Before development, we agree on what you sell, how customers order and pay, and how your business processes each order. Those answers have a major influence on the proposal. A webshop with a smaller catalogue, straightforward delivery and manual order processing has a different scope from a store connected to inventory, accounting and a sales team.

Both stores can look simple on their homepages while supporting different business processes behind the scenes. It therefore helps to describe both what customers see and what needs to happen after an enquiry or purchase. This guide explains what determines the cost, the different levels of integration and how to prepare a sufficiently clear description for a quote.

How much does webshop development cost?

Gravity Group provides webshop pricing on request. We prepare a proposal after reviewing your products, sales process and required functions. Before accepting it, you can see what the development includes and which external services are arranged separately.

For an initial assessment, tell us roughly how many products you have, whether there are variants and where you sell. Then describe payments, delivery and everyday operations: who processes orders, where stock is managed and which application you use to issue invoices. If you already have a store, transferring existing data also matters.

Packages for informational websites and proposals for webshops cover different work. An informational site presents services and receives enquiries. A store with payments connects products, the shopping cart, orders, payments and subsequent processing. You can review the basic packages on our website development page, while we assess webshops according to your business requirements.

When comparing quotes, ask for a list of functions and responsibilities. A price without an explanation of scope does not tell you how many products will be entered initially, how stock is managed or what accounting integration actually covers. These details determine how much work you will later need to perform manually.

Do you need an enquiry catalogue or a store with checkout?

First establish what customers should be able to do on the site. Some businesses need a catalogue where visitors request a product quote. Others need a shopping cart and payments, while another business may require special conditions for registered trade customers. These are different implementations, even when the products themselves are similar.

Sales process
Enquiry catalogue
What the customer does
Views a product and requests a quote
What needs to be agreed
Form details and how interest is processed
Sales process
Enquiry basket
What the customer does
Selects several items and sends a combined enquiry
What needs to be agreed
Quantities, specifications and later price confirmation
Sales process
Store with ordering
What the customer does
Places an order with delivery and payment selected
What needs to be agreed
Cart, payments, notifications and statuses
Sales process
Store with customer accounts
What the customer does
Signs in and uses saved details
What needs to be agreed
Registration, access and available account functions
Sales process
Advanced store
What the customer does
Uses special prices, recommendations or connected business rules
What needs to be agreed
Price lists, benefits and agreed integrations

For example, a company selling equipment to order may need an enquiry basket. The customer selects products, after which the sales team confirms availability, pricing and delivery. In that process, a submitted enquiry is not yet a confirmed order or completed sale.

A retailer selling ready-made products may need direct ordering and payment. The complete journey then needs to work, from product selection to messages for the customer and the employee preparing the parcel. We therefore build the proposal around the actual sales process, rather than simply counting how many pages need designing.

What else influences the cost of a webshop?

Products, variants and initial catalogue entry

The number of products helps with assessment, but their structure is equally important. A product with a single version requires different preparation from an item with several sizes, colours and pack options. For each variant, we need to know whether it has its own price, photograph, identifier and stock quantity.

The proposal should distinguish building the product management system from entering the initial catalogue. We agree on who prepares the information, who enters it and how much entry work is included. A well-organised spreadsheet can simplify preparation, whereas separate prices, incomplete descriptions and unlabelled photographs need reconciling first.

Categories, search and filters

Customers should be able to find a product without understanding your internal organisation. Clear categories may be enough for a smaller catalogue. With a wider range, search and filters can help customers decide by size, intended use or compatibility.

Filters need consistent data. If you want customers to filter equipment by dimensions, those dimensions must be prepared for the relevant products. Before development, we therefore agree on the attributes and how they will be maintained when new items are added to the store.

Payments and delivery

Bank transfer, cash on delivery and card payments require different preparation. For card payments, a provider must be selected, access prepared and the successful payment, declined transaction and customer cancellation paths checked. Technical integration is separate from arranging the payment service and its fees.

For delivery, define the areas served and how the charge is calculated. A single flat rate differs from rules based on weight, destination or item type. Collection in person, free delivery above an agreed order value and products shipped in separate parcels also need clear rules.

Displaying delivery options in the cart and integrating with a delivery company have different scopes. Automatic label preparation, shipment data transfer and parcel tracking are agreed according to your workflow and the available functions of the selected system.

Moving an existing store

If you already have a webshop, we assess which products, photographs, categories and other information need transferring. Existing page addresses should be reviewed and their treatment after the change agreed. Data that is incomplete today will not become an organised catalogue merely by moving it to a different system.

The changeover also matters. The old store may continue receiving orders while the new one is being prepared. We therefore need to agree on a final reconciliation so orders or stock changes do not remain split between two separate systems.

Connecting accounting and business systems

The depth of accounting integration is an important factor in development cost and timing. The proposal should explain which data the store sends, which it receives and what happens at each stage of an order.

If you already use accounting or business software, we assess webshop integration against that system. Examples include e-racuni, Minimax, Pantheon, Luceed and other systems. Each has its own capabilities and access requirements, so the application name alone does not define the scope of integration.

  • e-racuni supports connecting webshops to orders, invoices, inventory and accounting. An application programming interface, or API, is available for custom-built stores. Official e-racuni integration capabilities
  • Minimax supports connecting external applications through its API, while webshop data can also be transferred by importing an XML file. An automated connection and an occasional import represent different scopes of work. Minimax integration guidance
  • Pantheon provides web services for exchanging data with other business systems. Before quoting, we check the available functions, access method and licences required for the particular environment. Official Pantheon web services documentation
  • Luceed provides an API for connecting its ERP and a webshop, including the exchange of stock, order and customer information. The exact data and transfer rules are defined for each project. Official Luceed API documentation

An API allows two systems to exchange agreed information. Having an API does not mean every requested function is automatically available or included in the webshop price. Before development, we check the software version, contracted modules, access permissions, required licences and whether a suitable existing connection is available or a custom one needs developing. If you use another system, send its name and describe the process so we can assess the options.

Basic level: orders and invoices

A basic scope may transfer customer details and ordered items so invoice information does not need entering again. We need to establish whether the invoice is created when the order arrives, after payment is confirmed or after a responsible person reviews it manually.

We also agree on who confirms the document, how it reaches the customer and what happens when an order is cancelled. Even at this level, distinguishing an expression of interest from a confirmed order and a received payment is useful.

Product and stock integration

A wider scope includes reconciling items and available quantities between the webshop and the business system. It is necessary to define where the main stock record is maintained, how product identifiers are matched and when changes are transferred.

If the same item is sold online and in a physical shop, we need to account for how both sales affect the quantity available. Function availability and the exact connection method are checked against the selected systems and the services your business has contracted.

Advanced business processing

A deeper integration may require rules for multiple warehouses, reservations, partial deliveries, returns and payment statuses. These are examples of possible scope that must be checked separately; selecting an accounting application does not automatically include all those functions in the webshop.

Before development, we describe when stock is reserved, what releases a reservation and who confirms a return. An integration transferring invoice data has a different implementation from a connection supporting the entire flow of goods, documents and payments.

How deeply should the webshop connect to your CRM?

A customer relationship management system, or CRM, can collect contact details or support the entire sales process. At a basic level, a form creates a new enquiry for the sales team to handle.

A more advanced integration can match an enquiry to an existing customer, record products of interest, assign a responsible employee and track a proposal. A store with purchasing may also need to link orders to the customer's history and exchange statuses between systems.

  • Which webshop information enters the CRM?
  • Are changes also transferred in the opposite direction?
  • How do we identify an existing customer and avoid duplicates?
  • What triggers enquiry assignment or a status change?
  • Which system takes priority if the same detail differs between them?

For example, sending each form as a new record is simpler than finding a customer, updating their existing record and linking an order to a sales opportunity. The name of the CRM application is therefore not enough for an estimate: we need to agree on how it will actually be used.

Advertising integration can cover basic visit tracking, purchase measurement or a connection to a later sales outcome in your CRM. Each level requires defining which events are sent and how their information is checked.

For an enquiry catalogue, distinguish opening a form from successfully submitting a request. For a store with payments, it is useful to track product views, additions to the cart, the start of checkout and purchases separately. Placing an order also does not mean payment is confirmed in every sales model.

Google supports different conversion types, including purchases and sales outcomes following an enquiry. Meta's Conversions API can connect events from a website, server or CRM. The appropriate implementation and function availability are checked for the project. Google conversion documentation, Meta Conversions API

A more advanced agreement may include order value, purchased items, catalogue connections and events sent directly from the system. When events arrive from multiple sources, it is necessary to check that the same action is not counted more than once. Settings also depend on platform rules, data processing and consent.

An ad click, an addition to the cart, an enquiry and a paid order are different outcomes. The proposal specifies what will be measured and connected. Technical integration and ongoing advertising campaign management should also be defined separately so the scope is clear.

Customer accounts, benefits and product recommendations

A customer account can provide saved addresses, order history and easier repeat ordering. A more advanced system may require different user roles or special conditions for business customers. For each function, establish what a customer can see and do.

For example, a special price list may depend on customer type or an agreement with the sales team. We then need to define who approves access, where conditions are edited and whether they come from accounting or the CRM. This goes beyond registration and sign-in alone.

Product recommendations also have different levels. A simpler option is manually selecting related items. A more complex implementation can use category, compatibility, cart contents or purchase history. A system personalised to an individual customer requires additional rules, information and checks.

For an equipment retailer, a useful recommendation could be a compatible accessory. For consumables, repeating a previous order may be more practical. We choose the function according to customer benefit and available information; automated recommendations are not a default part of every store.

What should the proposal specify?

The phrase "complete webshop" can cover different things. Before accepting a proposal, check whether it covers the store design and cart alone or also catalogue preparation, integrations and checking what happens after an order is submitted.

Area
Design and pages
What needs to be agreed
Homepage, categories, products, cart and checkout
Area
Catalogue and content
What needs to be agreed
Variants, initial entry, photographs and descriptions
Area
Payments and delivery
What needs to be agreed
Methods, rules, access requirements and external fees
Area
Accounting
What needs to be agreed
Invoices, inventory and the exact depth of data exchange
Area
CRM
What needs to be agreed
Contacts, enquiries, orders and statuses as agreed
Area
Advertising
What needs to be agreed
Events, values and platform connections
Area
Customer accounts
What needs to be agreed
Available functions, permissions and special customer conditions
Area
Handover
What needs to be agreed
Test orders and instructions for everyday use
Area
Timing and later costs
What needs to be agreed
Prerequisites, start, completion and support

A useful integration description identifies the data source, destination and timing of the transfer. For example, it should be clear whether the order is sent immediately, an invoice is created after confirmed payment or stock is checked at an agreed interval.

Exceptions also need consideration: an unavailable external system, a repeated notification for the same order or a changed quantity. We agree on how a problem is recorded, who checks it and how information is reconciled again. Those checks form part of assessing a reliable implementation.

Store operating costs after development

Separate initial development from running costs. After launch, there may be charges for payment processing, delivery, particular licences or subscriptions to accounting, CRM and other external tools. These items are checked according to the services selected.

Hosting is free with Gravity Group. Hosting should be distinguished from an external application's subscription and a payment provider's processing fees. During scoping, we therefore specify the cost of our work and anything that may be payable to other providers.

Editing products through the administration interface and developing a new integration have different scopes. Agree on which changes you can make yourself, where you report a technical problem and how future additions are assessed. Our website maintenance guide explains those responsibilities in more detail.

Also budget for work beyond the technology: product preparation, packaging, customer communication and attracting relevant visitors. Once launched, a store needs people and a clear way of working to support the orders it receives.

How long does webshop development take?

Development at Gravity Group usually takes around 10 days, depending on complexity. We confirm the final schedule after agreeing on scope. Deep connections to accounting, inventory or CRM systems and special sales rules may require a different schedule.

Catalogue preparation and available access also affect timing. The design may be ready for review while payment activation is still pending, or the product system may be complete before current prices are confirmed. We therefore need to record the prerequisites for development and for public launch.

Stage
Agreement
What we confirm
Sales process, functions and responsibilities
Stage
Preparation
What we confirm
Products, content, prices and access
Stage
Development
What we confirm
Structure, design and agreed connections
Stage
Verification
What we confirm
Orders, payments, documents and notifications
Stage
Launch
What we confirm
Approved content and readiness for real orders

If another market, customer benefits or an additional warehouse is introduced during development, we assess the effect on cost and timing. A rule change can affect several parts of the system, even when only one field changes on the screen.

The five-working-day timeline for website packages up to €500 applies to those packages. Webshops are assessed separately. Our guide to how long website development takes explains preparation and project stages in more detail.

How does project preparation work at Gravity Group?

First, tell us what you sell and how you currently receive orders. We use that information to distinguish launch requirements from possible later additions. If you already use accounting software or a CRM, tell us which system it is and what you want to retain.

After you pay the deposit, we send you a short form to complete so we can collect the information and materials needed. It helps bring products, content, business details and the ordering process into one clear agreement.

If you have no planned content or photographs, we prepare the structure, copy and suitable visuals within the agreed scope. For products, you need to confirm actual characteristics, prices and availability. Photographs should represent what customers order; dedicated product photography is arranged according to project requirements.

A clear product spreadsheet and an explanation of where the materials are stored are enough to start. Also designate the person who approves decisions so we do not receive different prices or contradictory changes for the same item during development.

Three examples of different webshop scopes

The following examples illustrate different needs. They are not fixed packages, price estimates or descriptions of particular clients. Each shows how the business process determines the functions and preparation required for a project.

A small producer with a clear catalogue

A producer sells a limited range of items within Croatia. Products have no variants, prices are confirmed and delivery follows a simple rule. An organised product presentation, ordering and agreed payment methods are important for launch.

If an employee handles orders manually, the initial integration may be narrower. Before introducing automation, it helps to identify which step takes the most time and what information is already maintained in the business application.

A retailer with variants and a physical shop

A retailer sells several sizes and colours of the same item, both online and in a physical shop. Each combination has its own available quantity. Preparing product identifiers, variants and stock reconciliation rules is therefore important from the start.

If the accounting system manages inventory, establish how the webshop retrieves stock and what happens during a reservation, cancellation or return. This project has a wider scope than simply issuing an invoice after an order arrives.

Custom products or trade customers

A company sells made-to-measure products or offers different terms to different customers. Pricing may depend on dimensions, quantity or a prior agreement. We then need to assess whether direct purchasing suits the actual sales process.

An enquiry basket, configurator or customer account with an approved price list may be relevant options. If the sales team manages proposals in a CRM, we define in advance how interest progresses to a quote, confirmation and order.

What should you check before launching the webshop?

Before the first real order, check the process as a customer and as the person preparing delivery. On a phone, select a variant, change quantity, check delivery and complete the order. Then review messages, the administration record and any documents that should be created.

Also check an interrupted payment, a repeated notification and a cancellation. In an integrated system, verify that prices, statuses and available quantities follow the agreed rules. For enquiries, confirm that information reaches the sales team or the selected CRM.

Prepare accurate information about the trader, purchasing, payments, delivery, privacy and customer rights. The European Commission explains that customers should receive clear information about products, the total price and additional charges before buying. Official guidance on online sales to consumers

Review specific legal and accounting requirements with an appropriate professional, particularly for special product categories or multiple markets. Preparing the relevant pages technically and verifying the content of business terms are separate parts of store preparation.

How do you attract customers after launch?

Connect the webshop to how people discover your products. Early visits may come from existing customers, recommendations, search or social media. Before spending on advertising, check whether visitors can understand the product, price, availability and delivery arrangements.

For search visibility, prepare clear categories and helpful descriptions. Google explains that product structured data can help it understand prices and availability and make certain richer appearances possible. It does not guarantee a particular ranking. Google guidance on product data

After launch, compare traffic sources with orders and their outcomes. If customers add products to the cart but leave before confirming, review delivery, payments and the clarity of the process. With cash on delivery or bank transfer, also track how many received orders are actually paid and delivered.

Enquiry quality, processing time and the amount of manual work also matter when assessing value. A webshop can support sales, but its effect needs to be checked against your own information. Launching a store or configuring an integration does not guarantee a customer count or a particular revenue figure.

Frequently asked questions

How much does webshop development cost at Gravity Group?

Webshop pricing is available on request. We prepare a proposal according to the sales process, catalogue, variants, payments, delivery and the depth of accounting, inventory, CRM and advertising integrations. Functions, content preparation and responsibilities are agreed before acceptance. If an existing store is being moved, we also assess the data transfer required.

How long does webshop development take?

At Gravity Group, the usual timeline is around 10 days, depending on project complexity. We confirm the final schedule after agreeing on scope and prerequisites. Product preparation, available access and external service approvals affect timing. More complex connections and special sales rules require a separate assessment.

Can the webshop connect to accounting and inventory?

Connecting to accounting and business applications, for example e-racuni, Minimax, Pantheon, Luceed and other systems, can form part of an agreed project, subject to checking the available interfaces, licences and contracted services. Transferring invoice information has a narrower scope than an integration covering products, stock quantities, reservations, deliveries and returns. Before development, we define which information moves, in which direction and at what point.

Can I edit products myself and use customer accounts?

Independent editing of products, prices and photographs is provided through the administration interface. Customer accounts, order history, special price lists and recommendations are agreed according to the store's needs. At handover, we demonstrate the functions included in your project. New connections and changes to business rules are assessed as separate additions.

What if I have no photographs or prepared descriptions?

Gravity Group can prepare the structure, copy and suitable visuals within the agreed scope. After you pay the deposit, we send a short form to gather the information required. For products, you need to confirm actual details, prices and availability. Dedicated product photography is arranged according to project needs.

Describe the store you want to launch

For the initial conversation, tell us what you sell, the approximate product count, delivery area and purchasing process. Include the accounting, inventory and CRM applications you use and what you want to connect to advertising. If you already have a webshop, send its address and explain what should be retained or improved.

You do not need to solve every technical decision in advance. Together, we define the functions required for launch, responsibilities and possible later additions. The proposal can then reflect the store you actually need to operate, rather than an unspecified list of extras.

Send us a brief description of your webshop so we can prepare a proposal with clear scope, pricing and a development timeline.

06Newsletter

Free tips to grow your business

Practical tips for tradespeople and small businesses - how to get a website, attract clients, and more. No spam.