Define the store you need
Describe how you sell before describing its appearance. Which products, variants, countries and customer groups must work at launch? Which tasks do people handle now, and which should the new store handle?
An existing store also brings data, search traffic and ongoing orders. List these requirements explicitly. If you prefer to handle the standard setup yourself, building a Shopify store explains the steps.
Initial costs depend on delivery scope
Both sides need to know what will be delivered and tested. A fixed price is comparable when assumptions, exclusions and changes are defined. Time-based delivery can also be transparent if budget limits and regular acceptance reviews are agreed.
We clarify scope through discovery and prepare a proposal afterwards. We quote actual project prices once the requirements are understood; this table describes cost factors rather than a price list.
| Work package | What the proposal should cover |
|---|---|
| Theme and design | Licensing, templates, pages and revisions |
| Product data | Volume, variants, preparation, import and validation |
| Migration | Data types, history, URLs and cutover window |
| Integrations | Systems, data direction, edge cases and error handling |
| Launch | Tests, domain, payments and launch assistance |
| Handover | Access, documentation, training and support |
Calculate recurring costs separately
Budget for the Shopify plan, app subscriptions, payment fees, external services where needed and ongoing support. A custom app also needs hosting and maintenance. Fees may vary with order volume, usage or plan.
For comparison, use the same planning formula: initial delivery plus twelve months of platform, apps and agreed support. Calculate payment fees separately against expected revenue and payment mix. This is a planning method rather than a guaranteed forecast. Use current Shopify pricing and the actual app plans.
Standard theme, custom theme or app?
An existing theme with tailored sections is often a sensible starting point. Check whether it supports your product pages and content. Custom theme code is useful for specific presentation or interaction requirements; a bespoke theme also needs maintenance and an update plan.
An ERP integration or a background order-processing workflow does not simply belong in the theme. It needs an integration or app. See theme customisation and custom Shopify app development. Assess checkout requirements separately because availability depends on the plan and extension type.
Write a brief that makes proposals comparable
Send the same brief to every provider. Mark requirements as essential at launch or suitable for a later release. Be open about data quality and unusual workflows: changing platforms does not remove preparation work.
- Starting point: a new store or existing platform and store URL.
- Catalogue: product count, variants, images and source data.
- Sales: countries, languages, currencies and B2B requirements.
- Design: examples and required page types.
- Systems: ERP, accounting, stock, fulfilment and marketing.
- Migration: customers, historical orders, documents and important URLs.
- Organisation: preferred date, owners and approval process.
- Operation: responsibilities, documentation and support requirements.
From discovery to launch
After the brief, requirements are checked against platform capabilities. Scope and acceptance criteria follow. An early demo using real products helps expose issues before the launch deadline.
A migration separates the test import, reconciliation and final import of new orders or stock. The launch date also depends on access, product data, payment-provider approvals and feedback. A schedule should recognise those dependencies. See our WooCommerce migration guide and Shopware migration guide.
Agency, freelancer or internal team?
Choose the skills the project needs. A freelancer may suit a clearly defined theme project. Several integrations or a migration require someone to coordinate data, development, testing and launch. An internal team makes more sense when development is continuous.
Ask specific questions: How are import failures detected? How are payment or shipping issues tested? Who handles Shopify API changes afterwards? These answers are more useful than a general claim that the store is optimised.
Agree acceptance and handover in writing
Your business should control store-owner access. Document domains, apps, payment providers and recurring contracts. Agree repository access and usage rights for custom code; third-party themes and apps retain their own licensing terms.
Accept delivery against agreed tests. Check products, mobile usability, shipping, payments, invoices, refunds and redirects where relevant. Define included defect resolution and any support commissioned separately after launch.
