Configuration
Control feature visibility and resolve operational defaults across teams, warehouses, merchants, products, and orders.
Configuration controls which ShipOS workflows are visible and how operational defaults are inherited.
Go to ShipOS → Settings → Configuration (opens the Cybership dashboard in a new tab).
How configuration is resolved
ShipOS starts with global defaults, applies the team value, and then applies supported values from more-specific resources.
| Configuration | Resolution order, most specific first |
|---|---|
| Order and fulfillment | Package → Fulfillment Order → Order → Merchant relationship → Team → Defaults |
| Warehouse operations | Warehouse → Team → Defaults |
| Product replenishment | Product → Warehouse → Team → Defaults |
| Team-only settings | Team → Defaults |
An unset value inherits from the next layer. A value explicitly set at a more-specific layer becomes the resolved value for that workflow.
Not every setting is available at every layer. The form shows the layers supported by the selected section and resource.
Select a resource
The Configuration page can navigate between supported:
- Team
- Warehouse
- Merchant relationship
- Order
- Product
Configuration also appears on relevant resource pages:
- Config on an order
- Config on a product
- Configuration while creating or editing a draft order
- Warehouse configuration
- Merchant settings
Use the indicator beside a field to see whether its effective value comes from the current resource, an inherited layer, or the global default.
Feature visibility
The team-level feature section controls whether these workflows appear:
- Bulk Ship
- Gaylords
- Work Orders
- Purchase Orders
- Vendors
- Returns
- Labor
- Automations
- Cycle Count
- Units of Measure
- Scan Forms
- International Shipping
The form labels this group Feature Toggles. Other areas may refer to the same controls as feature visibility.
Turning a feature off hides its navigation and feature-specific permissions where applicable. It does not delete existing records.
The same group also includes Managed Accounts Only. When it is on, Add Member offers only a , which your team owns and signs in with a team-chosen username, and hides email invitations for an , which the person owns. Existing members keep their current account type. See Managed and unmanaged accounts.
Packing
Packing settings include:
- Require Pack Shot
- Show Unfulfilled Items on Packing List
- Show Prices on Packing Slip
Supported merchant, order, fulfillment-order, and package overrides can narrow these defaults. Automations can set supported order values, including packing-slip price visibility.
Fulfillment
Fulfillment settings include supported behavior for:
- Customer fulfillment notifications
- Automatic fulfillment-request acceptance
- Automatic cancellation-request acceptance
- Automatic rejection of unshippable orders
- Tote QA
Use relationship-level or order-level overrides for exceptions instead of changing the team default.
Inventory and Cycle Count
Inventory settings include zero-stock cleanup. Cycle Count settings include:
- Blind Count
- Recount Discrepancy
- Auto Generate Recounts
- Unexpected SKU Recount
Replenishment
Replenishment settings include:
- Minimum, maximum, and increment levels
- Source strategy, including FIFO or FEFO
Product settings override the selected warehouse, which overrides the team. See Replenishment.
Picking
Warehouse picking settings include:
- Order Sorting Strategy
- Pick List Sort
- FEFO Override
- Batch Optimization
- Exclude Single-SKU Orders
- Due Today or Earlier
Order sorting supports priority/oldest, SLA-first, priority/SLA, and oldest-first behavior. Batch optimization can preserve manual selection order or optimize by location, location prefix, or fulfill-by date and priority.
See Picking Sessions.
Rate Shop
The Rate Shop section contains the four-to-six-digit Override PIN used to protect changes from one existing rate strategy to another. A supported warehouse value overrides the team value.
See Rate Shops.
Shipping
The Shipping section includes:
- Incoterm
- EEL/PFC
- Delivery Confirmation
- Insurance Policy
- International contents, declaration, customs, non-delivery, and restriction fields
International fields appear when International Shipping is visible. Leave Incoterm or EEL/PFC unset unless the merchant or shipment requires a specific value.
The resolved shipping configuration is carried to supported order, fulfillment, and label-purchase workflows.
Address verification
When Enable Address Verification is on, ShipOS checks the shipping address of each new or imported order automatically before the order can be ready to ship. You do not need to run anything by hand.
- Address changes: when a shipping address is edited or updated by a sales channel, the previous result is cleared and the new address is checked again.
- Supported addresses: only US addresses are checked. Orders shipping outside the US are not checked and are not held for verification.
- Failed checks: an order whose address fails stays off ready to ship until the address is corrected or someone selects Use unverified address.
- Manual checks: Verify Address on an order or fulfillment order runs the same check immediately. It appears only while this setting is on and the US address is not yet verified, which is useful after a temporary verification error.
Verified addresses are protected from later sales-channel overwrites. Each address checked on an order counts once toward your plan's address verification usage, whether the check was automatic or manual. Rechecking the same address on the same order is not counted again, and checks that fail because of a service error are not counted.
Merchant and order configuration can override the team default; leave the field unset to inherit it.
See Fulfillment Orders.
Billing and Labor
Team and warehouse configuration can expose applicable billing, Labor, scheduling, productivity, alert, and rounding settings. These sections depend on team type, enabled features, and permissions.
See Labor Settings and Rate Cards.
Save changes
- Select the resource you intend to edit.
- Update the required fields.
- Review the inheritance indicator and resolved value.
- Click Save Changes.
Existing operational records may retain values that were already resolved or copied when they were created.