Negotiation playbook.
Where the money is, who to negotiate with, what to ask for.
Product
Routor reproduces your operation transaction by transaction and returns the decision in the format your operation consumes: rules, playbooks, policy and counter-proof. It is not a report.
How we think
Your operation carries three active freight decisions at once. Each cuts across cost, revenue and experience. Each tends to live in a different place: contract, system, checkout. Routor puts all three under the same layer.
Which carriers you contract, in which ranges, with what service. The decision ships as a negotiation playbook and bid pack, benchmarked against your real operation.
Which carrier moves each order, weighing cost, contracted lead time and quality. The decision ships as executable rules, ready for your system.
Free-shipping threshold, regional offer, price tier by ticket size. The decision ships as a redesigned policy with explicit, testable assumptions.
Outputs
You do not get a report. You get the output in the format that goes into the next contract meeting, the routing system, the checkout. All with the audit trail procurement and compliance ask for.
Where the money is, who to negotiate with, what to ask for.
Per-order routing criteria, ready for your systems.
Thresholds, lead times and regional offers, with explicit and testable assumptions.
What each shipment should have cost, recalculated independently, against what was actually charged. You stop validating the carrier's invoice in the dark.
Application
You walk into the next rate-table round with an anchor proposal calibrated to your real operation, not to market averages. The carrier sees numbers they issued themselves. The conversation becomes engineering.
Instead of keeping five-year-old rules, you publish new ones in the format your TMS or your own engine consumes. Table changed? Recalculate. Rule changed? Versioned and auditable.
Regional thresholds, offers by ticket band, channel pricing. You simulate before publishing; ship with testable assumptions and a revision calendar.
Independent recalculation of what each shipment should have cost. If the carrier invoice diverges, you know where, on how many orders, on which lane. Negotiating in the dark ends here.
Category
TMS executes. Once you have picked the carrier, the rule and the rate table, it ensures the order goes out, tracking arrives and the invoice closes. Routor operates one layer above: it helps you reach that choice. The two coexist without overlapping.
BI observes. It shows what happened, with which carriers, in which regions. Useful for history, insufficient for prospective decisions (the future is not a regression of the past). Routor simulates order by order, combining real rate tables, candidate rules and demand history.
Integrations
Routor consumes what you already have: carrier rate tables in spreadsheet or PDF, order history via export from your ERP or TMS, current rules via document or system. It returns the output in the format that goes to the right place.
Rate tables, history, current rules. Spreadsheet, CSV, API, structured PDF. Onboarding handles normalisation.
Carrier mix rules in JSON for your routing engine. Policy in a format your checkout consumes. Playbook in PDF for the contract table.
Every decision with a version, recorded assumption and approver. Procurement and compliance get what they need.
In production
No long-term commitment. You send rate tables and history, you get the real operational picture in hours and decide the next step with data on the table.
I want the diagnostic