Shipping a second template on the same foundation without it reading as a recolour of the first. Buyers compare them side by side in the same marketplace listing.
What I did about it
Kept the architecture and changed the design language — apparel merchandising has different density, imagery and hierarchy needs to furniture, so the component set diverges where it matters and converges where it does not.
Both ship a CHANGELOG, CREDITS and a commercial licence, because a product with support expectations needs a paper trail a client project does not.
What I rejected, and why
Sharing a package between the two templates would have halved the maintenance. Rejected for the same reason as SCM Info: buyers own their copy, and a shared dependency means a fix for one customer's template can regress another's.
It shares an architecture with Megan but not a package, so a fix made in one does not reach the other and both drift. That was deliberate — buyers own their copy — but it means every improvement has to be applied twice.