For sellers
Settings keep channel promises, documents, and order handling consistent as SKUs and marketplaces grow.
Settings · Waves
Batch grouping gates that protect SLAs without micromanaging pickers
Express which channels mingle, freeze problematic SKUs apart, honour carrier pickups, or cap units per tray—logic sits upstream of walking routes.
Operational signals
- Carrier cutoffs baked inStop mixing late-deadline express lines with leisurely economy waves.
- Inventory realityRespect ATS across locations before you promise a homogeneous batch footprint.
- Readable defaultsOps groks why a grouping exists because rules map to commerce attributes, not obscure SQL.
Bulk processing inherits the cohorts batches shape first.
Why teams configure it
Settings are where repeatable operations become policy
The right settings reduce exceptions for sellers, warehouse teams, and support because everyday decisions are encoded before the rush starts.
Turn habits into repeatable rules
Fewer one-off decisions
Give teams the right defaults from day one
Cleaner onboarding
Keep permissions, labels, and workflows aligned
Better control
Prevent avoidable mistakes before orders move
Less rework
Workflow fit
Why this matters for sellers and fulfillment centers
For fulfillment centers
Defaults and permissions help teams execute the same way across sellers, shifts, and workstations.
For managers
Policies become visible in the platform instead of living in chat threads or local spreadsheets.
Ready to turn operational rules into defaults?
Configure ChannelDock once, then let the right settings guide daily work across channels and teams.