Customer Feedback

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.

Add feedback Subscribe
Status Shipped
Product Configured Commerce
Categories Shipping & Fulfillment
Created by Guest
Created on Sep 4, 2024

RELATED FEEDBACK

Restrict shipping options if PO Box address

I would like to see an option in the shipping rules section where I can restrict shipping carriers depending on what is in the customer order address 1 field or even a toggle.

Example: I am trying to restrict PO Box addresses only for USPS shipping carrier since all other carriers to do deliver to PO Box addresses. I can set up a rule for a carrier that does not allow PO Box addresses where the Customer Order Address 1 field does not equal PO Box but there is no wildcard character to add to take in consideration the PO Box number so the rule does not work. There is no 'contains' option in the Select Based On dropdown.

  • Post comment
  • Guest
    Reply
    |     Oct 21, 2024

    Can you refer me to the documentation that explains how to incorporate wildcards within the rule choices? This was my issue from the beginning. Also, will I still have to add multiple rules to account for different ways PO Box could be entered ex, PO Box, Po Box, po box, etc? An example of what this might look like once the new functionality is in place would be appreciated.

    Erica Cline
    Senior Programmer E-Commerce/Web Development

    Phone: 920-393-3878 | ecline@regalware.com
    Regal Ware, Inc. | 11270 W Park Pl #800 | Milwaukee, WI 53224 USA
    www.regalware.com

    [cid:image001.png@01DB2396.4A9A89F0]

    ~WRD0000.jpg
    image001.png
    ~WRD0000.jpg
    Open full size
    image001.png
    Open full size
    ~WRD0000.jpg image001.png
  • Optimizely
    Sara Winter
    Reply
    |     Oct 18, 2024

    Great news! Our team has added this new feature and it was included in October 2024 Release. 'Not Matches' condition has been added to the rules engine wherever 'Matches' is presented including the rule engine within shipping rules. 'Not Matches' rule will support wildcards the same way as Matches does.


  • Guest
    Reply
    |     Sep 10, 2024

    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.

  • Optimizely
    Sara Winter
    Reply
    |     Sep 6, 2024

    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