Book a Technology Review

Home/Insights/CRM Integration in Leicester

Insights

CRM Integration in Leicester

Why the CRM and the operational system disagree when you supply retailers, what a real integration must handle, and what it costs to keep running.

1 November 2026

In short

What does CRM integration involve for a Leicester business?

CRM integration for a Leicester supplier usually fails on who the customer is: sales deal with a buying office, operations ship to depots, and neither system agrees. GTX Digital settles that hierarchy first, then matches on the location codes the trade already issues.

  • Sales sell to a buying office. Operations ship to depots. Both are "the customer".
  • A listing decision is a relationship event, not an order.
  • 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.

Book a technology review See what we do

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 integration of this kind 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.

3Layers people call "the customer", and only one can be the record
4xThe work in two-way sync, and more than four times the failure modes
1Named person who gets the alert when a run fails

Who is the customer, exactly

In a business supplying retailers and wholesalers this is the question, and it is not the one people expect.

Sales deal with a buying office. That is where listings are won and lost, and it may never appear on a delivery note. Operations ship to depots, which have addresses, delivery windows and their own rules. Finance invoices a legal entity that matches neither.

The layerWhere it really livesWhat goes wrong when it is confused
The buying office or groupThe CRM. It is where the relationship isVolumes reported per depot look trivial
The delivery pointThe operational systemSales promise a service a depot does not take
The invoiced entityFinance, and it differs from bothCredit checked against the wrong company
The listing or rangeThe CRM, with datesNobody can say what is actually ranged

Write that hierarchy down once and defend it. Our CRM integration work starts there every time. Almost every argument about numbers traces back to this table not existing.

A listing is a relationship event

Worth treating as a first-class thing in its own right, because most systems have nowhere to put it.

Being ranged, delisted or moved between tiers is the most consequential event in a supplier's year. It usually lives in somebody's inbox.

Record it: which product, which customer, from when, at what price, and who decided. Then your volume forecasts, your production planning and your sales reporting all have the same starting point, and a delisting stops being a surprise discovered through falling orders.

One system owns it, the other displays it

With the hierarchy settled, the field question answers itself: whichever layer owns a record owns its fields, and everywhere else shows them read-only.

The failure when this is skipped is specific and quick. Both systems can edit, the sync overwrites in whichever direction ran last, and a correction made on Tuesday is gone by Wednesday. People stop trusting it inside a fortnight and start keeping their own list, which is how you end up with three versions instead of two.
## Match on the codes the trade already uses

Duplicates are the work, and supplying retail gives you an advantage most businesses do not have: the trade already issues identifiers.

Match onWhere it helpsWhere it does not
Global location numbersDepots and delivery points, which is exactly where duplicates breedBuying offices often have none
Company numberThe invoiced entityTrading names and divisions share one
Product codes used by the customerLines, where your code and theirs differOwn-label, where the code is theirs entirely
Postcode plus name fragmentEverything else, surprisingly wellTwo depots on one estate

Use the issued codes where they exist and keep your own reference alongside rather than instead. The common mistake is adopting the customer's code as the primary key, which works until you supply a second customer who numbers the same depot differently.

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 depots become one, and in a delivery context that is an immediate service failure.
## The forecast is where the two systems have to meet

This is the integration that earns its place in a production business, and it is usually the last one considered.

Sales hold the promise: what has been listed, at what volume, from when. Production needs that as a number, far enough ahead to buy material and book labour.

Where those live apart, planning is done from last year plus an opinion. Where they are connected, a listing won in March becomes a material requirement in April. Nobody rekeys it. And a delisting stops production before the stock is made, rather than after.

Two-way sync is not needed for this, and that is worth knowing: it is roughly four times the work and more than four times the failure modes. Sales need to see live order and despatch status; almost nothing needs to flow back except the new customer and the listing. One direction with a small exception is far simpler to build, test and keep running.
## Keeping it alive

Integrations are not finished when they go live. They decay, and the ways are predictable: an API version changes, a field is renamed, a new mandatory field stops records saving at the far end, a certificate expires.

So the build needs logging a non-developer can read, an alert to a named person when a run fails, and a safe way to re-run a batch without duplicating it.

The named person matters more than the logging. An integration nobody owns fails quietly for weeks, and in this business the first anyone hears is a customer asking why their order acknowledgement stopped arriving. The jobs around it are covered in business automation in Leicester.
## 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 live in one system and the pain is getting them out, you have a reporting job — ERP integration in Leicester covers that case. If they live in four places and disagree, settle the hierarchy first.

We work across food and FMCG and distribution and wholesale businesses in the city, and the Leicester page has the wider picture. When you want it scoped, get in touch.

Common questions

Why do our sales and operational numbers never agree?

Usually because they are counting different things. Sales report against a customer group, operations against delivery points, and nobody wrote down which is the record.

What is special about supplying retailers?

The decision that matters — whether you are listed — happens at a buying office that never appears on a delivery note.

Do we need a two-way sync?

Rarely. Two-way is roughly four times the work and more than four times the failure modes.

All articles

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.