You can manage products, bundles, variants, options, SKUs, barcodes, prices, media, categories, collections, tags, custom fields, localized content, and publication states.
Products & Catalog
Build a product catalog your team can trust.
A clearer catalog
Spend less time reconciling product records.
When product names, options, prices, images, and identifiers live in separate files, small changes create unnecessary cleanup. Wexcy keeps the structure of each product and variant together so teams can see what belongs where and what is ready to publish.
Product structure
Model each product without flattening its differences.
Start with the product record, then define the options and variants that make each version distinct. Wexcy preserves the relationship between the main product, its option values, and every resulting variant.
SKU comparison ignores letter casing and surrounding spaces while preserving the chosen display form.
Pricing & media
Keep the price, media, and physical details with the variant they describe.
Different variants can carry different prices, images, measurements, and identifiers. Keeping those details at variant level reduces ambiguity when teams review or reuse product data.
These are catalog records. Checkout, tax calculation, payment processing, and shipping services are separate capabilities.
Organize & combine
Group products the way your business needs to maintain them.
Use categories for lasting structure, collections for curated groupings, and bundles when several products need to be presented as one catalog offering.
How bundle components are reserved or fulfilled depends on separately enabled commerce and inventory capabilities.
Custom data & localization
Adapt the catalog to the product—and the language.
Not every product needs the same information. Wexcy lets you define structured Metafields for products and variants, then maintain localized customer-facing content for the languages configured in your organization.
Localization fields support managed multilingual content; they do not imply automatic translation. Search, filtering, comparison, and translation behavior also depends on the experience that consumes each field.
Import with control
Review product data before it enters the catalog.
A CSV import should not be a blind upload. Wexcy separates analysis, mapping, preview, and commit so teams can understand how rows will be handled before changes are applied.
Work with selected records
Publish, unpublish, or archive supported products, variants, bundles, categories, and collections in bulk.
Import scope depends on the source file, identifiers, mappings, data condition, and agreed validation process. Do not promise one-click migration or an error-free import.
Analyze the file
Inspect columns, values, and detectable data issues.
Map the columns
Map product names, SKUs, barcodes, categories, prices, options, and custom fields to the right catalog roles.
Preview and resolve
See which rows are expected to create, update, skip, or fail, then address reported issues before commit.
Commit and review
Apply the approved import and retain its result and issue report for review.
A foundation for connected work
Start with a dependable catalog, then connect the capabilities your organization enables.
Catalog keeps product and variant identity structured. Enabled Wexcy capabilities can use that context without moving responsibility for stock, orders, checkout, or fulfillment into the catalog itself.
Connected capabilities require their own configuration and integration scope. Catalog edits do not update inventory; inventory workflows remain responsible for stock changes.
Catalog questions
What to know before you organize product data in Wexcy.
Clear answers about products, variants, identifiers, organization, localization, imports, and connected capabilities.
Yes. You can define product options and values, then assign their combinations to individual variants. Each variant can have its own SKU, optional barcode, price, media, and physical details.
SKUs must be unique within each organization. Comparison ignores letter casing and surrounding spaces, while the stored SKU keeps its chosen display form.
Categories provide a hierarchy for long-term catalog structure. Collections are curated groups whose product membership you choose directly.
Yes. A bundle can contain component variants and use either a fixed price or a price derived from its components. Component reservation and fulfillment depend on separately enabled commerce and inventory support.
Yes. You can maintain localized names, descriptions, search keywords, variant titles, option values, and routes for the languages configured in your organization. Translation remains managed content, not an automatic promise.
Yes. Products and variants can use structured Metafields with supported data types, validation rules, and behavior flags. How a field is searched, filtered, compared, or translated depends on its definition and the consuming experience.
The import flow supports analysis, column mapping, preview, issue review, commit, and a result report. Supported records also provide bulk publication and archiving actions.
No. Catalog manages product structure. Stock balances, reservations, movements, and transfers must be changed through Inventory workflows.
No. Products & Catalog manages catalog data. Online Store, Orders, Payments, POS, Shipping, and related fulfillment capabilities are separate products with their own configuration and operating requirements.
Start with a stronger catalog
Build a catalog your team can keep working from.
Start with the products and structure you need now. Add variants, collections, bundles, custom fields, languages, and connected capabilities as your operation requires them.