Thanks Joie, I had tried peer-to-peer replication but here all the nodes are available for read-write and conflict resolution is based on peer id.

Merger replication will add an id field in all the tables, since its an application database so cannot take the risk of it (future application/db updates may delete the id field, guessing).

In any way can we change the roles of a database to primary-to-seconday and secondary-to-primary based on time (secondary will be read-only) so that no management or monitoring will be needed for conflict resolution.