A delivery text knew my ZIP code, and I nearly treated that as proof

I was expecting a pair of running shoes, so the delivery text did not feel random. It used my ZIP code, said the address needed confirmation, and warned that the package would be returned if I did not act that day.

The link looked close enough to the carrier's name that I opened the message twice before stopping. What made me suspicious was the requested “redelivery fee.” The order page from the store showed the package moving normally and did not mention an address problem.

I had treated the ZIP code as private evidence. It was really just one correct detail attached to a request. A message can know something about an order without earning the right to collect payment information.

I did not use the link. I opened the retailer's order history and the carrier site from a saved bookmark, entered the tracking number there, and confirmed the status through those channels. I also saved a screenshot of the text before deleting it, in case I needed the sender details later.

The awkward part is that legitimate delivery messages also ask people to act. “Never trust a text” is not a workable rule when carriers, pharmacies, schools, and utilities all send real notices. The rule I need is about how I move from the message to the account: use a known app, bookmark, statement, or independently typed address instead of letting the alert choose the route.

What detail in a delivery message is useful context but not proof? And what is your quickest routine for checking a time-sensitive package problem without either ignoring a real notice or handing a suspicious link your card number?