972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Shipping and logistics

HANMOV Cargo/goods handling and movement

The UN/EDIFACT message used to order handling services and movements of goods at a warehouse, and to report them back.

Sent by
Owner of the goods or logistics service provider
Received by
Warehouse, distribution center or owner of the goods
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT HANMOV message?

HANMOV is the UN/EDIFACT cargo/goods handling and movement message. The directory gives it two functions: a message from a party to a warehouse or distribution center identifying the handling services, and where required the movement, of specified goods; and a message from a logistics service provider, such as a warehouse, reporting handling and movements carried out.

Handling services include relabeling, repacking, quality checks, kitting and moving goods between locations or stock statuses. Ordering and reporting them electronically keeps the owner's stock records aligned with the warehouse.

How the EDIFACT HANMOV message worksDiagram of the UN/EDIFACT HANMOV Cargo/goods handling and movement message. Owner of the goods or logistics service provider sends it to warehouse, distribution center or owner of the goods. It usually starts the exchange. It is usually followed by INVRPT. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 8 conditional segment groups are listed by their trigger segment.How the EDIFACT HANMOV message worksCargo/goods handling and movement: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeHANMOVSENDEROwner of the goods orlogistics serviceproviderRECEIVERWarehouse,distribution center orowner of the goodsCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINVRPTInventory report2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage HANMOVUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 8 conditional groups, starting with:TCCRFFNADTDTTODLINGIDEQDBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for HANMOV. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT HANMOV message worksDiagram of the UN/EDIFACT HANMOV Cargo/goods handling and movement message. Owner of the goods or logistics service provider sends it to warehouse, distribution center or owner of the goods. It usually starts the exchange. It is usually followed by INVRPT. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 8 conditional segment groups are listed by their trigger segment.How the EDIFACT HANMOVmessage worksCargo/goods handling and movement: whosends it, where it fits and what the directorymarks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeHANMOVSENDEROwner of thegoods orlogistics serviceproviderRECEIVERWarehouse,distributioncenter or ownerof the goodsCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINVRPTInventory report2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message HANMOV (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 8 conditional groups, starting with:TCCRFFNADTDTTODLINGIDEQDBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for HANMOV.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends HANMOV, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around HANMOV and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Ordering relabeling or repacking at a warehouse
  • Ordering stock moves between locations or statuses
  • Reporting handling performed by the warehouse

Where it fits in the message flow

This message HANMOV Cargo/goods handling and movement
Usually followed by INVRPT Inventory report

Structure

Mandatory segments in HANMOV (directory D.21A)

In UN/EDIFACT directory D.21A, the HANMOV message has 86 segment positions arranged in 23 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • UNT

Practical example

HANMOV in practice

A toy importer needs 2,000 units relabeled for a new market before they ship. It sends its logistics provider a HANMOV ordering the relabeling and the move of the units to a different stock status. The warehouse performs the work and returns a HANMOV reporting the quantities handled, which the importer uses to update its stock and check the service charges.

Implementation

Implementation considerations for HANMOV

  • Use service codes agreed with the warehouse.
  • Reconcile reported handling with orders and invoices.
  • Keep stock status changes in step with inventory reports.
  • Distinguish handling orders from despatch instructions.

How ECOM helps

Automate HANMOV with ECOM

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related shipping and logistics messages

All 7 shipping and logistics messages

Need help with HANMOV?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us