Last Sold Date Not Updating

Discussion Forums Technical Issues
1

When products are sorted by last sold date, the most recent products sold are from three days ago (5/28/22). My earning report says I’ve had sales since then.  Is anyone else experiencing this?

2

I am. 
I bought something from my own store and it’s not showing in last sold date and didn’t give me any royalty either.

another lady bought something from me-same story 

3

I find that there’s a lag time of up to or sometimes more than a week.  I don’t know why that it is but it’s always been that way.  I don’t know if it has to do with the date that the sale actually gets sent.  It would be good to hear from Admin if that is the case.  I know that notifications of “sales” are according to the date the product is sent so maybe that’s the way it goes with last sold date corresponds to as well.

4

Yep - it’s not updating for me either which is frustrating as I prefer to use that visual view to see what’s been selling. 

5

Same for me…three days ago.

6

Stats have been lagging, but sales and referrals generally don’t, by more than a few minutes or so, at slowest an hour or so…If it’s been some time, it’s likely you didn’t get a royalty. Getting a royalty on your own merchandise can be tricky…. It has to be a published product and you cannot make any changes - not even replacing template text. To also get a referral can be even trickier… you must make sure your browser cookies are clear of any possible 3rd party cookies. 

7

me, too – last day sold showing as 5/28/2022.
in the past, I have seen (and expected) it to take 24 hours to update the Last Date Sold statistics, but not 3 days.

W.H.

8

Same for me

Cover photos also haven’t been updated to the #zazzleinspiration stream or my store’s media page yet since 28th May either  (that could just be mine though)
Perhaps when they do a site update, things will get back to normal? 🙌

9

I prefer to visualize what’s selling also. Going one by one from the earning report is too time-consuming for me.

10

Hi all,

Thanks for flagging this issue. The team are aware and a ticket has been created for the issue. Hopefully we can have a fix soon.