The SCAC is how automated systems refer to a carrier. It appears on the bill of lading, in EDI transactions like the 204 load tender and 214 status, and in a shipper’s or broker’s routing guide that assigns lanes to specific carriers.
Codes are assigned and maintained by the National Motor Freight Traffic Association (NMFTA) and renewed annually. Certain government and intermodal programs require one; many large shippers will not set a carrier up in their TMS without it.
A carrier onboarding with a retail shipper or a broker that runs EDI will usually be asked for its SCAC early in the process, alongside its MC number and insurance.
Example
A broker onboards a new carrier for a retail account that tenders loads by EDI 204. The carrier provides its SCAC; the broker enters it in the routing setup so that every tender, acceptance, and status update for that account references the carrier by code automatically.
Why it matters
Without a SCAC, a carrier cannot be added to many shippers’ routing guides or EDI setups — it is a prerequisite for the retail and brokered freight that runs on automated tendering.
How teams use this term
In a carrier operation, SCAC belongs in the conversation about load closeout, billing readiness, and evidence management. The useful question is not only what the term means, but which record or decision it changes. A dispatcher may see it while planning a load, a driver may create evidence for it in the field, and accounting may need the same context before a customer invoice or carrier settlement can be finalized. Keeping the term attached to the related workflow prevents a definition from becoming disconnected vocabulary.
When reviewing SCAC, ask who owns the next action, what evidence supports the record, and what date or threshold makes the situation change. The answer can vary by equipment, lane, authority, customer routing guide, or contract. A small carrier should document the assumption it used rather than treating a general explanation as a universal rule. The related terms on this page are intended to help a team move from the definition to the operational decision.
A practical review starts with the example above, then compares it with the carrier's own settlement, dispatch, document, or compliance records. If the term affects a regulated filing, payment obligation, or customer requirement, verify the current primary source before acting. Trailflow can provide workflow context, but the carrier remains responsible for the policies, records, and professional advice that apply to its operation.
In Trailflow, this shows up in EDI.