In the Basket - 6th June 2025

Hey sellers 👋 welcome to this week’s issue of In the Basket!

This week, we’re unpacking the recent issues with Etsy’s new delivery profiles feature, and what you need to know and do right now. We’re also looking at how to drive more consistent sales, and whether expanding to other marketplaces is worth your energy.

As always, if you’ve got a win, spotted a weird glitch, or have a burning question, hit reply and share it with us! We love hearing what’s happening in your shop.

Let’s get into it 👇

⏳ Etsy Pauses Processing Profiles After Delivery Glitch

Etsy’s new Processing Profiles feature, which was meant to help sellers set different processing times for listing variations, has had a bumpy launch. Many sellers have reported a glitch which caused some listings to lose estimated delivery and “Ship By” dates, leading to confusion for buyers and extra work for sellers 😩

Etsy has announced via an email yesterday (June 5th) that they’ve now paused the feature and rolled back your processing times to what they were in your shipping profiles as of May 20.

📦 Why it matters

Missing delivery info can hurt buyer trust and mess with your shop’s shipping stats. While Etsy’s fixed the immediate issue, it’s on sellers to double-check settings and prevent ongoing problems.

What to do now

  • Review your Shipping Settings: Make sure your processing times reflect your current workflow.

  • Update if needed: Any changes made after May 20 may have been lost.

  • Communicate with buyers: If orders came in during the glitch, confirm their ship dates directly.

💬 Bottom line
This was a helpful feature, but its rollout has caused real disruption. Until it’s fixed, stick with your shipping profiles, and keep a close eye on any Etsy tool updates, and announcements.

Have thoughts on this one? We’d love to hear your take, pro, con, or somewhere in the middle.

Subscribe to keep reading

This content is free, but you must be subscribed to In the Basket to continue reading.

Already a subscriber?Sign in.Not now