C
Jewson Direct connection · Builders Merchant Last reviewed: August 2026
🇬🇧 UK Direct

Jewson EDI,
working in the background.

Supply Lens automates the Jewson supplier document cycle. Purchase orders in, invoices out, mapped to your ERP or IMS with the right branch codes, supplier IDs and Jewson tolerance rules built in.

Orders in
Purchase orders handled automatically
Every Jewson purchase order lands in your ERP without manual intervention
Direct connection
Nothing to set up on your side
Direct link to Jewson's gateway, set up and maintained by us
Branch network
Every branch resolved on receipt
Orders arrive from branches across the country and each routes to the right account automatically
99.9%
Uptime SLA
Monitored around the clock, helping keep documents within transmission windows
Supply Lens · Jewson Live Flow Live
Jewson PO JWS-2026-64025 received via direct connection · 24× line A · 16× line B · branch routing resolved PO IN
EANs mapped · location resolved Branch matched · supplier code confirmed · trade pricing applied PROCESSING
Sales order SO-19483 created ERP / IMS · 40 units · ref JWS-2026-64025 CREATED
Invoice transmitted to Jewson £3,268.40 · validated against PO · confirmed received SENT
Jewson-Specific Requirements

Orders in, invoices out.
The detail is in the rules.

Jewson's flow looks straightforward on paper. The work is in the branch codes, the trade pricing behind every line and the tolerance rules on every invoice. Get any of it wrong and you eat a deduction. Supply Lens is configured for those rules out of the box.

Direct connection

Jewson receives supplier documents through a direct connection. Supply Lens manages the certificates, the partner profile and the gateway on your behalf, so you have no gateway of your own to build, run or maintain.

Branch level ordering

Merchants order to individual branches rather than to a central depot, so a single supplier can be delivering to hundreds of addresses on a rolling basis. Supply Lens resolves the branch on every order and sets the delivery destination in your ERP, so orders route correctly without anyone interpreting a code.

EAN to item code mapping

Jewson identifies products by GS1 EAN and an internal product reference. Supply Lens maintains a cross-reference table mapping both to your own item codes, so the order lands correctly in your ERP regardless of which identifier Jewson sends.

Invoice tolerance rules

Jewson applies strict invoice matching on price and quantity. Supply Lens validates the invoice against the originating purchase order and your agreed cost list before transmission, flagging any discrepancy for review rather than sending it and risking a deduction later.

Branch routing

Each Jewson purchase order names a destination branch by code. Supply Lens maps every active branch to the correct routing in your warehouse system, so the order lands against the right destination in your ERP without manual intervention.

Trade pricing rules

Merchant pricing is rarely a single list. Contract rates, volume breaks and branch-level agreements all affect what a line should be invoiced at. Supply Lens applies your agreed Jewson pricing when the invoice is generated, so the value Jewson receive matches what was agreed rather than a default rate somebody has to correct later.

Document Flow

Every document.
Every direction.
Automatically.

Supply Lens handles the full Jewson document set inbound and outbound, so documents are produced and transmitted automatically, without manual rekeying.

  • Purchase orders received and validated against your supplier profile
  • Invoices pre-validated against the purchase order and your agreed Jewson trade pricing before transmission
  • Branch resolved on every order so deliveries route to the right destination without manual lookup
  • Tolerance, branch and trade pricing rules applied per message automatically
  • All Jewson-specific document structures generated and read correctly without your team seeing the format
Jewson document cycle
Purchase Order INBOUND
Jewson
Invoice (pre-validated) OUTBOUND
Jewson
What's mapped automatically
Jewson reference Resolved automatically
Branch location codes
Pre-loaded
Product codes and Jewson references
Resolved per order
Trade pricing and contract rates
Applied per line
Tax and currency
UK VAT, GBP
Configuration

Configured for Jewson.
Connected to your
system.

Supply Lens holds Jewson's rules and the connection itself so you don't have to. Your team provides credentials, product mappings and the agreed trade pricing. Everything else lives in the Supply Lens layer.

