Territorial Logic Layer Initiative

The internet doesn't understand complex territories. TLL does.

A new foundational layer that connects real-world territorial complexity with digital systems, commerce, and infrastructure. Reach customers competitors block. Stop bleeding support hours on tax, address, and routing errors.

Reflects reality

Åland, Faroe, and Canaries modeled as themselves, not as their parent states.

System agnostic

One HTTP call. Works with any tax engine, payment provider, or carrier.

Universal layer

Address, tax, locale, licensing all read the same profile.

Future proof

Versioned profiles with dated diffs and source citations.

Built for payment platforms, commerce stacks, logistics APIs, and content distributors
EU VAT in the Digital Age · 2025 → 2035

The EU is digitising VAT. The map underneath hasn't caught up.

Today, selling VAT-correctly across the EU means juggling 27 national registrations, half a dozen national e-invoice formats, and a different rulebook for every digital platform. ViDA collapses that, by 2030, into one VAT registration per business, one e-invoice standard for every cross-border B2B sale, and uniform rules that force short-stay and ride platforms to collect the VAT themselves. The plumbing only works if the stack can tell where each address actually sits for tax. Today it can't: Mariehamn resolves to Finland, Las Palmas to Spain, Belfast to plain UK. TLL is the territory layer ViDA assumes already exists.

  1. 31 Dec 2026 first transposition deadline Now
  2. 1 Jul 2028 single VAT registration starts
  3. 1 Jan 2030 platform deemed-supplier mandatory
  4. 1 Jul 2030 intra-EU e-invoicing on EN 16931
See how TLL closes the gap
The problem, in 30 seconds

A country code is not a rule set.

Dozens of territories around the world sit partly inside and partly outside the regimes that commerce stacks model as single countries: customs unions, VAT areas, licensing zones, postal networks. ISO 3166-1, ISO 3166-2, WIPO ST.3, EU VAT, and UPU each answer differently. The stack silently picks one, and gets the rest wrong. We start with the EU special regions because that is where European commerce platforms feel the pain first.

01 / ADDRESS

Checkout breaks.

Country selector doesn't know the territory exists, or aliases it to its sovereign parent. Postcode validation rejects the local format, or accepts the parent country's. Valid addresses bounce with a generic error.

abandoned carts
02 / PAYMENT

Tax is wrong.

Parent country's VAT rate is applied. The territory may be outside the VAT area, under a local regime, or require a customs declaration instead.

tax exposure · per-order
03 / LOGISTICS

Delivery fails.

Carrier routes as domestic. Parcel arrives at an international sorting facility without paperwork, is held or returned to sender.

SLA miss
04 / LANGUAGE

Wrong locale served.

Locale is inferred from country, not territory. Swedish-speaking Åland gets Finnish copy. Catalonia gets Castilian. Quebec gets metropolitan French.

localisation gap
05 / DATA RESIDENCY

Wrong privacy regime.

Greenland and the Faroes sit outside EU GDPR; Åland sits inside. Country-level routing picks the wrong lawful basis, controller location, and cross-border transfer rules.

regulatory risk
06 / CONTENT

Wrong licensing applied.

Streaming windows and rights regions are bound to country codes. Territories silently inherit their parent state, so Greenland gets Danish rights and the Faroes get something inconsistent. The licence that should apply, does not. Viewers see catalogues they shouldn't, or miss catalogues they've paid for.

rights breach