How decisions stay traceable

Principle · 01

#Data sources are normalized

Routes, services, weight bands and scopes are expressed as consistent public facts, not copied source documents.

Principle · 02

#Rules are dated

Published rules and reference facts carry reviewed dates, and effective dates are attached where the underlying rule has a defined effective period.

Principle · 03

#Results carry reason codes

Every decision returns machine-readable reason codes and a plain-language explanation — not just a yes or no.

Principle · 04

#Public rates include effective and reviewed dates

A reference rate is shown only when it matches the route, service scope and chargeable-weight band.

These rates are public benchmarks. Confirm pricing, final carrier acceptance and customs requirements before shipment.

Principle · 05

#Every candidate service is qualified independently

The service matrix evaluates each active service across three layers — postal coverage, cargo capability and physical limits — then rolls those per-service decisions into one overall decision.

Principle · 06

#Only normalized public facts are published

Public outputs contain the decision fields customers need. Upstream sourcing detail and private commercial terms are not part of the public record.

Service-specific qualification · 01

#Postal evidence states

A service's published postal dataset falls into one of three evidence states:

Positive rule

The dataset carries explicit serviceability evidence, so a matched positive rule can qualify the service.

Exception list

The service's exception list is confirmed complete, so “no exception matched” may qualify the service.

Unknown

Completeness has not been proven. “No exception matched” cannot produce a Qualified result on its own.

Service-specific qualification · 02

#A missing exception is not coverage

The imported USA and UK datasets publish exceptions — remote areas and areas a service does not reach — not a complete list of everywhere the service goes. So “no row matched” for a postcode means “no published exception for this service at this postcode”, never “this postcode is covered”.

The distinction only moves a decision when the exception list itself is confirmed complete. Where that confirmation exists, an unmatched postcode is read as evidence rather than as silence. Where it does not, the same unmatched postcode stays at coverage confirmation required (manual review) instead of resolving to an automatic Qualified result.

Service-specific qualification · 03

#Cargo evidence

Cargo capability is read per service from its published cargo rule and mapped to one of four public states: capability documented, additional cargo review, restricted for this cargo class, or capability not documented.

“Capability not documented” is deliberately not “refused”. A service with no published statement for a cargo class has simply not declared a capability either way.

Service-specific qualification · 04

#How the overall decision is formed

Each service's postal, cargo and physical outcomes combine into that service's decision. The overall decision then follows the best available outcome across candidate services:

Qualified

At least one active service can carry the shipment within the published scope.

Conditional

One or more services need a condition confirmed before the shipment can be finalized.

Manual Review

A postal, cargo or physical detail needs a closer look before routing.

Restricted

Every active service is restricted for this shipment.