How to pack your Slimbook to send it to our RMA service

If you need to send your Slimbook to our technical service, either to process a warranty claim, a return, or simply because you want to make a voluntary change, it is important to consider the following points when packaging it:

PACKAGE YOUR SLIMBOOK AS FOLLOWS:

For exchanges or returns, it is necessary to use the original box and all its accessories. Do not include mice, briefcases, or other accessories that do not fit in the original box.

1. For repairs or warranties, it is recommended to use the original packaging, but it is not mandatory. You can use any other box as long as the equipment is well protected during transportation, especially if it is international.

2. Fill out the PDF form provided by our support team and make sure to print both sheets.


3. Once both sheets are printed, place the filled-out sheet between the keyboard and the screen of your laptop.


4. It is advisable to place some cushioning material, such as bubble wrap or cork, between the original Slimbook box (if possible) and the outer box to protect it from possible impacts during transportation.

5. Carefully seal the box to prevent it from opening during transportation.

6. Once you have properly packaged your Slimbook securely, attach the sheet containing only the RMA number and the date to an external and visible part of the box.

Shipping conditions for acceptance to process products under warranty:

- If you decide to send the package on your own, we recommend that you insure it. Slimbook will not be responsible for damaged equipment during shipping, even if it is within the warranty period. If upon receipt of the product, damages due to poor packaging are evident, it will be returned and will be outside the warranty.

- Before proceeding, the product will be inspected to verify that it has not been tampered with, misused, or suffered direct damage such as impacts, breakages, or scratches.


How to pack your Slimbook to send it to our RMA service
Eusebio Giner Slimbook
12 February, 2016
share
archive