S
selfcancelsignal
Guest
I suppose.We are paid well to be inconvenienced that way
I suppose.We are paid well to be inconvenienced that way
I have one smart pickup that has only shipped about five times in the last two years. Always wonder why this guy pays a weekly fee versus an OCA.
Have you suggested that option to him?
There's a business on my route that is a smart pickup but for some reason it cancels the pickup even when they have stuff shipping out <snip>
They may have changed the application (Worldship or PickUp API) but the way it works is that if they do not ship a package within one hour of their scheduled pickup time in DCS, the pickup is canceled.
They can then schedule an On Call P/U if they want to but their "Scheduled P/U" is flagged as "NO" in the system and is removed from the driver's DIAD.
BTW, Smart Pickup was my project and why I became interested in Brown Cafe again. I was the person that laid out the rules and helped architect the system.
So what your saying is a customer who's p/up account is enabled as a smart p/up can be inconvenienced if they have a shipment within 59 minutes of their scheduled pick up time. Sometimes these new services that UPS offers are more of a benefit to UPS than the customers. I think that if you are still paying the same rates as a daily, and not for just the days we come by, the customer is being stolen from.Okay... I'm not a UPS employee. I'm a customer, one that's putting forth the effort to integrate shipping into my internal workflow applications. I'm using the Shipping API and the Pickup API. I ran across this forum while searching for a solution as to why I couldn't trigger a Smart Pickup. I was compelled to join to share what I have learned...
I'd be willing to bet that the mentioned business is using the API. I ran into the same problem. The Shipping API does not provide any means to schedule a pickup - that's what the Pickup API is for. BUT, the Pickup API has provisions to schedule only on-call pickups. It can not trigger a Smart Pickup. Since this capability is absent, the pickup drops off your board.
A workaround for this is to have your customer use UPS Internet Shipping to schedule a Smart Pickup each day they have a shipment.
From what I've been able to learn, the decision to not support triggering of a Smart Pickup was made by the business to prevent third-party software from triggering it. Such software, apparently, uses the same API that I use. I don't pretend to understand the reasoning behind this - perhaps it would expose some form of vulnerability to abuse.
As a Smart Pickup customer, I'm paying for the pickup whether I use it or not. So, at least for me, it boils down to communicating with the driver to come by, which is accomplished most easily by triggering the Smart Pickup.
With all that said, perhaps the API for triggering a Smart Pickup should be available for customers that have it enabled on their account.
Sales people??? Do they still exist?? My larger pick up accounts hear more from the FedEx salespeople trying to convert them over than our own people.That's not his job. that's the salespersons job
Okay... I'm not a UPS employee. I'm a customer, one that's putting forth the effort to integrate shipping into my internal workflow applications. I'm using the Shipping API and the Pickup API. I ran across this forum while searching for a solution as to why I couldn't trigger a Smart Pickup. I was compelled to join to share what I have learned...
I'd be willing to bet that the mentioned business is using the API. I ran into the same problem. The Shipping API does not provide any means to schedule a pickup - that's what the Pickup API is for. BUT, the Pickup API has provisions to schedule only on-call pickups. It can not trigger a Smart Pickup. Since this capability is absent, the pickup drops off your board.
A workaround for this is to have your customer use UPS Internet Shipping to schedule a Smart Pickup each day they have a shipment.
From what I've been able to learn, the decision to not support triggering of a Smart Pickup was made by the business to prevent third-party software from triggering it. Such software, apparently, uses the same API that I use. I don't pretend to understand the reasoning behind this - perhaps it would expose some form of vulnerability to abuse.
As a Smart Pickup customer, I'm paying for the pickup whether I use it or not. So, at least for me, it boils down to communicating with the driver to come by, which is accomplished most easily by triggering the Smart Pickup.
With all that said, perhaps the API for triggering a Smart Pickup should be available for customers that have it enabled on their account.
So what your saying is a customer who's p/up account is enabled as a smart p/up can be inconvenienced if they have a shipment within 59 minutes of their scheduled pick up time. Sometimes these new services that UPS offers are more of a benefit to UPS than the customers. I think that if you are still paying the same rates as a daily, and not for just the days we come by, the customer is being stolen from.
The developer must know certain keys that are not published to the public in order to initiate a Smart Pickup transaction. The Pickup API is used for Smart Pickups.Okay... I'm not a UPS employee. I'm a customer, one that's putting forth the effort to integrate shipping into my internal workflow applications. I'm using the Shipping API and the Pickup API. I ran across this forum while searching for a solution as to why I couldn't trigger a Smart Pickup. I was compelled to join to share what I have learned...
I'd be willing to bet that the mentioned business is using the API. I ran into the same problem. The Shipping API does not provide any means to schedule a pickup - that's what the Pickup API is for. BUT, the Pickup API has provisions to schedule only on-call pickups. It can not trigger a Smart Pickup. Since this capability is absent, the pickup drops off your board.
A workaround for this is to have your customer use UPS Internet Shipping to schedule a Smart Pickup each day they have a shipment.
From what I've been able to learn, the decision to not support triggering of a Smart Pickup was made by the business to prevent third-party software from triggering it. Such software, apparently, uses the same API that I use. I don't pretend to understand the reasoning behind this - perhaps it would expose some form of vulnerability to abuse.
As a Smart Pickup customer, I'm paying for the pickup whether I use it or not. So, at least for me, it boils down to communicating with the driver to come by, which is accomplished most easily by triggering the Smart Pickup.
With all that said, perhaps the API for triggering a Smart Pickup should be available for customers that have it enabled on their account.
Totally wrong on all accounts (pun intended).So what your saying is a customer who's p/up account is enabled as a smart p/up can be inconvenienced if they have a shipment within 59 minutes of their scheduled pick up time. Sometimes these new services that UPS offers are more of a benefit to UPS than the customers. I think that if you are still paying the same rates as a daily, and not for just the days we come by, the customer is being stolen from.
But it's so much fun.Totally wrong on all accounts (pun intended).
The customer can schedule an OCP easily from the same API if the cut-off time is passed ... using WorldShip or the Pickup API or ups.com.
Smart pickups are usually free or at least half the price of a normal Daily Pickup.
All this is on ups.com if you cared to investigate.
You should at least have some facts straight before telling a customer wrong information.
It always better to say nothing than make stuff up.
Okay... I'm not a UPS employee. I'm a customer, one that's putting forth the effort to integrate shipping into my internal workflow applications. I'm using the Shipping API and the Pickup API.
With all that said, perhaps the API for triggering a Smart Pickup should be available for customers that have it enabled on their account.
P*I sent you a Conversation message ... please provide the info requested and I will forward your request to someone that can help facilitate and make a decision.
So what your saying is a customer who's p/up account is enabled as a smart p/up can be inconvenienced if they have a shipment within 59 minutes of their scheduled pick up time.
You are confused as to your terminology.
<snip>
It sounds as though you would be better served to switch your account to the Smart Pickup.
The developer must know certain keys that are not published to the public in order to initiate a Smart Pickup transaction. The Pickup API is used for Smart Pickups.
UPS made that decision based on the complexity of the Smart Pickup on UPS operational systems and driver communications. UPS saw it more of a Enterprise level tool for a large customer with many locations.
<snip>
Talk to your Sales Rep and see if he/she can get you the instructions on how to implement Smart Pickup using the Pickup API. It is a lot of work and coordination on the customer side as well as UPS.
I have converted 4 of my daily pickups to Smart Pickups. Each of them were occasional shippers and appreciate the savings.
The Walmart Vision Center was changed to a Smart Pickup and they still can't grasp the concept. They get mad at me when they don't process anything, which means I don't stop, yet have prepaids going out. They have called in concerns saying that I missed their pickup.