It looks like your order posts will have an additional custom field with a slug of 'second-person'. It's not a Types field, but if you insert a Views filter it should still find this custom field if you already have some order posts that have a value for this field, and you can simply create a filter as normal, just like it was a Types field.
I edited an existing product and made up a custom field that I added to that one product – a custom field with a slug of "nigel". (I used the Screen Options tab at the top of the edit page to expose the standard custom fields metabox to add this custom field as a simpler alternative than directly adding the field to the database.)
So now I have one product which has a custom field with a slug of "nigel".
I then created a View and inserted a Query Filter. You can see in the second screenshot that the custom field was immediately available, Views recognised that a product has a 'nigel' custom field.
If you do not see your custom fields available then it likely means that the data is not saved correctly, that if you check in the database you will find that there are no products that have postmeta with keys second-person, dog-field, or affiliation-field.