Skip to content
Kyle Rivelli.

Work

API integrations and data sync · Live · since August 2026

Rate overrides and the margin floor.

Every rate in the platform flows through one chokepoint: a hand-set override beats the percentage rules, and no rung of the ladder can book a loss.

Livepure pricing moduleeditable settingstests
gategateledger

The problem

Three programs priced three ways, plus loads the owner wanted priced by hand, plus a negotiation ladder that could in theory walk past the sell rate. Rate logic was spread across eight call sites.

How it works

  • One function decides the rate for a shipment: a per-load override wins, then the program's rule. All eight call sites were pointed at it, so a rate can only be wrong in one place.
  • The negotiation ladder got a margin floor: a maximum percentage of the sell rate that binds every rung. A binding cap spreads the rungs instead of flattening them, so the bot still negotiates, just inside the line.
  • In October the rule tightened: the bot never pays over 96 percent of sell, overrides included. The lookups show a loss-load banner so everyone on the desk sees it, with no name attached.

// one chokepoint for every rate; the bot's ceiling is 96 percent of sell, no exceptions

The result

Rates stopped disagreeing with each other, the owner edits percentages in the UI, and a loss can no longer be booked by a robot.

Your version of this exists.

Different industry, same shape: a repetitive workflow, a fragile spreadsheet, an inbox someone babysits. Tell me what the manual work looks like and I can usually name the first build in one conversation.