Hi, Nick
All you had to do was ask 
It is, actually, quiet simple.
Here are the exact steps to recreate the problem:
1. Create a consolidated DB (like the cons.db, which I sent). Create the table only, not the mobilink server.
2. Create a remote1.db (like a remote1.db, which I sent). Create the table only, not the publication.
3. Create a remote2.db with the same table, but a changed column order.
4. Install mobilink server on the cons.db. Select the remote1.db to be the remote schema.
5. Deploy the resulting sync model on the cons.db. Create a publication and the sync subscription on the remote1.db.
6. Run a schema comparison between the remote1 and remote2 db's. Run the resulting script (minus the column ordering, which would be in comments anyway and the remote id, which has to be null).
Now any row you add to remote1 db will sync correctly, and rows in remote2.db will sync incorrectly.
Regards,
Arcady