Conditional writes
Itineraries, zones, collections, and the other resources you edit carry an etag. Send it back as If-Match, and the write lands only if nobody changed the resource since you read it. Otherwise it is refused with 412 Precondition Failed, and nothing changes.
The samples below create a collection, update it under its tag, then try the old tag again. They need a session token minted for a member, as act as a member shows.
Response to the stale write
On a 412, read the resource again, decide whether your change still applies, and send it with the new tag. The ETag header of the refusal names the current version. Leave out If-Match, and the last write wins.