Products & Catalog owns the structured product record—variants, media, prices, categories, collections, and localized content. Online Store presents that maintained information to customers and carries their choices through the cart into order creation.
Wexcy Online Store
Turn your catalog into a store that stays connected to every order.
Present products and bookable services through a branded customer experience, let shoppers shape a cart, and carry verified customer, price, currency, channel, and stock context into the order.
A clearer storefront
Give customers a clear way to find, compare, and choose.
Use the product names, descriptions, media, variants, prices, categories, collections, and localized routes your team maintains in Catalog. Update the source record without rebuilding the product story in disconnected tools.
Product presentation
Keep customer-facing names, descriptions, media, and publication details grounded in the product record.
Meaningful choices
Present the variant or offering choices that distinguish what the customer is buying or booking.
Browseable groups
Use categories and collections to shape practical paths through the assortment.
Localized discovery
Serve maintained names, descriptions, and routes for the languages configured by the organization.
One purchase context
Keep the purchase context intact from the storefront to the order.
Each stage adds a decision without discarding the context established before it.
Present
Show maintained product or service information in the right language and route.
Choose
Capture the variant or offering, quantity, customer context, and compatible currency.
Validate
Apply the relevant ownership, pricing, channel, and stock rules before conversion.
Create the order
Carry a dependable snapshot forward so the operating team can continue the work.
A cart that keeps its context
Let the cart change without losing what the customer chose.
Customers can add supported products or bookable services, adjust quantities, and continue as a guest or signed-in customer. Wexcy keeps the relevant selection and commercial context together while applying the implemented validation rules.
- Customer or guest
- Maintain a usable cart before sign-in and merge it with the customer cart under the implemented rules.
- Selection and quantity
- Preserve the chosen variant or offering and update quantities deliberately.
- Compatible currency
- Keep cart lines within a currency context that the cart can process consistently.
- Stock-aware changes
- Where inventory context applies, validate changes and maintain the related reservation behavior.
From intent to operating record
Create an order your team can keep working from.
When the purchase is converted, the order carries a snapshot of the selected lines and the context needed for the next responsible team to understand what happened.
- Customer context
- customer or guest identity and the relevant address data
- Item snapshot
- selected product variant or service offering, quantity, and recorded detail
- Price and currency
- the commercial values carried into the order
- Channel and stock context
- the commerce channel and applicable warehouse or reservation relationship
Connected, with clear responsibilities
Let each part of commerce own the work it is built for.
Wexcy shares context across the purchase journey without pretending that every responsibility belongs to the storefront.
Catalog
owns product structure, variants, media, pricing records, categories, collections, and localized product content
Online Store
owns customer-facing discovery, selection, cart context, and purchase conversion
Inventory
owns warehouse balances, reservations, movements, and controlled transfers
Orders
owns the commercial record teams continue after conversion
Online store questions
What to know before you shape the customer purchase journey.
Clear answers about catalog context, choices, carts, languages, currency, stock, orders, and connected responsibilities.
Yes. Maintained product variants can be presented as sellable choices, and the selected variant is carried into the cart and order context.
Yes. Supported bookable service offerings can be added with the customer’s selection; their quantity behavior follows the implemented service rules.
Yes. A guest can start a cart before signing in, and it can be merged with the customer cart under the implemented rules.
A cart keeps one compatible currency context for its lines. Pricing and currency are validated before the purchase becomes an order; automatic currency conversion is not implied.
No. A cart is not a fulfillment guarantee. Final validation or reservation depends on the product, warehouse, channel, and rules that apply when the purchase is converted.
Yes. The store can present the names, descriptions, and routes your team maintains for the languages configured by the organization. Translations remain maintained content.
No. Cash on delivery is the payment method represented in the current Commerce model. Online payments, tax, carrier services, and returns require separately verified and configured capabilities or integrations.
Start with the purchase journey
Bring the storefront and the work behind it into one purchase context.
Start with the catalog and customer journey your business needs, then keep the order understandable as teams take over.