Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Before a booking decision, the record should be normalized without losing the originally submitted values, checked for completeness and validity, compared against an authoritative source for carrier identity and status where the workflow uses SCAC, reconciled for consistency across shipment, party and route fields, and linked to a stable shipment ID before anything is tendered. Every external check should keep its source and the time it was run. A carrier status result is one signal in that gate. It does not show that a carrier is safe, legally authorized, insured, or suitable for a particular load.
The sequence below is a practical process built from published building blocks: NMFTA’s SCAC services, FMCSA’s data-quality measures, GS1 US’s voluntary tender guide, and the U.S. advance-data rule for truck cargo. No single published standard covers the full chain, so treat it as process design for your own gate, not as a certified procedure.
Where the gate sits in the booking process
A pre-booking check answers one question: is this record complete and trustworthy enough to commit capacity to it? It comes before the carrier accepts a tender, before pickup, and before any customs filing. Those later stages have their own checks, and mixing them up is a common reason teams either over-check a routine load or skip a required filing.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Stage | Question it answers | Typical check |
|---|---|---|
| Before booking | Is the record complete, and is the carrier identity consistent with an authoritative source? | Quality checks, SCAC status lookup, field consistency, documented hold rules |
| Tender and response | Did the carrier receive the tender, and did it accept? | Functional acknowledgement and a separate acceptance response (GS1 US tender guide) |
| Pickup and in-transit | Is the shipment still linked to the tendered record? | Shipment ID continuity across status updates |
| Customs filing, covered U.S.-bound truck cargo | Was the required advance electronic data filed in time? | Data elements and timing under 19 CFR 123.92 |
Step 1: Normalize without erasing the original
Systems can only compare records when names, addresses, units, dates and identifiers follow the same conventions. Normalization becomes a problem when it overwrites the source value, because a later dispute cannot be traced back to what the shipper or carrier actually submitted. The following controls keep the record auditable. They are recommended practice drawn from data-quality and identifier-integrity guidance, not a requirement stated by a single body.
#1 Best Overall
- Store the submitted value and the normalized value side by side, with the normalization rule that produced the second one.
- For every external value, record the source name, the field returned, and the retrieval time.
- Show conflicts in the record. A silent replacement of one value with another hides exactly the mismatch the gate exists to catch.
- Standardize units (for example pounds versus kilograms), date formats, time zones and identifier formats before comparison.
Step 2: Check quality and completeness
FMCSA’s data-quality evaluations for certain IRP and IFTA state data use five dimensions. They are useful as a model for pre-booking checks, but FMCSA does not define a booking score on them, and the measures were designed for state-reported data rather than shipment records.
- Timeliness: whether the value was updated recently enough for the decision it supports.
- Completeness: whether every required field is populated.
- Accuracy: whether the value matches the authoritative source.
- Validity: whether the value conforms to the expected format or code set.
- Update frequency: how often the source is refreshed, compared with how often your records change.
FMCSA’s data-quality page lists monthly reports and included reports through August 2026 when it was reviewed.
Decide what blocks a booking and what only triggers review
The five dimensions tell you what to measure. Your organization still has to decide which failures stop a booking. The table gives a workable starting point; the thresholds are a policy choice for each shipper, broker or 3PL, not a published rule.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Condition found | Suggested handling |
|---|---|
| Carrier identifier missing | Block the tender until the identifier is supplied and checked |
| Check result older than your freshness limit | Rerun the check before commitment |
| Name or address differs from the authoritative source | Hold and escalate if it affects carrier identity; otherwise review |
| Weight or quantity differs between order and carrier-facing record | Hold if it changes equipment or compliance data; otherwise review |
| Check could not be completed | Mark the field unverified. Never treat it as a passed check |
Step 3: Confirm the carrier identity and status signal
This check applies to U.S. motor-carrier workflows that use Standard Carrier Alpha Code (SCAC). Outside that scope, the sources reviewed here do not establish an equivalent check, and you should not describe a SCAC result as global carrier verification.
NMFTA states that SCAC verification for non-Class 8 carriers takes place during application, renewal or reinstatement. It includes identity and address validation designed to confirm legitimacy, carried out either through FMCSA data or through a government-ID process. NMFTA’s identity-verification overview was last updated May 26, 2026. NMFTA’s SCAC lookup and API make the current status and verification indicators available to you at the time of checking.
What a status result establishes
- The SCAC’s status and verification indicators as returned by NMFTA’s source at the time of the check.
- A dated, sourced data point that you can store in the shipment record and cite later.
What a status result does not establish
- Operating authority, insurance coverage, safety performance or compliance history.
- Available equipment or capacity for the specific load.
- Whether the movement itself is lawful, suitable or safe for the cargo.
Where your organization or the applicable law requires those points, corroborate them through the appropriate separate checks and keep those results in the same record.
Rank #4
Step 4: Validate shipment, party and route-specific fields
Once the carrier identity is settled, check that the shipment record is internally consistent. A carrier can be verified and the load still be wrong, for example when the consignee on the tender does not match the consignee on the bill of lading. Confirm that the following fields agree with each other and with the tender:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Origin and destination parties, with addresses in a consistent format.
- Shipment references, including the shipper’s reference and any carrier-facing reference.
- Cargo description, quantities, weight and units.
- Equipment or container details and the equipment type requested.
- Pickup and delivery timing, including any preset appointment information.
- Special handling fields, including hazardous-material indicators.
Covered U.S.-bound truck cargo: 19 CFR 123.92
For covered incoming truck cargo arriving in the United States, 19 CFR 123.92 requires advance electronic data. As the rule is reproduced in the Cornell Legal Information Institute text reviewed for this article, the required elements include:
- The carrier’s SCAC.
- Shipment references.
- Quantities and weight.
- A precise commodity description, or a six-digit HTS number.
- A hazardous-material code when applicable.
- Shipper and consignee details.
The timing is also rule-specific. Depending on the CBP-approved electronic system used, the data must be transmitted 30 minutes or 1 hour before the carrier reaches the first U.S. port of arrival, or within a lesser authorized period. This is a filing deadline for that rule and that movement, not a general booking target. Before operational or legal reliance, check the current text and CBP implementation details in official government sources, because the Cornell text is a secondary reproduction.
How mode and geography change the checks
| Scope | What the reviewed sources support | Limit |
|---|---|---|
| U.S. motor carrier using SCAC | SCAC status lookup and FMCSA-linked identity verification | One signal, not a full carrier assessment |
| Covered U.S.-bound truck cargo | Advance electronic data elements and timing under 19 CFR 123.92 | Applies to the covered rule and shipment only |
| Full truckload tender (U.S. workflow) | Voluntary GS1 US guidance on shipment ID linkage, tender response and acknowledgement | Voluntary and dated 2015 |
| Other modes or other countries | Not established by the reviewed sources | Needs its own review of applicable identifiers, rules and authoritative sources |
Step 5: Route conflicts to a decision
When a material conflict remains after normalization and checking, the booking should not proceed on the strength of the record alone. Route the conflict under a documented exception policy that names who can release a hold and what evidence they must record. The following decisions illustrate one way to structure that policy.
| Conflict | Action |
|---|---|
| Carrier identifier not verified at check time | Hold. Do not tender until the check is rerun or the issue is resolved |
| Party identity differs from the authoritative source | Hold and escalate to a named reviewer |
| Quantity, weight or hazardous-material fields disagree between records | Hold where the difference changes equipment or compliance data; otherwise review |
| Formatting difference that disappears after normalization | Proceed, keeping both original values in the log |
Step 6: Preserve the shipment ID through tender and downstream messages
A gate is only useful if its result stays attached to the shipment. GS1 US’s voluntary full truckload (FTL) tender guide, version R2.0 dated December 16, 2015, recommends a stable shipment ID linkage across the tender and later messages, preset appointment information where applicable, and a distinct response to each tender. Because the guide is more than a decade old, check whether your trading partners follow newer implementation guidance before relying on its message sequence.
- Create the tender only after the pre-booking gate has passed or an exception has been recorded.
- Carry the same shipment ID through the tender, the carrier’s functional acknowledgement and the carrier’s acceptance response.
- Recognize that the functional acknowledgement confirms receipt, not acceptance. The guide suggests returning it within 15 minutes of receiving the tender. This is voluntary implementation guidance, not a legal deadline.
- Keep the status updates and billing records tied to the same shipment ID and to the stored verification record from the gate.
Comparing ways to run the check
When choosing how to perform carrier checks, the main options are manual lookup, real-time API integration and scheduled bulk data. NMFTA describes all three for SCAC data. The table compares them on the axes that matter for a booking gate. Where the reviewed NMFTA pages do not state a value, the cell says so.
| Method | Best fit | Data freshness | Fields returned | Access and limits |
|---|---|---|---|---|
| Manual lookup (on-demand SCAC verification) | Low volume, exception handling, spot checks | Current at the moment of lookup | Not stated in the reviewed pages beyond status and verification | Process through NMFTA’s public lookup. Usage terms not stated |
| Real-time API | Integrated tender workflows that need a check before each booking | Real-time check, per NMFTA’s description | Status and verification indicators. NMFTA states it does not expose personal or sensitive identity data | Available to approved partners only. Price and service terms not verified here; confirm with NMFTA |
| Scheduled bulk data | Batch screening and reporting across many records | Refresh frequency not stated in the reviewed pages | Not stated in the reviewed pages | Confirm availability, terms and permitted use with NMFTA |
NMFTA’s SCAC API page makes the purpose of the integration explicit: “The SCAC API provides programmatic access to SCAC status and verification indicators so organizations can integrate trust checks directly into their systems.” The statement describes what the data is for. It does not turn a status indicator into a guarantee of safety, authority or fit for a load, and the gate described above still applies after the lookup returns.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
