Yes. Inventory can track product-variant quantities by warehouse within an organization. A warehouse is a storage location and should not be presented automatically as a customer-facing store or branch.
Wexcy for retail
Know what you sell. Know where it is. Keep the next move clear.
Build a structured product catalog, track stock by warehouse, and move quantities through controlled inventory records. Add orders, customer context, and sales channels only as those capabilities are enabled and configured for your organization.
- Product identityThe item the team intends to sell.
- Warehouse balanceThe stock position behind the decision.
- Controlled movementThe next permitted inventory action.
Merchandising foundation
Build the assortment once. Keep its structure intact.
Catalog gives each product and variant a stable identity before stock work begins. Organize the details customers and teams need without turning merchandising edits into inventory movements.
- Product identity
- Keep names, descriptions, categories, collections, tags, custom fields, localization, and publication state with the product record.
- Options and variants
- Define the values that make each variant distinct, maintain a unique SKU within the organization, and add a barcode where the operation uses one.
- Selling context
- Attach supported prices, media, bundles, and publication details. Storefront or order use depends on the corresponding capability being enabled and configured.
Catalog changes define the item; they do not change its on-hand, reserved, or available quantity.
Explore Products & CatalogStock by warehouse
See the balance before the team makes the next move.
Inventory keeps quantity work with the product variant and warehouse it belongs to, so the team can review the current position and the record behind it.
- Balance by warehouse
- Review on-hand, reserved, and available quantities for each tracked variant in each warehouse.
- Reservations and movements
- Keep supported reservations, replenishment, damage, adjustment, and other stock movements attached to their references and history.
- Controlled transfers
- Move quantities through a transfer order that records the source, destination, lines, quantities, notes, actors, and state changes.
Governed growth
Give each team the context it needs—and no more.
Retail work becomes easier to review when ownership, access, and the order of rollout are explicit inside each organization.
- Owner or administrator
- Set the organization context, invite the right people, and review the roles and capabilities enabled for the operation.
- Merchandising or catalog team
- Maintain product identity, options, content, prices, and publication context within its permitted scope.
- Stock or warehouse team
- Review warehouse balances, reservations, movements, and transfers that the team’s organization role permits.
Sales or service teams use order and customer context only within the organization’s configured scope and their role permissions.
Clean the source records
Map product identifiers, variants, warehouse balances, and references before migration.
Define context and access
Agree the organization, warehouses, roles, and permissions before inviting the wider team.
Validate, then expand
Verify balances and controlled transfers first; enable conditional order, customer, or workflow layers deliberately.
Migration scope, validation, sequencing, and timing depend on the source systems, identifiers, data condition, integrations, and operational requirements. Do not promise one-click migration or zero downtime.
Retail questions
What to know before you organize retail work in Wexcy.
Clear answers about product records, warehouse stock, controlled transfers, conditional order work, access, and migration.
The supported record can include products, variants, options, SKUs, optional barcodes, prices, media, categories, collections, tags, bundles, custom fields, localization, and publication state, subject to the current model and configuration.
Inventory keeps on-hand, reserved, and available quantities by variant and warehouse, with supported reservations, movements, references, adjustments, and controlled transfer orders. “Shipped” is an internal transfer state, not a carrier service.
When Orders and the relevant commerce workflow are included in the organization’s configured scope, supported order work can create, promote, release, or consume inventory reservations. This conditional workflow does not include payment processing.
This page covers product, stock, and transfer records. It does not promise payment terminals, in-person payment processing, or checkout; provider, market, configuration, and operating requirements must be evaluated separately.
Yes. Roles and permissions define what a user can access or perform within each organization. Any more specific warehouse or location scope must be verified in the current source before it is promised.
Migration depends on source systems, identifiers, catalog structure, warehouse balances, data condition, integrations, and operating requirements. Scope, sequencing, validation, and timing are agreed after review.
A verifiable starting point
Start with the retail core you can verify.
Create your Wexcy account, set up the organization, and begin with the product and stock records your team needs most. Expand after the next workflow’s scope, configuration, permissions, and review steps are clear.