Set transactional replication to overwrite on conflict

I have basic transactional replication setup (no subscriber updates) for a few key tables from production to non-production environments.  Sometimes data for one of these tables that was tested in non-production is not removed when it goes to production, resulting in a conflict that breaks replication and forces a DBA to manually remove the data.  How can I set replication to automatically overwrite data on conflicts?  The @conflict_policy of sp_addpublication seemed promising, but apparently only applies to subscriber update publications.