Getting Started
Interface Basics
Printers and Scales
Shipping
Order Processing
Order Allocation
Order Processing Loop
Packing Solutions
Backorders
Ready to Ship
"Unable to Process" Order status
Address Validation and Classification
Packaging Features
Orders
Custom Fields for Orders
Reference Numbers
Other Shipping Options
Packing Instructions
Shipping Accounts
External Shipping Methods
Third Party Billing
Manifest Couriers
Packing Slip Design
Service Levels and Target Ship Dates
Outbound SSCC Barcodes
International Shipping
Tracking Numbers for Offline Shipments
Serial Number Tracking
Receiving
Deliveries (ASNs, RMAs, etc.)
Double-Scan to Begin Count
Auto-Advance to Put-Away After Processing ASN
Actionable Reports
Catalog
Bill of Materials/Work Orders
Bill of Materials
Bill of Materials - Quantity-types
Work Orders
Import Bill of Materials
Virtual Inventory
Regulations
Products
Product Attributes
Lots/Expirations Tracking
Product Velocity
Import Products
Operations
Warehouse
Picking Classes
Picking Batches
Bulk Fulfill Orders
Manifests (Loading)
License Plates
Time Tracking for Administrators
Time Tracking for Staff
Relocations
Import Locations, Lots and Inventory
Rating
Rate Shopping
Rating Maps
Rate Groups and Plans
Fee Schedules and Adjustments
Virtual Shipping Methods
System
Configuration
Merchants and Brands
Warehouses
User Management
User Roles
User Groups
Login via Badge
Protected Customer Data
Enumerations
Technical Contact
Integrations
Shopify
Integrations Overview
Amazon Merchant Fulfillment
Amazon Selling Partner
CartRover
EasyPost
eHub
External Shipping Method API
Freight Club
Magento 1 / OpenMage
Merchant API Users and Roles
SPS Commerce
ShipStream Plugin Fostering Program
Webhooks
WooCommerce
UPS
Scripting
Scripting Basics
Before Create Order Scripts
Preprocess Packing Solution Scripts
Ready to Ship Time Scripts
Picking Class Shipment Matching Scripts
FAQ
How-To: FedEx Production Key Certification
How-To: Brand-Specific Shipping Account
Pattern and Replacement RegEx
ShipStream's Subprocessors
ISO Alpha-2 Country Codes
Printer Troubleshooting
ShipStream Flow
Release Notes
ShipStream Releases
Version 2024.5
Version 2024.4
Version 2024.3
Version 2024.2
Version 2024.1
Version 2024.0
Version 2023.2
Version 2023.1
Version 2023.0
Package Tracking API Migration Guide (2023.0)
Version 2022.2
Version 2022.1
Version 2022.0
Version 2021.6
Version 2021.5
Version 2021.4
Version 2021.3
Version 2021.2
Version 2021.1
Version 2021.0
Version 2020.2
Version 2020.1
Version 2020.0
Version 2019.9
Version 2019.8.1
Version 2019.8
Version 2019.7
Version 2019.6
Version 2019.5
Device Hub Client Updates
Table of Contents
- All Categories
- Operations
- Warehouse
- Location Types
Location Types
Updated by Colin
Location Types allow you to assign labels or "types" to your Locations. ShipStream comes loaded with some default Location Types for you to use, but of course you can establish your own standards for naming your location types based on your needs.
The default Location Types are provided without any Auto-Assignment patterns and listed below:
Name | Pickable | Sort Order |
Default | Yes | 65535 |
Non-Pickable | No | 65535 |
For existing installations before the 2021.4 release the following Location Types will be added as well to replace the previous "Pallet" attribute of locations which has since been removed.
Name | Pickable | Sort Order |
Pickable Pallet | Yes | 10 |
Pickable Shelf | Yes | 20 |
Pallet | No | 30 |
Other | No | 40 |
Pickable
The Pickable designation indicates when creating a Picking Batch that the System will assign pick locations that only include locations that have a Pickable type. This is true unless the Picking Batch uses the option to "Include Non-Pickable Orders", which will allow the System to use non-pickable locations. Therefore, you should ensure that the locations you want your pickers to visit during normal picking operations are assigned to Pickable types and all other locations are assigned to non-Pickable types.
Auto-Assignment
When a new location is created either during put-away, cycle count or relocation, if it did not previously exist it will be created on the fly and assigned a location type automatically. You can also create locations one-by-one or via import and specify the location type with the input data but in some cases, this could be quite tedious. This is where auto-assignment comes in handy!
Auto-Assignment allows you to specify patterns called regular expressions to match the location labels to a location type. When a location's type is set to "Automatic" the system will evaluate each location type in ascending order based on the Sort Order until one matches. If there are no patterns specified for a given type then it will not match any locations automatically, but it can still be assigned to a location manually using the location edit page, the Operations > Warehouse > Locations grid mass action titled "Assign Location Type" or an import file (see Import Locations).
Example
If you wanted all areas of your warehouse to be in a pickable area, but only the bottom three shelves of the racks to be pickable and your locations were labeled as {rack}-{shelf}-{slot}
and the bottom three shelves were "1", "2" and "3" then your location types may be configured like so:
Name | Pickable | Patterns | Sort Order |
Default | Yes |
| 10 |
Non-Pickable | No |
| 20 |
This would match location labels that had any character repeated one or more times (.+
) followed by a literal hyphen (-
) followed by a single "1", "2" or "3" ((1|2|3)
) followed by another literal hyphen (-
) and then any character repeated one or more times again (.+
) to the "Default" location type and all others to the "Non-Pickable" location type.
The result for some sample location labels would be:
Label | Location Type | Why |
A5-1-F | Default | Shelf 1 matches Default pattern |
C4-4-A | Non-Pickable | Shelf 4 does not match Default pattern |
C4-10-D | Non-Pickable | Shelf 10 does not match Default pattern |
SP-2-floor | Default | The "2" appears to be a shelf number so it matches the Default pattern |
Dock2-14 | Non-Pickable | The label does not match the {rack}-{shelf}-{slot} pattern |