Price on Request Still Needs a Clear Workflow

“Price on request” is a small phrase on a yacht listing. Behind it, the brokerage still needs a process. A buyer asks, a broker responds and somebody must know which information is approved for that response.

The public wording should be a deliberate publication choice. It should not be the automatic result of an empty price field, unless that is how the business has explicitly designed the workflow.

Separate the public label from the internal record

A listing may need an internal asking-price field, a currency and a public display setting. These are different pieces of information. The team should be able to distinguish an approved price that is not displayed from a price that has not been confirmed.

That distinction prevents an incomplete record from looking finished. It also helps a reviewer understand whether the next task is checking information or approving its publication.

Define the broker’s response

Who receives a price enquiry? Does the listing broker answer directly, or does a coordinator assign it? If the responsible person is away, where does the request go? These questions belong with the enquiry workflow rather than the website’s visual design alone.

Record the response appropriately in the CRM, including the yacht concerned and the next agreed action. The goal is continuity when another team member later speaks to the buyer. Avoid relying on a separate private note as the only record of what was discussed.

Check the documents as well

A PDF brochure should follow its own agreed publication rules. If the website hides a value but the document automatically includes it, the outputs may contradict the intended policy. Specify the fields each template may use and test a price-on-request record.

Also review what happens after the asking price changes. Newly generated documents can use the approved source, while previously downloaded copies remain separate versions.

This is a small example of why listing management, CRM and PDF workflows should be discussed together. A clear phrase on the public page needs an equally clear process inside the team.