The Re-shopping feature automatically performs an additional scan for a specific shop, to see if its prices have changed since the initial shop.
In cases where the shop price has changed and a price discrepancy no longer exists, you will be able to conclude that the original price discrepancy was most likely caused by systems latency, caching issue, price inconsistency or due to a price update.
Each re-shopped case will now be displayed and accessible next to the original shop data instead of overriding it. That way, both: the original shop data and the re-shopping one will be accessible and comparable with statuses and screenshots, etc.
In addition to the BML lose cases, the automatic re-shopping will also perform for brand.com sold out cases, allocation issues, and brand connectivity issues.
- Re-shopped cases will have re-shopping status icon explaining the updated BML after re-shopping (B,M,L, OTA N/A, Brand N/A).
- The filter was added to include only cases that were re-shopped (as mentioned above)
See screenshot below:
- The re-shopped data information will be available right below to the original shop information to allow easy comparison and investigation (price, BML, screenshots, etc)
See screenshot below:
FornovaDI analyzes the data for customers twice a day:
The first one is set by the customer, and the second time which is normally several hours later, is a re-shop for all the LOSE cases (marked with red) that appeared for the first time.
If the re-shopping icon appeared to be yellow (BEAT) or green (MEET), as in the example:
it can mean that either the issue was fixed or you have the latency issue with this OTA/MSE.
If the re-shopping icon is grey, it means that the Brand.com or the channel we compared it with was unavailable at the time of re-shopping scanning.
Why does re-shopping not influence your DHS:
While in the past we have recalculated the score after the re-shopping process, we now only base the score on the original shop. The reason for this is that the parity issues that appeared on the first scan and are resolved several hours later are still considered an issue. This is because, throughout the period that the prices were not updated it's possible you were losing direct booking and be exposed to BRG claims.
If it is a contracted OTA, the latency issues can be addressed and resolved.