Product detail

The detail is the one place you see a product whole — and, more importantly, where you see where each value came from. On a product that has been through an import, a mapping, a rule and the AI, it is the only reliable answer to "why does it say that".

1 — Name and product code2 — Edit product3 — Type4 — Status5 — Description origin6 — Generate7 — Vendor8 — Brand9 — Manual category10 — Vendor categories11 — Internal ID12 — External ID13 — Enabled14 — Visible in listings

Controls on this screen

1. 1Name and product code — The code is the feed identifier — what the product is matched by on every later import.
2. 2Edit product — Opens the editor. The only route to a manual change runs from here.
3. 3Type — Set automatically from the number of variants; only Bundle / Digital are chosen by hand (informational).
4. 4Status — Draft, published or archived.
5. 5Description origin — "Manual" means a person or the AI wrote it — and that an import will not overwrite it.
6. 6Generate — Has the AI write a description from the name, parameters, brand and category.
7. 7Vendor — Which feed the product came from.
8. 8Brand — The unified manufacturer brand.
9. 9Manual category — Your category. Nothing here means the product is unmapped.
10. 10Vendor categories — Categories as the feed sent them. The star marks the primary one.
11. 11Internal ID — Monokaido's identifier. This is the one that appears in the page address and the API.
12. 12External ID — The vendor's identifier.
13. 13Enabled — Your decision that the product may be sold.
14. 14Visible in listings — Whether the shop actually shows it — a product can be enabled and still hidden.

Where each value came from

This is the main question the detail answers:

More actions (⋯)

Next to the Edit product button sits the ⋯ menu with the actions you do not need every day:

Someone who can only view products has no ⋯ menu.

Parameters: row actions

The Parameters table has one row per value and, at the end of each row in the Action column, a ⋯ menu of its own. Editors and administrators see it, and it holds only what can actually be done with that value.

The Parameter column shows in bold the parameter the value is stored under (for a value nothing has stored yet, the parameter the sync writes it into), with its code. When another feed name brought the value, that name is shown next to it in grey. On a parameter several feed names write into (say seven EMOS rooms into “Vhodné do miestnosti”) every value thus shows where it came from. The product stores one value of a parameter once, under one feed name; the table does not list the other feed names carrying the same value on their own.

A feed value that a parameter mapping moves into another parameter only at the next sync is in the state Awaiting sync and shows under its name where it goes — for example “→ Vhodné do miestnosti · after the next sync”. A value nothing has stored yet is in the same state right under the parameter the sync writes it into, with no arrow. A value that a Don't carry this value over rule drops at that sync shows “→ Vhodné do miestnosti”: the parameter goes there, the value nowhere. When only some of a parameter's values move (say a value from a product merge or one a person wrote stays), every value says its own way, and the one that stays says “stays”.

On a feed value that a parameter mapping brought into the parameter, the Map value dialog also offers the Scope of the rule: whether the rule applies only to the feed parameter or to the whole parameter — see Value mappings.

A feed value kept out by a Don't carry this value over rule shows in the table in the state Not carried over, greyed out and struck through, with “Value mapping: Not carried over” under the value; its Origin column shows Value mapping. Hovering over the state names the parameter whose rule decides it, or says the value stops being carried over only at the next sync — until then it is still sent. The row stays in the table even after the stored value is removed, so that Don't carry this value over can be unticked through Edit value mapping. It has no Suppress value item: the rule already keeps the value out (at the latest from the next sync), so there is nothing to suppress.

Map parameter follows the Origin column:

A value written by a rule or by the system has no Map parameter item — they would write it again. On a row in the Unmapped state only the mapping is saved, and the next sync writes the value. All vendors does not move the values of a vendor that has a mapping of its own for the same name — that one takes precedence.

A move of AI or manual values does not reach the derived products of a split: the values the AI or a person wrote on them do not move and have no Map parameter item. The dialog counts them among the values that stay under the parameter.

Once you pick an existing target parameter, the dialog says before you confirm how many values will move and how many will merge: when a product already has exactly the same value under the target parameter, the two rows become one. Another spelling (Áno and áno) stays a value of its own. If a feed parameter mapped into the target parameter has value mappings of its own, Monokaido recalculates the touched products' values from the stored feed data after the move, so a rule's result (say “áno” → “Kancelária”) comes back as a value of its own. The message after you confirm says whether the recalculation is done, still running (with many products this can take a few minutes; the table refreshes by itself meanwhile, and if the values still have not changed, reload the page) or failed — then the next sync recalculates the values. A product without stored feed data gets the rule's result only at the next sync. A value you have suppressed under the target parameter does not get there: a feed value is removed, a value from the AI or a person stays where it is. The dialog also says what happens to the value you opened it from. It then names the parameter-mapping rule that will be created or updated (or says it already exists), where to find it (Parameters → Parameter Mappings) and where the next syncs will write the values. For values from the AI or a person it warns that no rule is created and the values move once.

When templates list the parameter, the dialog names them and offers Replace it in the templates: the original parameter is replaced there by the target one. The option is ticked in advance when no value is left under the original parameter after the move. While a template lists the original parameter, the AI fill writes it again on products that lack it. When templates are assigned automatically by this parameter, the dialog warns that this stops once the values move.

System settings