Sending Dispatch Instructions

This is the right section for you if you are acting as a supplier and looking to send dispatch instructions to your fulfillment provider.

Throughout this guide you will learn how to send new dispatch instructions to the Procuros API.

PHP examples are included but you will likely also want to look at the relevant API calls in the API reference.

Table of Contents


These are usually the steps taken when sending a dispatch instruction to Procuros:

  1. Check, if this document should be sent via Procuros (see: Enabled Trade Partners)
  2. Verify this document has not already been sent (see: Tracking Document Status)
  3. Build the transaction payload to be sent via Procuros
  4. Send the transaction payload via the Procuros API


You will need an API token to authenticate.
We use a bearer token which has to be included in each request you send to the API.

Please read the Authentication section of our API reference for a detailed description.

Error Handling

The API will return a 2xx status code for successful requests. Anything else indicates an error.

Please read the Errors section of our API reference for a detailed description plus examples of how to handle them.

Send Dispatch Instructions

The API call Send transaction is used to create transactions, including dispatch instructions.

The following fields are required:

  • type (Transaction type. In this case DISPATCH_INSTRUCTION)
  • content (The details of the dispatch instruction.)

Inside the content you will need to build all dispatch instruction items. All details can be found in the DISPATCH_INSTRUCTION schema as described in the API reference.

An example request would look like:

// install dependency
// $ composer require guzzlehttp/guzzle


$client = new \GuzzleHttp\Client();

$transaction = [
    "content" => [
        "header" => [
            "orderIdentifier" => "valid-order-id",
            "orderDate" => "2023-06-01",
            "shipmentIdentifier" => "valid-dispatch-instruction-shipment-id-1",
            "noticeDate" => "2023-06-01",
            "requestedDeliveryDate" => "2023-06-05",
            "customer" => [
                "addressId" => "valid-dispatch-instruction-customer-1",
                "identifiers" => [
                        "identifier" => "3220010000001",
                        "domain" => "GS1",
            "supplier" => [
                "addressId" => "valid-dispatch-instruction-supplier-1",
                "identifiers" => [
                        "identifier" => "3220010000002",
                        "domain" => "GS1",
            "shipFrom" => [
                "addressId" => "valid-dispatch-instruction-shipFrom-1",
                "identifiers" => [
                        "identifier" => "3220010000003",
                        "domain" => "GS1",
        "items" => [
                "orderLineNumber" => 1,
                "shippingNoticeLineNumber" => 1,
                "shippedQuantity" => 1,
                "orderedQuantity" => 1,
                "openQuantityAction" => "DISCARDED",
                "unitOfMeasure" => "EA",
                "identifiers" => [
                        "identifier" => "valid-dispatch-instruction-identifier-1",
                        "domain" => "GS1",

$response = $client->request('POST', '', [
  'headers' => [
    'Accept' => 'application/json',
    'Authorization' => 'Bearer <your-api-token>',
  'json' => $transaction,

Mark Document Status

Finally, as per the instructions mentioned under Tracking Document Status you must now track the status of the document locally, based on the returned HTTP response.

The document should be marked with either status TRANSMITTED or NO_ACTION. If there is an error with the document and it is not accepted, do not mark it with a status so it may be retried. For more information on retrying failed documents, please see: Retrying Documents.

For example:

$statusCode = $response->getStatusCode();

if ($statusCode == 201) {
} else if ($statusCode == 202) {
} else {
  // No need to do anything if it's not accepted, in an error case the document should be retried.