From email tenders to TMS–e?auction: SCAC?normalized lanes and auditable awards

Overview

A food manufacturer’s freight tenders were coordinated via email and spreadsheets, which led to missed lanes, inconsistent rate capture, and slow awards. Intelligex integrated the company’s Transportation Management System (TMS) with an e-auction module, automated lane packaging with carrier tier rules, and pushed awarded rates back into the TMS with an auditable trail. Tender cycles became predictable, coverage improved, and manual copy-paste errors dropped without changing how carriers moved loads day to day.

Client Profile

• Industry: Food manufacturing and distribution
• Company size: Multi-plant network serving national retail and foodservice customers
• Stage: Mature logistics function modernizing freight procurement and governance
• Department owner: Procurement, Supply Chain & Logistics
• Other stakeholders: Transportation/Logistics Operations, Finance/Controllership, Category Sourcing, Legal, IT/TMS, Plant Scheduling, Carrier Partners

The Challenge

Annual and mid-cycle freight events were run by emailing spreadsheets to carriers. Each workbook represented a lane package with tabs for origin-destination pairs, volume bands, and accessorials. Carriers returned customized files with added columns, different units, or incomplete coverage. Planners merged responses by hand, and tender timelines slipped as everyone reconciled versions. Some lanes never made it into the final award set, while rates and accessorials for others were captured inconsistently.

The TMS held the live lane and rate structure for execution, but it was not feeding or receiving data from the tender process. Buyers exported lane lists from various reports, carriers bid against the spreadsheet snapshot, and awards were rekeyed into the TMS at the end. Approvals were handled in email, and the rationale for award scenarios lived in personal files. Finance needed a clear audit trail, Legal wanted exceptions documented, and Transportation needed awards to reflect the same lane attributes used to plan loads. None of this fit neatly into a process built on attachments and ad hoc macros.

Switching TMS or replacing carrier-facing tools was not an option. The team needed a thin integration layer that turned the TMS into the source for lane definitions and accepted awarded rates back cleanly, while giving carriers a consistent e-auction experience. Governance had to be built in without slowing bid cycles or imposing new accounts on carriers unnecessarily.

Why It Was Happening

Lane masters drifted across spreadsheets. Different buyers exported lane lists with slightly different keys, such as varying city names, zip boundaries, or service levels. Carriers returned bids with modified templates, so normalization happened late, under deadline pressure. Accessorials were free text, which made comparisons unreliable. The TMS rate model was well structured, but it sat downstream of a spreadsheet-driven tender process with no common identifiers.

Carrier data was inconsistent. Some carriers bid under a parent brand, others under regional subsidiaries, and several used different names on contracts than in the TMS. Without a standard like the Standard Carrier Alpha Code (SCAC), coverage reports were misleading and award rollups were fragmented. Meanwhile, approval rules—such as tiering incumbents, limiting awards to preferred carriers, or requiring secondary review for high-risk corridors—were written in playbooks but not enforced by the process.

The Solution

Intelligex connected the TMS to an e-auction module and introduced a governed lane master and packaging service. The TMS became the source for lane definitions and attributes, while the e-auction managed carrier invitations, bid collection, and scenario evaluation. Automated lane packages were generated with mode- and region-aware rules, and carrier tiering guided eligibility. Bids were validated and normalized on entry, and once awards were confirmed, rates and accessorials were written back to the TMS with effective dates and an approval log. Carriers continued using a familiar portal for bidding; internal teams gained a predictable, auditable flow.

• TMS integration for lane exports and rate ingestion; reference pattern based on Oracle Transportation Management.
• E-auction and sourcing optimization module for carrier bid collection, scenario analysis, and awards; example product reference: Coupa Sourcing Optimization.
• Lane master and packaging logic that grouped lanes by mode, region, and service level, with volume bands and accessorial catalogs sourced from the TMS.
• Carrier master normalization using Standard Carrier Alpha Codes (SCAC) to align bids and awards across systems; background: NMFTA SCAC.
• Bid template standardization with unit, currency, and fuel surcharge normalization; validation blocked missing fields and improper units at upload.
• Carrier tier and eligibility rules (incumbent, core, regional, new-to-network) enforced at package creation and invitation.
• Scenario modeling that honored constraints such as minimum lane coverage, capacity caps, incumbent protections, and diversification targets.
• Approval workflow requiring Procurement and Finance sign-off for exception scenarios, with Legal review for terms variations.
• Write-back to the TMS of awarded rates, accessorials, effective dates, and carrier assignments, plus attachment of award letters and approval logs to lanes.
• Dashboards showing coverage by lane, bid freshness, validation errors, award decisions, and effective dates for upcoming changes.

Implementation

