# A high address-match rate can hide failed deliveries

Measure whether people finish the address task and whether downstream work uses the intended destination. Provider matches alone are an incomplete success measure.

By Cobnex editorial. Published 2026-09-10. Updated 2026-09-11.

## Define the outcome for each address role

For a postal-contact form, success may mean a confirmed address that produces an accepted label. For a field-service job, it may mean the technician can identify the correct premises and access point. These should not share one undifferentiated Valid address metric.

Track manual completion as a legitimate outcome. If users can enter a real destination that the reference service lacks, the fallback has done its job. Counting every unmatched entry as failure encourages teams to remove useful flexibility.

Separate incomplete input, provider outage, ambiguous candidate and service-specific rejection. Each suggests a different improvement.

## Watch where users abandon the form

Measure lookup latency, selection rate, manual-entry use and validation loops without collecting unnecessary address text in analytics. Repeatedly editing the same component may indicate that the suggestion is wrong or the input model is too restrictive.

An illustrative funnel has 1,000 address attempts, 850 candidate selections and 120 successful manual entries. Reporting only an 85 percent match rate misses most of the actual completions and the 30 unresolved attempts.

Investigate the unresolved group by error category and interface state. Do not infer that all 30 addresses were fictitious.

## Reconcile quality with downstream evidence

Sample returned deliveries, corrected service destinations and support cases. Determine whether the cause was user entry, stale reference data, formatting, carrier restrictions or a later address-role mix-up.

A lookup match can coexist with a dropped unit number in a label adapter. Link the analysis to the revision actually used for the shipment rather than the customer's now-corrected profile.

Keep business outcomes in proportion. A delivery can fail for reasons unrelated to address quality, so avoid attributing every return to the validation component.

## Set acceptance around known edge cases

Require the supported unit, postal and manual-entry cases to survive storage and every relevant export. Verify that changing billing details leaves unrelated service locations alone.

Review accessibility and mobile completion alongside data quality. A technically accurate lookup that cannot be operated with a keyboard or small screen will still drive bad entries and abandonment.

The useful acceptance statement describes a completed task and preserved information. A percentage of green validation ticks does neither on its own.

## Sources

- [Australia Post Developers: address guidance](https://developers.auspost.com.au/content/apis/shipping-and-tracking/info/api-resources/addresses.html)