Skip to content
Inovo Media

Integrations

Your website, built from the system you already run.

Stock in Sage, listings in a CRM, bookings in something else. If the website can’t see it, someone types it in twice or it never goes online. I build the website to work from the system, so nobody has to.

Why it hasn’t happened yet

Most attempts ask you to get the data out yourself.

It’s usually the first thing a developer asks for: export everything to a spreadsheet so it can be shaped for the website. With thousands of products, each with its own price, VAT and stock, that never gets done, and the project stalls.

Getting the data out is my job, not yours.

One product

What Sage holds, and what the website shows.

W.R. Wright & SonsOne of their top 1,000 products
Sage 200wrwright.co.uk
FieldIn SageOn the website
NameRipon Pinhead Rusk 20Kg··R/PHRipon Pinhead Rusk (20kg)House code dropped, pack size tidied
Price29.6000 · Zero Rated£29.60, no VATPriced and taxed as Sage has it
Stock513 in the HOME warehouseIn stockAvailability, not a warehouse count
AllergensNot in SageFrom the manufacturer’s spec sheetRequired before food can go live
The result
Ripon Pinhead Rusk (20kg)
Rusk & BindersRipon Pinhead Rusk (20kg)£29.60In stockRUSK00040

Sage stays the source for products, prices, VAT and stock. Descriptions and photos added on the site survive every re-import.

How it works

The same steps, whatever your system is.

  1. Paid discovery

    I find out what’s in your data and what it means, including the rules nobody wrote down. It ends with a fixed quote for the build.

  2. I get the data out

    Straight from the system, read-only to start. You don’t export anything or fill in a spreadsheet.

  3. Clear ownership

    Your system owns what it holds. The website adds the rest, like photos and descriptions, and never overwrites it.

  4. Looked after

    Once it’s live, I look after the connection. When something in your system changes, I sort the website side.

Two examples

Two businesses, two systems, the same approach.

wrwright.co.uk/product-category/sausage-casings
Sausage casing product cards from the W.R. Wright & Sons shop, with prices, stock and codes from Sage
Sage 200 · WooCommerce

W.R. Wright & Sons

Thousands of products in Sage 200 and none of them online. The trade store is now built from a Sage export, with the products behind 90% of their sales live and a two-way sync to come.

Read the Sage 200 case study
belcor.london/properties
BELCOR office listings in Shoreditch, synced from Kato
Kato · WordPress

BELCOR

Every listing typed into Kato, then again on the website. The site now syncs from Kato every 15 minutes, and nobody retypes anything.

Read the Kato case study

Other systems

Not on Sage or Kato? That’s fine.

Those are the two examples above, not the only systems I work with. I’ve also worked with Salesforce, Brevo, Resend, n8n and Cloudflare Workers, among others.

If your system is one I haven’t used, I’ll tell you before you pay for anything.

Questions

What people ask first.

  • Do you need access to our system? Yes, read-only to start and only to what the website needs. Nothing changes in your system unless we’ve agreed it should.

  • What if we don’t know what all our data means? That’s normal, and it’s what discovery is for. Most of it comes out of the data itself, and I ask the people who use it about the rest.

  • How much does it cost? It starts with paid discovery, which ends in a fixed quote for the build. I’ll tell you the cost of discovery on the first call.

Call David.

Tell me what the system is and what the website needs from it, and I’ll tell you straight whether it’s one for me.