The latest news and insights from the first and last mile

Page 3 of 7 — 62 articles

eCommerce returns: a Doddle roundtable

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

Why ASOS might start charging for returns, and what that means

ASOS increased the minimum spend for next-day delivery for its Premier subscribers - are returns next?

Two opportunities for carriers to improve customer retention

To retain customers, carriers need to solve key issues merchants are facing: high return rates and reduced consumer spending.

Espresso returns - the future of parcel drop-off

Self-Service Kiosks open up new possibilities for returns and sends to be dropped off in coffee shops, gyms, fast food chains and more.

Why Retailers Need Ecommerce Returns to Recover In-Store Revenue

Automating in-store returns with kiosks will increase footfall and revenue, without disrupting staff.

The top 3 insights from WMX Asia

Our key takeaways from three days of speeches, discussions and brainstorming with leading regional and global carriers.

Why 3PLs are uniquely positioned to lead returns

Retailers have a returns problem. 3PLs should take the lead as the only providers able to supply full end-to-end solutions.

What 3PLs can learn about returns following GXO’s acquisition of Clipper

GXO holds a powerful position against its 3PL competition to offer end-to-end services to address the retail returns crisis.

How one UK omnichannel retailer is leading the way on returns

Next proposes keeping 195 loss-making stores open to better service ecommerce demand and power a truly omnichannel 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.