Products

Double-click any picture — in the products table, on a colourway card, in the image library, on an order line — and it opens full screen. Escape or a click outside closes it; where a set of images belongs together, the arrow keys walk through them.

The preview loads a full-size rendering, not the thumbnail scaled up, so it is worth using to check a photo properly.

Open the product and look at §02, the article you are editing. The colour name sits next to its dot and is a text field — click it and type. It applies to every size of that article, and saves with the page.

An article shows “No colour” when the field is genuinely empty, not because something went wrong. The usual cause is a Shopify import where the colour lives somewhere QUOMODA was not told to look — see *My products vary by fabric, not colour* under Integrations.

You can also set it per size row when creating or editing a product, in the variants table.

Connecting a second system to a catalogue you already had writes one duplicate per style. Nothing links the two records: Shopify matches on its own product id, and a product you typed in QUOMODA has none. Their names often differ too — *Heel Drop Racer* against *Heel Drop Racer in black* — and so do their article numbers.

What they do share is the SKU on every article. QUOMODA looks for that, and shows the pairs it finds in a panel at the top of the Products page.

1. 1Open Review on a suggested pair to see both records side by side.
2. 2Choose which record survives — everything points at it afterwards.
3. 3Then choose a winner field by field. The survivor does not have to win every value: a Shopify import usually has the better images, while the record you typed has the composition and the HS code.
4. 4Merge. Orders, invoices, allocations, stock and linesheet blocks all follow the survivor.

The review screen shows stock and committed quantities on both sides before you decide: units on hand, units customers have ordered, units on order from suppliers, and how each of those splits between the two records — often the stock sits on one and the orders on the other, which is exactly what the merge brings together. Order lines are never re-cut or combined; each stays on its own order at its own price. Stock is added together where the same SKU exists on both sides and moves across untouched where it does not, and units already allocated to a customer stay allocated. Purchase orders follow their article rather than the product, which comes to the same thing.

Yes. Tick exactly two products in the list and choose Merge on the bar that appears — the same review screen opens, whether or not the pair was suggested.

Define your canonical Category › Subcategory tree in Settings → Products → Product hierarchy — it powers the dropdowns on product cards and keeps filters and documents consistent.

1. 1Click Build from my catalogue to seed the tree from what your products (and connected integrations) already use.
2. 2Tidy it up: rename or remove categories, add subcategories as chips.
3. 3Anything on your products that falls outside the tree appears under needs a home — pick where it belongs and click Move.

On the Products page, Filter holds Category and — once a category is chosen — Subcategory, scoped to that category. The same subcategory filter appears in the linesheet product picker.

Yes. The product page has a customs block: HS / tariff code, country of origin, composition, and per-unit net & gross weight (kg). They apply to every size and colourway of the style (per-size weights synced from Shopify are kept as-is), flow onto invoices, order confirmations and packing lists, and can be overridden per line on any invoice.

One row, under the title. Search is on the left, Filter holds category, subcategory, supplier, season, status and Shopify, and View holds the grid / table switch and, in the table, which columns show, their order and which are frozen.

Whatever Filter is narrowing by shows as a chip beside it — click a chip to drop that one filter, or Clear inside the menu to drop them all. Nothing filters the page without saying so on the page.

The line under the title counts what is in front of you — articles, styles, and how many have no season yet.

Yes — in the table view every column except the article name and article number is edited in the row. Click the cell, type or pick, and it saves when you leave it. Category, subcategory and gender are dropdowns; supplier, product type, country, composition and HS code are text, with the suppliers you already have offered as you type.

The cells are borderless until you touch them, so a long list still reads as data rather than as a wall of boxes.

The article name and article number are the two that still open the slide-in panel instead, because what you do to them there — colourways, sizes, images, the bill of material — is not a single value you can type into a row.

Go to the Products page and click "Add product". Fill in the name, SKU, category, and pricing details. You can add images, variants (sizes/colors), and assign the product to a season.

When a Shopify store is connected, the Products Filter menu gains a Shopify filter — In Shopify / Not in Shopify — so you can see exactly what has and hasn't been synced. Select several products (tick them) and the bulk bar shows "Create in Shopify" for the ones not yet there, or "Sync" for the ones already linked — pushing the whole selection in one go.

Every bulk action on the Products page — Edit fields, Group siblings, Ungroup, Create in Shopify, Sync, Delete — stops at a confirmation that names the change rather than asking "Are you sure?". It tells you:

