Offer Management

An offer is a conversation, and today it travels as forms, PDFs and email between systems that cannot speak to each other.

A listing agent and a buyer’s agent are usually on different platforms. An offer is written in one, sent as an attachment and re-entered in another, and a counter returns the same way. Nothing connects the two sides except the people, so the record of what was offered and when remains in an inbox.

The Data Dictionary has nowhere to record it. Of the forty three resources today, none is an offer, and offers appear only as two values on a field about transactions. Each system has therefore defined its own shape, and none of them align.

How It Works

An offer is a thread, not a record. Each turn replies to the one before it. A counter is a new turn, earlier turns stay exactly as they were, and both sides read them in the same order.

The terms never travel in the message. The activity on the wire carries who, when and what it replies to. Price, buyer and financing sit behind a protected link that only an authorized party can open.

Nothing published today changes. Three new resources are proposed and no existing resource is modified.

Documentation

• How It WorksThe thread, the protected payload and what each side records.
• SpecificationRCP-57, as proposed on RESO Transport.
• ToolsThe reference implementation and the artifacts built alongside it.

Playground

A browser playground plays both desks of a negotiation: an offer, a counter, an acceptance or a withdrawal, showing exactly what crosses the network at each turn. Nothing is saved and nothing leaves the page.