Statuses

Canonical meanings for channel-connection and listing lifecycle statuses.

Last updated:

Use these status meanings consistently in UI copy, support runbooks, and operational reporting.

Connection statuses

  • pending: connection setup started but not yet verified as ready.
  • connected: credentials and verification succeeded; connection is ready.
  • error: connection or callback flow failed; review the error details and retry.
  • disconnected: connection was intentionally disconnected and credentials were cleared.

Listing draft statuses

  • draft: default status for new drafts and ongoing edits.
  • ready: optional prep state retained for API compatibility (not exposed as a manual picker in current Website/eBay draft editors).
  • publishing: publish is currently in progress (automated for eBay + Website during publish calls).
  • published: draft publish completed successfully (automated).
  • error: publish failed and last_error was recorded (automated).
  • archived: draft is retired from active draft workflows via archive actions.

open is a filter grouping (not a stored status value). It means “not archived and not published”.

Published listing statuses

Canonical published-listing status values:

  • published: listing is retained in active ChannelWeave listing workflows.
  • ended: listing was intentionally ended and is no longer live.
  • archived: listing is retained for history and manually removed from active workflows.

These values are internal lifecycle state, not channel runtime state.

eBay marketplace statuses

eBay runtime state is tracked separately from published-listing lifecycle state:

  • draft: listing exists as a channel draft only.
  • scheduled: listing is accepted and scheduled to start later.
  • active: listing is currently live on eBay.
  • unsold: listing ended without sale (when explicitly known).
  • unknown: runtime state has not yet been positively classified from channel reads.

UI note: in Listings grids, unknown is presented as Ended for clearer operator language.

ChannelWeave keeps these two status tracks separate so unsold is not auto-mapped to internal lifecycle states.