Stock ownership

Principle

Every field should have one authoritative owner to avoid silent drift.

Practical model

• ChannelWeave owns stock records, warehouse balances, reservations, purchase orders, and the operational view of orders.
• Sales channels own their own marketplace listing and transaction state.
• Listing drafts are the review space between a ChannelWeave stock item and a live channel listing.
• Channel-specific mappings decide what can be sent to or read back from each connected channel.
• Eden uses approved operational facts from ChannelWeave and turns them into narrative guidance; it should not become the source of truth for a field.

Conflict resolution

When two systems disagree, check:

1. Which system owns that field.
2. When the latest trusted change happened.
3. Whether a sync, publish, order import, or manual edit is still pending.
4. Whether the affected record has a visible warning, event, or validation message.

Resolve the owner first, then update the other side through the normal workflow rather than editing both places independently.

Everyday examples

• Stock quantity should be corrected in ChannelWeave, then allowed to flow to connected listings.
• A marketplace order should be imported from the channel, then fulfilled in ChannelWeave.
• A product description can be drafted from stock facts and reference facts, but should still be reviewed before it becomes listing copy.
• A supplier receipt belongs in purchase orders/warehouse receiving, not as an unexplained stock adjustment.