https://issues.redhat.com/browse/SWATCH-2056 is released in prod and it created product tags for 8731 skus.
Maybe its not a bug but, there are 7949 product tags missing even after the nightly sku offering sync. The reason could be there is no matching product config in SWATCH for them or maybe some other reason.
Investigating and determining why it didn't sync is the goal of this card. Should we remove the offerings that don't match our product configuration?

Gabi query to see the difference:

 select count(distinct(o.sku)) from offering o left join sku_product_tag sp on o.sku=sp.sku where sp.sku is null

Done Criteria{}

1. Figure out if all the offerings with no product tag are ones that should not have a product tag due to no mapping product configurations. 
2. Validate what happens today when a new subscription comes in & we don't have a matching product configuration/product-tag. 
3. Based on 2, figure out whether we need to properly handle product configs that don't have a product-tag or how we get things synced up for all accounts when a new product configuration is created. 
4. Document above & review with the team

Notes:

• Document - Did we mess up? If we did, how do we fix it? - Review with the team. 
• Create cards if there is a bug
• If its not a bug then decide on deleting the offerings hat doesn't match our product config
• Since we have product tags for 8731 skus can QE verify in prod if the product tags are returned correctly using api http://localhost:8000/api/rhsm-subscriptions/v1/internal/offerings/<sku>/product_tags
  This will be a blocker before we start using product tags everywhere including https://issues.redhat.com/browse/SWATCH-1840
• What offerings are we currently syncing? All offerings, or just those we have matching product-tags for?
• How does a null product tag on an offering record behave in our code?
• How do we get product tags applied to existing offerings when product configuration is changed?