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 | 219788508 | Release Date | 2026/05/03 | List Price | $62.00 | Model Number | 219788508 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
Minimalist and functional, our Weekday tote bag is thoughtfully designed with ample space for everyday essentials. Inside, a padded laptop pocket will keep valuables protected and a mesh waterbottle pocket is very handy. It's versatile, too: carry it by hand or over the shoulder.
| UPC | 061643130691 |
|---|---|
| size | Medium |
| Brand | Hunter |
| Color | Other Black |
| Pattern | Solid |
| Seasons | Fall |
| Capacity | 6.16 Liters |
| Item Shape | Rectangular |
| Model Name | Weekday Tote Bag |
| Strap Type | Top Handles and Shoulder Straps |
| Style Name | Weekday |
| Fabric Type | RECYCLED NYLON 85%, POLYESTER 5%, NYLON 5%, Silica |
| Handle Type | Top Handles, Shoulder Straps |
| Item Weight | 25.75 Ounces |
| Closure Type | Zipper |
| Manufacturer | Hunter Handbags |
| Style Number | 13891094 |
| Occasion Type | Casual |
| Inner Material | Polyester |
| Item Type Name | Tote Bag |
| Outer Material | Nylon |
| Item Dimensions | 22.44 x 1.18 x 14.17 inches |
| Material Fabric | Nylon |
| Number of Items | 1 |
| Target Audience | Unisex-Adults |
| Material Features | Recycled |
| Number Of Pockets | 2 |
| Number of Handles | 2 |
| Handbag Silhouette | Satchel |
| Lining Description | Polyester |
| Number of Sections | 2 |
| Age Range Description | Adult |
| Fit to Size Sentiment | Neutral |
| Apparel Fabric Stretch | No Stretch |
| Number of Compartments | 1 |
| Manufacturer Part Number | 13891094 |
| Product Care Instructions | Hand wash only. Avoid bleach. Do not iron. Do not dry clean. Store in a cool, dry place. |
| Zippered Compartment Count | 1 |
| Apparel Fabric Weight Class | Lightweight |
| Compatible Device Size Maximum | 22.4 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