Prepare destination-specific content, commercial values, media, categories and eligibility; approve the listing state; publish to selected client-owned or marketplace destinations; synchronise supported availability and status data; then expand by category, site or channel using the same accountable controls.
Publish and Scale is the commercial activation stage of the How It Works journey. It does not assume every stored or digitised item should become public. Inventory can remain private, storage-only, draft, restricted, enquiry-only or unpublished according to owner policy, condition, rights and destination capability.
The commercial route can start with one destination and expand later. A client can operate its own website, use selected Vault marketplaces, connect supported external channels or combine these models without duplicating the underlying inventory record.
Publish approved inventory to the client’s own website or commerce experience while the client retains brand and destination policy.
Make approved inventory eligible for selected Vault destinations such as CostumePeti, Vault.Fashion, Vault.Wedding, Vault.Furniture, Vault.Productions or Vault.Luxury.
Connect several approved destinations through Commerce OS Marketplace Connections or other supported integrations.
The publishing workflow should preserve a clear separation between the authoritative internal inventory record and the commercial representation created for each destination.
Check catalogue completeness, condition, owner intent, rights, media and destination capability before any publishing action is released.
Prepare destination-specific title, description, category, attributes, variants, media, pricing/rental values and visibility.
Validate the destination draft, review errors and lock the approved version before creating or updating the live listing.
Monitor listing state, availability, failures and drift, then expand in controlled waves using repeatable templates and reports.
Start with the complete publication architecture, then move through eligibility, destination content and values, draft creation, review lock, publish state, availability synchronisation, channel exceptions, drift reconciliation and controlled rollout.
The first publishing decision is whether the inventory should be commercially exposed at all. Storage-only, confidential, restricted, condition-held or rights-limited inventory can remain private even when its internal catalogue record is complete.
Eligibility can differ by destination. An item approved for one Vault marketplace or client website does not automatically become eligible for every other destination.
Confirm the required descriptive record is complete for the selected destination.
Prevent inventory on unresolved hold from being treated as freely marketable.
Commercial publication should follow the owner’s approved scope.
Apply the rules of the actual destination rather than one universal publish flag.
The canonical inventory record should remain authoritative for custody, identity and stock. Destination mappings can then hold the commercial fields needed for a specific website or marketplace without duplicating the physical inventory truth.
Commercial values can differ by destination according to the approved policy. Rental pricing, sale values, deposits, visibility and media order should not be overwritten globally merely because one channel requires a different presentation.
Translate the internal record into the fields required by the destination.
Allow destination-specific merchandising while preserving the canonical media library.
Store the approved commercial values appropriate to each destination.
Decide what the destination may expose and commit.
The publication workflow should prevent catalogue preparation from turning into an accidental live listing. A destination draft can be created or updated, reviewed and locked before the final live action is released.
The internal system and external destination can temporarily show different states because the channel may reject a field, process asynchronously or become unavailable. The platform should show the last known destination state and any actionable error.
Check the destination requirements before creating or updating the listing.
Create or update the remote draft without automatically making it live.
Require the configured human approval before the live action.
Keep destination truth visible even when it differs from the intended state.
Once listings are live, the platform should keep the channel mapping and operational state visible. Stock, reservation or availability updates can be synchronised where supported, but external APIs may be delayed, rate-limited or temporarily unavailable.
Scaling should therefore include connection health, retry queues and staged rollout—not a promise that every external destination updates instantly or identically.
Keep destination commitments aligned with the authoritative internal inventory state where the connector supports it.
Make failed or stale updates actionable.
Do not silently overwrite conflicts when the external destination has changed independently.
Expand using repeatable mappings and approvals instead of activating everything at once.
The sequence keeps commercial activation deliberate while making it repeatable enough to support large inventories and several destinations.
Confirm catalogue, condition, owner intent, rights and destination eligibility.
Map category, content, media, variants, commercial values and visibility for the selected destination.
Check required fields and create or update the destination draft without automatically publishing it.
Preview, correct, approve and lock the reviewed version before the live action.
Track destination state, availability, failed updates, stale sync and external drift.
Expand by category, inventory group, site or destination using validated bulk actions, reporting and exception review.
Publish and Scale explains how inventory becomes commercially active in the end-to-end journey. It does not turn Commerce OS into the marketplace operator or collapse all channels into one set of rules.
Eligibility, content, values, visibility, rights, availability and approval remain controllable by item, inventory group and destination.
The client or inventory owner decides where and how inventory may be commercialised. Seller Central and Commerce OS prepare and synchronise the approved data, while each destination retains control of its own marketplace or platform rules.
These states answer different questions. Treating them as one status makes it difficult to understand whether the issue is content, approval, channel publication or actual stock availability.
The exact publishing path depends on owner intent, catalogue readiness, destination capability, connector availability, commercial rules and whether the inventory is being rented, sold or simply kept private.
No. Catalogue readiness is separate from destination eligibility, owner approval, draft creation and live publication.
No. The connection only enables supported data exchange. Each item or approved group still needs the required eligibility, mapping, content, values and publication state.
Yes, where the destination mapping supports it. Channel-specific content and commercial values can differ while the internal custody and inventory identity remains authoritative.
Yes, where the selected destinations and connectors support it. The aim is one authoritative internal inventory record with separate destination mappings rather than duplicated stock truth.
No. A draft is a prepared or remotely created listing state. The final publish action remains separate and can require review approval.
Yes. External destinations control their own required fields, images, categories, terms and acceptance processes. Rejections should remain visible with a correction or retry path.
No. Supported connectors can synchronise stock and status, but external APIs may be delayed, rate-limited or temporarily unavailable. Last-sync and exception visibility are therefore important.
Where the external API exposes that change, the platform can identify drift and apply the configured reconciliation rule instead of silently overwriting one side.
Yes. The listing can remain live while authoritative availability is zero because the item is reserved, on hold, under care or otherwise not eligible for commitment.
Publish and Scale completes the planned How It Works journey. The operation then continues as a cycle: listings create demand, fulfilment moves inventory, returns restore or restrict it, catalogue and location data change, and selected channels are monitored and expanded over time.
Keep owner intent, catalogue readiness, destination mappings, commercial values, approval, availability and external listing state visible so one controlled inventory record can support several commerce routes without losing accountability.
Login