Every Tuesday afternoon the newsletter is published here with the latest info for all hubs!
Operations
__________________________________
[GO-LIVE] Mandatory Bike Assignment for Riders đ˛- Thursday 09/28
With Mandatory Bike, each Rider must select a bike within 3 minutes prior to the start of their shift in order to go online and deliver orders.
Please note:
the bike should be selected by the rider, which will be actually used
if 3 minutes are exceeded, the Rider will be set to 'Temporary Offline' automatically
no defective or already assigned bikes will be displayed
the selected bike can be changed at any time during the shift under 'Vehicles'.
Important: Create a damage report for each broken bike immediately
đ¨ď¸Feedback
âšď¸ HubWiki
[INSIGHT] Delivery Outsourcing - 2nd rollout wave of
We start the next wave in the Uber Direct rollout on October 02. The automatic outsourcing of orders will then be available in the following cities.
Hamburg
Cologne
DĂźsseldorf
Leipzig
Hanover
Aachen
Bochum
Bonn
Brunswick
Darmstadt
Dortmund
Dresden
Duisburg
Ludwigshafen on the Rhine
MĂśnchengladbach
Potsdam
Important: Please make sure that one additional handover shelf for external providers (Wolt, UberDirect, etc.) is installed in your hubs until September 30th.
Click here for more information on delivery outsourcing: Newsletter CW 38
Work Safety & Food Control + Architecture & Hub Layouts
__________________________________
[GO-LIVE] New template for instructions/ Drive folder for uploading various documents
The instruction templates have been extended.
You can now also find a template here with instruction topics for the Riders. If you have any questions about this, please post them in the #work-safety-support Slack channel.
From now on you will find your hub folder in the drive.
This is where fire safety assistants, first responders, safety officers and all other credentials will be uploaded, so you can always find them.
In addition, you will find all print templates for your folder and all documents that must be posted.
Workforce Shared Service Center
__________________________________
[INSIGHT] A high number of unsolved tickets in People Services Team
Due to absences and Visa Recollection in the People Services team, we have a high number of unsolved tickets in both queues. We have 1319 cases for People Services.
We expect to be able to solve multiple cases during the week and reduce this number.
We kindly ask you to remind the employees to not open multiple tickets so that their issues can be solved more quickly and to choose the best suitable option in the contact form for faster reply times.
[INSIGHT] Zendesk Numbers
Solved - 2502
Team | Number of Open tickets |
SSC - Workforce Support | 578 |
SSC - People Services | 1319 |
[INSIGHT] Expected delays - Conservative waiting time estimation for Employees
Please note that the weekend is included in all the numbers below:
Team | Conservative waiting time estimation |
SSC - Workforce Support | 33h |
SSC - People Services | 29d 6h |
[INSIGHT] Expected delays - Conservative waiting time estimation for Hub Managers Escalations
Please note that the weekend is included in all the numbers below:
Team | Conservative waiting time estimation |
SSC - Workforce Support | 45.5h |
SSC - People Services | 5.8h |
[1.0 Hubs] Shelf Changes
__________________________________
[ACTION] 1.0 Hubs Shelf Changes
IMPORTANT: The shelf change is valid only for the hubs in the old hub setup.
You can find the shelf changes here.
The changes will go live tonight between 01am and 7am, please reorder the products tonight/ tomorrow morning.
Please feel free to reach out to @space_planning for further questions. Many Thanks!
[2.0 Hubs] Shelf Changes
__________________________________
[ACTION] 2.0 Hubs Shelf Changes
IMPORTANT: The shelf Change is only Valid for the Hubs that are in hub 2.0 setup.
In the google drive folder you will find the G sheet files for all the hubs that are affected in the shelf changing. Please only follow the ones that have exactly the same naming of your hubs and also be careful with following the same hub code while downloading the files.
Please find the file here {LINK}
Some notes on the sheets:
the sheets are, as mentioned above, Hub specific. So only the sheet named with your hub code counts;
"SKU" you can find a the SKU which needs to be moved to another shelf space;
"oldShelf" - 4th column: If the cell is empty, we just assigned this product to your Hub, so please just store it in the shelf mentioned in "new shelf";
"newShelf" - 5th column: If the cell is empty, you can get rid of the product (same process like delisting);
if both "shelf" and "newShelf" have a shelf number, it's a normal shelf change.
The changes will go live tonight between 01 am and 07 am, please reorder the products tonight/ tomorrow morning.
If you have any questions, please contact @space_planning.
Thank you!
[3.0 Hubs] Shelf Changes
__________________________________
[ACTION] 3.0 Hubs Shelf Changes
IMPORTANT: The shelf Change is only Valid for the Hubs that are in hub 3.0 setup.
In the google drive folder you will find the G-sheet files for all the hubs that are affected in the shelf change.
Please only follow the ones that have exactly the same naming of your hubs and also be careful with following the same hub code while downloading the files.
Please find the file here {LINK}
Some notes on the sheets:
The sheets are, as mentioned above, Hub specific. So only the sheet named with your hub code is valid for your hub.
"SKU" you can find a the SKU which needs to be moved to another shelf space;
"shelf" - 3rd column: If the cell is empty, we just assigned this product to your Hub, so please just store it in the shelf mentioned in "new shelf";
"newShelf" - 5th column: If the cell is empty, you can get rid of the product (same process like delisting);
if both "shelf" and "newShelf" have a shelf number, it's a normal shelf change.
The changes will go live tonight between 01 am and 07 am, please reorder the products tonight/ tomorrow morning.
If you have any questions, please contact feel free to reach out to Muhammad Al Zabir Rakin.
Thank you!