Last week, we launched the new battery management feature in hub one. Thank you to the hubs that have already input their inventory of batteries, but we still have some hubs not yet started:
​

Please ensure this is completed ASAP, the next step, the battery count feature, will go live in the near future, and it will not be possible to complete if the inputting of battery inventory step hasn't been started.

This update will provide a new Battery Inventory system directly in HubOne, replacing the current battery counting via Google Forms/Slack.

By tracking every battery and its operational status individually, we’re improving traceability and ensuring no asset gets lost.

Go to Hub One -> Inventory -> Battery Management to access the new system:

Battery not scannable? Create a Zendesk ticket for a damaged battery (form will be updated soon).
​
​👉 Check out all details about the process here!

We’ve identified 2 SKU’s that potentially have a wrong handling unit size in the system. We’re asking all hubs to check the stock of the following products and correct it to the right amount if needed:

If the handling is indeed incorrect, we’re requesting that the hubs with a full box of these products create a Hub Alert ticket, including a photo of the box showing the correct amount, so we can adjust this.

This week's Fruit & Vegetables leaflet is mainly about availability issues. Bad weather has affected almost all European productions, particularly lettuce. See more here Week 9.

To improve how we manage our fleet, we have added a new column to the Vehicle View > Reported Damages section of the Hub Portal. This update identifies the specific individual reporting vehicle damage, allowing for quicker follow-ups if you need more context on a report. This added visibility ensures our reporting system remains accurate and accountable across the team.

​

The data is clear: fewer missed restocking events = faster picking. If your hub processes 250 orders a day, you will save 1 OA hour if your average picking time drops by just 1 second, time that can be used for other tasks in the hub.

Shout-out to the top 20 hubs with the lowest amount of missed restocking events in the last 8 weeks 🚀

For all Hub managers, a recurring placeholder has been added to your calendars. Every Wednesday from 11.00 - 12:00.
​
This is a recurring placeholder designed to centralise and streamline all HM <> HQ communications.

The Goal:

By grouping our calls into this dedicated window, we aim to reduce calendar fragmentation and provide Hub Managers with a predictable schedule for better operational planning and higher meeting attendance.
​

Action Required:

For HMs: Please keep this time slot clear of other commitments whenever possible.

For HQ: We will prioritise scheduling all syncs and updates within this specific window to respect the team’s time on the floor.
​
To avoid confusion. This is not a weekly scheduled meeting; therefore, there is no link to join. If an HQ department wants to schedule a meeting, they will schedule it on top of this placeholder.

Speed in the Hub is the key to faster deliveries. All time saved in preparation goes directly toward shorter fulfilment times, which has a big impact on our customer experience

The Impact

The progress on our average rider preparation time:

Shout-out to the top 20 hubs and especially NL_ZAA_NOOR with a rider preparation time yesterday of only 30 seconds per order!

Shelf Changes

The shelf changes will be posted at 15:00 today and will go live tonight. Please move products to their new locations after closure or tomorrow morning. Don't forget the back stock!

In the shelf change output file, you will now find two additional columns: one showing the number of facings for the product being moved to the new shelf, and another indicating whether the product is stored as an HU. If the cell is blank, it means the product should be stored as an SU.

If you do not find your hub's file in the folders, it means there are no shelf changes for you this week.

For further info please read this article.