Operational data

The remaining Custom Link commands, one subsection each. See the Command reference for the full table linking back here.

Hours (worked-hours shifts)

Retrieve

RequestHours retrieves worked-hours shifts by filter, including their nested activity paths.

Store

StoreHours creates or updates shifts, including nested activity paths:

<?xml version="1.0" encoding="windows-1252"?>
<EoCustomLinkStoreHours Type="TEoCustomLinkStoreHours">
  <Data Type="TEoHoursShiftList">
    <_TEoListBase_Items>
      <EoHoursShift Type="TEoHoursShift">
        <Id>-1</Id>
        <TimeWindow Type="TEoDateTimeWindow">
          <DateTimeBegin>2026-07-22T08:00:00</DateTimeBegin>
          <DateTimeEnd>2026-07-22T17:00:00</DateTimeEnd>
        </TimeWindow>
        <OperatorId>104</OperatorId>
      </EoHoursShift>
    </_TEoListBase_Items>
  </Data>
</EoCustomLinkStoreHours>

Invoices (read-only)

RequestInvoices retrieves invoices by filter, optionally nested.

No store command exists

There is no StoreInvoices command — invoices are read-only through Custom Link. Invoice creation and payment happen in MendriX itself or via the REST API’s invoice endpoints.

Capacity buckets (free-tier availability)

RequestCapacityBuckets retrieves live capacity-bucket availability for a client/product/period combination — useful for real-time order feasibility checks. Unlike most Custom Link commands, this is a free-tier operation that requires no Custom Link registration; any authenticated caller can use it.

Packaging transactions

Retrieve

RequestPackagingTransactions retrieves pallet/container transfer records for given order Ids.

Store

StorePackageTransactions registers a transfer against a task or good. PackingId is required on every transaction, plus at least one of TaskId/GoodId — the packing, and the task or good, must all resolve to existing records or the item is rejected:

<?xml version="1.0" encoding="windows-1252"?>
<EoCustomLinkStorePackageTransactions Type="TEoCustomLinkStorePackageTransactions">
  <Data Type="TEoCustomLinkPackageTransactionList">
    <_TEoListBase_Items>
      <EoCustomLinkPackageTransaction Type="TEoCustomLinkPackageTransaction">
        <GoodId>429</GoodId>
        <TransferIn>5</TransferIn>
        <TransferOut>3</TransferOut>
        <PackingId>6</PackingId>
      </EoCustomLinkPackageTransaction>
    </_TEoListBase_Items>
  </Data>
</EoCustomLinkStorePackageTransactions>

Measurements (sensor data)

StoreMeasurements stores sensor readings (e.g. temperature) tied to a vehicle via MaterialId/SensorCode. Requires the Conditioned Transport module. If no sensor is configured for the vehicle, that measurement is silently dropped (srError in the response, not a hard failure of the whole call). This per-item leniency only applies once your tenant has the Conditioned Transport (GV) module license — without it, the entire call fails as a single srError, not per-item:

<?xml version="1.0" encoding="windows-1252"?>
<EoCustomLinkStoreMeasurements Type="TEoCustomLinkStoreMeasurements">
  <Data Type="TEoCustomLinkMeasurementList">
    <_TEoListBase_Items>
      <EoCustomLinkMeasurement Type="TEoCustomLinkMeasurement">
        <SensorCode>2</SensorCode>
        <MaterialId>1</MaterialId>
        <MeasurementTypeId>0</MeasurementTypeId>
        <Measurement>7.92</Measurement>
        <Moment>2026-07-22T10:30:00</Moment>
      </EoCustomLinkMeasurement>
    </_TEoListBase_Items>
  </Data>
</EoCustomLinkStoreMeasurements>

Memos

StoreMemos attaches a note to an order or other entity via MasterId:

<?xml version="1.0" encoding="windows-1252"?>
<EoCustomLinkStoreMemos Type="TEoCustomLinkStoreMemos">
  <Data Type="TEoMemoList">
    <_TEoListBase_Items>
      <EoMemo Type="TEoMemo">
        <MasterId>346</MasterId>
        <MemoType>mtManual</MemoType>
        <Moment>2026-07-22T09:07:45</Moment>
        <Subject>New Custom Link order</Subject>
        <Text>A new order was entered via Custom Link</Text>
        <Visible>True</Visible>
      </EoMemo>
    </_TEoListBase_Items>
  </Data>
</EoCustomLinkStoreMemos>

Questionnaires

Questionnaire answer retrieval (both the preferred structured command and the legacy XML blob) now has its own page: Questionnaires.

Keep-alive and server time

RequestKeepAlive keeps a raw-socket connection open past its 5-minute idle timeout — largely irrelevant over SOAP, where there is no persistent connection to keep alive. RequestDateTime is the simplest possible Custom Link call (see the server time example) and is excluded from MendriX’s internal usage tracking, making it a safe connectivity check.

Distance and time calculation

NavigationDistanceAndTimeRequest computes route distance/duration for a list of 2-50 postal-code/country pairs. Netherlands only, and requires the Postcodes Plus NL license.

Unique-number (Id) management

• RequestGiveNextId claims the next Id for a named sequence (e.g. OrderId) — use this if your system needs to pre-allocate an Id before a store call.
• RequestProbeNextId is deprecated — do not use it in new integrations; it may be disabled for your tenant already.
• StoreIncreaseNextId bumps the OrderId sequence forward by 0-200 (values of 0 or 1 are accepted but have no effect) — currently the only Name value accepted. Per the implementation’s own comment, this is essentially a single-client special case, not a general-purpose feature — do not build new integrations around it without confirming with your MendriX contact that it applies to your tenant.

Related commands

• Command reference — the full table.
• Order intake, Order update, Clients, Employees — the higher-traffic entities these commands support.
• Questionnaires — driver/task questionnaire answer retrieval, now on its own page.