Insight / Blog

Doddle News – NRF2019

Posted on 25th January 2019

NRF is always a calendar highlight but was particularly exciting for us this year as we announced our US launch at the New York based retail show.

Our launch will see US retailers and carriers able to invest in our full technology suite from click & collect and returns software and pick and ship from store software through to physical in-store pick up and returns infrastructure solutions that help drive valuable footfall into stores.

Speaking at NRF, our CEO Tim Robinson explained: ‘We want to create a better retail ecosystem.  Through our tech and partners we enable each stakeholder in the retail space – from brands to logistics providers to customers – to get a better experience in an increasingly complex and challenging landscape.’

With our new US Manager, Dan Nevin, in place, a huge consumer appetite to tap into (70% of US shoppers used click & collect in the last six months) and a number of exciting partner talks already in advanced stages, it looks like the expansion stateside is going to be an exciting one. Watch this space…

Related articles

Important lessons from Leaders in Logistics 2024

Leaders in Logistics 24 dived into AI & automation, sustainability, changing ecommerce behaviours, emerging consumer expectations & predicted what the next decade had in store.

Postal results, reforms, and returns

Posts around the world are seeking reform, but how can they drive improved results in the short term?

5 Changes We Predict in eCommerce Delivery & Returns in 2024

Our predictions for 2024 in ecommerce delivery and returns, plus a roundup of our 2023 predictions.

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


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.
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.