Primary key and index column for Merge replication- Id vs GUID
I disagree with some of that advice.  GUID as a clustered PK is ok as long as you use sequential GUID generation, eg NEWSEQUENTIALID().  

Sequential GUID generation, even if only "locally" sequential, mitigates the bulk of the performance problems you will experience with random GUID generation.  The alternative designs end up just needing too many indexes.  

You need GUIDs for distributed key generation, and that's never going to be as efficient as using int, but the uniqueidentifier column is a requirement for Merge Replication.  So your tables can simply be

create table SomeTable(Id uniqueidentifier rowguidcol default newsequentialid(), . . .)