(Responded) Avg Price mis-match on share transfer

Product Feedback 🗣️
1

@Dhan , @Anirudha

I recently noticed a sudden drop in profit for one of my holdings, Embassy. When I checked the price chart, everything looked fine - the stock was trending upward. On further investigation, I realized that my average price had suddenly jumped to around 381, which didn’t align with my trade book or the transfer of holdings from Zerodha to Dhan.

After raising this with the support team and explaining why that price wasn’t possible, they acknowledged the issue and corrected my average price back to 353. While I appreciate the fix, this incident raises some serious concerns:

  1. Reliability of Average Price
    The average buy price is a critical metric for investors and traders. It directly influences decisions on profit booking and stop-loss levels. Such a key value should be sacrosanct and not subject to unexplained changes.

  2. Trust in Platform Data
    If core numbers on the UI can change arbitrarily, it undermines investor confidence. Users shouldn’t have to second-guess whether the figures displayed are correct.

  3. Are other holdings Avg price correct
    I just happened to notice Embassy but now I’m not sure if this is the only scrip which had issues :expressionless:

Can you pl help me understand what might have happened here?

2

Hi @erankitjain When one transfers shares from another broker to Dhan (or any other platform) we do not get the avg buy price. We rely on the buy price entered by the user as the same gets highlighted to user as stocks without avg / buy price.

It seems that you may have accidentally entered incorrect price, or just pressed OK without confirmation when the price is entered.

3

@PravinJ ,
The Price I entered were correct as the correct price was being shown for last 1-1.5yrs. This anomaly started recently (atleast I started observing recently), some days I see correct avg price of ~351 and some days it become ~380 something.
Had it been the wrong price since day 1, I would have understand this but if you look at ticket history via chat also, you can see the issue is raised for 380 and later on it got corrected in UI to ~350