You are here:  » Correcting EANs

Active Forum Topics


Correcting EANs

Submitted by scoobydoo on Thu, 2014-10-30 14:21 in

Guys,

I just notice some same products (normalised_name) has different EANs coming from the feeds. I know its not the fault of the PT script but Im just wondering is anyone here was able to have some sort of solution for this one, correcting EANs, maybe 3rd party services etc., im not sure.

The reason is as much as possible we want to group products not just by normalised_name but EANs as well. Coz sometime normalised_name is quite ddifferent from each other although they are same products. So we decided EANs but problem is same products but different EANs (vice versa)

TIA

Submitted by support on Fri, 2014-10-31 18:39

Hi,

Grouping really has to be by one field (name) or another (ean) so I think the thing to do would be to decide which, as it sounds, would provide the best matching, which I would imagine would be EAN.

What I would suggest, if you have not already tried it would be the Automatic Product Mapping by UID scripts and see how that performs, and then if it is easily possible to manually identify products that have an incorrect EAN, let me know and I'l describe how to modify Product Mapping so that you can add a custom EAN value for individual products in order to override the incorrect feed value...

Cheers,
David.
--
PriceTapestry.com

Submitted by stevebi on Sat, 2017-09-16 09:15

Hello David,

Is it possible to provide me the way of adding manually part_number values for individual products?

Thank you

Cheers

Steve

Submitted by support on Sat, 2017-09-16 10:15

Hi Steve,

That's documented at Additional custom fields in Product Mapping using the example field `keywords`, so having implemented for `part_number`, for any product you wish to manually assign a part_number simply create a Product Mapping entry for it if not in place already and enter the part_number value in the custom field on the configuration page for the mapping. The Alternatives box can be left empty if that functionality is not required...

(custom fields in Product Mapping are applied at import time)

Cheers,
David.
--
PriceTapestry.com