Shipping errors only occur for Self Service Portals with Shipping Agreements enabled, or when running a Shipping Action.
The shipment error message will be displayed as an internal note, and will look similar to this:
The information we specifically look at here, is the suggested solution: "Check destination, weight and dimensions.".
Since weight and dimensions are prefilled to standard values in our shipping integrations, the issue will in 95% of all cases be with the destination.
The issue for this case is, most frequently, that the Shipping Identifier, in this case 701, is pointing towards a shipping agreement in fx: Webshipper, that doesn't allow shipping from the customers address, to your return address.
Tip: The shipping identifier is found in the first line of the error message, and displayed directly after: "Unable to book shipment with shipping identifier: XXX"
The issue can also be your return address
The issue can in some cases be caused by a wrong return address on your end. This guide describes how to find end edit your return address.
See more details on the shipping agreement causing errors
You can see your shipping agreements by going to the Company View, and selection "Shipping Agreements" in the left-hand menu.
In the column "Shipping Identifier", find the shipping agreement corresponding to the shipping identifier that caused the error, as here:
Find the shipping deal in Webshipper, Homerunner or Cargoflux
To amend this issue, you need to find the shipping agreement, in your shipping integration provider, and identify, wether it can handle shipments from your customers address to your return address:
Contact us for assistance with other shipping integration providers.
Resolve the issue
If you find that the shipping agreement is not available for your customers country, you should either disable the shipping agreement for their country, or create a new shipping agreement.
Other errors that contain /data/relationship/carrier and error code 422
Generally error that contain /data/relationship/carrier are due to errors between Webshipper and the carrier.
Example of such an error:
This error can exist for two reasons
Claimlane is sending the incorrect data
The carrier setup in Webshipper is incorrect.
To debug this error, first go to agreement on Webshipper and test if you can manually create a label with the specified input data, most importantly use the same from and to address as you used in Claimlane.
If you cannot manually create a label the error is due to the Carrier's setup in Webshipper. You will need to contact Webshipper and/or your carrier. There are generally two reasons:
The carrier does not support the requested freight
The carrier is set up incorrectly in Webshipper
If you can manually create the label, please reach out to Claimlane and they can help you debug the issue.
The following is an example of an error that is due to the Webshipper