1

Jewson supplier onboarding

Your Jewson supplier code, GLN and trading partner profile registered with Jewson's gateway. Supply Lens manages the connection identifiers and certificates, so there is no setup needed your side.

2

EAN and product cross-reference

Jewson EANs and product references mapped to your item codes. Pack-size variants, promotional lines and multi-pack SKUs are handled automatically once their cross-reference is established.

3

Branch routing and entity mapping

Each Jewson branch code mapped to your correct warehouse, customer account or delivery address in your ERP, so orders route cleanly to the right destination on receipt.

4

Tolerance and trade pricing

Your agreed Jewson trade pricing registered for invoice validation, including contract rates and volume breaks, so price discrepancies surface your side first.

EAN → item code cross-reference
Jewson reference Your item code
50142880031001 AMB-BEAN-400G
50142880031002 AMB-SOUP-400G
50142880031003 CHL-CHED-200G
prd:6620418-A SUPP-CO-6620418
Order ingest
Direct connection
ON
SO creation
On PO ingest
ON
Branch resolution
Per order
ON
Invoice out
On despatch
ON
Trade pricing
Per-line rates
ON
Exception queue
Email + dashboard
CONFIG
Jewson Edge Cases

The situations that
catch suppliers out.

Supply Lens handles the scenarios that typically cause invoice rejections, deductions or document mismatches in the Jewson flow.

"Jewson send documents in a format our system cannot read. We've been doing it manually for months."

The format never reaches your system. Supply Lens turns Jewson's purchase order into a clean payload your ERP already understands and renders every outbound document in the structure Jewson requires on the way back out. Your team works in their normal interface, the format conversion happens in the Supply Lens layer.

"Jewson queried an invoice because we billed at list price instead of their contract rate."

Invoice values are validated against the originating purchase order and your agreed Jewson trade pricing before submission. Contract rates and volume breaks are applied per line, so discrepancies are flagged before the invoice is sent rather than surfacing as a query weeks later.

"Orders come in from dozens of branches and somebody has to work out where each one goes."

The branch is resolved before the order reaches your ERP. Every active Jewson branch is mapped to the matching account and delivery address your side, so the order arrives with its destination already set. Your team picks and despatches rather than looking up codes.

"A new Jewson EAN started arriving and our system rejected the order because the product wasn't mapped."

Unrecognised EANs go to an exception queue immediately. The order is held, your team is notified with the full Jewson context, the mapping is added and the order is re-triggered. No silent drop, no late invoice, no missed delivery window.

Getting Set Up

What you need to
go live with Jewson.

Jewson onboarding involves their supplier team, the connection setup and your internal product and pricing data. Supply Lens manages the configuration, the gateway and the format conversion. You provide the inputs.

  • Jewson supplier code and any associated GLNs
  • Product EAN list with your internal item codes
  • Jewson product reference cross-reference where used
  • Active branch list and delivery addresses
  • Agreed Jewson trade pricing for invoice validation
  • Contract rates and volume break structure
  • ERP or IMS credentials (Unleashed, Enterpryze or other)
  • Sample Jewson purchase orders where available
  • Tolerance rules confirmation per supplier agreement
Typical delivery timeline
Day 1

Supplier data & credentials

Jewson supplier code, GLNs, ERP credentials and trade pricing received

Day 2–3

Mappings built

Product cross-reference, branch routing and pricing configuration completed in staging

Day 4–5

End-to-end test

Test purchase order processed and invoice generated, validated against Jewson's specification

Live ✓

Go live

Production enabled, first live Jewson purchase order processed end-to-end

ERP & IMS Connections

Connect Jewson to your back-office system.

Supply Lens routes Jewson purchase orders directly into Unleashed, Enterpryze or other connected ERPs with the right item codes, document series and branch routing.

Ready to automate
your Jewson EDI?

Most suppliers are live within five days. No long contracts, nothing to set up on your side. We handle the Jewson-specific configuration, you confirm the mappings.