It seems that your structural needs would be best solved with creating a separate Content Type for each of the combination of data that can meaningfully stand independently on its own.
Company seems to be one, you'll probably need one CT for Companies.
If Product type info always comes together in one whole then it makes sense to create a CT for Product. But if different product info are independent then they should be just fields in your "global", "combination" Content Type.
That last CT should reference a Company through an Entity Reference field and include other text fields for your Product data, or one ER field if Product is an independent CT.
With the help of Inline Entity Form module you can make the Company nodes automatically when creating your global node, if you need that feature, but sort out your structure before you play with this.
You can use Paragraphs module to rearrange references to other CTs in your global CT, so they are different in each node, but it doesn't seem that you need that, or the Layout builder module to override layout for each global node.
You need to be able to pick new combinations from existing data then it makes sense to create Content Types and Taxonomy Vocabularies and terms, and then create the final Content Type that references those CTs and Taxonomies.
There are various options available on how to display the referenced data on the final CT pages.
I don't think you need to learn about Views to solve this problem. But the concept of Content types and Taxonomies is the basis for Drupal and web dev Information Architecture in general. You can find tutorials about those basics online, Drupal specifically so I expect you can easily solve your problem with these instructions after you learn the basics.