Price on Request Still Needs a Clear Workflow
14 February 2026What Should Happen When a Boat Is Sold?
26 February 2026
There is a satisfying moment when a new yacht listing goes live. The specifications have been checked, the description reads well and the team can send the link to a buyer. It is easy to treat that moment as the end of the job.
In practice, the record keeps changing. A specification is corrected. Viewing arrangements change. A description needs clarification. The yacht is withdrawn or sold. The software should make those ordinary changes manageable.
Think in states rather than one publication switch
Preparing information and approving it are separate activities. A draft can contain useful internal work without being ready for buyers. A review state can make the remaining questions visible. Published, withdrawn and sold records may need different behaviour on the website.
| Listing stage | Question for the team |
|---|---|
| Draft | What information is still missing? |
| Review | Who approves the public wording? |
| Published | Which outputs use the approved record? |
| Sold or withdrawn | What does an old link now show? |
These labels are examples. Use the states that reflect the brokerage’s actual decisions and define what each one means. If staff cannot explain the difference between two statuses, the distinction may not deserve a separate button.
Keep the reason for a change understandable
A corrected field tells the team the current value. A suitable record of the change can explain why it changed and who reviewed it. Decide which events are useful to retain, especially where several people maintain the same inventory.
The public page does not need to expose every internal edit. It needs the approved information and the availability wording appropriate for buyers. Keep internal review comments separate from the published description.
Include the last stage in the brief
Sold or withdrawn yachts should be tested before launch, not discovered as an awkward case afterward. Decide whether the page stays visible, how it is labelled and whether it remains in active search results. Internal retention is another decision: the team may still need the historical vessel record.
A listing website and its administration system should support the same agreed lifecycle. Bring a recently changed or withdrawn listing when discussing custom development. It reveals more about ongoing maintenance than a newly published example.