Order intake

Order intake means pushing orders from your system into MendriX. Today this goes through the legacy SOAP Custom Link call StoreOrdersNormal — the same XML on both the manual and the n8n path.

Coming soon REST order creation

A native REST endpoint for creating orders is planned. When it ships it will appear in the REST API reference and this guide will gain a REST path. Until then, use the SOAP StoreOrdersNormal call below. Do not build against REST order-creation endpoints — they do not exist yet.

Endpoint

https://<your-client-name>.mendrix.cloud:5564/soap/ICustomLinkSoap

Operation: StoreOrdersNormal. The WSDL is published at https://<your-client-name>.mendrix.cloud:5564/wsdl/ICustomLinkSoap. See the SOAP overview for connection and authentication details, and the full order-intake example for a complete request/response pair.

The order payload

Orders are described by the EoCustomLinkStoreOrdersNormal structure (defined in GdxEoStructures.xsd). A new order has OrderId/Id set to a negative value (negative = insert), a client reference, and one or more tasks (typically a pickup and a delivery):

<EoCustomLinkStoreOrdersNormal Type="TEoCustomLinkStoreOrdersNormal">
  <ApplyImportSettings>1</ApplyImportSettings>
  <Data Type="TEoOrderMxList">
    <_TEoListBase_Items>
      <EoOrderMx Type="TEoOrderMx">
        <!-- Negative Id requests a new order. ClientNumber is resolved to a
             ClientId automatically when ClientId is not supplied. -->
        <OrderId Type="TEoKeyIntInfraMx_NoData"><Id>-1</Id></OrderId>
        <ClientNumber>1001</ClientNumber>
        <Reference>PO-2026-00042</Reference>
        <Tasks Type="TEoTaskMxList">
          <_TEoListBase_Items>
            <!-- Pickup task -->
            <EoTaskMx Type="TEoTaskMx">
              <TaskId Type="TEoKeyIntInfraMx_NoData"><Id>-1</Id></TaskId>
              <Address Type="TEoAddress">
                <Name>Acme Warehouse</Name>
                <Street>Havenweg</Street>
                <Number>12</Number>
                <PostalCode>3011 XA</PostalCode>
                <Place>Rotterdam</Place>
                <CountryCode>NL</CountryCode>
              </Address>
              <ContactName>Jan de Vries</ContactName>
              <Requested Type="TEoDateTimeWindow">
                <DateTimeBegin>2026-07-22T08:00:00</DateTimeBegin>
                <DateTimeEnd>2026-07-22T12:00:00</DateTimeEnd>
              </Requested>
              <GoodDescription>2 pallets general cargo</GoodDescription>
              <GoodWeight>480</GoodWeight>
              <Instructions>Call on arrival</Instructions>
              <ReferenceYour>PICKUP-42</ReferenceYour>
            </EoTaskMx>
            <!-- Delivery task -->
            <EoTaskMx Type="TEoTaskMx">
              <TaskId Type="TEoKeyIntInfraMx_NoData"><Id>-2</Id></TaskId>
              <Address Type="TEoAddress">
                <Name>Beta Distribution</Name>
                <Street>Industrieweg</Street>
                <Number>88</Number>
                <PostalCode>5651 GH</PostalCode>
                <Place>Eindhoven</Place>
                <CountryCode>NL</CountryCode>
              </Address>
              <Requested Type="TEoDateTimeWindow">
                <DateTimeBegin>2026-07-22T14:00:00</DateTimeBegin>
                <DateTimeEnd>2026-07-22T17:00:00</DateTimeEnd>
              </Requested>
              <ReferenceYour>DELIVERY-42</ReferenceYour>
            </EoTaskMx>
          </_TEoListBase_Items>
        </Tasks>
      </EoOrderMx>
    </_TEoListBase_Items>
  </Data>
</EoCustomLinkStoreOrdersNormal>

Confirm the exact field set for your tenant

Which fields are required and how tasks are typed depends on your tenant’s import settings (ApplyImportSettings). The structure above is grounded in GdxEoStructures.xsd; validate your payload against that schema and confirm the mandatory fields with your MendriX contact before going live.

Submit the order

Manual (REST)

There is no REST endpoint for order creation yet (see the callout above). Submit via SOAP by POSTing the SOAP envelope that wraps the structure above to the Custom Link endpoint:

curl "https://<your-client-name>.mendrix.cloud:5564/soap/ICustomLinkSoap" \
  -X POST \
  -H "Content-Type: text/xml; charset=utf-8" \
  -H "SOAPAction: StoreOrdersNormal" \
  --data-binary @store-orders-normal.soap.xml

store-orders-normal.soap.xml is the SOAP envelope containing the payload; see the full example for the complete envelope and a sample response, and the SOAP overview for how the token is supplied.

n8n

The n8n path posts the same SOAP XML with an HTTP Request node:

1. Add a Manual Trigger (or a Webhook trigger to accept orders from your system).
2. Build the SOAP XML — a Set/Code node that fills the order fields into the envelope template.
3. Add an HTTP Request node:
   • Method: POST
   • URL: https://<your-client-name>.mendrix.cloud:5564/soap/ICustomLinkSoap
   • Headers: Content-Type: text/xml; charset=utf-8, SOAPAction: StoreOrdersNormal
   • Body Content Type: Raw/Text, body = the SOAP XML.
   • Authentication: attach the SOAP token as configured for your tenant (see SOAP overview).
4. Parse the XML response (an XML node) to read the created order id(s).

Importable workflow: order-intake.json.

After the order is created

• Track its progress via Order status & track-and-trace.
• Update non-intake fields later using the REST Order endpoints (PATCH) — see the reference.