What could possibly cause error in UPS response for 1 locale while it works fine for other locale?
답변 2개
#UPS토론 중인 항목 0개
- 최근 활동
- 생성 날짜
- 추천 항목
- 모든 질문
- 인정받은 답변이 있는 질문
- 미답변 질문
- 인정받은 답변이 없는 질문
I am trying to generate return label for France locale through UPS but reason codes: Produit défectueux ou endommagé, Produit différent de la photo, Produit endommagé durant da livraison
returns error code "120623" with description "Invalid merchandise description of package".
How can I resolve it?
답변 1개
Hi Dristi,
You would perhaps need to check this with UPS Support/UPS developer team which deals with their own APIs. You would need to share the request details so that they can see what's mapped in their system. If there's any document related to UPS APIs available with you, you can refer the same, and see if there's anything mentioned related to your error.
Hi, all!
Does anyone here have experience using UPS API with Salesforce?
While we don't use Salesforce to ship our product, we do store tracking information in our opportunities. I'm curious what options there are for automating alerts based on tracking events - for instance, notifying an account manager if there's a delay or updating a field when the shipment has been delivered. #UPS #API #Integration #Automation #
답변 1개
Hi Margaret,
We highly recommend to contact UPS for Salesforce to provide a complete guidance how to integrate UPS to Salesforce accordingly.
Rgards,
Hello guys, has anyone implemented CPQ in logistic service providers - such as FedEx, UPS etc? I have a couple of burning questions and any case study or a short call would help tremendously to validate some of our assumptions.
댓글 1개
What are your questions and assumptions? More context would be helpful. Many CPQ principles apply across industries.
Posting an update so others can learn. RE: EDI to API for Salesforce consumption.
A freight broker of ours uses a software called PCSSoft for freight orders and tracking, and we wanted to integrate with their system to consume real-time updates as we do with UPS. About a month ago I commenced a trial deployment to explore the costs of EDI data transmission (characters) and the accuracy of the data. It would be 1 document (214) with a limited set of statuses (1650/1651).
We contracted PCSSoft partner Kleinschmidt for the job, and I put my developer on the task of setting up a sandbox and the appropriate structure to receive and map the data out correctly.
As of this week, we've decided to defer the project for the following reasons:
- Massive costs. Remember, this was a trial/test run. Understanding EDI to assist our partner with the documentation consumed many hours, and we’re behind several weeks. For many EDI partners, API integration is new – specifically, pushing to Salesforce.
- Our freight broker is manually updating status in PCSSoft. It’s not automated where the trucks check-in automatically with scans or a geolocation service (think UPS). Considering the costs, if the data isn’t automated, it’s of limited value.
I expect to integrate at some point in the future, most likely using KS (they were courteous, seemingly competent) and I’ve also started the conversation with our freight broker to encourage them to up their game and move to a proper database with the appropriate technology to automate check-ins and status updates.
There's of course lots of information I've left out of the picture, if you've got questions, please feel free to ask.
We (Mark Andy) Pick/Pack and Ship about 200 orders per day, each one consisting of about 2 or 3 boxes. Most of these ship through UPS plus we ship about 25 skid orders per day via various LTL carriers. We are using ZenKraft Shipmate right now as the integrated tool to RS for the UPS. We have two shipping lines that do about half of the orders on each with one person manning each shipping station. We will be going live in about a month and I'm looking for ways to streamline the fulfillment process screens, so each shipping person can print out a shipper packing list and process the UPS shipment through ZenKraft as fast as possible with the least amount of steps. Has anyone modified the fulfillment screen process to make it easy for a shop floor shipping station? Has anyone integrated barcodes and scanners to move through the fulfillment process? Does anyone use any LTL 3rd party apps to integrate LTL PRO# shippers into RS?
댓글 2개
BTW -- we had to pay for a Rootstock RFQ to develop a 'Pack Only' API method so that we could programmatically update the quantity packed and thus create a shipper object.....this is supposedly going out in the Spring release.