Have you include Episerver.Find.Commerce via nuget?  Normally this should add what you need for the automated Find indexing.

Episerver.Find.Commerce is installed via nuget. 

Also EPiServer.Commerce.FindSearchProvider should be added.

Check in the Mediachase.Search.config that the Find Search Provider is the one being used

Episerver.Find.Commerce is the "real" find integration, working the same way as with pages and blocks. It works entirely with the typed content models, so you need to have typed models with properties corresponding to your meta fields for them to get indexed. 

@Janaka: No, you either need Find.Commerce, or FindSearchProvider. You don't have to have both of them. 

I'm a bit too busy to write an explaination, but you can find more information here http://vimvq1987.com/2017/03/find-commerce-not-commerce-manager/

Hi Quan Mai,

The official documentation states to use either or both? If that's not the case then this should be updated.
https://world.episerver.com/documentation/developer-guides/find/Integration/episerver-commerce/

I would agree only find.commerce is really needed as most projects don't utilise the commerce manager search indexing approach that much these days.

However as Par has already said that's installed but not working.  Perhaps it's more to do with Magnus's suggestion on creating typed classes?

The documentation says that "You can use the integration package, the Find.Commerce package, or both. The integration package uses Find as a search provider in Commerce manager and the ECF search APIs.", which is correct. You can use Find.Commerce for front-end and FindSearchProvider for Commerce Manager. However there is no such requirement to have to install both. 

Regarding the original problem, I think Magnus's answer is correct. Find can only index the strongly typed types. If you don't have strongly typed types for your metaclasses, then only base classes (ProductContent, VariationContent, etc.) are indexed. 

Hi,

It seems that Magnus is correct. We have typed models but there is no property that is mapped to meta fields. I am guessing someone was cutting corners when doing an upgrade from CMS 6.

It works perfectly when I am adding property’s to the typed models.

Thanks guys for a quick response