Style and variant hierarchy
A style holds its barcode-level variants, each with its own SKU, colour, size, MRP and status. The product is managed as one design, not as a loose list of codes.
One master for styles, SKUs, barcodes, attributes and production runs.
Stylify is the product master for fashion and production teams. A style carries its barcode-level variants and configurable attributes, maintained through spreadsheet uploads instead of five divergent files, so production runs and labels start from one record.
Standalone · GST-aware where relevant · Pilot before rollout
Each capability is traced to the working product. The panel on the right shows a real label from the screen where it appears.
A style holds its barcode-level variants, each with its own SKU, colour, size, MRP and status. The product is managed as one design, not as a loose list of codes.
Define the attributes your products need, such as brand, gender, department, category, sub-category, HSN, fabric, sleeve, pattern and season, and add as many as the range requires.
Pick a master colour and a size group, and the variants are generated instead of typed. Each combination receives its own SKU and barcode under the rules you set.
Barcode and SKU values follow rules you set, so identifiers are generated rather than invented by hand. The same rule keeps numbering consistent across uploads and new styles.
Create or update styles and variants from a CSV or XLSX file. The file is read and previewed before anything is saved, and progress is shown on large uploads.
When an upload contains an attribute value that does not exist yet, Stylify adds it instead of rejecting the row. Rows that do not fit are flagged so they can be fixed.
Keep a product in draft while it is incomplete, and publish it when it is ready for other teams. Drafts stay separate until they are complete.
Tax code and unit of measure are held on each product and can be inferred during upload. The rate, such as 5% or 18%, follows the tax code set for that product.
Attach product image URLs to styles and variants, so catalogues and listings can carry the right picture for each size and colour, in the same record.
Reusable company, store and financial-year masters keep every record consistent, so the same definitions apply across the whole product master and every new style starts from them.
Control which variants are active and visible in the catalogue. Inactive variants stay in the record, so the master keeps its history while the catalogue stays clean.
Download the product master, the variant sheet and the attribute list as structured XLSX files for other teams and systems to use. The columns follow the attributes you defined.
Every colour and size is its own SKU, so a production run can be planned size by size and colour by colour from the same master record.
Fabric, season and the other attributes sit on the style itself, so the production team and the buying team read the same record instead of separate sheets.
Barcodes and SKUs generated by rule sit in the master, ready to take into labelling for production and dispatch. Exports carry them to the teams that print.
Three operating problems this product is built for. Each one is answered by a capability on this page.
One style-to-variant master with configurable attributes.
Barcode and SKU rules generate them for every size and colour.
One style record holds fabric, season, colours and sizes for production planning.
Five steps, in the order the work happens.
Decide which attributes describe your products, such as brand, department, fabric and season, and the values each can take.
Upload a CSV or XLSX of styles and variants. The file is read and previewed before anything is saved.
Missing attribute values are created and rows that do not fit are flagged, so one bad cell does not block the sheet.
Open a style and see every colour and size, with MRP and status. Edit what needs editing.
Download a structured sheet for another team, or let a connected product read the master.
Each role has its own job in the product and a clear gain from it.
Defines styles, colours and sizes.
One style record instead of many sheets.Uploads sheets and reviews flagged rows.
Problems caught before they spread.Checks MRP and status per variant.
Current prices in one place.Reads the master for stock and display.
No guessing which list is current.Sets attributes and barcode rules.
Rules applied the same way every time.Stylify is a product master and production-data layer, not a checkout, a warehouse or a full ERP. Tax code and unit are held per product, so a rate such as 5% or 18% follows the tax code set for that product.
We would rather you hear this in the first conversation than find it later.
Seven situations this product is built for.
Merchandising, stores and e-commerce each kept their own file. A single style-to-variant master removed the argument about which was current.
Every new article meant typing each size by hand. Choosing a size group now generates the variants and their barcodes.
A seasonal MRP change touched thousands of rows. Uploading a sheet shows the changes before they are saved.
New product types needed new descriptors. Attributes are defined by the team, so a new field does not need a project.
Stores kept stale price lists. Stylify holds MRP and status per variant, and downstream products read from one place.
Half-finished products leaked into reports. Draft and publish keep incomplete records out until they are complete.
Production runs were planned from a sheet that did not match the size codes. Every size and colour is a SKU in the master, so the run follows the record.
One open at a time. The full list has 35 questions.
Stylify is QGenx’s product master data product. It holds styles, their barcode-level variants and the attributes that describe them.
The single, agreed record of each product: its style, variants, barcodes, prices and attributes, which other systems rely on.
Fashion, footwear and lifestyle teams and anyone with SKU-heavy ranges that live in spreadsheets today.
A style is the product as a design, for example a cotton shirt. Variants are its purchasable forms, such as each colour and size with its own barcode and MRP.
No. It is the product layer. Billing and checkout belong to POS and Billify.
No. It serves as the product master that other products and sheets draw from.
No. It stands alone, and connects to others only when that removes repeated work.
Yes. Attributes are configurable columns with their own values, and you can have many of them.
Choose a master colour and size group and the variants are generated, with barcodes following your rule.
Barcode and SKU identifiers follow settings you control, so they are generated rather than typed.

Tell us about your current workflow, look at the product closest to the problem, and choose a 30-minute slot. A working walkthrough, not a slide deck.