A single flow of records leaving one system and arriving in another that a person actually reads.

Connect Shopify without losing track of the data.

We define which system owns each record, what crosses the boundary, what happens when a call fails and who is responsible after launch.

Discuss a store See starting prices

The expensive failures are often quiet

An integration can return a successful response and still write the wrong stock level, customer, price or order status. An alert for failed calls is not enough if bad data can pass through as valid.

The first scope is therefore the data contract, not the API endpoints.

What we agree before building

which system owns products, stock, prices, customers and orders;
identifiers used to match records across systems;
direction and frequency of each data flow;
transformations and validation rules;
duplicate and out-of-order event handling;
retry behaviour and limits;
monitoring for failed calls;
reconciliation that catches successful calls carrying wrong data;
manual recovery when automation cannot safely decide;
who maintains each side of the integration.

Launch and ongoing responsibility

We test with representative records and volumes before live use. The launch plan states how writes are enabled, how results are checked and how the flow is stopped without corrupting the source of truth. Monitoring and reconciliation ownership are agreed before release.

The shape of it

Where an integration sits

Three stages, and the direction each record actually travels.

Shopify

ShopifyStorefront, orders and customer records

Shopify to Integration service

Orders, customers and product data leave Shopify.

Integration service back to Shopify

Values owned elsewhere — typically stock and price — are written back to Shopify.

Integration service

Named ownership per entityOne system holds the truth, the others hold a copy
Direction and timingOne way or two, on a schedule or on an event
Failure handlingWhat happens when a call fails, decided before it does
ReconciliationCompared against source counts on a schedule

Integration service to Connected systems

Each boundary is scoped separately, because each one fails differently and at a different urgency.

Connected systems

ERP and inventoryStock, product data, purchase orders and multi-location availability
Accounting and taxOrders, refunds, payouts and fees
Fulfilment and carriersOrders out, tracking back, and the exceptions
CRM, email and feedsCustomer and order data with consent state carried

Shopify, the integration service in the middle, and the categories of system on the other side of the boundary.

These are system categories, not named products. Which system owns each entity is a business decision, made before any code exists, and the specific systems are named per project rather than published here.

Money

What this work starts at

Integration delivery

Scoped after a technical review

One bounded piece

Project sprint

£1,500$2,000

One bounded improvement: landing pages, a template rebuild, an analytics implementation, or a build-readiness review credited against a larger project.

One defined outcome, agreed before work starts
Fixed price and a fixed finish line
Credited against a larger project where it leads to one

Fixed price

Plus, B2B, multi-market

Advanced Shopify

From £8,000From $10,500

Shopify Plus, B2B, multi-market, multi-language, custom integrations or headless work. These configurations are sized after discovery, not instant-priced.

Trade accounts, price lists and B2B rules
Multi-market and multi-language configuration
ERP, PIM, WMS and accounting integrations
Headless or custom storefront work where justified

Starting price · scoped after discovery

Ongoing responsibility

Monitoring and maintenance after launch

Per month

Optimisation

From £1,250From $1,650

A live improvement programme on one site. You set the priorities each month, we work the queue in order, and the month closes with what changed and what it did.

Outcome: measurable improvement to one live site
Queue: one active workstream, reprioritised monthly
Response: next working day
Scope: conversion, SEO, content and development work

Starting price

Per month

Development partner

From £3,000From $4,000

Continuous delivery across an agreed portfolio, with planning ahead of the work rather than a queue you have to keep feeding.

Outcome: continuous delivery across your estate
Queue: two active workstreams, planned a month ahead
Response: same working day, UK working days
Scope: Shopify and marketing-site delivery, plus roadmap planning

Starting price

Integration work is scoped after reviewing the other system’s API, its rate limits and the volumes involved. A published figure before that would be a guess, and integration guesses are expensive in one direction only.

Pricing

Questions

Your questions

Do we need custom development, or will an app do?

An app or a middleware platform is usually the better first answer, because someone else maintains it against platform changes. Bespoke work earns its place where the flow is specific to how your business operates and no off-the-shelf mapping fits.

Who owns the integration afterwards?

Whoever is named in the scope. APIs are versioned and deprecated on the vendor’s schedule, not yours, so an integration without a maintenance owner is a fault waiting for a quiet week. That is agreed before it is built.

Can you integrate with a system that has no public API?

Sometimes, through scheduled exports, a database connection or a file drop. It is slower and more fragile than an API, so it is scoped with those limits stated rather than presented as equivalent.

How do we know it is still working?

Monitoring and a scheduled reconciliation report. Alerting on failure is not enough on its own, because the most expensive integration faults are the ones that succeed with the wrong data.

Which systems do you need to connect?

That answer, rough daily volumes and a sample record are enough for a useful first conversation.

Discuss a store See pricing