Skip to content

Transfer Orders Realtime-enabled — SmartConnect can trigger on changesRealtime-enabled

GETPOSTPATCHDELETETable: Transfer Header

eOne/core/v1.0/transferOrders

Move stock between locations. POST a full transfer, header plus transferOrderLines, in one call.

Resolve the warehouses

Set the from/to locations by code, or by their eOne integration key with transferFromLocationIntegrationId / transferToLocationIntegrationId. The store's transfer Id round-trips on integrationId.

Release before shipping

Business Central will not post a shipment for a transfer order that is still Open, so a transfer created here has to be released before ship will do anything:

POST /transferOrders(<id>)/Microsoft.NAV.release

reopen is the counterpart, and puts a released transfer back to Open so it can be changed. Both are the standard Business Central release, so the same line checks run as in the client.

Ship then receive

Two bound actions, ship (post the outbound shipment) and receive (post the inbound receipt). For non-direct transfers, ship first, stock moves to the in-transit location, then receive:

POST /transferOrders(<id>)/Microsoft.NAV.ship
POST /transferOrders(<id>)/Microsoft.NAV.receive
The originating Id is mirrored onto both posted documents, so a shipment and its receipt both carry the store's transfer key.

One transfer per integrationId

Sending the same integrationId twice is rejected, naming the transfer that already holds it. The check also looks at posted transfer shipments and receipts, so a retry after a transfer has already shipped is refused too.

This matters more here than on the sales and purchase endpoints. A duplicated transfer has no customer facing document and no numbering collision to trip over, so without the check a retried POST would create a second transfer, and shipping both would move the quantity out of the source location twice and receive stock into the destination that never existed.

A blank integrationId is always allowed through, and an administrator can turn the check off with Reject Duplicate Documents on the eOne Integration Setup page.

Dimensions

shortcutDimension1Code and shortcutDimension2Code are writable, and are what Transfer Header carries - there is no 3 to 8 on a transfer. Set them and the resulting item ledger entries carry them; leave them and Business Central defaults from the locations as before.