Open torvista opened 6 months ago
Hmm, looks like those attribute-stock additions will require a means to use Google's <g:product_group_id>
attribute (https://support.google.com/merchants/answer/6324507?sjid=15274844753760358442-NA).
That's going to require some "thinking".
As far as I can see only the base product is created.
If an attribute stock-handler is in use, attributes will be products in themselves (with their own model/mpn/characteristics),
Having hacked the previous Google Merchant Feed for my own situation, I appreciate that making GPSF flexible enough for all permutations is a world of pain and time and probably not for release 1.
But, how best to implement the scenario where a base product is effectively a place-holder and the attributes are the products (with their own model/mpn/GTIN), without hacking the main code.
I would have thought a decision would be made here https://github.com/lat9/gpsf/blob/e73e3974a3989eb88e59051343a1dc78a6533d92/includes/classes/gpsfFeedGenerator.php#L341-L344 and the next section to be looped per attribute.