The latest news and insights from the first and last mile

Page 1 of 4 — 35 articles

Lessons from a decade in the first and last mile

A decade as Doddle taught us some lessons - and Blue Yonder helps us see what will matter in the next decade.

Parcel lockers vs parcel kiosks: which is best for parcel drop-off?

We explore the benefits and drawbacks of parcel lockers and kiosks to help decide the best self-service solutions.

What do out-of-home networks look like in the UK?

We dive into the biggest logistics operators and their current OOH networks in the UK

4 ways that C2C commerce is transforming the last mile

As consumers adopt recommerce, out-of-home networks are having to adapt to increased demand.

What consumers think about parcel lockers and how carriers can encourage adoption

Parcel lockers offer carriers automation, consolidation and increased efficiency. But what do consumers really think about them?

InPost's Changed PUDO Strategy

InPost has launched a UK PUDO network, highlighting its new attitude to PUDO as part of its expansion plans.

2023 ecommerce heads towards optimisation of returns and delivery

2023 has seen small adjustments to delivery & returns - driving a major shift in the ecommerce business model from growth to profitability.

How we design for consumer behaviour change

We build psychological insights into our product design processes - here's how it drives better outcomes for consumer, carrier and merchant.

Regulation is coming for European ecommerce logistics

European postal operators and carriers need a plan to deal with increasing last-mile regulation.

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.