Infrastructure for Automated Purchase Requisition Generation

Carrier contracts formally documented with rates, service levels, and terms. RFP processes defined for new lane procurement. Vendor qualification procedures exist (insurance verification, safety ratings, legal checks). But the strategic knowledge—carrier relationships, negotiation approaches, market intelligence—remains largely in procurement manager's head. Procurement teams small (often 1-3 people) with limited time for documentation. Competitive knowledge viewed as personal asset. Relationship management is art, resists standardization. High dependency on experienced procurement managers who resist documenting their approach.

Carrier rate tables entered into TMS manually or via spreadsheet import. Contract terms documented when signed. Carrier performance data flows from operations (on-time, claims, etc.) but often not formally logged for procurement use. RFPs and carrier responses tracked in email or basic spreadsheet. Much procurement work happens in relationships—phone calls, trade show conversations, informal carrier check-ins. This context rarely captured beyond high-level notes. No systematic process for logging market intelligence or carrier feedback. Spreadsheet-centric culture means data captured in fragmented files.

Carrier master data structured in TMS (company name, SCAC, insurance, safety rating). Rate tables organized by lane, equipment type, service level. Contracts have standard sections (parties, rates, terms, SLAs). But procurement knowledge poorly organized—carrier capabilities, relationship history, negotiation outcomes exist in unstructured documents and memory. Qualitative carrier intelligence not structured—"this carrier is good for white-glove service" exists nowhere queryable. Procurement insights from RFPs never formalized into reusable knowledge. No taxonomy for carrier capabilities or relationship quality.

Contracts stored as PDFs in SharePoint or shared drives—searchable only by filename. TMS has carrier data but limited API access. Carrier portals exist for rate updates but don't integrate with procurement systems. Procurement works largely in spreadsheets and email, neither exposing data programmatically. Procurement viewed as "soft" function, not tech priority. Contract management systems expensive, never budgeted. TMS carrier modules basic—not designed for strategic procurement. No procurement-specific software in mid-market logistics. Spreadsheet culture means data lives in individual files, not queryable systems.

Rate tables updated during annual bid cycles or when carrier raises rates (reactive). Carrier insurance and safety ratings refreshed when contracts renew or when operations flags issue. Carrier scorecards compiled quarterly but not used to systematically update carrier classifications or strategies. No owner for carrier data quality beyond compliance minimums. Procurement team reactive, focused on current negotiations. Market intelligence gathered but not systematically maintained. Carrier landscape changes (acquisitions, capacity shifts, service changes) not tracked proactively.

Procurement systems largely separate from operations. Carrier contracts and rates flow to TMS (one-way), but carrier performance data doesn't flow back to procurement systematically. Billing data disconnected from carrier scorecards. Finance handles carrier payables with limited visibility into service quality. Procurement and operations often separate organizations with minimal system integration. No procurement platform connecting contracts, rates, performance, and spend. TMS designed for execution, not procurement strategy. Finance systems disconnected from operational quality metrics.