Start with the catalogue and the customer
A theme is only one part of a store build. Product options, collections, filtering and delivery information determine whether a shopper can make a confident choice. Map those requirements before buying apps or commissioning custom code.
- List product types, variants and required filters
- Identify wholesale, subscription or account requirements
- Document delivery zones and returns information
- Choose a realistic launch catalogue
Build a store your team can operate
Ask how promotions, stock updates, orders and refunds will be handled after handover. A launch that needs a developer for every small change creates avoidable ongoing cost. Agree reusable sections and a clear editing workflow.
- Define who maintains product data
- Check inventory and accounting connections
- Budget platform, theme and app fees separately
- Agree training and handover notes
Plan the release before changing anything
Existing stores need a redirect map, rehearsed data migration and rollback decisions. New stores need representative test orders and a launch checklist. Launch or migration work is quoted separately from an improvement sprint after the catalogue and integrations are reviewed.
- Test variants, discounts and shipping
- Confirm payment and fulfilment workflows
- Preserve useful existing URLs
- Set a release date around promotions
A common question
Is a new Shopify build included in a sprint?
No. A sprint improves an agreed part of an existing store. A new build or full migration needs its own scope and quote.