API & systems integration that ends the retyping.
Your website, shop, accounts package, CRM, booking system and couriers all hold pieces of the same information, and someone in your business spends their week copying it between them. We connect the systems so the data moves itself, reliably, with a record of what happened and someone to call if it stops.
★★★★★ Rated on Trustpilot & Google · PHP and WordPress developers since 2006
Good systems, badly introduced to each other
Most businesses have bought decent software. The cost is in the gaps between the pieces, and it is paid in staff time and mistakes rather than invoices, which is why it goes unnoticed.
The double-entry tax
Orders retyped into accounts, enquiries retyped into the CRM, bookings retyped into a calendar. Hours a week, and every retype is a chance for an error.
Systems that almost talk
A Zapier zap that works until it does not, a CSV export every Friday, a plugin that syncs one way. Fragile, unmonitored and nobody owns it.
Data that disagrees
Stock says available online and sold out in the warehouse. Prices differ between the site and the till. Customers notice before you do.
The systems a UK business actually runs on
These are the connections we build most often. If yours is not listed, the last card applies.
Accounts
Xero, Sage, QuickBooks and FreeAgent: invoices raised from orders and enquiries, payments matched, customers kept in sync.
CRM and sales
HubSpot, Pipedrive, Zoho, Salesforce and bespoke CRMs: leads created from forms and calls with source and context attached.
Ecommerce and stock
WooCommerce with EPOS, warehouse and supplier systems: stock, prices and orders synchronised in both directions.
Couriers and fulfilment
Royal Mail, DPD, Parcelforce, Evri and fulfilment houses: labels, tracking and delivery notifications without the copy and paste.
Bookings and calendars
Booking engines, Google and Outlook calendars, room and resource systems, with deposits and reminders handled.
Payments and finance
Stripe, GoCardless, PayPal and Klarna: recurring billing, payouts reconciled, refunds reflected everywhere.
Marketing and email
Mailchimp, Klaviyo, Brevo and Meta: audiences kept current from real customer behaviour rather than exports.
Google services
Business Profile, Analytics, Search Console, Ads and Sheets: reporting and automation on your own data.
Anything with an API
If a system has an API, a webhook, a database or even a scheduled file export, it can be connected. If it has none of those, we will tell you.
Integrations that still work at 2am on a bank holiday
Anyone can make two systems talk on a demo. The work is making the connection survive outages, API changes, bad data and staff turnover without anyone babysitting it.
We build integrations the way we build everything else: in code you own, hosted where we can see it, with logging, retries and monitoring as standard rather than extras. The result is a connection you stop thinking about, which is the whole point.
Event-driven where possible. Webhooks push changes the moment they happen; polling is the fallback, not the default.
Queued, retried, logged. If a system is down at 2am, the job waits and retries rather than silently failing. Every run is logged so problems can be traced.
Least-privilege access. API keys scoped to what the integration needs, stored encrypted, rotated on a schedule. Never a shared admin password.
Built in the open. Plain PHP and WordPress code you own, documented, with the credentials and runbook handed over. No lock-in to a middleware subscription.
Monitored after launch. Failures alert us before they reach your inbox, and integrations are included in the care plan so they survive the next API version.
- Webhooks over polling
- Queued and retried
- Every run logged
- Code and credentials yours
What businesses usually ask us to connect first
Orders to accounts
Every WooCommerce order raises an invoice in Xero or Sage, payments reconcile automatically, refunds post as credit notes.
Enquiries to CRM
Website forms, calls and chat land in the CRM as leads with the page, campaign and town attached, and the right person is notified.
Stock and price sync
EPOS or warehouse stock reflected online in near real time, so you never sell what you do not have.
Courier automation
Paid orders generate labels and tracking with the carrier, and customers get the notifications, without anyone touching a dashboard.
Customer portals
Logged-in customers see orders, invoices, bookings or PODs pulled live from the systems that hold them. See membership websites.
Reporting dashboards
Sales, enquiries, ad spend and reviews combined from several systems into one page the owner actually reads.
Where integration fits with the rest
Custom web development
Portals, platforms and applications where integration is one part of a bigger build. Custom web development.
Custom plugin development
When the connection is best packaged as a WordPress plugin your team can configure. Plugin development.
AI automation and workflows
Adding decisions to the data flow: routing, summarising, drafting and flagging. AI automation.
Quoted to the systems and the rules
A one-way push from a form to a CRM and a two-way stock sync between a warehouse and a shop are different orders of work. We scope the systems, the data and the rules first, then quote a fixed figure for the build with monitoring and care as a clear monthly amount.
Fixed, in writing
A short call or our project brief, then a written quote with exactly what is included. The figure does not move unless you ask for more.
What moves the price
- Number of systems and direction of sync
- Quality of the APIs involved
- Rules for conflicts and edge cases
- Portals or dashboards on top
Always included
- Logging, monitoring and alerts
- Documentation and a runbook
- Code and credentials in your name
- Care plan cover for API changes
Contact us for a quote
Tell us which systems are involved and where the retyping happens today. We come back with a fixed price, a plain description of what will move where, and an honest view of anything that cannot be automated.
API and integration questions
Can you connect our website to our accounts software?
Yes. Xero, Sage, QuickBooks and FreeAgent are the usual ones. Orders and enquiries become invoices or contacts, payments reconcile, and refunds are reflected. Tell us which package and what should trigger what.
We use Zapier. Why would we need custom integration?
Zapier and Make are fine for light, low-volume connections. They struggle with volume, two-way sync, complex rules and anything that must not fail quietly, and the monthly cost climbs with use. Custom integration is for the connections your business depends on.
The system we use has no API. Is that a dead end?
Not always. Many systems offer webhooks, scheduled exports, a database we can read, or an email we can parse. We will tell you honestly what is possible and how robust it would be before you spend anything.
How do you keep our data secure?
Credentials are stored encrypted and scoped to the minimum needed, traffic is encrypted, and nothing is copied to a third-party middleware service unless you choose one. We document what data moves where so you can answer GDPR questions.
What happens when one of the systems is down?
The job waits and retries. Failures are logged and alert us, and once the system is back the queue clears in order. You do not lose orders because a courier API had a bad hour.
Do integrations break when software updates?
APIs change over time, which is why integrations are built defensively and included in your care plan. When a provider announces a version change, we handle it before it bites.
Can you build a two-way sync?
Yes, though two-way sync needs clear rules about which system wins when both change. Working those rules out with you is most of the design work, and it is where off-the-shelf tools usually fall over.
Will we own the code?
Yes. Integrations are written as WordPress plugins or standalone PHP services in your name, documented, with credentials handed over. If you ever move on, they go with you.
How long does an integration take?
A single well-documented connection is often a couple of weeks. Two-way syncs, portals and anything involving legacy systems take longer. We scope it before quoting so the timeline is realistic.
How much does API integration cost?
It depends on how many systems, whether the sync is one-way or two-way, and how well documented the APIs are. Simple connections are modest; portals and multi-system syncs are bespoke builds. We quote a fixed figure in writing after scoping, and the ongoing care is a clear monthly amount.
Let the data move itself.
Tell us which systems you run and where the copying and pasting happens. We will map what can be connected, what it would cost, and what it would save.
Mon–Fri, 9am–5pm · Kings Lynn, Norfolk · Replies within one working day.