The latest news and insights from the first and last mile

Page 2 of 7 — 61 articles

Case Study: What carriers can learn from Evri’s returns kiosk network

Evri's use of kiosks provides a great lesson for carriers on expanding PUDO networks and capturing volume in the valuable returns and C2C segments.

2023 report reveals 11% YoY increase in merchants struggling with returns

We explore how the returns market, and merchant perceptions, have changed in the last year.

Watch: Shifting the balance with online returns

Find out how retailers, 3PLs and carriers shift the returns balance.

Why carriers need to provide returns management solutions over reverse logistics

Returns are a massive opportunity for logistics providers to secure growth and new parcel volume by offering returns management solutions.

Should carriers and posts "DIY" their self-service solutions?  

Carriers and posts should invest in self-service solutions. But is building in-house the best option?

Q2 product release highlights – faster deployment and customer journeys

This quarter, we’ve sped up the customer journey and returns deployment time, added sends to the kiosk & deployed container handovers for PUDO stores.

Why carriers should help retailers identify and target problematic returners

Become a more valuable retailer partner and secure volume by solving one of ecommerce’s hardest problems.

Q1 product release highlights – reacting to global customer insights

Find out how we’ve improved our products in Q1 2023.

eCommerce returns: a Doddle roundtable

Our Doddle roundtable looked at real-world returns behaviours and how these could inform carrier strategy.

Sign up for our newsletter to stay on top of the latest industry trends, challenges and solutions.

Required

Doddle needs the contact information you provide to send you our monthly newsletter. You may unsubscribe at any time. Doddle will not sell your information to any 3rd parties. For more information, please review our Privacy Policy.

Wrong value for the component.
Required
Wrong value for the component.Wrong value for the component.Wrong value for the component.
This field is for validation purposes and should be left unchanged.