Which attribute is used to map Recipient Portal functions to a delivery stop?

Which attribute is used to map Recipient Portal functions to a delivery stop?

• A. Address
• B. City
• C. Stop ID
• D. Postal Code

Answer: (C)

The key idea is to map portal actions to a specific delivery point using a unique identifier. The Stop ID provides that unique, stable reference to one exact stop in the route, so any Recipient Portal function—like status updates, notes, or delivery instructions—appears on the correct stop even if there are multiple deliveries to the same address or the route changes. Other attributes like Address, City, or Postal Code aren’t reliable for precise mapping because they can be shared by many stops or shipments and may vary, creating ambiguity or misrouting. So, Stop ID is the best choice because it uniquely identifies each delivery stop and anchors portal functionality to the correct point in the delivery sequence.

The key idea is to map portal actions to a specific delivery point using a unique identifier. The Stop ID provides that unique, stable reference to one exact stop in the route, so any Recipient Portal function—like status updates, notes, or delivery instructions—appears on the correct stop even if there are multiple deliveries to the same address or the route changes. Other attributes like Address, City, or Postal Code aren’t reliable for precise mapping because they can be shared by many stops or shipments and may vary, creating ambiguity or misrouting. So, Stop ID is the best choice because it uniquely identifies each delivery stop and anchors portal functionality to the correct point in the delivery sequence.