Amazon Repricer - Missing Competitor Information Repricer Error

Printer-friendly version    Send to friend    2 replies
Vick Tran
User offline. Last seen 3 weeks 4 days ago.

I was able to configure the Repricer to work.  However, on about 10% of my inventory, I receive this error.  "Missing Competitor Information Repricer Error"  Is there a current workaround for this error?

SKU "12345" could not be repriced as all shipping prices for competitor products could not be located on Amazon for comparison.

 

0
Your rating: None

Jennifer Cerar
User offline. Last seen 20 hours 34 min ago.
RE: Amazon Repricer - Missing Competitor Information ...

We've been having the same problem. Our repricer is set to look at featured merchants only and when I opened a case this is the response we got from engineering:

"From Engineering, it looks like this is a case where the Featured Merchant scenario doesn't meet our logic's requirement, so a workaround would be removing the "Only compare against Featured Merchants" filter or creating a new rule for select products/categories.

Here's what's going on, directly from Engineering:

"Because the new API does not specify who the featured merchants are we are making our own determination. The featured merchants for this item do not meet our logic, which is why we do not consider them featured merchants and are therefore not included in the results for repricing.

We found that our featured merchant calculation is accurate for most categories and items, and are finetuning it where we can. if this is a problem for this seller's items, perhaps the seller should consider either not using the featured merchant filter for these particular items or setting their own competitive filters."

Not sure if this matches your situation as well, but I'd like more information on this as well if it's out there.

JC

Vick Tran
User offline. Last seen 3 weeks 4 days ago.
RE: Amazon Repricer - Missing Competitor Information ...

Thanks Jennifer,  I had no filters on and will toggle around with that.  One of our team members is working on another workaround.  Ill update if I find anything new.