Partnered carrier tells ORF2 that Amazon does not respond to appointment requests for LTL delivery
We shipped our FBA (LTL-3 pallets) shipment with partnered carrier Central Transport 2 weeks ago for delivery to ORF2. However, since there was no development regarding delivery in this process, we contacted the partnered carrier.
They told us that they created an appointment request and Amazon is still not responding. We have been waiting in this way for a long time.
We have opened a case to the seller support regarding this issue. However, contrary to the question we asked, we received irrelevant answers.
There can be no uncertainty in commercial affairs. This is the rule if you want to give your customers the best experience.
We know where to watch what. Of course, we will not ask for the appointment only for Central Transport, which is a partnered carrier. Non-partnered Carrier is more useful than such partner carrier, resolver. Is there any solution to this?
What kind of situation is this?
Partnered carrier tells ORF2 that Amazon does not respond to appointment requests for LTL delivery
We shipped our FBA (LTL-3 pallets) shipment with partnered carrier Central Transport 2 weeks ago for delivery to ORF2. However, since there was no development regarding delivery in this process, we contacted the partnered carrier.
They told us that they created an appointment request and Amazon is still not responding. We have been waiting in this way for a long time.
We have opened a case to the seller support regarding this issue. However, contrary to the question we asked, we received irrelevant answers.
There can be no uncertainty in commercial affairs. This is the rule if you want to give your customers the best experience.
We know where to watch what. Of course, we will not ask for the appointment only for Central Transport, which is a partnered carrier. Non-partnered Carrier is more useful than such partner carrier, resolver. Is there any solution to this?
What kind of situation is this?
7 replies
TaylorR_Amazon
Hi @Seller_WaZXtBdAaoHv3, we have been discussing this issue in another thread, but I will go ahead and move the conversation here! I'll be back when I have an update.
