Skip to main content

Filter Export Containers by IPI Origin

A new Has IPI Origin filter is now available in Explore, letting you isolate Export containers that move by rail before reaching the port of loading (an inland, or "IPI," origin).

What Is IPI?

IPI stands for Interior Point Intermodal. It describes cargo that travels part of its journey by rail to or from an inland point, instead of moving the entire way by truck. On the Export side, an IPI origin is an inland rail ramp where a container starts its journey before being railed to the port of loading. On the Import side, an IPI destination works the same way in reverse: a container is railed inland after it's discharged at the port.

Where to Find It

Open Explore, click Filtered By [X] Field(s) to open the Filter Records panel, then add Has IPI Origin as a filter.

How It Works

Set the filter to Yes to see only containers that originate inland and travel by rail to their port of loading, or No to see containers moving directly from the port. This mirrors the existing Has IPI Destination filter, which does the same for Import containers moving inland after discharge.

Example

Say a shipper loads containers at an inland rail ramp in Dallas before they reach the port of loading in Houston. Those containers travel by rail from Dallas to the port, adding a rail leg and extra transit time that direct-port shipments don't have. A team that wants to see just those rail-origin Exports, whether to compare transit times, flag lanes that need extra lead time, or check which shipments involve a rail leg, can set Has IPI Origin to Yes and filter straight to that group of containers.

Why This Matters

Inland-origin moves carry different transit timelines and risk factors than direct port moves. This filter makes it easy to isolate and monitor that segment of your Export volume for reporting, exception monitoring, or operational planning, without manually cross-referencing origin data.

Did this answer your question?