# Infor Nexus Network TMS with QAD Precision parcel for Infor ERPs

> Source: https://netray.co/stack/infor-nexus-network-tms-parcel-infor-m3
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

Infor Nexus Network TMS is a global transportation management product on the Infor Nexus network, and Infor added multi-carrier parcel execution to it through QAD Precision. It is used alongside Infor ERPs such as M3. The public announcement describes the capability, not the ERP-level integration, so treat M3 specifics as a project to confirm.

## Erp

Infor M3 (with Infor Nexus)

## Erp Key

infor-m3

## On Prem

true

## Product

Infor Nexus Network TMS with QAD Precision parcel

## Vendor

Infor / QAD Precision

## Category

Freight TMS

## Integration

**Method:** Multi-carrier parcel execution embedded in Infor Nexus

**Detail:** Parcel rating, labels and carrier execution are part of the Nexus TMS through QAD Precision rather than a separate add-on. Infor's announcement does not document the ERP connection, so confirm how shipments and orders flow from your ERP with Infor.

**Method:** Order and shipment exchange with the ERP

**Detail:** In general a TMS needs delivery or shipment data from the ERP and returns carrier, cost and tracking. For M3 this commonly means ION-based or API-based exchange, but this is a general pattern, not a documented M3 specification.

## Data Flows

**From:** Infor ERP (for example M3)

**To:** Infor Nexus TMS

**Data:** Shipment or delivery requests

**Trigger:** Delivery released

**From:** Infor Nexus TMS

**To:** Carrier

**Data:** Rate, booking and parcel label request

**Trigger:** Carrier selected

**From:** Infor Nexus TMS

**To:** Infor ERP

**Data:** Carrier, tracking and freight cost

**Trigger:** Shipment executed

**From:** Carrier

**To:** Infor Nexus TMS

**Data:** Tracking events

**Trigger:** Carrier status update

## Setup

### Define freight scope

**Detail:** Identify whether you need parcel, truckload, ocean or air, as the TMS is wider than parcel shipping.

### Confirm ERP integration route

**Detail:** Ask Infor how your ERP connects to Nexus TMS and who delivers it.

### Prepare ERP shipping data

**Detail:** Ensure addresses, weights, dimensions and incoterms are accurate in the ERP.

### Load carriers and contracts

**Detail:** Configure carrier accounts, rate agreements and service levels.

### Define routing rules

**Detail:** Set rules for mode and carrier selection by lane, weight and service.

### Pilot with one lane or site

**Detail:** Compare freight cost and tracking against current practice before wider rollout.

## Pitfalls

- Buying a global TMS when parcel shipping software would meet the need.
- Item master data with no weight or dimensions, causing poor rating.
- Carrier contracts not loaded correctly, so quoted rates differ from invoices.
- Tracking events not linked back to ERP orders for customer service.
- Assuming ERP integration is included without a written scope.
- Cloud network dependency not reviewed against site data policies.

## Ai Layer

### Freight cost analysis

**Description:** A private assistant reading TMS shipments and ERP orders can explain where freight cost rose, by lane and carrier, read-only.

### Late shipment triage

**Description:** Combine tracking events with ERP promised dates to list orders likely to miss, with a draft customer message for approval.

### Master data gap detection

**Description:** List items and addresses likely to cause rating failures before they ship.

### Plain-language shipment questions

**Description:** Let customer service ask where an order is and get one answer from both systems.

## Alternatives

- Multi-carrier parcel software such as ProcessWeaver if your need is parcel labels and manifests.
- ERP-native shipping features with carrier integrations for simple distribution.
- A TMS from another vendor if you do not use the Infor Nexus network.

## Faq

### Is Nexus TMS the same as a parcel tool?

**Answer:** No. Infor Nexus Network TMS is a broader transportation management product on the Nexus network. Parcel execution through QAD Precision was added to it, so it covers parcel inside a wider freight scope.

### Does it work with M3?

**Answer:** Infor positions it for use with its ERPs, but the announcement does not describe the M3 connection. Ask Infor for the integration design and responsibilities for your M3 version before planning.

### Can I use it with on-premises M3?

**Answer:** Nexus is a cloud network, so on-premises M3 would exchange shipment data with it across your boundary. Check the network path and data handling with your security team.

### What does QAD Precision add?

**Answer:** Infor says it adds multi-carrier parcel execution to Nexus TMS, meaning rating, labels and carrier choice for parcels.

## Source

https://www.ajot.com/news/infor-announces-global-transportation-management-software-now-supports-parcel-shipping-with-qad-precision

## Search terms

infor nexus transportation management parcel, infor nexus tms m3, qad precision parcel infor, infor nexus network tms, m3 transportation management, infor parcel shipping tms

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
