Supply Lens automates the KeHE Distributors supplier document cycle. Purchase orders and order changes in, acknowledgements and despatch advices out, mapped to your ERP or IMS with the right location codes, supplier IDs and GS1-128 labels generated for every carton.
KeHE's flow looks straightforward on paper. The work is in the supplier and depot codes, the tolerance rules on every invoice, the despatch advice timing and the format KeHE expects each message to follow. Get any of it wrong and you eat a deduction. Supply Lens is configured for those rules out of the box.
KeHE 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.
Every carton needs a compliant label, and the serial number printed on it has to match what the despatch advice says is inside. Supply Lens generates both from the same despatch event, so the label on the box and the record KeHE receives cannot drift apart. This is the single most common cause of chargebacks and it is handled for you.
KeHE 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 KeHE sends.
KeHE expect an acknowledgement back before an order is treated as accepted, including any lines you cannot supply and the ship date you are committing to. Supply Lens raises it from your ERP automatically, so nothing sits in limbo and you are not chased for a response.
Each KeHE purchase order names a destination by code. Supply Lens maps every active KeHE location to the correct routing in your warehouse system, so the order lands against the right destination in your ERP without manual intervention.
KeHE revise orders after raising them, sometimes more than once. Supply Lens matches each change to the original order and updates it in place rather than creating a duplicate, so your warehouse picks against current quantities and the shipment you confirm matches what KeHE are expecting to receive.
Supply Lens handles the full KeHE document set inbound and outbound, so documents are produced and transmitted automatically, without manual rekeying.
Supply Lens holds KeHE's rules and the connection itself so you don't have to. Your team provides credentials, product mappings and your label requirements. Everything else lives in the Supply Lens layer.
Your KeHE supplier code, GLN and trading partner profile registered with KeHE's gateway. Supply Lens manages the connection identifiers and certificates, so there is no setup needed your side.
KeHE 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.
Each KeHE location code mapped to your correct warehouse, customer account or entity in your ERP, so orders route cleanly to the right despatch point on receipt.
KeHE carton label layout and SSCC allocation configured against your despatch process, so every label is compliant on the first shipment rather than after a chargeback.
Supply Lens handles the scenarios that typically cause invoice rejections, deductions or document mismatches in the KeHE flow.
The label and the despatch advice are generated from the same event, so they cannot disagree. Each carton gets its own serial number, that number appears on the printed label and in the record KeHE receive, and their inbound team scans against exactly what you told them was coming.
Each change is matched to the order it revises and applied in place, so there is one live version at all times. Your warehouse picks against current quantities and the despatch advice is built from the revised order, which is what KeHE match against on receipt.
The acknowledgement goes back automatically as soon as the order is accepted in your ERP, with any lines you cannot supply and the ship date you are committing to. KeHE see the answer in their own system rather than phoning to ask, and the despatch advice follows the same route when the goods leave.
Unrecognised EANs go to an exception queue immediately. The order is held, your team is notified with the full KeHE context, the mapping is added and the order is re-triggered. No silent drop, no late invoice, no missed delivery window.
KeHE 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.
KeHE supplier code, GLNs, ERP credentials and label requirements received
Product cross-reference, location routing and label configuration completed in staging
Test purchase order processed, acknowledgement, change and despatch advice generated, labels validated against KeHE's specification
Production enabled, first live KeHE purchase order processed end-to-end
Supply Lens routes KeHE purchase orders directly into Unleashed, Enterpryze or other connected ERPs with the right item codes, document series and location routing.
Most suppliers are live within five days. No long contracts, nothing to set up on your side. We handle the KeHE-specific configuration, you confirm the mappings.