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. Fresh sync and channel updates stop until reconnection; existing ChannelWeave stock, orders, and listings are not deleted by this status.

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 in progress (set automatically for Amazon, eBay, Shopify and Website publish calls).
  • submitted: publish was accepted by the marketplace but is not yet confirmed active; used for Amazon Listings Items submissions awaiting reconciliation.
  • published: draft publish completed successfully (automated).
  • error: publish failed, or a stale interrupted publishing state was recovered, and the 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”.

Draft Delete is a permanent removal action for unpublished drafts only. Published or publishing Website/eBay/Shopify drafts must be retained and moved out of active workflows with Archive instead. Amazon drafts in publishing, submitted, or published represent marketplace submission state and are also retained for reconciliation history.

Publish actions accept only active unpublished draft states. Drafts already marked publishing, submitted, published, or archived are blocked and must be left as history, restored from archive, reconciled, or revised through a fresh revision draft. Publish retries first recover stale publishing drafts before re-validating the draft. Recovery moves any matching running provider attempt to reconcile_required; it does not permit a second remote publish while the first outcome is ambiguous.

Draft detail reads for eBay, Shopify, and Website also run stale-publishing recovery, so a refresh self-heals after the stale window. Their draft editors show Recover publishing while a draft is still marked publishing; the button uses the same recovery rules and stays unavailable until the stale window has elapsed.

Every listing draft must be linked to a ChannelWeave stock item. New drafts, template-created drafts, revision drafts, relist drafts, and draft variations must stay linked to stock; direct draft unlinking is blocked. Published listings imported from a marketplace may temporarily be unlinked until a team member links or creates the corresponding stock item.

Each publish execution records an attempt before the channel write or local Website publish completion. eBay, Shopify, and Amazon attempts retain enough detail for interrupted remote publishes to be reviewed; Amazon accepted submissions continue through reconciliation.

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 ChannelWeave 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 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 user-facing language.

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

Listing inventory sync statuses

When a stock-consuming order is imported and allocated, ChannelWeave clamps every published listing linked to that stock item to the newly available quantity. Website listings are local and update immediately. External channel offer updates move through these statuses:

The first clamp records the listing's original quantity cap. When reservations are released, ChannelWeave can raise the offer again up to that cap, but never above current available stock.

  • queued: the external offer quantity must be written to the channel.
  • processing: ChannelWeave is applying the update.
  • completed: the channel accepted the quantity update.
  • failed: retries are exhausted or the error is non-retryable.
  • blocked: the channel cannot be updated until configuration or publish metadata is fixed.
  • skipped: reserved for jobs that are deliberately retired without a channel write.

The core invariant is one stock truth: four channel listings for one unit do not represent four units of stock. Once one channel order reserves the unit, the other offers must move to zero availability.