Sort of. Original requirement is only for updating branding info for entitlements for currently installed products. 

The tricky part for doing it on product cert install is we have to check branding for all installed entitlement certs, and ideally, just the installed valid entitlement certs, which means doing status and compliance updating, which
the product id install code paths currently do not do (since it requires candlepin connections, and since that code path is hit from the yum plugin). 

We could trigger it sans the compliance status though, the client side checks for it are relatively quick (at least compared to anything making REST API calls), it could potentially include old/bogus/expired ent certs though, which could potentially have valid branding info.