What supply chain visibility software actually does
At its core, supply chain visibility software collects status from every carrier you use, turns it into one consistent timeline per shipment and tells you when something needs attention. The better tools add a predicted arrival time, alerts that reach the people who can act, and a way to share status with your own customers without forwarding carrier emails.
For a mid-sized shipper, the value usually comes from three places.
- Less manual checking: nobody spends the morning copying status lines from carrier sites into a spreadsheet.
- Earlier warnings: a delayed container or a stuck LTL shipment shows up before the customer calls.
- Better data for decisions: on-time performance per carrier and lane, dwell at terminals, and the cost of delays.
Start with the shipments you actually move
Before you look at any product, list your freight for a typical month by mode and by carrier. Note who books each shipment (you, a broker, a forwarder or a 3PL) and which reference you get back (PRO, container number, air waybill, parcel tracking number, bill of lading). This list becomes your test set later, and it quickly shows which coverage matters to you.
| Mode | Typical reference | What good visibility looks like |
|---|---|---|
| Parcel | UPS, FedEx, USPS tracking numbers | Every scan, exceptions, delivery confirmation |
| LTL | PRO number | Terminal events, appointment and OS&D exceptions, POD |
| FTL | Load ID, BOL, PRO | Location updates, ETA to the consignee, check calls replaced |
| Ocean | Container number, bill of lading | Vessel milestones, transshipment, discharge, last free day, empty return |
| Air | Air waybill number | Acceptance, flights, received from flight, ready for pickup |
Coverage, by mode and by carrier
Ask how each mode is covered, not just how many carriers are on a list. Coverage counts mean little if the carriers you use most are thin or delayed. Bring ten real numbers per mode from the last month and check them during the trial.
- Parcel: the major US carriers, plus any regional carriers you use.
- LTL: national carriers such as ODFL, Estes, Saia and XPO, and the regional carriers on your routing guide.
- Ocean: the lines on your import lanes, such as Maersk, MSC, CMA CGM, Hapag-Lloyd and ONE, including transshipment events.
- Air: the airlines your forwarders book, tracked by master air waybill.
- Truckload: how location data arrives (carrier apps, ELD data, broker feeds) and what happens when a carrier provides none.
How shipments get into the system
The best tracking data is useless if adding shipments is slow. Look at every intake path and ask who maintains it.
- Pasting or uploading numbers, with the carrier detected from the number format.
- CSV upload and scheduled SFTP feeds for teams without an integration budget.
- Connectors to your ERP, order management or ecommerce platform.
- An API for your own systems and webhooks back out.
- Email forwarding of carrier confirmations, where offered.
Auto detection deserves a test of its own. Container numbers follow ISO 6346 and air waybills carry an airline prefix with a check digit, so a good tool identifies them reliably. LTL PRO numbers are carrier specific, so expect the tool to ask which carrier when the format is ambiguous rather than guess. See how to track a container by number for what a solid format check looks like.
Data quality and event normalization
Every carrier names events differently. One line says discharged, another says unloaded from vessel, a third uses a code. A visibility tool earns its keep by mapping all of them into one set of milestones so a filter like "discharged, not gated out" works across every carrier. During the trial, open the same type of shipment from three carriers and check that the timelines read the same way, that times are shown in a clear time zone, and that duplicated or out of order events are handled.
Predicted ETA and alerts
Carrier ETAs are often optimistic and rarely updated when a vessel skips a port or freight misses a linehaul. A predicted ETA from the tool should come with a range, so your team knows how much confidence to place in it. Be wary of any vendor that quotes a fixed accuracy figure without showing how it is measured on your lanes.
Alerts are only useful if the right person gets them in the right place. Check that you can set rules by mode, customer, lane or carrier and send them by email, Slack or webhook. Ask how noise is controlled, because a tool that sends fifty alerts a day is ignored by the second week.
Customer facing tracking
If your customers ask "where is my order", a branded tracking page and automatic notification emails can remove a large share of those tickets. Look for your logo and colors, your own domain on higher tiers, and the ability to hide carrier names or internal references from the customer. Our page on the branded tracking page shows what this looks like in practice.
Integrations and API
Ask which systems are supported out of the box and which require a project. For mid-sized shippers the usual list is Shopify for ecommerce, NetSuite, SAP Business One or Microsoft Dynamics for ERP, Slack for alerts, plus CSV and SFTP for everything else. If you plan to build on the data, read the API documentation before signing: check authentication, rate limits, webhook retries and whether events arrive already normalized.
Carrier scorecards and reporting
Visibility data becomes negotiating data once it is summarized. Look for on-time delivery per carrier and per lane, dwell at terminals, exception counts and export to CSV. These numbers matter in rate talks, as explained in our article on carrier on-time performance.
Security, users and access
Even a mid-sized team needs basic controls: separate users rather than a shared login, roles that limit who can change settings, and an audit log for larger teams. If you are a 3PL, ask about client sub-accounts so each client sees only its own freight. If your IT team uses single sign-on, check which plan includes SAML.
Pricing and contract terms
Enterprise visibility suites often require an annual contract, a sales process and a paid implementation. That model fits a global manufacturer, not a team that wants results this month. Compare tools on these points.
| Question | Why it matters |
|---|---|
| Is the price public | You can budget without a sales cycle |
| What counts toward the limit | Shipments added per period, containers, users, history |
| Can you buy without a contract | Lower risk if the tool does not fit |
| Are integrations included | Avoid surprise project fees |
| How does upgrading work | You should pay the difference and get the higher limits immediately |
ShipmentVisibility publishes every plan, from Starter at $49 a month ($24 a month billed yearly) to Enterprise at $1,499 a month ($749 a month billed yearly), with self-serve checkout and no sales call. Details are on pricing.
How to run a two week evaluation
- Week one: load last month's numbers for every mode and compare the timelines with the carrier sites. Note missing carriers, missing events and confusing labels.
- Week one: set alerts for two real situations, such as containers discharged and not released, and LTL shipments with no event for a business day.
- Week two: connect one data source (CSV feed, Shopify or your ERP) and stop adding shipments by hand.
- Week two: share the tracking page with one friendly customer and ask whether it answered their questions.
- At the end: count the hours your team no longer spends checking carrier sites and decide on facts, not on a demo.
A short checklist to take into demos
- Covers every mode and the carriers you use most.
- Detects carriers from numbers and asks when unsure.
- Normalized milestones with clear time zones.
- Predicted ETA with a confidence range.
- Alert rules by email, Slack and webhook.
- Branded tracking page and customer emails.
- Integrations you need without a project.
- Public pricing and no long contract.
To see how one tool handles all of this, read the supply chain visibility software overview or walk through the features.