31 October 2026
In short
What does CRM integration involve for a Northampton business?
CRM integration for a Northampton business usually fails on hierarchy rather than on fields: the CRM holds a brand, the operational system holds ship-to sites and a rate card. GTX Digital settles what a customer is before connecting anything.
- Settle what a customer is before you connect anything.
- A brand, its ship-to sites and its rate card are three different things.
- One direction solves more than you think, at a quarter of the work.
- Duplicates are a matching problem, not a sync problem.
- An integration with no named owner fails quietly for weeks.
Think this applies to your business?
We will tell you straight whether it is worth doing, what it would take, and what we would do instead if it is not.
Tired of the two systems disagreeing? Book a technology review. Bring both screens and the spreadsheet somebody keeps on the side — that third one tells us the most.
Every CRM integration starts with the same complaint. The numbers in the CRM do not match the numbers in the system that does the work.
The technology is almost never the reason.
Decide what a customer is
In a distribution business this is the question, and it is not the one people expect.
Sales sell to a brand. Operations ship to sites. Finance invoices a legal entity. Those are three different things and all three get called "the customer".
| The layer | Where it really lives | What goes wrong when it is confused |
|---|---|---|
| The brand or group | The CRM. It is who the relationship is with | Volumes get reported against a site and look tiny |
| The ship-to site | The operational system, which knows the address and the rules | Sales promise a service the site does not have |
| The invoiced entity | Finance, and it often differs from both | Credit is checked against the wrong company |
| The rate card | Operations, versioned, with dates | Sales quote last year's price in good faith |
Write this down once, with a hierarchy, and defend it. Almost every disagreement about numbers traces back to this table not existing.
Then decide who owns each field
For every piece of data living in both systems, which one is right when they disagree?
Pick an owner. The owner can be edited. Everywhere else it is displayed and read-only.
Skip this and you get the classic failure: both systems can edit, the sync overwrites in whichever direction ran last, and someone's correction disappears overnight. People stop trusting it within a fortnight, and then they keep their own spreadsheet. Now you have three versions rather than two.
This mapping takes an afternoon with the right people in the room. It saves weeks.
Duplicates, which is the real work
Ask what the biggest CRM problem is and most teams say duplicates.
The same brand exists four times. One under the trading name, one under the limited company, one with a typo from 2018, one created by somebody who did not find the first three.
That is not a sync problem. It is a matching problem, and it has to be solved before any integration, or you will faithfully copy four customers into the other system.
In this town the awkward part is that a brand and its 3PL both appear as customers, sometimes in the same list. Decide early which one you are selling to, because it changes the match rule. Software development for Northampton logistics companies covers the operational side of the same tangle.
Whatever rule you choose, run it over the real data and have a person review the merges. Automatic merging of near-matches is how two genuinely different firms become one.
One direction solves more than you think
Two-way sync sounds obviously better. It is roughly four times the work and more than four times the failure modes.
Before agreeing to it, check what people actually do. Usually sales need to see live order and despatch status, and nothing in the CRM needs to flow back except the new brand record.
That is one-way with a small exception, and it is far simpler to build, test and keep running.
Our CRM integration work usually starts by narrowing the brief in exactly this way, and the Northampton page for it covers the local engagement.
What sales actually need to see
Not everything has to be live, and pretending it does is what makes these projects expensive.
| What they want | How fresh it has to be | Why |
|---|---|---|
| Has it shipped | Live, or close to it | They are on the phone when they ask |
| Volumes this month | Overnight is fine | Nobody makes a decision on today's number |
| Current rate card | Live, always | A stale price is a commitment you have to honour |
| Service failures | Live, and pushed rather than pulled | They would rather hear it from you than the client |
Marking each figure honestly on the screen is better than implying everything is live. "As at 06:00" is fine. A confident wrong number is not.
What breaks it after go-live
Integrations are not finished when they go live. They decay.
The vendor changes an API version. A field is renamed. Someone adds a mandatory field and records stop saving at the other end. A certificate expires. Rate limits change and the overnight run stops halfway.
So the build has to include three unglamorous things.
- Logging you can read without a developer.
- An alert when a run fails, to a person who will act on it.
- A way to re-run a failed batch without duplicating everything.
And it needs a named owner. Not a team — a person. Integrations with no owner fail quietly for weeks, and the first anyone hears is a client asking where their stock report went.
Where to start
List the five numbers your sales team asks operations for most often. Next to each, write where it lives and how fresh it has to be.
If most of them live in one system and the pain is getting them out, you have a reporting job and it is solvable in weeks. ERP integration in Northampton covers that case.
If they live in four places and disagree, settle the hierarchy first. Nothing else works until that is done.
We work across logistics and 3PL and professional services firms in the town, and the Northampton page has the wider picture. When you want it scoped, get in touch.
Common questions
Why do our CRM and operational numbers never agree?
Usually because they disagree about what a customer is. The CRM holds a brand, operations holds ship-to sites, and nobody has written down which one is the record.
Do we need a two-way sync?
Rarely. Two-way is roughly four times the work and more than four times the failure modes. Check what people actually do before agreeing to it.
What breaks an integration after go-live?
API versions, renamed fields, new mandatory fields, expired certificates and changed rate limits. It needs readable logging, an alert to a named person, and a safe way to re-run.
Next step
Start with a technology review, not a proposal.
A short, structured conversation about where your systems are costing you time, margin or growth — and what the realistic options are. No pitch deck.