Entity

Freight Shipment Record

The tracking record for each inbound or outbound freight movement — containing carrier, origin, destination, mode (truck, rail, ocean, air), weight, cost, pickup/delivery dates, real-time tracking events, and exception flags for delays or damages.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI cannot optimize transportation routes, predict freight costs, or provide end-to-end visibility without structured shipment data; without it, 'where is my shipment and when will it arrive' requires calling the carrier or checking their portal manually.

Supply Chain & Procurement Capacity Profile

Typical CMC levels for supply chain & procurement in Manufacturing organizations.

Formality
L2
Capture
L2
Structure
L2
Accessibility
L2
Maintenance
L2
Integration
L2

CMC Dimension Scenarios

What each CMC level looks like specifically for Freight Shipment Record. Baseline level is highlighted.

L0

Freight shipments are arranged by phone or email with no tracking record. The logistics coordinator calls the carrier, gives them a pickup address and delivery window, and that's it. When someone asks 'where is that shipment of castings from Supplier X?' the answer is 'let me call the carrier and find out.' Freight costs are discovered when the invoice arrives.

AI cannot provide any shipment visibility, cost analysis, or delivery prediction because no shipment records exist in any system.

Create a shipment log — even a shared spreadsheet tracking carrier, origin, destination, pickup date, expected delivery, and cost for every freight movement.

L1

Shipments are logged in a spreadsheet or email folder. The logistics coordinator enters carrier name, PO number, and expected arrival date — but the format varies depending on who's on shift. Some entries have tracking numbers, others don't. Finding out 'what did we ship last month via LTL?' means scrolling through rows and hoping the mode column was filled in.

AI could scan the spreadsheet for basic volume counts, but inconsistent fields and missing tracking numbers make reliable cost analysis or delivery performance trending impossible.

Standardize the shipment record — same fields (carrier, mode, weight, cost, tracking number, pickup/delivery dates) for every movement, enforced by a template or form.

L2Current Baseline

A standard shipment record template is used consistently. Every freight movement gets logged with carrier, mode, origin, destination, weight, cost, and dates in a shared system or structured spreadsheet. The logistics team can pull a report showing all ocean shipments in Q3. But tracking events (picked up, in transit, delivered, exception) aren't captured — just the plan and the final outcome.

AI can generate freight spend reports by mode, lane, and carrier, and flag cost outliers. Cannot predict delivery delays or provide real-time visibility because in-transit tracking events aren't recorded.

Implement a TMS or freight management system that captures real-time tracking events (pickup, in-transit milestones, delivery confirmation, exceptions) linked to each shipment record.

L3

Shipment records live in a TMS with enforced fields and tracking event capture. Every movement has carrier, mode, weight, cost, and a timeline of events: booked, picked up, in transit, delivered, or exception. The supply chain manager can query 'show me all late deliveries from Carrier Y on the Chicago-to-Detroit lane this quarter' and get an accurate answer within minutes.

AI can perform carrier performance scorecarding, lane optimization analysis, and delivery ETA prediction based on historical patterns. Cannot yet intervene in real-time because tracking updates arrive in batches, not live.

Integrate real-time carrier tracking APIs so shipment status updates flow into the TMS as events happen — not when someone checks a carrier portal or receives an EDI update hours later.

L4

Shipment records are schema-driven with formal entity relationships — each shipment links to the purchase order, supplier, carrier contract, warehouse dock assignment, and production schedule it serves. The data model is API-queryable. An AI agent can ask 'what shipments are currently in transit for Production Order 4821, and what's the ETA impact on the production schedule?' and get a structured, cross-referenced answer.

AI can perform end-to-end logistics optimization — rerouting shipments based on production schedule changes, automatically rebooking carriers when delays exceed thresholds, and calculating total landed cost including freight, duties, and warehousing.

Implement real-time event streaming — shipment status changes publish as events the moment they occur, enabling instant downstream reactions.

L5

Shipment records are living streams of real-time events. GPS, IoT sensors, carrier APIs, and port systems continuously feed position, temperature, shock, and customs clearance data into a unified shipment model. The record isn't a document someone created — it's an automatically maintained digital thread of every event from booking through final delivery confirmation.

Fully autonomous freight management. AI monitors every shipment in real-time, predicts disruptions before they happen, reroutes proactively, and optimizes the entire transportation network continuously.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on Freight Shipment Record

Other Objects in Supply Chain & Procurement

Related business objects in the same function area.

Purchase Order

Entity

The transactional record authorizing procurement of materials or services from a supplier — containing line items, quantities, agreed prices, delivery dates, terms, approval status, and receipt/invoice matching state tracked from requisition through payment.

Supplier Master Record

Entity

The comprehensive profile for each supplier in the procurement network — containing company identity, financial health indicators, geographic locations, capabilities, certifications, performance history, risk scores, and relationship status (prospect, qualified, preferred, suspended).

Item Inventory Position

Entity

The real-time and projected stock status for each SKU across all storage locations — including on-hand quantity, allocated quantity, in-transit quantity, on-order quantity, safety stock level, and days-of-supply calculation by warehouse, zone, or bin.

Supplier Contract

Entity

The formal agreement governing the commercial relationship with a supplier — containing pricing schedules, volume commitments, rebate tiers, service level agreements, penalty clauses, renewal dates, and amendment history maintained by procurement and legal.

Warehouse Layout and Slot Assignment

Entity

The physical and logical configuration of warehouse storage — defining zones, aisles, racks, bins, slot dimensions, weight capacities, temperature requirements, and the assignment rules that map SKUs to specific storage locations based on velocity, pick frequency, and product characteristics.

Spend Category Taxonomy

Entity

The hierarchical classification scheme that categorizes all procurement spend into standardized groups — from top-level categories (direct materials, indirect, services, MRO) through subcategories to commodity codes, enabling spend aggregation, benchmarking, and strategic sourcing analysis.

Sourcing Award Decision

Decision

The recurring judgment point where procurement selects which supplier(s) receive business for a category or commodity — evaluating bids against weighted criteria (price, quality, lead time, risk, sustainability), applying split-award rules, and documenting the rationale for audit and supplier debriefs.

Replenishment Trigger Decision

Decision

The recurring judgment point where planners decide when and how much to reorder — evaluating current inventory position against demand forecasts, lead times, supplier capacity, and cost trade-offs to determine order timing, quantity, and source for each SKU or material group.

Supplier Qualification Rule

Rule

The codified criteria that determine whether a supplier is approved, conditionally approved, or disqualified for specific commodities — including financial stability thresholds, certification requirements, audit score minimums, capacity verification standards, and the escalation path for exceptions.

Inventory Reorder Policy

Rule

The formal parameters governing automated replenishment for each SKU or material class — including reorder point formulas, safety stock calculations, economic order quantities, min/max boundaries, lead time assumptions, and service level targets that planners set and periodically review.

Procure-to-Pay Process

Process

The end-to-end procurement workflow from requisition creation through purchase order issuance, goods receipt, invoice matching, and payment execution — defining approval hierarchies, matching tolerances, exception handling steps, and the handoff points between procurement, receiving, accounts payable, and treasury.

Supplier-Part Qualification

Relationship

The formally managed link between a specific supplier and the specific parts or materials they are qualified to provide — including qualification status, test results, approved manufacturing sites, capacity allocations, and the conditions under which the qualification is valid or expires.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.