Products-Feed: Local Inventory feed

[JannikZed]

The Saleor Products Feed should support the creation of an additional feed, that can be used to send inventory information back to google to support the promotion of local in-store pickup.

This issue should be used to plan the feature, discuss it with the core-team and to raise a PR for it.

Relevant documentation from Google: https://support.google.com/merchants/answer/14819809?sjid=853897533693969763-EU

It works in a very similar way than the current feed generation, but it has some other fields. It has one entry per active warehouse.

We need allow the mapping of the [store_code] attribute. By default, we would just use the warehouse name here, but customers might want to overwrite it with a product attribute.

[pickup_method]:
Supported values:
Buy [buy]
Reserve [reserve]
Ship to store [ship to store]
Not supported [not supported]
-> these could be filled automatically / default using the inventory settings of a warehouse in Saleor. Alternatively, we should support setting a global default here and optional customers could overwrite it with attributes

[pickup_sla]:
same day [same day]
next day [next day]
2-day [2-day]
3-day [3-day]
4-day [4-day]
5-day [5-day]
6-day [6-day]
Multi-week [multi-week]
-> this is mandatory and we should support setting a default with the option to allow the overwriting with an attribute value

[local_shipping_label]: set it in the attribute mapping similar to the regular feed.

The saleor app needs to support an additional feed URL

[krzysztofwolski]

@JannikZed Hello! Confirmed with app maintainers we would love to start collaboration on that 💪

Separate feeds

It will require taking in account the App is working on Vercel and feed is generated in a single serveless function invocation - it means processing time limit.
We'll need to check if we can generate feeds for all of the stores same time or safer way will be splitting to separate requests as we do with per-channel feed.

Speaking of channels - since we have to include product availability, some channel mapping might be needed. On the one hand I'm worried about possible amount of generated files (number of stores * channels), on the other decision to suport just a one per shop might limit the functionality. How would it look in your use case?

SLA logic

Would those be stored on Product or Warehouse entity? My intuition would be to define it for Warehouses - "delivery from main warehouse usually takes 3 days". If we would use Product to store it, it would require defining SLA for each store making it possible a long list of attributes.

Implementation plan

Would like to divide this feature into smaller milestones:

• finalize design decisions [we are here]
• Non customizable base: generate feeds per warehouse, basic SLA/Method logic (based on warehouse setting, no attribute overrides). Might be a good idea to keep it non public at this point, before we'll be sure of performance limits. Could be done with allowlist of blessed environments
• Attribute based customization
• Perf + and making it public