On the Mexico–U.S. corridor, freight tendering means offering the trip to the carrier · requesting a quote or capacity · comparing under the same assumptions · awarding with a trail. It is not a public-works tender and not a TMS module pamphlet: it is the daily act that decides whether the dock has a unit on time and whether accounts payable can defend the rate.
This guide separates operating tender from RFQ/RFP procurement, explains spot vs contract, and shows why a portal that “publishes routes” is not enough if the close still happens on WhatsApp and the invoice arrives without a file. Short definition in the tendering glossary; product that executes: assignment agent.
- two cadences, one verb
- Spot / contract
- price is not the only score
- Rules + SLA
- pre-pay anchor
- Written trail
- pattern when auditing 100%
- 5–7%
Cluster: Freight tendering · Assignment agent · OCL vs Unigis
What freight tendering is for the shipper
For the shipper or the logistics operator (3PL) buying capacity, tendering is the short commercial cycle: freeze the shipment brief, send it to the network, receive offers, compare, and award. It can be a single trip or a recurring lane.
English terms (tender / freight RFQ · request for quote) sit next to Spanish corridor phrases for offering the trip and assigning a unit. The label matters less than whether assumptions are identical for everyone (equipment, window, handling, insurance) and whether the award survives until the invoice.
Spot vs contract: same verb, different cadence
Confusing spot with contract is how opaque rates get justified. Both are tendering; rhythm and risk change.
What is offered
Spot: One shipment (or an urgent peak)
Contract / lane: Recurring capacity on a lane
Typical response SLA
Spot: 30–60 min on hot lanes · 2–4 h on cold
Contract / lane: Agreed award / refresh windows
Scorecard
Spot: All-in price + time-to-unit + recent history
Contract / lane: Price + service by category + committed capacity
Typical failure
Spot: Late coverage to appointment / OTD break
Contract / lane: Award in a slide deck · execution in chat
Minimum trail
Spot: Winning offer + runner-up + assumptions
Contract / lane: Rate card + capacity + written exceptions
Related: spot vs contract · rate confirmation.
How the process runs on the corridor
Discipline sits in the assumptions, not in trendy software. Use this sequence for spot and for refreshing a contractual lane.
Operable cycle
From brief to award
Freeze brief
Origin, equipment, window
Network + SLA
Primary and backup
Identical RFQ
Same template to all
Scorecard
Price and service
Award
Winner and runner-up
Write trail
Rate in the trip file
- Minimum brief: origin/destination, equipment type, weight/cube, hazmat, load/unload windows, handling, free time, insurance, and documents (Carta Porte when applicable).
- Ban incomplete offers: without an all-in total or accessorial breakdown, they do not enter the comparison.
- Notify the rest: the market only improves when the network sees a clean close.
Rules that actually move price, SLA, and category
A portal that “favors better prices and service levels by category” only works if those rules are written and applied to the same shipment finance will see.
All-in price
What it decides: Fair comparison (base + accessorials)
What breaks if missing: Cheapest on paper · most expensive on the invoice
Response SLA
What it decides: When the tender closes
What breaks if missing: The tender never dies · the dock waits
Category / service
What it decides: Who can see the offer (insurance, equipment, lane)
What breaks if missing: You assign capacity that cannot perform
Rejection window
What it decides: Time to say no without breaking coverage
What breaks if missing: Late rejection = OTD already lost
Award record
What it decides: Evidence for pre-pay audit
What breaks if missing: Accounts payable matches against chat
TMS product pages usually list automation, business rules, digital audit, and integration. Use those as a capability checklist. The buying question is different: who runs the tender Monday at 7:40 a.m. when the carrier only replies on WhatsApp?
WhatsApp and paper: useful channel, failed official clock
WhatsApp scales conversation. It does not scale a market. The planner pastes three variants of the same brief, loses timestamps on forwards, and builds the spreadsheet mid-morning while the CEDIS appointment clock is already running.
| Dimension | WhatsApp + Excel / paper | Structured tender |
|---|---|---|
| Time to comparison | 2–6 h on large networks | Minutes (parallel outreach) |
| Serious carriers contacted | 5–12 from fatigue | Dozens depending on network |
| Homogeneous assumptions | Rare | Mandatory template |
| Evidence for accounts payable | Weak / none | Offer + award recorded |
| OTD impact | Late coverage to On Time break | Early coverage protects the appointment |
Loose paper and PDFs have the same hole: the “agreed” rate is not a system object. When the digital tax invoice (CFDI) arrives, nobody can prove the all-in without chat archaeology.
Audit, OTD, and POD: the tender does not end at “yes”
Awarding is the first act. The second is a trip file that survives the journey.
- On-time delivery (OTD) / OTIF: late coverage starts with a slow tender or no backup.
- Proof of delivery (POD): without dock evidence, the award does not close the service cycle.
- Freight audit: the awarded rate is the one you match against the invoice, the POD, and the GPS before you pay.
Operations that audit 100% of freight inflow often see a recovery pattern on the order of 5–7% (calibrate with your sample · not a guarantee). That number does not appear because “the module is auditable”: it appears because rate, evidence, and exception live on the same trip ID.
UniGIS-style module vs finished work
UniGIS describes, on its public Tendering page, publishing routes to carriers so they accept the offer and assign a vehicle; favoring price and service by category; and leaving a record for auditable processes · with benefits of automation, rules, digitalization, and integration. That is module capability. The shipper question is whether the work gets done without another screen to feed.
Publish routes / accept offer / assign vehicle
What it means in the field: Useful if the network already lives in that portal
OCL outcome (finished work): WhatsApp tender where carriers already reply · status written into your systems
Price and category rules
What it means in the field: Configuration inside the TMS
OCL outcome (finished work): Comparison with homogeneous assumptions + operable scorecard
100% auditable process (register)
What it means in the field: Module log
OCL outcome (finished work): Trail that feeds pre-pay audit (same trip ID)
Automation + integration
What it means in the field: API / flows between modules
OCL outcome (finished work): Agents on screens/portals · coexist without day-one migration
Exceptions
What it means in the field: Often left with the TMS operator
OCL outcome (finished work): Ticket with file ready · your team decides
Full field guide: OCL vs Unigis · comparison article. The wedge is not “another tender button”: it is finished work, owned exceptions, and recovery when 100% runs through pre-pay.
Not a public-works RFT or generic procurement
Search results mix three worlds. Separate them before you buy software or copy a purchasing playbook.
RFT / RFP / RFI / government tender
What it describes: Procurement: documentation, evaluation, and long award
What it does NOT solve: The 7:40 a.m. spot toward Monterrey
Open / selective / negotiated tender
What it describes: Procurement typology (purchasing / construction)
What it does NOT solve: Carrier response SLA on WhatsApp
TMS tendering / UniGIS-style
What it describes: Module: publish · accept · assign
What it does NOT solve: Close on the real channel + pre-pay match
Freight tendering (this article)
What it describes: Offer the trip · compare · award with a trail
What it does NOT solve: Replacing human judgment on severe exceptions
OCL assignment agent: tender with a trail
OCL Cargo is an autonomous TMS with agents. The assignment agent does not invent a portal carriers ignore: it offers the trip on WhatsApp like dispatch, consolidates rates, closes with a trail, and writes status where you already operate. Agent glossary: transport assignment agent.
OCL assignment
From chat to trip file
WhatsApp tender
Offer like dispatch
Consolidate
Rates and conditions
Close trail
Who and at what price
Write system
Pilot TMS / ERP
Feed Auditor
Pre-pay anchor
The same trip identifier feeds tower, POD, and the Audit agent. OCL can stamp invoices and Carta Porte when fiscal scope requires it; a typical pilot is 6–8 weeks on a real corridor without turning off your TMS on day one. Order of magnitude ~$50 MXN per shipment when scope fits · validate in a diagnosis.
6–8 week pilot and honesty checklist
Do not measure “modules enabled.” Measure time to comparison, % of awards with a trail, and pre-pay leakage on one corridor.
Elige un paso para ver el detalle
Detalle del paso · 01
Single template
Key takeaways5 points
- Freight tendering = offer the trip, compare under equal assumptions, award with a trail · not a purchasing RFT.
- In Mexico the typical close still lives on WhatsApp: the channel works; chat as the system of record does not.
- Spot and contract use the same rules (template, SLA, scorecard); cadence changes, discipline does not.
- Without a written rate + POD + trip ID, accounts payable pays blind and OTD bleeds from late coverage.
- OCL runs the tender and leaves a file; your team owns exceptions. Module ≠ finished work. Pilot 6–8 weeks · 5–7% pattern.
Is your tender still living in the shift chat?
Related reading
- What freight tendering is
- Transport assignment agent
- Product: assignment agent
- OCL vs Unigis compare
- False digitization and the human bridge
- TMS system guide
- WhatsApp in logistics
- Freight audit
Frequently asked questions
Offering the trip to one or more carriers, comparing offers under the same assumptions, and awarding with a trail. On the Mexico–U.S. corridor it is usually spot (trip by trip) or contract (recurring lane). Sister definition: freight tendering.
No. A request for proposal (RFP), request for information (RFI), or public-works tender is a procurement cycle. Freight tendering is the daily operating act of placing capacity. Conflating them is the classic mistake of generic Experian-style blogs.
Contract covers the baseline on stable lanes. Spot covers peaks, refusals, and urgencies. Both need a template, a response service-level agreement (SLA), and a written rate — only the cadence changes.
It works as a channel. It fails as the system of record: without a forced template, recoverable timestamps, and a scorecard, accounts payable cannot match the invoice to what was awarded. See WhatsApp in logistics.
Late coverage = late unit = on-time delivery (OTD / OTIF) failure. Without proof of delivery (POD) and the rate in the same trip file, the carrier’s “yes” does not survive the handoff to finance.
A module that publishes routes, accepts offers, and assigns vehicles helps if the network already lives in that portal. If the real close happens on WhatsApp and pre-pay audit still samples, the module becomes another screen to feed. Compare on OCL vs Unigis.
It runs the tender where carriers already reply (WhatsApp), consolidates offers, closes with a trail, and writes status into your systems. Your team owns exceptions. It feeds pre-pay audit. Product: /asignador. Typical pilot 6–8 weeks; 5–7% recovery pattern when auditing 100%; ~$50 MXN per shipment order of magnitude when scope fits.