Domain catalogue Locations

Ship-to and delivery addresses

Verified, standardised addresses with geocodes and delivery instructions, shared by customers, suppliers, sites and contacts.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPSalesforceCRMSnowflakelakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN SHIP-TO AND DELIVERY ADDRESSESShip-to and delivery addressesone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the ship-to and delivery addresses record comes from, how it is assembled, and who reads it. Other systems have their own page.
2 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
3
match keys
catalogue
1
hierarchies the record sits in
catalogue
3
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

Today addresses are typed into every system in a different format; carriers reject 4% of them and the same building has six spellings.

With Lima the addresses are read where they live, matched on standardised address string and country and geocode within 25 metres, assembled field by field and published as one golden record per real ship-to, with every source key underneath. The parties using the address and the deliveries and visits that went to it are one click away, because the transactions sit in the same bed.

The golden record

4 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Standardised addressstreet, house number, unit, postcode, city, region, country in the country's format
wins: verification service
Geocode and delivery datalatitude, longitude, dock hours, delivery instructions, restrictions
wins: verification service and logistics
Usagewhich parties use it and in which role
wins: the party records
Validityvalid dates, replaced-by
wins: stewards
How records match

The keys, in order

standardised address string and countrygeocode within 25 metrespostcode + house number

One address record can serve a customer as ship-to and a supplier as remit-to; usage is a relationship, so the address is kept once.

Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.

Where it sits

1 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Geographycountry → region → city → address

A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
Columnpostcode matches the country pattern
country is in the ISO list
latitude and longitude are inside the country
Rowa ship-to used for hazardous goods carries a restriction flag
a replaced address names its replacement
Businessno party keeps an unverified address as its only ship-to for more than 30 days
carrier rejections per address open a review after two
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
DeliveriesSAP LIKP; carrier events
Carrier rejectionscarrier feeds
Service visitsfield service
verified sharerejections per 1,000 deliveriesaddresses per party

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the parties using the address and the deliveries and visits that went to it.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Addresses of private individuals under the privacy policy; business addresses readable by all. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/address/verify
{
  "line1": "Werkstr. 12",
  "postcode": "71034",
  "city": "Boeblingen",
  "country": "DE"
}
response
200 OK
{
  "golden_id": "AD-118204",
  "standardised": "Werkstraße 12, 71034 Böblingen, DE",
  "geocode": [
    48.6846,
    9.0118
  ],
  "confidence": 0.99,
  "used_by": [
    "L-00731",
    "S-0114"
  ]
}

The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.

A parcel-heavy retailer verified 2.1 million addresses once and reused them across the ERP, the CRM and the carrier integration. Failed first-delivery attempts fell by 18% in the first quarter.

illustrative scenario · Ship-to and delivery addresses
Terms on this page

StandardisationRewriting an address into the format its country uses, so equal addresses look equal.
GeocodeLatitude and longitude of the address, used as a match key.
UsageThe role an address plays for a party: ship-to, bill-to, remit-to.
Golden recordThe one record for a real ship-to, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.

How long to the first golden view?

One working day for the first two sources; 2 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Logistics and 3PL, Consumer goods, High-tech and semiconductor, Industrial manufacturing. The industry pages show the domains each starts with.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.