Ideas Portal
Several of our subscribers struggle with customers entering in incorrect or incomplete shipping addresses. Often times, this leads to shipments being returned, requiring manual intervention, increased expenses and customer service challenges.
Many eCommerce platforms offer address verification/validation that will check for accuracy, prompt the customer when a mismatch is detected and give them the option to accept the suggested correct or override it. There are many address verification services out there with open APIs, including USPS. Having this functionality available in Pressero is a much needed feature that all subscribers could take advantage of and see benefits from.
Thank you,
Ryan Mastako
Digital Marketing & eCommerce Manager
Alliance Franchise Brands
Address Validation/Verification is definitely needed. Character Limits are needed too. FedEx only accepts 35 Characters, and UPS only accepts 50 characters for all fields, Company Name, First Last Name combined, Address 1, Address 2, and City. It's too late to deal with bad addresses at the shipping stage. And we have users that put the street address in Address 2 field that is also not accepted by most carrieres, included FedEx or UPS.
This has been labeled as a 'new idea' since July 2020, any news on moving this up? Our competitors already have this functionality with their portals. And not only is it not functional and delays shipping jobs, it's embarrassing to tell clients we can't validate addresses.
This feature is definitely needed. Most online ordering sites have address validation now.
This would be a game-changer for our Pressero integration w/ our MIS system.
Cdyne was a real time address correction API we utilized at a previous company to provide US and Canadian address correction. Shipping companies make their profits from surcharges for Residential, extended area, address correction, etc. While the long term imbedded solution is considered at Aleyant, real time address correction and shipping rate comparison is available by conecting your Aleyant order flow to XPSShip.
We had the issue where "no shipping options" was showing up in the cart due to the address not being correct, but yet there wasn't an error that stated it was incorrectly entered. Thankfully we noticed this in testing rather from a concerned customer, but there needs to be something implemented to validate the addresses.
check out xpsshipper.com...we implemented this as our shipping software pushing Pressro orders from API. Real time price comparisons across all carriers including USPS, addresses validation including Residential/Commercial. Reduced our address correction weekly fees by 85%
100% agree also, we have actually invested in some software at https://addressfinder.com.au/ for this specific reason (IF YOUR BASED IN AUS), which is just simple adding a script to your site. This is so important for good in when trying to dispatch goods to clients and them not entering addresses correctly and have time delays on orders and clients unhappy etc etc.
Unfortunately the way pressero setup the State or Province field isn't 100% compatible with the script, however i am working on a solution which hopefully from this input pressero will take action.
I couldn't agree more. This should include the ability to detect if the address is a business or residence. That would help solve the other issue we encounter where we are losing money when someone ships to a residence.
Currently, when setting up shipping methods, we have the option of choosing Residential rates, which is just terrible. That means that we have to potentially include two different versions of every method that we want to allow, one for businesses and one for residences. Of course, no user is going to choose the more expensive residential option if they are shipping to their residence...they will choose the less expensive business option.
Both UPS and FedEx have the ability to include a residential rate indicator in their APIs. If you were gathering this information when an address was collected, you could provide that via the API, and we would not have to create multiple versions of every shipping method, or lose money when a customer intentionally chooses the cheaper version.