redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 217197697 | Release Date | 2026/04/19 | List Price | $8.80 | Model Number | 217197697 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
This wireless charging case replacement is designed specifically for AirPod Pro 1st and 2nd Generation earphones, offering a convenient solution to keep your earbuds powered and protected. The sleek white hard shell case features both wireless and wired charging capabilities, giving you flexible options whether you're at home or on the go. With Bluetooth pairing functionality, this charging case seamlessly connects to your device and displays battery status through a 3-way battery indicator, so you'll always know when it's time to recharge. The compact design measures approximately 2 inches in length, 1 inch in width, and 1.5 inches in height, making it perfectly portable for daily use. The case provides secure storage compartments for both earbuds while charging, and the convenient LED indicator light keeps you informed of charging status. Compatible with standard wireless charging pads and USB-C wired charging, this replacement case ensures your AirPod Pro earphones are always ready when you need them.
| UPC | 740625724072 |
|---|---|
| Brand | MEEPZ |
| Color | White |
| Theme | Bluetooth, Modern, Portable Electronics, Tech, Wireless Charging |
| Pattern | Solid |
| Shell Type | Hard |
| Form Factor | Case |
| Item Weight | 0.2 Pounds |
| Manufacturer | MEEPZ |
| BuiltIn Media | 1 |
| Item Dimensions | 2 x 1 x 1.5 inches |
| Compatible Devices | Headphones |
| Enclosure Material | Silicone |
| Additional Features | Wireless Charging Compatible |
| Warranty Description | 1 |
| Water Resistance Level | Moisture Resistant |
| Compatible Phone Models | Airpod Pro 1st Generation, Airpod Pro 2nd Generation |
| Compatible Device Size Maximum | 2 Inches |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form