Documentation

Search guides and browse sections.

Search
Documentation / Service / Support and troubleshooting
Service
7 min read Updated Mar 2026

Support and troubleshooting

Find the quickest path to resolution when listings, connections, or stock updates do not behave the way you expect.

Most issues are easier to solve with the item, action, and marketplace context in hand.

Start with the queue and connection state before editing listings manually.

Support moves faster when you describe the internal record and the affected channel separately.

Run a quick first check

Before opening a support request, confirm whether the issue is tied to one inventory item, one marketplace connection, or a broader queue backlog. That simple classification often narrows the problem immediately.

You should also review the last action state for the affected item. A failed action tells a very different story than a pending one, and support can respond faster when that context is already included.

Note the inventory item or variant involved.

Record the marketplace and listing state you expected.

Check whether the latest action is pending, completed, or failed.

Describe the issue in inventory-first terms

When reporting a problem, describe the internal inventory record first and then the marketplace representation that looks incorrect. That mirrors how Xlistr is designed and makes it easier to identify where the discrepancy started.

A clear report usually includes the item, the channel, the expected outcome, the actual outcome, and any recent change that might have triggered the problem.

Share the item title or SKU and the affected marketplace.

Explain what changed right before the issue appeared.

Include whether other channels updated correctly.

Helpful support note

Mentioning the last successful or failed marketplace action often saves a full round trip in the support conversation.

Know when to escalate

Escalate quickly if the issue affects active stock safety, a large batch of listings, or billing and access for the whole team. Those situations usually have broader operational impact than a single listing draft issue.

For smaller problems, gathering a few precise details before reaching out is often the fastest route to a fix. The goal is not more information for its own sake, but enough context to avoid guesswork.

Escalate stock-risk issues immediately.

Raise billing or access issues before renewal or team deadlines.

Use support for repeated failures instead of manually patching each listing one by one.