The recommended methods of generating returns labels are:
You need to use the Printing Properties within each call to generate the relevant documentation.
In each of the above calls, a
labels element is created at the end of the response containing a string from which the label can be generated.
In addition, if the return is from one trading bloc to another (including between Great Britain and Northern Ireland), then:
If the consignment is going via a postal carrier and is under 270
GBP, an encoded CN22 is automatically returned as part of the
labelselement. This will either be in the form of a second label or integrated with the delivery label. The
documentselement will then be empty.
If the consignment is going via a postal carrier and has a value of 270
GBPor more, an encoded CN23 is automatically returned in the
If the consignment is going via DHL, then a waybill is generated.
If the carrier integration supports paperless trade, the
documents element is empty.
You create a text file from the string in the
labels element, and, if one has been generated, the
documents element. You then load each text file into a Base64 decoder (e.g. https://www.base64decode.org/) to generate the labels/customs documents. Refer to the best practice example.
If you need to generate the documentation manually, proceed as follows:
Click Home and then select the Ready to Manifest status and the relevant returns carrier service, before clicking Search.
In the left hand column, tick the boxes against the consignments for which documentation is to be printed:
Click Print Selected Labels.
A Print dialog is displayed to allow you to select the required printer/output format.
Click Print to output the documentation, e.g.
You can now send the paperwork to the recipient so that they can attach it to the return ahead of the carrier collection.