For sellers
Settings keep channel promises, documents, and order handling consistent as SKUs and marketplaces grow.
Settings · Identity
Company profile defaults that ripple through labels, slips, and APIs
Legal entity, taxation hints, locales, outbound sender strings—baseline metadata cascades to packing slips printers and partner paperwork so rebrands do not chase thirty templates.
Operational signals
- Locale disciplineTime zones affecting cut-offs stay tied to HQ facts—fewer heroic ops patches during DST chaos.
- White-label cohesion3PL tenants inherit master branding rules while honoring per-seller supplements.
- Integration payloadsWebhooks/API consumers receive consistent identifiers because org metadata is normalized once.
Often edited alongside Team permissions onboarding new jurisdictions.
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.