Ideas Portal
It would be great if we could specify shipping method options per site. For instance, the account # to be billed, the surcharge per package, etc. In this way we could simplify the shipping method setup.
Currently, we have different surcharges depending on the volume of business that each customer does with us. If they order a lot, we don't charge as much per package. This is possible using the current system, but is EXTREMELY unwieldy.
Additionally, some of our customers use their own shipping accounts with FedEx or UPS. Since we are only able to setup a single UPS or FedEx account, all pricing is based on our shipper #, and as such the amount that the customer is ultimately billed by FedEx or UPS often does not match. This displeases them greatly. There is no possible work-around in the current system for this issue.
Once again I find myself responding to this idea. Is anybody at Aleyant even looking at these ideas anymore?
It should be trivial to modify the code to use the Integration ID in the Shipping Method setup page instead of the name, if it is populated. This would be a non-breaking change for customers that do not use it. Additionally the help popup for that field reads "Identification ID to be used with by the Embedded Services integration". Since we use Embedded Services to integrate with PressWise, it logically should use that field, if populated.
Our sales staff continues to have to edit every order that uses non-standard names (ex: "UPS Ground (B1)") when the order reaches PressWise. I realize that there are multiple ways to tackled this issue, as a user. I could name all the shipping methods the same as they are in PressWise (ex "UPS Ground"). However I would not easily be able to tell the difference when selecting a shipping method for a site. If I could specify surcharges at the site level, this would not be an issue.
Circling back to this idea. It has become more and more painful to try to manage this with the current setup.
Again, it has not even been reviewed, as far as I can tell. I know that you aren't going to be able to make every request happen, but this seems to be somewhat popular.
This continues to be a pain point for our company. Especially since we use the PressWise integration. If we want this to work perfectly, we have to duplicate every different named shipping method in Pressero. That is just not viable, nor should it be necessary.
Being able to use the integration ID that is already setup would help, however, it would also be hugely beneficial to be able to specify the surcharge per site.
This has been a New Idea since I first suggested it in 2019. It hasn't even been reviewed, apparently.
Hi Chris,
Is there any prediction of having this request available in the new Pressero v7?
Sincerely, Alisson Salles.
But getting customers to get their meter number, etc. etc. is a hassle so it has to be done for customers that are worth the effort.
I agree - we currently have 10 "UPS Ground"'s with inconspicuous codes at the end of each name to figure out which goes to what store. Handling markups and handling fees at a site level would make this much cleaner.
The customer carrier account has actually been there for a while. We currently use it with our stores and it works great.
Katherine,
Great catch on the Customer Carrier Account. I never noticed it, so I don't know if it's always been there, or was recently added. I would love to think that I would have noticed it before, but who knows. Yes, that works perfectly for that part of my request.
For using a customer carrier account, we are able to override the Pressero default (our account) at the site level. This is found under Settings > Shipping > Carrier Accounts (first dropdown). I don't know when this was released as I only noticed it about a month ago. Will this work for that part of this request?
Regarding the surcharges, I 100% agree. I often use handling fees and customize per customer, which requires a separate shipping method.
In addition, if you use the shipping integration with ParcelCast (formerly OnPoint), having multiple shipping methods for each custom with the same carrier method info (such as the many UPS Ground methods we have), this causes an issue with the method reported back to the customer and they seem to pick a random UPS Ground to display.