We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
I was prepared to enter multiple rules to take into consideration how PO Box could be entered. I guess if it were me I would set a rule using 'contains' for PO Box and in the code itself strip any period that might be typed in (P.O. Box) and then either force upper or lower case to then see if entered text is in the Address 1 field.
Or maybe even have a toggle option on the main Details finger tab of the Carrier to allow PO Box addresses and then all of the logic listed above still would apply just without having to set up a special rule.
Thank you for submitting this request! We have added this item to our backlog for future consideration and prioritization.
Some carriers may work with USPS for 'last mile' portion of the delivery but I understand that there are use cases which would benefit from early detection and correction for shipping addresses.
Question - Regarding how the shipping rule would be leveraged would the desire that this be based on text match only (may require multiple entries to cover various ways users may enter the data) or would there be an expectation of address validation?
If there are any other details or related use cases which should be considered please feel free to add as comments