Merge module's don't get executed as they don't get shipped with the installer. They get consumed during the build and merged into an MSI. The CustomActions get listed in the Module*Sequence tables with instructions to merge before or after standard actions.
Other then you have to think a bit more abstract and bulletproof because the module has to work within the context of more then one product MSI, there really isn't anything different.