Creators,
Have you seen the newest Product Launch? It will have you barking with excitement. 😅. Take a look at it here and feel free to share your thoughts with us!
8 Likes
Just to let someone know…the published pet leashes are not showing up in the back end of the store. I think someone else mentioned this in another thread somewhere on the forums.
5 Likes
Thanks @northwestphotos . We’re addressing this now. 😊
3 Likes
Seems like this is happening with all new products that have been introduced lately. Thank you for looking into this.
3 Likes
I mentioned with a few times today. Pet leash product is not showing up in the store management. This is a 1999 problem happening in 2024. 
1 Like
My retractable leash designs also are still not showing in the backend, that I made starting since 10/14. Can only find them via search.
1 Like
product not appearing on my store either, this is Bad, here is mine I created.
Personalize with Your Pet’s Photo | Custom Retractable Pet Leash
1 Like
Hi, any update on this? All of my retractable leashes are still not showing up in my backend since my first one created 10/14, and none showing up from ones I created since then either. Saw other designers are asking the same thing by creating some separate new threads under other forum sections. Thanks
1 Like
5 days gone by…still working on it?
Follow Zazzle on X.com and then post your concerns there as well. The sometimes respond. I think it is a different part of the company, maybe USA based? They have a presence in California and Ireland.
I go to their main X.com page and then click “post” and write my message or plea for help.
They look great with two sided printing!
Hi @FantabulousMerc , the support available here is across multiple continents. The most direct route is via this Community Forum or email. Posting via multiple channels not only wastes resources but causes delays in a resolve too. 😊 We appreciate your patience while we look into all inquiries.
Correct @Colorfulgalshop , it was. There was a back end filtering issue causing this which I think we have now corrected.
Anyone still experiencing this issue, please provide the PID and we can take a look. 😁