We need to map an attribute to the BC default price. For non-matrix items we can do that. When syncing the template does the process use the Stock Item mapping or does not sync use the template mapping and uses the stock item data?
Best answer by smarenichView original
@dgodsill97 the Template Item sync uses its own mapping. So if you map an attribute in the Stock Item entity, it won’t be used during the template item sync.
Hope it answers your question.
Is the the default price from the template or for each matrix stock item?
If we add a user field for catalog price are ItemSettings from each of the matrix stock items or the template?
Source field is right, as it comes from the Matrix item, but the Target Object is not right, as it should be the Variant, not the product. I checked and we don’t have variant in the mapping, as it will require many to many mapping, which is not yet implemented.
As a workaround I suggest you to look at the Sales Prices sync using Prices Entity here
It should do what you need.
They would like the price in BC to be the stock based price for one store and the customer group price in the other store.
Customer Group price sync is supported using Price List entity.
Related to stock based price, it may be something that is not supported.
Base Sales Price does not synch matrix items (Acu Case 241363). I am not sure of Price List because I have not tested that.