Skip to content

Configure Carriers, Origins, and Related Settings

Carriers, origin addresses, stores, filters, rules, templates, and automations: the CLI entry points and where the web app takes over.

Updated September 3, 20261 min readPostsale CLI

Orders need carriers, ship-from addresses, and optional rules before labels flow smoothly. This article orients you to the configuration surfaces available in the CLI.

In this article, we will list the main configuration groups, call out destructive actions, and point you to doctor for health checks.

Before We Begin

This article assumes that:

  • You are authenticated
  • For product UI walkthroughs of the same concepts, see postsale.com/help (Carrier Settings, origin addresses, automation). Here we map the CLI entry points.

Where each setting lives

text
Account
  ├── Carriers
  ├── Origin addresses
  ├── Stores (read-only)
  ├── Filters (saved server-side searches)
  ├── Shipping rules
  ├── Templates
  ├── Automation (workflows and webhooks)
  └── Manifest (end-of-day)

Always confirm flags with postsale <group> --help and postsale schema <slug> when a slug exists.

First-time setup path

Here's how to get from an empty carrier list to a doctor report with no failed checks:

  1. Sign in (Auth).
  2. Validate carrier credentials without saving: postsale carriers validate --input ...
  3. Add the carrier: postsale carriers add --input ...
  4. Create an origin (ship-from) address: postsale origin-addresses create --input ...
  5. Run postsale doctor --human until carriers and origins look healthy.

In the web app, the same concepts live under Carrier Settings and origin address screens. Product help: postsale.com/help.

Carriers

bash
postsale carriers list
postsale carriers validate --input ...
postsale carriers add|update --input ...
postsale carriers delete <id> --yes

Sensitive fields are redacted unless you pass --include-sensitive.

Origin addresses

bash
postsale origin-addresses list
postsale origin-addresses create|update --input ...
postsale origin-addresses delete <id> --yes

Stores

bash
postsale stores list

Read-only in this release. Credentials redacted by default.

Filters, rules, templates, automation

bash
postsale filters list
postsale shipping-rules list
postsale templates list
postsale automation workflows list
postsale automation webhooks list

Creates and updates accept --input / --json where documented. Deletes require --yes.

Note

Automation workflows, webhooks and templates need a login session. On an API key they answer api_key_unsupported (exit 100) whatever permissions the key has. See Use an API key.

Note

Filter create/update still run under postsale run --dry-run (not intercepted).

Manifest

bash
postsale manifest list ...
postsale manifest close ... --yes

Close is destructive. See Shipping, labels, and rates.

Quick health check

Here's how:

bash
postsale doctor --human
postsale carriers list
postsale origin-addresses list

Good to Know

SymptomLikely causeWhat to do
Rates failNo carriersAdd and validate carriers
Doctor origin warningMissing ship-fromCreate an origin address
Accidental deleteDestructive commandRequire --yes deliberately

End state for setup: postsale doctor is healthy enough for your environment, carriers list shows the accounts you expect, and origin-addresses list has a usable ship-from.

Additional Reading

Related

Keep reading