WEXCY REFERENCE

Documentation

A reference to core Wexcy concepts and how their responsibilities relate.

Explore account and organization context, product and stock records, and website content.

Account, organization and access

The account identifies the user. Their role is considered within an organization.

User account
A user identity that can be associated with more than one organization.
Organization
The context in which the user's role and the organization's work are considered.
Role
A role assigned to the user within an organization, with eligible permissions managed in that context.
Effective permissions
Access can include role permissions and direct grants.

A role in one organization does not describe the user's role in another. Removing one role does not necessarily remove all access, because other roles or direct grants can remain.

Products, variants and stock

Catalog records describe the item. Inventory records describe quantities for a variant in a warehouse.

Product
The general identity and descriptive information for an item.
Option
A choice such as size or finish used to distinguish versions of a product.
Variant
A particular combination of option values, with its own SKU and associated details.
Warehouse
A stock-storage location whose record is distinct from a customer-serving branch.
Stock quantities
On-hand is the recorded quantity. Reserved is the quantity held by active reservations. Available is on-hand minus active reserved quantity.

Changing a product description does not itself establish or adjust stock quantities. Keep the variant and warehouse context when reviewing a balance.

Website, content and publishing

Website presentation and editorial content have related but different responsibilities.

Theme and presentation
Website Builder prepares the website presentation system and validates it for a theme release.
Editorial content
Pages, articles and blog material organized and edited through the CMS.
Localized content
Language-specific content and route information for the organization's configured languages.
Content publishing
Editorial records follow their own publishing states, such as draft, published and archived, separately from a theme release.

Releasing a theme and publishing an article are different operations. Language-specific content remains under editorial control; supporting multiple languages does not imply automatic translation.