For those sellers who wish their workflow to move to 'Printed' after label printing (refer to How do I Print and Manifest separately?), this method allows you to flag an array of 'Printed' consignments as 'Ready to Manifest'. This allows the manifesting processes (e.g. createManifest and createManifestForFutureDespatch) to pick them up.


It is assumed that you have worked through Creating your first Request to a Service and are familiar with the Properties needed to Call or Create a Consignment.

How to submit a request

Proceed as follows:

  1. If you have not already done so, open a new project using the WSDL ConsignmentService.xml.

  2. Create a new request under markConsignmentsAsReadyToManifest,

  3. Enter the authorisation for the request.

  4. Specify the code(s) of the existing consignment(s).

  5. Click Arrow.png to submit the request.

Example Request

<soapenv:Envelope xmlns:xsi="" xmlns:xsd="" xmlns:soapenv="" xmlns:ser="urn:DeliveryManager/services">
      <ser:markConsignmentsAsReadyToManifest soapenv:encodingStyle="">
          <consignmentCodes xmlns:soapenc="" xsi:type="ser:ArrayOf_soapenc_string" soapenc:arrayType="soapenc:string[]">

If the input is valid, then the consignment statuses are updated, and true is returned, as in the example below.


The maximum number of consignments that can be submitted in a single API request is 999.

Example Response

<soapenv:Envelope xmlns:soapenv="" xmlns:xsd="" xmlns:xsi="">
      <ns1:markConsignmentsAsReadyToManifestResponse soapenv:encodingStyle="" xmlns:ns1="urn:DeliveryManager/services">
         <markConsignmentsAsReadyToManifestReturn xsi:type="xsd:boolean">true</markConsignmentsAsReadyToManifestReturn>