Slotting Rules
Slotting Rules let you encode your storage policy once and have ShipStream enforce it at the moment of placement. Without them, a worker can put a product into any open location, and a mis-slotted item — a temperature-sensitive SKU on a dry-storage shelf, an oversized item in a forward-pick bin — is only caught when someone notices. With rules in place, the Scanner checks every put-away and relocation scan against your policy before the mistake is made.
Slotting is built from four pieces: Product Profiles and Handling Classes classify your catalog into labels a rule can refer to, Location Profiles name the sets of locations a rule can point at, and Slotting Rule Sets pair those labels with the location sets they must, must not, or should ideally live in.
Classifying your Products
Products are matched to rules through two kinds of classification, both evaluated automatically in the background as your products and stock change.
Product Profiles
A Product Profile is a reusable flag a product can carry — Fragile, Hazmat, Requires Overbox — and a product can match as many profiles as apply. Manage them at System -> Product -> Product Profiles.
To create one:
- Navigate to System -> Product -> Product Profiles and click Create New Product Profile.
- Fill in the Name and a Code (the code is used by integrations and cannot be changed later).
- Build the matching conditions with the visual condition builder over product attributes — weights and dimensions are unit-aware — or switch to an advanced expression for anything the builder does not cover.
- Click Save.
The grid shows how many products currently match each profile and whether its classification is up to date. Products are reclassified automatically after you change a profile's conditions; the Reclassification column tracks the progress.
Handling Classes
A Handling Class is a mutually exclusive, per-warehouse bucket — Smalls, Team Lift, Fork-Only — where each product lands in at most one class per warehouse. Manage them at System -> Product -> Handling Classes.
Classes are evaluated in the Sort Order you control, and the first class whose conditions match wins, so classification is always predictable. Assign each class to the Warehouses it applies to; the same product can land in different classes at different warehouses.
A product that matches no class at a warehouse stays unclassified there rather than falling into a default bucket, and rules that act on a Handling Class will not apply to it. If you want every product covered, give the last class in the Sort Order conditions that match anything left over. Only enabled simple products are classified — disabled and non-simple products stay unclassified no matter what the classes say.
Defining Rules
Slotting Rule Sets live at System -> Operations -> Slotting Rules. A rule pairs a subject (products, chosen by Merchant, Product Profile, or Handling Class) with a relation and a Location Profile (the named set of locations the relation applies to):
- Require and Forbid are hard rules — a placement that violates them is blocked.
- Prefer and Discourage are weighted suggestions — they warn, but let the operator proceed.
The Location Profile field is required. Pick an existing profile belonging to the rule set's warehouse. Profiles are created and edited on the Location Profiles page, where their membership is defined by Zones, Racks, Location Labels, Slot Types, or Location Tags. A newly created profile builds its location list in the background, and a rule referencing it can be saved once the profile is ready.
Rules are grouped into rule sets that you enable or disable as a unit — a hazmat segregation program, a Q4 seasonal layout — so a whole policy can be turned on for the season and off again without touching individual rules. Each rule set belongs to a single Warehouse.
When you Duplicate a rule set into a different Warehouse, warehouse-specific Zone and Rack criteria cannot carry over — each affected rule is linked to a different, broader Location Profile in the target warehouse, and the copy is saved inactive so you can re-scope the rules before activating.
ShipStream continuously checks your active rules for contradictions — combinations that would leave some products with no valid location at all — and flags the affected rule sets in the Conflict Check column, so you catch an unworkable setup before it reaches the floor.
Enforcement on the Scanner
During Put-Away and Relocation, the Scanner shows the operator the rules that apply to the product in hand and delivers a single verdict when a location is scanned:
- A forbidden location (or one excluded by a Require rule elsewhere) blocks the placement and names the rule that blocked it.
- A discouraged or non-preferred location shows a warning the operator can acknowledge and continue past.
- A location that satisfies a rule continues quietly — no confirmation toast on the quantity counter.
Warehouses with no active rule sets see no change to these flows.
Where Classifications Appear
Read-only Profiles and Handling Class columns — both filterable — are available on the Products, Velocities, and Inventory Holds grids, so you can audit how your catalog is classified without opening each product.