1. 1How many products will change, and which field they change.
2. 2The outcome in one sentence when they all land on the same value — *Category becomes “Knitwear” on all 332*.
3. 3A Now → After preview of the first five, and how many more follow.
4. 4Anything you selected that will not change, and why — *12 of the 40 products you selected will not change: they already hold these values*.
5. 5A closing line that says either You can undo this for 7 days or This cannot be undone.

Yes, for 7 days. The toast that follows a bulk change carries an Undo, and every bulk change is also listed under History at the top of the Products page.

1. 1Open History — bulk changes newest first, each with what it did, when, how many products and how many values.
2. 2Click Revert on a row and confirm. The values it replaced are written back exactly as they were, blanks included.
3. 3Past 7 days the row reads Undo window closed instead of offering a button.

Grouping and ungrouping siblings, bulk field edits and applied AI suggestions all land there. Each field is its own entry, so you can put a category sweep back and keep the descriptions applied in the same pass.

Two edges to know: undoing an ungroup rebuilds the exact grouping, but only inside the window — after that nothing records which products were siblings. And seasons are stored outside the product record, so undoing a bulk edit that also changed seasons puts every other field back but not the season assignment.

Suggest with AI runs over a batch of styles. Tick rows and use the button on the bulk bar, or use the header button to point it at everything in view (whatever your filters show) or at a whole season.

1. 1Pick the fields it may propose — product name, category, subcategory, product type, gender, colour name, tags and description are on by default. HS code is off unless you switch it on, because a customs code is your liability.
2. 2Choose Fill blanks only — the default, which leaves anything you have already written exactly as it is — or also propose improvements to existing values.
3. 3Check the credit line and press Run.

The run lives in the app header, not in a dialog: leave the page, work on an order, come back. The pill counts styles done, estimates what is left, and has a Stop.

Nothing is written by the run itself. When it finishes, the header pill offers Review N proposals.

The queue opens by field: every product name together, then every category, then every description. That is what makes it fast — answers within one field rhyme, so you judge the pattern once and accept the group. A By product toggle groups them the other way when you would rather read one style end to end.

1. 1Proposals that fill a blank arrive ticked. Proposals that would replace something you wrote arrive unticked and flagged in amber — an overwrite never happens by not looking.
2. 2Tick individually, or use Accept all / Skip all on a field group.
3. 3Descriptions and other long copy are shown current-versus-suggested side by side instead of squeezed into a row.
4. 4Press Apply — only the ticked proposals are written.

The apply lands in History as one entry per field, revertable for 7 days like any other bulk change.

One credit per style attempted. A style that comes back with nothing — or fails outright, usually a style with no image to read — still spends its credit: the credit is taken when the request is made, not when it succeeds.

The scope dialog weighs the run against your balance before it starts: this month’s included allowance plus any credits in reserve. If the run needs more than that it says so up front, and stops when the balance runs out — the styles already done keep their proposals, and you can still review and apply them.

Variants represent different options of a product — typically size and color combinations. Each variant can have its own SKU, barcode (EAN), and stock level.

In the SKU details table at the bottom of a product, each size shows its stock per location, a Total, and On PO — the units of that size ordered on purchase orders that are still open. A purchase order counts as open until it is fully received, cancelled or archived; an unsent draft does not count yet.

On PO is everything ordered, not everything still to come. Receive half a delivery and On PO stays where it is while the stock columns go up — it is the size of the commitment to the supplier, which is what you need when deciding whether to order more. The +N badge beside Stock on the Products list is the other number: what is still to arrive.

You set SKUs manually per product and variant — we don't force a scheme, but a consistent one makes everything downstream (picking, packing, Shopify) easier to scan.

For colourways, each colour is its own article/row, so the colour usually lives in the article number rather than the SKU.

Each product can carry an article number (style level), and each variant its own SKU, EAN barcode, and internal reference. EANs appear on packing lists and sync with Shopify. You can type them manually, include them in the bulk-upload file (variant_barcode column), or auto-generate them.

1. 1Register your EAN range under Settings → Products → EAN / Barcodes (e.g. your GS1 company prefix).
2. 2When adding or editing a product, click Generate EAN.
3. 3QUOMODA assigns the next free numbers from your series to each variant — no duplicates, no spreadsheets.

Yes. Click Bulk upload on the Products page and upload an Excel (.xlsx) file. Download the template first — it has one column per price list, so you can import prices in the same pass.

Click on a product to open its detail view. You can drag and drop images or click to upload. The first image is used as the cover in linesheets.