Tangensys • Plan, deliver, measure
Shopify development
Build the missing store capability while respecting the platform’s extension and API limits. The right solution may be a theme change, an app or an integration.
The work to plan together
A scope shaped around this requirement.
- Custom theme developmentScope
- Custom Shopify appsReview
- ERP, CRM and fulfilment integrationsCheck
- VisitorArrives on a phone or desktop
- NavigationFinds the right page quickly
- Form or integrationEnquiry, booking or order
- Your teamReceives it in the right place
In short
What does Shopify development involve?
Shopify development builds custom themes, apps and integrations for Shopify stores.
When Shopify development is a useful fit
Shopify and Shopify Plus stores
Review theme, catalogue and checkout constraints before selecting the implementation route.
Brands needing custom features
Specify the customer action, required data and external system behind the feature.
Agencies
Agree code ownership, a development store and sign-off checks for the client handover.
Problems worth addressing first
Use these situations to identify the work that deserves attention before expanding the scope.
- Apps cannot do what the store needs
- The theme needs custom sections
- Inventory or ERP data is out of sync
A practical example
A retailer connecting inventory to an ERP needs a stock authority, a sync schedule and an exception queue; a successful API request alone does not prove stock is accurate.
This is an illustrative scenario to explain the approach, not a claimed client project.
The work we can include
The final quote identifies the deliverables, quantities, approvals and exclusions. Select the work that serves your goal rather than assuming every item is required.
- Custom theme development
- Custom Shopify apps
- ERP, CRM and fulfilment integrations
- Checkout extensions where allowed
Where we usually begin
Plan restrictions, app charges, API limits and third-party access affect scope. Checkout customisation is assessed against the store’s actual capabilities.
Practical detail
A stock integration with a reconciliation route
Imagine a store whose warehouse supplies stock quantities. An integration needs one agreed source of truth and a way to resolve delayed or failed updates.
| Part of the work | Example output | How to review it |
|---|---|---|
| Mapping | Warehouse SKU → Shopify variant; quantity and location fields | Representative variants resolve to the correct store records. |
| Sync behaviour | Update frequency, duplicate handling and failure log | A repeated message does not create a second product or conflicting stock change. |
| Store test | Available, sold-out and cancelled-order scenarios | The customer-facing state agrees with the intended inventory rule. |
| Handover | Configuration, permissions and reconciliation instructions | Staff can find a failed update and decide how it should be corrected. |
The implementation route depends on current platform capabilities, store plan and available APIs. App distribution and access requirements are checked against current Shopify documentation before agreeing the build.
Define where the store change belongs
A Shopify development request may involve the theme, an app, product data or an external integration. Identify the owner of the behaviour first. A visual product-page change differs from stock synchronisation or a checkout-related requirement, and each has different access and platform constraints.
Write the expected behaviour using a realistic product or order example. Include variants, unavailable stock and any customer restrictions. Review what the actual store setup permits before promising a particular implementation; development scope should follow confirmed capabilities.
How we check its should include the existing buying journey and the specific change. Keep app permissions, recurring charges and data flows visible in the handover. Release authority stays with the merchant or nominated owner, even where a developer has access to make changes.
Free technical review
Start with a clear scope and a practical next step.
Tell us what you want to improve and share the relevant website or project details. We will review the starting point, recommend a suitable scope and provide a custom quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Process
How the work is delivered
Review the starting point
Review the current setup, examples of the problem and the information needed to agree the work.
Agree scope and sign-off
Discovery covers existing code, users, data and external systems. We turn the main workflow into sign-off checks, then agree milestones and responsibilities.
Deliver and review
Changes are reviewed on a test environment before release. Handover includes agreed documentation, access and a maintenance route; ongoing support is separately defined.
Hand over the next steps
Review the agreed outputs together. Confirm what your team maintains and what needs a separate ongoing arrangement.
What progress should mean
Measures that match the work
Verify order and inventory consistency, error recovery and customer-facing behaviour. Track integration failures separately from store sales.
A record of delivery
See what was completed, reviewed and still dependent on access or approvals. Project delivery and business results are reported separately.
Clear limits in the data
We explain what can be verified and where a result is only an estimate. Contact clicks, conversations and sales are different actions.
Scope and responsibilities
You keep ownership of your business accounts and approved deliverables under the agreed contract. Any third-party licences, subscriptions or usage fees are identified before you commit.
Can custom store behaviour be reviewed before committing to a build?
Yes. Share the desired journey and the store setup for a feasibility review. We can identify dependencies and possible approaches. A complex request may need a separately scoped discovery or prototype before a reliable implementation quote is possible.
Can every Shopify checkout change be developed?
No. Available customisation depends on supported capabilities and the store’s setup. We confirm a supported route before including a feature in the quote.
Who pays for integration apps or usage?
The proposal identifies any recurring app, provider or usage charge. Those costs should not be hidden inside an assumed development fee.
Do you work with Shopify Plus?
Yes.
How is Shopify development priced?
We quote against your goals, current setup and agreed scope. The quote separates delivery from third-party costs and ongoing support. You receive a custom quote within 2 working days.
How long does the work take?
The timeline follows the size of the agreed scope, access, content and approvals. We confirm milestones in the quote; a simple change and a full implementation need different schedules.
How will we communicate?
Your point of contact agrees a review rhythm with you. We use email, WhatsApp and scheduled calls, with decisions and scope changes recorded clearly.
What do you need to get started?
Share your current website or system, your main goal and examples of what is not working. We then agree the access and information needed for discovery.
Is everything included in the free review?
No. The free initial review helps define the next step. Detailed research, design, implementation and ongoing support are included only when stated in your quote.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days