The following are the possible error codes that can be generated using the Shipping SOAP API:
Table 25. Shipping API Error Codes
Error Category |
Specific Error Code |
Description |
Action |
---|---|---|---|
|
N/A |
These are internal, critical errors that prevent Delivery Manager as a whole from working properly. |
Metapack handles these automatically. |
|
These are usually generated in response to user input, but also cover things such as invalid arguments to URLs and security violations. |
Check the input parameters. |
|
|
An invalid character has been entered, e.g. entering a "£" into a UK postcode. |
||
|
The postcode provided is not in the appropriate format. The UK postcode structure is a little complicated, but it is specific (BS7666) |
||
|
The URL provided is not formatted correctly. |
||
|
You are trying to view something that has already been deleted. This can also occur when you attempt to look for a record that never existed. |
||
|
You do not have the required access rights for the action that you are trying perform. |
||
|
You have supplied an invalid URL. |
||
|
Delivery Manager does not support the address type specified (it only supports either “business” or “residential”). |
||
|
The country code specified is not defined in accordance with ISO-3166 (Alpha-2, Alpha-3 and Numeric). |
||
|
The page for which you are looking cannot be found – check the URL. |
||
|
The XML file specified is not in a valid format. |
||
|
The task that you are trying to view has been terminated. |
||
|
There was a problem in creating the manifest. |
||
|
The consignment is already on a manifest. |
||
|
A delivery option condition has been applied to something that does not support it. |
||
|
The specified delivery condition is not valid. |
||
|
The file you are attempting to import is not valid. |
||
|
The UPI (Unique Parcel Number) cannot be found as it appears to be invalid. |
||
|
There are no more unique numbers available for your account with the carrier. Contact the carrier to obtain a new set so that the new number range can be added. |
||
|
The service attribute specified is not known to Delivery Manager. |
||
|
The service specified is not known to Delivery Manager. |
||
|
The attribute type is not known to Delivery Manager. |
||
|
The consignment status is not known to Delivery Manager. |
||
|
The delivery condition specified is not known to Delivery Manager. |
||
|
The depot specified cannot be found. |
||
|
The manifest status is not known to Delivery Manager. |
||
|
The barcode format is not supported by PDF. |
||
|
The company name of the retailer/shipper must be supplied. |
||
|
The first name of the recipient must be supplied. |
||
|
The surname of the recipient must be supplied. |
||
|
The email address of the recipient must be supplied. Many carriers require this. |
||
|
The shipper/retailer already exists in Delivery Manager. |
||
|
The transaction type specified is not supported. It should be either “delivery” or “pick-up”. |
||
|
The consignment status is not valid. |
||
|
The operation that you are trying to perform can only be carried out on consignments that have already been allocated to a carrier. |
||
|
The carrier requires an account code to be assigned to each warehouse. |
||
|
The manifest cannot be sent as it is not valid. |
||
|
The name of the recipient must be supplied. |
||
|
The address is not valid. The first two lines, the postcode/zip, and the country code, are required. |
||
|
The consignment weight must be a positive number. |
||
|
The number of parcels must be a positive integer. |
||
|
The order number/reference code must be supplied. |
||
|
Delivery Manager can only return between 1 and 50 dates (inclusive). |
||
|
The warehouse code for the consignment has has not been provided. |
||
|
The main parameter is missing from the SOAP call, making it appear 'null'. |
||
|
You must provide the carrier service code. |
||
|
You must provide the consignment code (starting with "DMC…"). |
||
|
The consignment is already allocated to a carrier. |
||
|
The carrier service specified cannot be used for this consignment. |
||
|
Labels cannot be printed for the consignment at its current status. |
||
|
The parcel does not exist. |
||
|
You can only reprint labels that have previously been printed. |
||
|
The parcel code must be supplied. |
||
|
You cannot make changes to a consignment at this status (e.g. it might have been manifested, in which case no modifications can be made). |
||
|
At least one of the parameters provided in your setup is invalid. |
||
|
The POD (Proof of Delivery) type specified is unknown. |
||
|
Delivery Manager is unable to process the type of file provided. |
||
|
Unrecognised data type. |
||
|
Delivery Manager is unable to determine the best carrier for this consignment. |
||
|
Delivery Manager is unable to determine the best delivery option to be allocated to this consignment. |
||
|
The carrier’s depot has been deleted. |
||
|
The sender's name is missing. |
||
|
An attempt has been made to print a label for a parcel while it was not at a valid status. |
||
|
The status of the message cannot be determined. |
||
|
There was no carrier suitable for the consignment (i.e. no delivery options were available). |
||
|
The insurance code provided is unknown to Delivery Manager. |
||
|
An invalid value has been provided for a scheduled task. |
||
|
Although the best carrier service can be identified, it cannot be used as the costing configuration is incomplete. |
||
|
The value passed for one of the parameters is too long. |
||
|
The order already exists. |
||
|
Delivery Manager was unable to determine any delivery dates for the consignment. |
||
|
Your costing mechanism includes an unknown cost type. |
||
|
Parcels are missing from the request. |
||
|
The delivery duty type is unknown. |
||
|
The invoice type is unknown. |
||
|
The booking code is not valid, possibly because of the formatting. |
||
|
You can only validate an allocation before the labels have been printed. |
||
|
The notification type for the sender is not valid. |
||
|
The notification type for the recipient is not valid. |
||
|
The carrier code provided is not known in Delivery Manager. |
||
|
The number range cannot be found and so allocation is not possible. |
||
|
Some information provided about the product is invalid. The actual detail is provided in the error message itself. |
||
|
Delivery Manager does not support the message type specified (it only supports either “Email” or “SMS”). |
||
|
Delivery Manager does not support the type of email attachment provided. |
||
|
Internal error that cannot resolve. |
||
|
|||
|
The recipient's contact phone number is invalid. |
||
|
The input data is has failed validation. The accompanying message will identify which part of the data failed validation. For example, either a zero or negative consignment value or weight is not valid. |
||
|
The chart type specified is not recognised. |
||
|
Delivery Manager does not support the shipment type you’ve specified (it only supports “samples”, “gifts”, “possessions” or “merchandise”). |
||
|
Delivery Manager does not support the terms of trade you’ve specified. For the terms supported, refer to |
||
|
Delivery Manager cannot perform the operation as the carrier does not support it. For example, certain carriers allow you to change the number of parcels in a consignment after it has been allocated or printed, while other carriers do not. |
||
|
An expression has a compilation error. More detail is shown in the error message itself. |
||
|
An error occurred while the expression was being evaluated. More detail will be shown in the error message itself. |
||
|
The file provided is not in the correct format. This could be due to version incompatibility. |
||
|
An unknown record type was specified. |
||
|
An invalid date format was used when importing consignments. |
||
|
Internal error that cannot resolve. |
||
|
|||
|
An invalid value was used in a consignment. |
||
|
An invalid parameter was used. |
||
|
An invalid SOAP parameter was used. |
||
|
An invalid search parameter was used. |
||
|
An unrecognised notification type was provided. |
||
|
An invalid parameter was used when trying to update a consignment. |
||
|
The consignment has already been shipped and so the operation cannot be performed. |
||
|
Delivery Manager was expecting a warehouse code, but none was provided (or else its value was 'null'). |
||
|
The retailer/shipper property for maximum days allowed to void a consignment has been exceeded. |
||
|
An invalid property was provided for a consignment. |
||
|
An invalid country code was provided. |
||
|
The system limit for parcels allowed in a consignment has been exceeded. |
||
|
A parcel cannot have a negative value. |
||
|
A parcel cannot have a negative depth. |
||
|
A parcel cannot have a negative height. |
||
|
A parcel cannot have a negative width. |
||
|
An invalid insurance amount has been provided. |
||
|
The user has cancelled the job. |
||
|
Internal error that Metapack cannot resolve. |
||
|
|||
|
|||
|
Delivery Manager does not support the report field. |
||
|
Internal error that Metapack cannot resolve. |
||
|
|||
|
Delivery Manager does not support the document type. |
||
|
The currency used in the consignment is not supported by the retailer/shipper. |
||
|
Delivery Manager does not support the DPI specified for the ZPL label. |
||
|
Internal error that Metapack cannot resolve. |
||
|
|||
|
|||
|
Delivery Manager does not support the language code provided. |
||
|
A carton ID is mandatory here. |
||
|
The manifest group code provided is invalid. |
||
|
One or more fields in the feed file provided are not valid. |
||
|
Internal error that Metapack cannot resolve. |
||
|
|||
|
Delivery Manager does not support the package type provided. |
||
|
The COD (Cash On Delivery) amount provided for the consignment is invalid. |
||
|
The COD (Cash On Delivery) amount provided for the parcel is invalid. |
||
|
Delivery Manager does not support the payment type provided. |
||
|
Delivery Manager does not support the label format provided. |
||
|
Incorrect HTTP method used, please use correct method. |
||
|
The address is not valid. The first two lines, the postcode/zip, and the country code, are required. |
||
|
The name of the recipient must be supplied. |
||
|
|
These tend to be temporary and sometimes resolve themselves. |
Either wait and try later, or else contact MetaPack Support if the error persists. |
|
The browser closed the connection before the process could be completed. |
||
|
The database is too busy to handle any more requests at the moment. |
||
|
The email could not be sent. |
||
|
The FTP process failed. |
||
|
The file could not be uploaded. |
||
|
The file could not be found. |
||
|
Unable to create the temporary folder. |
||
|
Failed to save the file. |
||
|
Failed to copy the file. |
||
|
Failed to write the XML file. |
||
|
Failed to notify anyone of the problem. |
||
|
Failed to process status files from the carrier. |
||
|
Failed to create the label. |
||
|
The delivery options could not be determined as the remote options provider (usually the carrier) could not be contacted. |
||
|
The delivery options could not be determined as a problem occurred at the carrier’s end. |
||
|
A problem occurred at the carrier end while trying to cancel the consignment. |
||
|
A problem occurred at the carrier end while trying to allocate the consignment. |
||
|
Internal error that Metapack needs to resolve. |
||
|
An error occurred while communicating via |
||
|
An error occurred while communicating via SOAP. |
||
|
Internal error that Metapack needs to resolve. |
||
|
An error occurred while communicating via the |
||
|
An error occurred in the communications to/from a socket. |
||
|
N/A |
These occur when there is an issue with the database. |
There is nothing you can do here besides report the error to MetaPack. |