Does valid email syntax prove delivery?

No. Syntax checks do not prove mailbox existence, ownership, deliverability, or consent.

Does a postal lookup verify the whole address?

No. It provides regional context or a candidate code; full address verification is separate.

Does a valid tracking number prove movement?

No. Carrier scans and shipment status are needed to prove movement.

Contact and Shipping Identifier Validation

Goal and scope

Normalize and validate email, phone, postal, and tracking identifiers before import or dispatch.
Use this guide to turn the stated scope into a reviewable result. Keep the source, intermediate outputs, and decisions together so the next person can understand what was checked and why.

Prepare evidence and make decisions

Keep the original value beside every normalized field.
Record country, region, and carrier context before contextual checks.
Decision: Which identifier?. Route email, phone, postal, and tracking values to domain-specific rules.
Decision: Is context required?. Provide country or region for international phones and postal codes, and carrier context for tracking.
Decision: Single value or batch?. Investigate an exception individually, then use batch checks before import.

Complete the workflow

1. Preserve and classify

Copy raw fields, classify each identifier, and separate blanks from invalid values. Use text-phone-normalizer.

2. Normalize contact fields

Format phone text, resolve calling context, and check email and phone syntax. Use phone-number-formatter, calling-code, email-validator, phone-validator, global-phone-validator.

3. Validate address and shipment

Check region-aware postal values and tracking structure without treating format as delivery proof. Use global-postal-code-validator, us-zip-code-validator, postal-code-finder, tracking-number-validator.

4. Run batch gates

Recheck contact columns, retain row-level failures, and manually review ambiguous records. Use batch-email-validator, batch-phone-validator.

Verify the result before handoff

Accepted values have normalized forms and confirmed types.
Rejected values retain domain-specific reasons.
Country or region assumptions are explicit.
Batch output preserves row identity and separates valid, invalid, and ambiguous records.

Common questions

Does valid email syntax prove delivery? No. Syntax checks do not prove mailbox existence, ownership, deliverability, or consent.
Does a postal lookup verify the whole address? No. It provides regional context or a candidate code; full address verification is separate.
Does a valid tracking number prove movement? No. Carrier scans and shipment status are needed to prove movement.

Choose the right path

Which identifier?

Route email, phone, postal, and tracking values to domain-specific rules.

Is context required?

Provide country or region for international phones and postal codes, and carrier context for tracking.

Single value or batch?

Investigate an exception individually, then use batch checks before import.