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.
  • connecting: verified credentials have acquired a short provider-identity claim while remote setup completes. A stale claim expires to error rather than remaining indefinitely.
  • 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: a remote create or publish operation is in progress (set automatically for Amazon, eBay, Shopify, WooCommerce and Website calls).
  • submitted: the marketplace accepted the submission but it is not yet live; used for Amazon Listings Items submissions awaiting reconciliation and WooCommerce products intentionally retained in remote Draft state.
  • 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. WooCommerce drafts can be archived or deleted only before a remote product has been created; sent drafts are retained as immutable submission 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, WooCommerce 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, WooCommerce and Amazon attempts retain enough detail for interrupted remote publishes to be reviewed; Amazon accepted submissions continue through reconciliation, while WooCommerce can correlate a remote product to its ChannelWeave draft before allowing another action.

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. ChannelWeave retains active as the stored runtime token and presents it as Live in listing badges and filters.
  • unsold: listing ended without sale (when explicitly known).
  • unknown: runtime state has not yet been positively classified from channel reads.

Listings present unknown as Unknown and the Status: Unknown filter selects external-channel listings whose runtime state has not been positively classified. A listing is presented as Ended only when its ChannelWeave lifecycle status is ended.

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

Discogs imported listing statuses

A manually downloaded Discogs Marketplace Inventory CSV creates local Listing state only after explicit review and confirmation:

  • before confirmation, your newest review remains staged, can be resumed on return, and can be explicitly discarded without changing Stock or Listings
  • an eligible For Sale row is stored with ChannelWeave lifecycle published and marketplace runtime active
  • a Sold row remains an excluded diagnostic and does not create, end or update a Listing; it is never mapped to unsold or ended
  • an existing local Listing omitted from a newer file remains unchanged; absence is never treated as evidence that it ended or was removed

These values record what the confirmed file said at import time. ChannelWeave does not retrieve later Discogs Marketplace state, synchronise the remote listing, or send listing-inventory quantity updates to Discogs. A newer file can only add or update an explicitly confirmed For Sale row; it is not an automatic runtime transition or a complete-state replacement.

From a live Discogs Listing detail, Order placed creates a Discogs Sales order, reserves the linked Stock item and moves the local Discogs lifecycle to ended. The reduced availability is applied immediately to linked Website Listings and queued for Amazon, eBay, Shopify and WooCommerce. Mark ended makes the local lifecycle transition without claiming an order or changing Stock. Restore as live moves an ended Listing back to local lifecycle published and marketplace runtime active; a Listing linked to a non-cancelled Discogs Sales order cannot be restored. None of these actions changes Discogs.

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 or eBay ending action.
  • 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. For eBay, zero availability is an explicit remote end rather than a quantity-zero assumption; the local eBay Listing becomes ended only after eBay confirms the request. If the Sales order is later cancelled, other eligible published offers can recover their availability, but an ended eBay Listing is not automatically relisted.