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.
Model sellable options explicitly
If a buyer can choose between sizes, colors, or conditions, those options should exist as explicit variants inside Xlistr. Structured variant data gives you dependable stock tracking and clearer marketplace mappings.
When you hide variants inside plain text, you lose the ability to audit stock confidently or understand which exact sellable option changed after an order or revision.
Create one variant row for each sellable option.
Track quantity at the level where the sale actually happens.
Keep variant attributes consistent across channels for easier mapping.
Use shared stock rules intentionally
Shared stock means the available quantity you publish should reflect business priorities, not just the total on hand. Xlistr supports minimum thresholds and channel-aware decisions so you can protect the paths that matter most.
This is especially useful when you want to hold back buffer inventory, prefer a marketplace with stronger margins, or avoid promising the last unit in too many places at once.
Reserve a buffer before distributing stock outward.
Decide which channel gets priority when availability becomes limited.
Review quantity settings whenever you introduce a new sales channel.
Keep revisions predictable after a sale
When a sale happens, inventory should change first. From there, Xlistr can calculate how much stock remains available for each marketplace and schedule the right revisions or delists in the right order.
That flow keeps your operators focused on one source of truth while the system carries the burden of updating channel representations in a safe and repeatable way.
Record the sale against the inventory item or variant.
Let the queue revise affected marketplace listings.
Use logs to confirm which channels were updated and when.