# Vendor negotiations recorded. Terms remembered.

> How a procurement team stopped arguing with suppliers about what was agreed by letting the recording answer for them.

Canonical: https://erp-ai.ireadcustomer.com/products/solutions/procurement
Published: 2026-05-02
Role: Head of Procurement
Industry: Retail

## What changed

- **Vendor disputes opened**: −91%
- **Terms compliance**: +47%
- **Quote-to-PO cycle**: −35%
- **Vendor records kept current**: +220%

## What changes when this team adopts iReadCustomer

- **Every supplier call becomes a record** — Voice Summary captures the agreed price, MOQ, lead time, payment terms, and freight assumption — written into the supplier record automatically.
- **Disputes settled by the recording** — When a supplier challenges a term, the team opens the recording — not the inbox. What took days takes a few minutes.
- **Vendor scorecards that update themselves** — Compliance against agreed terms is computed continuously from the recorded ledger — no quarterly survey, no scoring meeting.
- **Hand-overs to new buyers in one read** — The supplier history reads like a short article: this is what was agreed last quarter, this is what changed, this is what is still open.

## Story

The job description for a procurement manager has the word
"remember" in it more often than any other. Remember the discount.
Remember the lead time. Remember that the supplier said they would
absorb the freight on the second order. The job is unfair to memory
alone.

## What changed

Every supplier call — quotes, escalations, payment terms — went
through Voice Summary. The fields the team most cared about (price,
MOQ, lead time, payment terms, freight) were written into the
supplier record. The record became the source of truth, not the
email thread.

> Supplier disputes used to be 'he said, she said.' Now they are 'open the recording.'

## What stayed the same

The supplier list. The PO format. The accounting integration. The
team's biggest fear was that we would replace their familiar PO
template — we did not. We added a layer that reads what was said
and writes it next to the PO.

## What we left out

A bot that negotiates for you. Tempting; we declined. A Thai
supplier relationship is built on tone of voice, not on a chatbot.
The recording captures the tone for next time. The negotiation
stays human.

## Modules in this story

- [Voice Summary](https://erp-ai.ireadcustomer.com/products/voice_summary.md): Record once. Search the spoken word forever.
- [CRM](https://erp-ai.ireadcustomer.com/products/crm.md): Customers as a first-class object, not a row in a spreadsheet.
- [AI Chat Summary](https://erp-ai.ireadcustomer.com/products/ai_chat.md): LINE conversations become a clean ledger of what was actually agreed.

## Frequently asked

### What if a supplier prefers email?

Email threads are read the same way as chat. The recording layer is additive — written-only suppliers still get summarised, just from text.

### Can suppliers see what we recorded?

Configurable. Most teams keep recordings internal; some share the structured summary (price, terms) with the supplier as a confirmation step.

### Does this replace our PO system?

No. POs flow through the existing tool. The recording adds a layer of context that travels with the PO into accounting.