• Discovery: Cataloged current lanes, modes, and accessorials in the TMS. Collected past tender files to identify normalization pain points. Mapped carrier identities to SCACs and documented tiering policies. Gathered approval requirements from Procurement, Finance, and Legal.
• Design: Defined the lane master schema and identifiers to survive export and reimport. Designed packaging rules by mode and region, and standardized a bid template with unit and currency controls. Mapped award data back to the TMS rate structures and accessorial tables. Specified approval gates and exception paths.
• Build: Implemented TMS connectors for lane export and rate ingestion. Configured the e-auction module with carrier profiles, SCAC mapping, packaging logic, and validation rules. Built normalization services for bids and a scenario engine aligned to business constraints. Created write-back services to update the TMS with awards and attach artifacts.
• Testing and QA: Ran a mock tender in shadow mode using recent lanes and synthetic bids. Verified normalization of units and accessorials, scenario outcomes, and award write-back to a TMS sandbox. Tested edge cases: partial coverage, multi-stop lanes, and carriers bidding under different legal entities. Confirmed audit logs captured decisions and approvals.
• Rollout: Piloted with a subset of lanes and a core carrier group while keeping the legacy spreadsheet process as a safety net. Expanded to remaining modes and regions after the pilot, with feature flags to adjust validation strictness based on real-world behavior.
• Training and hand-off: Delivered short sessions for buyers on packaging and scenario reviews, for Transportation on interpreting awards in the TMS, and for carriers on portal submissions and required fields. Published quick-reference guides and held office hours during the first live cycle.
• Human-in-the-loop review: Procurement reviewed scenarios and selected awards; Finance and Legal approved exceptions. Automation enforced rules and normalization, but humans finalized awards and documented rationale for any deviations.

Results

Tender cycles settled into a repeatable rhythm. Lanes originated from a single master, carrier eligibility followed tier rules, and bids were validated at the door. Buyers evaluated scenarios instead of reconciling spreadsheets, and carriers saw consistent packages and response formats. Awards flowed back into the TMS cleanly, so operations moved forward without rekeying.

Auditability improved. Each awarded lane had a linked decision history, attachments, and effective dates. Finance could trace rate adoption and confirm that approvals matched policy. Transportation gained confidence that awarded rates, accessorials, and carrier assignments in the TMS lined up with what carriers agreed to in the e-auction. Manual copy-paste errors and late lane fixes faded from the process.

What Changed for the Team

• Before: Email-based spreadsheets with custom carrier edits; After: Standardized e-auction packages generated from a governed lane master.
• Before: Inconsistent units and accessorials; After: Validation and normalization at bid upload with controlled catalogs.
• Before: Unclear coverage and late-discovered gaps; After: Eligibility rules and dashboards showing lane coverage before awards.
• Before: Awards rekeyed into the TMS; After: Automated write-back of rates, accessorials, and effective dates with an audit trail.
• Before: Approvals scattered in email; After: Scenario approvals captured with rationale and attached to awarded lanes.
• Before: Carrier identities varied by document; After: SCAC-aligned carrier master across sourcing and execution.

Key Takeaways

• Use your TMS as the source for lane definitions and push awards back into it; avoid spreadsheet-driven drift.
• Normalize carrier identities and enforce standard bid templates so comparisons are meaningful and repeatable.
• Encode carrier tiering and eligibility rules in the packaging process to prevent avoidable gaps and rework.
• Validate units, currencies, and accessorials at submission to stop errors at the source.
• Keep humans in control of awards and exceptions, but let automation handle packaging, validation, and audit logging.
• Pilot with a subset of lanes and carriers, run in shadow mode, and scale once the write-back and approvals behave predictably.

FAQ

What tools did this integrate with?
The flow connected the existing TMS for lane and rate records, an e-auction module for carrier bidding and awards, and internal approval systems for Procurement, Finance, and Legal. The TMS integration followed patterns like those documented for Oracle Transportation Management, and the e-auction configuration aligned to platforms such as Coupa Sourcing Optimization. Carrier identities were standardized using SCAC codes.

How did you handle quality control and governance?
We introduced a lane master with stable identifiers, a bid template with unit and currency controls, and validation that blocked incomplete or malformed submissions. Carrier eligibility and tiering rules were enforced at packaging. Scenario selections required Procurement approval and, when applicable, Finance and Legal sign-off. All decisions, exceptions, and awarded rates were logged and attached to lanes in the TMS.

How did you roll this out without disruption?
We ran a mock tender in shadow mode to validate normalization and write-back, then piloted with a limited set of lanes and carriers while keeping the legacy process available as a fallback. Feature flags let the team adjust validation strictness during early cycles. Carriers received concise instructions and support during the first live event to minimize friction.

How did you handle carrier and lane normalization?
Carriers were mapped to SCAC codes and consolidated under a single master, addressing differences between parent brands and regional subsidiaries. Lanes used a consistent key derived from origin-destination, mode, and service level. Accessorials came from controlled catalogs, and bid submissions were normalized for units and currencies at upload.

How were awards communicated and pushed back to execution?
After scenario selection and approvals, awards were written back to the TMS as rate records with effective dates and accessorials. Award letters and approval logs were attached to lanes. Carriers received notifications through the e-auction portal and email, and Transportation saw the updates reflected directly in planning and tendering screens without manual re-entry.