Transportation Management / Rate Shopping is where ERP discipline either begins or breaks.
Carrier Rate Shopping and Carrier Selection at Shipment Creation looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Average freight cost per shipment reduced by 8% within 6 months; routing guide compliance above 95%; rate shop time reduced from 15 minutes manual to under 30 seconds
The control flow a finance team actually needs.
Step 1
Rate Shop Across At Least 10...
Step 2
Return Ranked Results Within 10 Seconds
Step 3
Apply Customer-Specific Negotiated...
Step 4
Enforce Routing Guides That Mandate...
Step 5
Require Reason Code For Routing Guide...
The ERP surface involved.
Module
Transportation Management / Rate Shopping
Actors
Shipping Clerk, TMS Rate Engine, Carrier APIs, Logistics Manager
Tier
Tier 2
Finance area
Supply Chain, Demand Planning & Logistics
Region lens
US and UK finance teams
Publication date
May 17, 2026
Rate shop across at least 10 pre-integrated carriers simultaneously; return ranked results within 10 seconds; apply customer-specific negotiated rates from rate tables; enforce routing guides that mandate preferred carriers for specific lanes; require reason code for routing guide override; store quoted rate for cost accrual and audit; support parcel, LTL, FTL, and express service types; log all rate shop results for lane analysis
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Rate shop across at least 10 pre-integrated carriers simultaneously | Given a shipment ready with weight, dimensions, origin/destination, and service level requirements |
| Control 2 | return ranked results within 10 seconds | when the rate engine queries at least 10 pre-integrated carrier APIs simultaneously |
| Control 3 | apply customer-specific negotiated rates from rate tables | then ranked results are returned within 10 seconds applying negotiated rates and routing guide rules, the compliant lowest-cost carrier is auto-selected, and the quoted rate is stored for cost accrual |
| Control 4 | enforce routing guides that mandate preferred carriers for specific lanes | negative) when a clerk overrides the routing guide mandatory carrier without a reason code then the system must return 422 ROUTING_GUIDE_OVERRIDE_REASON_REQUIRED. |
| Control 5 | require reason code for routing guide override | Average freight cost per shipment reduced by 8% within 6 months; routing guide compliance above 95%; rate shop time reduced from 15 minutes manual to under 30 seconds |
| Control 6 | store quoted rate for cost accrual and audit | Average freight cost per shipment reduced by 8% within 6 months; routing guide compliance above 95%; rate shop time reduced from 15 minutes manual to under 30 seconds |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | When a shipment is ready for booking, the shipping clerk initiates carrier selection in the TMS. The rate engine sends a real-time rate request to pre-integrated carrier APIs (UPS, FedEx, DHL, regional LTL carriers) with package weight, dimensions, origin/destination, and service level requirements. All qualifying rate quotes are returned and ranked by cost, transit time, and carrier reliability score. The system auto-selects the carrier that meets the required transit time at the lowest cost, or the clerk may override with a preferred carrier and reason code. The selected carrier and rate are confirmed, and a booking reference is generated. |
| Control rules | Rate shop across at least 10 pre-integrated carriers simultaneously; return ranked results within 10 seconds; apply customer-specific negotiated rates from rate tables; enforce routing guides that mandate preferred carriers for specific lanes; require reason code for routing guide override; store quoted rate for cost accrual and audit; support parcel, LTL, FTL, and express service types; log all rate shop results for lane analysis |
| Acceptance proof | Given a shipment ready with weight, dimensions, origin/destination, and service level requirements; when the rate engine queries at least 10 pre-integrated carrier APIs simultaneously; then ranked results are returned within 10 seconds applying negotiated rates and routing guide rules, the compliant lowest-cost carrier is auto-selected, and the quoted rate is stored for cost accrual; (negative) when a clerk overrides the routing guide mandatory carrier without a reason code then the system must return 422 ROUTING_GUIDE_OVERRIDE_REASON_REQUIRED. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`rate_shop_request` { request_id: string, shipment_id: string, service_type: enum(PARCEL/LTL/FTL/EXPRESS), origin_zip: string, destination_zip: string, weight_lbs: numeric, dimensions_cbft: numeric, required_transit_days: int }; `carrier_rate_quote` { quote_id: string, request_id: string, carrier_id: string, service_level: string, rate_amount_minor: int64, rate_currency_code: char(3), transit_days: int, reliability_score: numeric, routing_guide_compliant: bool }; `shipment_carrier_selection` { selection_id: string, request_id: string, quote_id: string, override_reason: string, selected_by: string }; (reference, product may differ).API and events
`POST /v1/rate-shop/requests` { shipment_id, service_type, origin_zip, destination_zip, weight_lbs, dimensions_cbft, required_transit_days } -> 200 { request_id, quotes[] }; `POST /v1/rate-shop/requests/{request_id}/select` { quote_id, override_reason } -> 201 { selection_id, booking_reference }; emits `shipment.carrier.selected` event; idempotent via `external_id`.State transitions
`PENDING -> QUOTED -> SELECTED -> BOOKED`; terminal `EXPIRED` if no selection within configurable window; guard: routing-guide non-compliant selection blocked without override_reason.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.