Apps in this category may contain mild or occasional cartoon, fantasy or real-life violence, as well as occasional or mild adult, sexually suggestive or horrifying content and may not be suitable for children under 9 years of age.

12+

Apps in this category may contain occasional mild indecent language, frequent or intense cartoon or real-life violence, minor or occasional adult or sexually suggestive material, and simulated gambling, and may be for children under 12 years of age.

17+

You must be at least 17 years old to access this App.

Apps in this category may contain frequent and intense offensive language; Frequent and intense cartoon, fantasy or realistic violence: frequent and intense adult, scary and sexually suggestive subjects: as well as sexual content, nudity, tobacco, alcohol and drugs, may not be suitable for children under 17 years of age.

Earnings by Zazzle Captures d'écran

iPad

iPhone

About Earnings by Zazzle

Hey Zazzle Designers!

If you have a store on Zazzle, you can view your Earnings, Royalties, and Bonuses using our new Earnings App. In the future, you can expect this app to be the place to manage your Zazzle Store, Communicate with Customers, and get news from Zazzle HQ. Stay tuned!

We would love to hear your feedback! Shoot us a note at mobile@zazzle.com or request your features at https://forum.zazzle.com

Quoi de neuf dans la dernière version 2.2

Last updated on Nov 27, 2019

Vieilles Versions

Bug fixes.

Version History

2.2

Nov 27, 2019

Bug fixes.

2.1

Jul 9, 2019

Bug fixes.

2.0

May 8, 2019

Behind the scenes updates!

1.0.1

Jun 28, 2017

Hi Zazzle Designers! Remember that "Open Product" button that you used and loved? Well, it was broken in Earnings v1.0. SORRY about that!

With Earnings v1.0.1, we fixed that Open Product button so you can see the products users have ordered. When you tap on that button, now we will either deep-link you to that page in the Zazzle app (if you have it installed) or open the webpage on your mobile browser.

Thanks for your patience as we fixed this issue!

1.0

May 29, 2017

Feedback Report