Negotiator Agent
Negotiates tail spend, order by order
Limit
Negotiates within the agreed range and approval limit; anything outside it goes to the buyer with the counteroffer ready.
The network, the catalog and the quotation flow belong to ME. UpFlux operates the order that never even goes out to quote: the low-value item repurchased from the catalog, the order issued in a batch, the recurring purchase that goes through without anyone looking at the price.
See also: TOTVS Protheus · UpFlux + SAP Ariba
ME keeps the supplier network and onboarding; the order stays in the ERP.
Each agent has a role, a limit and an audit trail. Anything past the limit goes back to a person, with the case ready.
Negotiates tail spend, order by order
Limit
Negotiates within the agreed range and approval limit; anything outside it goes to the buyer with the counteroffer ready.
Chases suppliers, sends reminders and keeps the process moving
Limit
Follows up on its own in the agreed tone; critical delays go to whoever owns the delivery.
Orders the queue by impact in reais
Limit
Orders the queue; never removes items or changes owners.
Answers “where is my order?”
Limit
Informs; never changes the case or the due date.
Catches prices paid above the reference
Limit
Flags; renegotiating belongs to the buyer or the Negotiator Agent.
A controls scorecard from order to payment
Limit
Flags; handling the deviation belongs to the controls team.
Process mining on the ERP events answers the question nobody has a number for: what fraction of the fragmented spend goes through quotation with enough responses, and what fraction is issued directly. The overlap with the platform is measured, not assumed.
For the item that comes back every month, the agent compares the current price with the recent floor in the company's own history and negotiates the difference within the approval limit. New suppliers, critical items and prices outside the tolerance still go to the buyer.
Expediting, chasing and invoice mismatches become the digital team's work. The buyer uses the platform for what it does well and stops spending the day on follow-up.
When the company exports the quotation event with the proposals received, savings can be measured against the lowest proposal recorded on a platform that is not ours. It is the hardest baseline to dispute there is.
The critical path does not depend on the platform opening an API. The connection starts in the ERP, where the order ends up, and the quotation data comes in when the company exports it.
Protheus and Datasul through the standard routines and the TOTVS Store; SAP through the ERP's own standard interfaces. No parallel platform and no data migration.
From the event export, we deliver the map of the real process and the target in hard currency: variants, bottlenecks and addressable return.
The first agent starts on the recurring low-value item, within the approval limits that already exist, with the savings baseline agreed before the first order.
Questions from teams that already use an e-procurement platform and want to know what to do with the tail.
In two weeks we show, with the events from your ERP, how much of the fragmented spend goes out to quote and how much is repurchased at the catalog price.
Talk to UpFlux