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.
The source of truth lives inside Xlistr
Xlistr is designed around the idea that your internal inventory record should own stock, variant structure, and the durable representation of the product. That makes it possible to reason clearly about what you are selling, even when the same item appears on multiple channels.
Marketplace listings still matter, but they are outputs of the inventory model. They hold channel-specific presentation details and marketplace state, not the authoritative stock logic for the business.
Use the inventory item to represent what you can actually sell.
Treat listing fields as channel adaptation, not the master record.
Record stock once and publish it outward carefully.
Why this model matters operationally
Without an internal source of truth, every marketplace edit creates the risk that another channel becomes stale. The more channels you add, the more likely it is that quantity, title, or condition data drift apart.
An inventory-first approach removes that ambiguity. Operators know where the real record lives, while background jobs handle the work of keeping channel listings synchronized.
Changes become easier to review.
Stock safety rules can be applied consistently.
Action logs tell a coherent story about what changed and why.
What not to do
Avoid designing your workflow around copying marketplace listings between channels. Use a shared inventory record and publish tailored marketplace representations from it.
When to create a new record
Create a new inventory item when the product is materially different in a way that affects how it is sold, stocked, or fulfilled. Use variants when the differences belong inside one product family, such as size or color.
This distinction keeps the catalog understandable and lets marketplace mappings stay clean. If you hide real sellable differences in text fields, inventory and revision behavior become much harder to trust.
Use a new inventory item for truly separate products.
Use variants for structured options under one item.
Keep sellable differences out of unstructured notes whenever possible.