Knowledge Base
Understand the model behind Xlistr so operational decisions stay predictable as your catalog grows.
Articles
3
Focus
Operational clarity
Best for
Teams building repeatable workflows
Inventory-first basics
Learn why Xlistr centers everything on internal inventory records and how that changes the way you think about crosslisting.
Inventory records own stock and structure.
Listings are channel-specific representations of the same item.
A strong internal model makes revisions safer and easier to audit.
Managing variants and shared stock
Use explicit variants, quantity thresholds, and marketplace priority rules so crosslisting stays accurate even when stock is tight.
Variants should be modeled explicitly, not buried in blobs.
Minimum stock thresholds protect your preferred sales paths.
Marketplace priority decides how revisions are applied when availability changes.
Background jobs and sync behavior
Understand how publish, revise, and delist actions move through the queue so you know what to expect during large or fast-moving updates.
Background jobs keep the UI responsive while protecting channel consistency.
Action states tell you whether a listing update is pending, processing, complete, or failed.
Queue-friendly workflows scale better than manual marketplace edits.
What you'll learn
Understand why marketplace listings are representations, not the system of record.
Keep variants explicit so edits, stock, and channel mappings stay trustworthy.
Learn how queue-backed actions propagate revisions and delists safely over time.
In this section
Need a different answer?
Use the search bar above to jump across all docs, or open the service section for billing, permissions, and support guidance.
Open Service Docs