SQL Remote "conflict resolution"

We have a consolidated database with 5 remotes attached. Unfortunately we are getting cases where the consolidated database decides that it knows better and sends transactions to a remote, undoing updates that the remote has just sent.

I can't even say that this is an update conflict. It seems to be a timing issue where the Verify clause on an update from the remote doesn't match what the consolidated has so it sends a correction, and then applies the update as received. The net result is the remote now has incorrect data and the consolidated has the correct picture.

I know we can put triggers on every column of every table (yawn!) but I wouldn't know what to code for this instance. Is there a setting somewhere where the consolidated can be told to accept updates from the remotes and not try to correct them.

Thanks, Paul