Record a territorial delivery rule as country, region or postcode, service state, conditions and confirming source. Distinguish unavailable delivery, conditional service and addresses that need individual verification.
Establish the exception's scope
Begin with a specific delivery service and market. Island, administrative region and postcode are different ways of describing an area. A country name does not establish identical conditions for all its territories.
This guide documents territorial exceptions. It does not compare carriers or determine a shop's legal obligations. Use the actual service's current terms and the shop's verified rules.
Record the source document
Obtain the area and conditions list from the delivery provider. Record service name, document version, effective date and shipment scope. Small-parcel conditions may differ from transport of a large product.
Assign a rule owner. The public table should follow those confirmed arrangements. Do not copy a charge from another shop or contract, or turn a general surcharge name into an invented amount.
Separate service states
- Standard: delivery under the documented base rule.
- Conditional: delivery possible with a stated charge, timeframe or method.
- Unavailable: the selected service does not deliver to the area.
- To confirm: the exact address has not been resolved.
A surcharge is not exclusion. Missing confirmation should not become a delivery promise. If suggesting an alternative collection method, verify that method too rather than adding it automatically to every exception.
Build a territorial rule matrix
Each row contains country, area type, exact identifier, service, state, condition, effective date and source document. Preserve local postcode formatting, including significant zeros, spaces or letters.
Explain how postcode ranges are interpreted. A from–to range needs a verified matching rule, not just alphabetical order. For overlapping rules, document precedence and confirm it against fulfilment configuration.
Fictional example: Region A has standard service, Island B needs a confirmed surcharge, Area C is excluded from this service, and Area D needs an address check. These are illustrative names, not a real carrier list. Fill amounts and alternatives only from confirmed facts.
Write a message for each case
For exclusion: “The selected service does not cover this area. Contact us to check available options.” For conditions: “Delivery is possible under the stated terms; check the confirmed amount and date for your address.”
For unresolved addresses: “Availability needs confirmation before ordering.” Do not add an unsupported date promise. Connect the message to the relevant row so a general country description does not hide the exception.
Test the rules on sample addresses
Test standard, conditional, excluded and unresolved addresses. Add boundary cases for postcode ranges. Compare results with source documentation and shop messages.
Do not put actual customer data in public examples. Use a safe test set prepared by the team. The goal is agreement between rule and description, not a promise for every address in a region.
Preserve freshness and translation meaning
After a document change, check affected rules and every place repeating the information. Retain the new version date and update owner.
Translate messages without changing country, service, state or postcode scope. A language version does not expand coverage. The matrix should identify which rule applies to an area and its confirming source.
