Counterparty Execution
Your systems manage what happens inside your company. Counterparty Execution manages what has to happen with everyone outside it. This page is the process itself, step by step, whether the party you are waiting on is a carrier, a receiving location, or a supplier.
The loop
A purchase order, a load tender, a delivery appointment, an invoice. What you are waiting on changes and the five steps do not.
Step 1
The request goes out from your own domain, in the format the other side already works with. For most carriers that is an email a dispatcher can answer from a phone at a truck stop.
Step 2
A confirmation, an objection, or nothing at all. Silence is tracked as an outcome, so a tender sent at 4:02 with no reply by 6:00 is a state with a clock on it, and the clock is one you set.
Step 3
Replies arrive as sentences, because that is how people write them. "Can't make 6am but I can do 7:30" is an objection carrying a counter-offer, and it gets written to the commitment that way.
Step 4
Two carriers accepted and one of them is cheaper. The receiving location wants Thursday and you promised Tuesday. Those go to a person: your coordinator, or the Novari Desk.
Step 5
The commitment ends in a state anyone on your team can look up, with a timestamp and the reply behind it. The test is whether somebody else can answer it when the person who sent it is out.
Across segments
The steps hold their shape across every commitment type Novari runs. What varies is the vocabulary of the reply, how long silence is allowed to run before something happens, and who else is downstream waiting to hear.
Shippers
The tender goes out staged the way your routing guide says. When nobody answers inside your window, it moves to the next preferred carrier on its own, because the truck has to move. What reaches your coordinator is the freight that actually went wrong.
3PLs and brokers
A brokerage runs the same waterfall with a second commitment stacked on top of it. When a load falls over, your customer is the party who has to hear it before the receiver tells them, so both loops close. Novari runs on top of the TMS your floor already uses.
Purchasing · January 2027
The purchase order goes out and the acknowledgment comes back confirmed by SKU, on quantity and on ship date, with that date watched and reconfirmed as it approaches. Purchasing ships in January 2027. Customers who scope it before then hold founding pricing and a call to say what we build first.
Your rules
The five steps are fixed. What moves a commitment from one step to the next is yours to set. Silence is the case people think of first. On a load tender it is effectively a no, since the truck has to move, so the routing guide takes it from there on whatever interval you set. On a purchase order the same quiet can mean your contact is out for a week, or the account changed hands and nobody told you, and rolling to another supplier would be an expensive mistake. The meaning and the interval are both settings, defined per commitment type rather than assumed.
Silence is one rule among several. A tender may not count as covered until the carrier has a signed rate confirmation and current insurance on file. Some customers hold the appointment back until the load has a driver name and a truck number against it. On the purchasing side an acknowledgment usually has to come back with a ship date by line item, because a yes with no date is not an answer. Whatever your team checks by hand today before letting an order proceed is a condition you can write down once and have enforced on every order after that.
Add-ons
Novari Core runs the loop described above. Two add-ons extend it, one at the point where an appointment has to be set and one at the point where a person has to decide something. Both sit on top of a Core subscription and neither is sold on its own.
Appointments
The carrier schedules around you. Once a load is awarded, Novari gathers the receiving location's availability under your name, sets the window against your own constraints, and hands the appointment to the carrier as a property of the load. This is the shipper's appointment desk, not the receiver's portal. Messages go out from your mailbox, and anything headed to a customer's receiving location is drafted for your approval unless you turn that off.
Book a 30-minute callExceptions
Step four hands the exception to a person, and the Desk is the option to have that person be ours instead of yours. It works from your SOPs, and where your rules run out the exception comes back to you. A customer whose own coordinators work those exceptions is running the complete system already.
Scope the DeskThe trial
There is no implementation project in front of this. Connect a mailbox, point it at the carriers and the routing guide you already work from, and send a real commitment today. By Friday each one sits in a state somebody can look up, and you will also know which of your counterparties answer and which ones never do.