CrowPrime Docs

Selling channels

Tokens, reconnecting & disconnecting

Marketplace access tokens are short-lived. CrowPrime keeps them alive in the background and tells you clearly when human action is required.

On this page

Connection states

connected

Meaning
Valid tokens, syncing normally
Sync running?
Yes

Expiring soon (health indicator)

Meaning
The access token is close to expiry; the automatic refresh takes care of it
Sync running?
Yes

needs_reconnect

Meaning
Authentication failed (for example after a marketplace password change) — reconnect required
Sync running?
No

expired

Meaning
The refresh token is no longer valid — reconnect required
Sync running?
No

frozen

Meaning
The channel is not included in your current plan after a downgrade; data is kept
Sync running?
No

disconnected

Meaning
Removed by a member of your organization
Sync running?
No

Automatic token refresh

Every connection stores an access token with a short lifetime and a longer-lived refresh token. A background job refreshes the access token before it expires; a refresh is also attempted on demand when an API call returns an authentication error.

  • Refresh is attempted well before the token expires, so normal operation never waits on it.
  • Failed refreshes retry automatically with backoff; the connection is marked expired only after retries are exhausted.
  • After the final failure the connection moves to expired and the owner and admins are notified by email and in the notification centre.
  • Refresh tokens are rotated when the channel issues a new one, and the previous value is discarded immediately.
log
10:02:11  refresh scheduled   channel=etsy   token=expiring_soon
10:02:12  refresh ok          channel=etsy   token=valid
10:14:48  refresh failed      channel=amazon reason=invalid_grant
10:19:48  refresh failed      channel=amazon reason=invalid_grant
10:29:48  connection expired  channel=amazon action_required=reconnect

Note

Changing the marketplace account password, enabling new security settings or revoking the app in the seller portal invalidates the refresh token instantly.

Reconnecting

  1. 1

    Open the affected connection

    Connections that need a reconnect are pinned to the top of the Integrations page with a Reconnect button.

  2. 2

    Authorize again

    Use the same marketplace account. Connecting a different account creates a new connection instead of restoring the old one.

  3. 3

    Catch-up sync

    On success CrowPrime imports everything missed during the outage: new orders, status changes and listing edits, then pushes any stock updates that were queued.

  • Reconnecting preserves product mappings, order history, invoices and reports.
  • Queued outbound stock pushes survive an outage and are flushed after the catch-up import, newest value wins.
  • If the marketplace account itself changed, review SKU mappings before enabling sync again.

Disconnecting

Disconnecting is a deliberate, organization-wide action available to Owners and Admins.

Tokens

Effect
Deleted from CrowPrime and revoked at the channel where the API supports it

Sync

Effect
Stops immediately in both directions; queued pushes are dropped

Listings

Effect
Remain live on the marketplace with their last pushed values

Historical data

Effect
Orders, invoices, refunds and reports are kept and stay readable

Products

Effect
Stay in the catalog; their channel listings are marked unlinked

Important

Because listings stay live after disconnecting, stock will no longer be reduced when those listings sell. End or pause the listings on the marketplace if you do not intend to reconnect.

Audit trail

Connect, reconnect, disconnect, scope changes and expiry events are written to the activity log with actor, timestamp and channel, and are visible on the dashboard activity feed and the connection detail page.