↑↓ selectEnter openEsc close

    1. Elbuz
    2. How to create a product and fill in its card

    What each product card field means

    11 min readUpdated

    Every product card field: what to enter, which ones the app fills in itself, and which go to your website and exports.

    When you need this:

    • A field can't be edited: the app maintains cost price and “Exported” itself; see where the values come from.
    • You need to set a product's weight or unit: “Weight unit” sits next to “Weight”, and “Unit” is the product's own unit.
    • Completeness is lower than expected: see which fields it's made of.
    • You need a Ukrainian version of the description: the card translates a language's empty fields from the default language.

    Where to start: find the field in the list of sections below.

    What's in the product card

    Protecting fields from price lists (the checkboxes in the “Import protection” group) is covered separately: how to stop a price list from overwriting a price or a product.

    Name, descriptions, tags

    The “Content” section has six fields that go to your website and exports:

    FieldWhat it is
    NameThe product name. It also appears in the card header, the window title and the product list
    Short descriptionText, with a “Visual editor” button next to it
    Full descriptionThe visual editor is always on
    InstructionA separate text with a “Visual editor” button: instructions for using the product
    Label (tag, nameplate, marker, badge)A short label text; the field caption lists all the names people use for it
    TagsProduct keywords on a single line

    Photos inside the description

    You can insert an image right into the text: press Ctrl+V or drag a file into the editor. The file is uploaded to your storage straight away, the text keeps a link to it, and the description is saved together with the image. You don't need to save the image anywhere else.

    • Wait until the text in the bottom bar changes to “Saved” before you close the card: if you close it earlier, the photo won't finish uploading.
    • If you see “Failed to upload image”, “Invalid file format (jpg, png, gif, webp expected)” or “File is too large (4 MB max)”, the editor removes that image from the text by itself, and the rest of the description is saved.

    Additional fields

    The collapsible “Additional fields” block holds nine more: “Name #2”, “Brief description based on attribute values” and seven fields “Extra field #1”…“Extra field #7”. The app rebuilds the second one itself every time the card is saved, so there's no point typing text into it.

    Other languages and translation

    If your account has one language, the section is a plain list of fields. A second language and beyond adds an accordion at the top with completeness chips, the “Expand all”, “Collapse all” and “Only incomplete” buttons, and translation.

    • The icon in the header of each language except the main one, with the tooltip “Translate all from ‹default language›”, translates all empty fields of that language from the default language one by one. It doesn't touch filled-in fields.
    • The “Translate from default language” icon next to each field does the same for a single field.

    This way, a Ukrainian version of a description is filled in from the Russian one in a minute, if Russian is your default language. To translate from a different language or many products at once, use bulk translation, where you choose the source language yourself.

    Prices and stock

    Three rows of three cells: five price fields, a live margin badge, two stock fields and the delivery cost. The currency is shown in the section header; prices are rounded to the number of decimal places set in the default currency.

    • Price: the price you sell at.
    • Cost price: read-only; under the field it says “Calculated automatically from price lists and the bundle; not editable”. The card never writes it: the value comes from the supplier's price list, the bundle composition, or a posted goods receipt, which writes its line price into the cost price (see warehouse inventory).
    • Margin / profit: not a field but a live badge. It updates as you type the price, before saving. If there's no cost price or it's zero, the badge says “no data”. The badge doesn't calculate a price from a margin: the rules that turn a supplier's price into yours are set in pricing rules.
    • RRP: the price at which the supplier recommends selling the product, for short.
    • Sale price and Old price: the promotional price and the crossed-out “before discount” price.
    • Stock status: a choice from a directory. The gear icon next to it opens “Manage availability statuses”.
    • Quantity and Delivery cost.
    The «Prices and stock» section of the product card
    1Cost price
    2Margin / profit
    3Stock status gear
    4Product price history
    1. Cost price — disabled field, the value comes from the price lists.
    2. Margin / profit — recalculated as soon as the price is typed.
    3. The gear next to «Stock status» opens the availability statuses manager.
    4. The product price history chip with a mini chart.

    Under the “Quantity” field, two extra lines can appear:

    • Stock breakdown by warehouse: “Warehouse A 12 · Warehouse B 3”. It appears when the product is linked to at least one warehouse.
    • “Reserved: N · Available: M”. It appears when warehouse inventory is turned on and open orders actually reserve some of the product. “Available” is the quantity minus the reserve; a negative value is highlighted in red.

    The section header has three links to companion windows: “Promotions” with its own counter, “Discounts” with its own, and “Product price history”. Next to the last one there's a of the price movement.

    The sparkline is drawn only if the history has at least two points; otherwise a plain chart icon is shown in its place.

    Inventory, dimensions and barcodes

    The “Inventory and logistics” section holds everything your warehouse, delivery and marketplaces need.

    First row: “Model”, “Warranty”, “Product condition”. Below it, on a separate row, is “Tax class”: the product's VAT rate, where the first option is “None” (see tax classes). The list to the right of the warranty is labeled “Warranty unit” and contains its units: “days”, “weeks”, “months”, “years”.

    Second row: “Min. order qty”, the “Subtract from stock” switch set to “Yes”, “Date Available” (a real date field with a calendar) and “Stock location”.

    Third row, dimensions and units: “Length”, “Width”, “Height”, “Length unit”, “Weight”, “Weight unit” and “Unit”, the product's unit of measurement from a directory (“piece”, “Pack”, “Kilogram”). The first list item, “---”, means no unit is set.

    Product condition

    The “Product condition” list is the last item in the first row, after “Warranty unit”: “New”, “Discounted”, “Used”, “Refurbished”. The default is “New”. The condition affects two things:

    • matching with price lists: a price list row is linked automatically only to a card in the same condition, so a supplier's discounted item won't end up in a new product's card;
    • export: the condition goes to Google Merchant (g:condition), eBay, Kaufland and the Horoshop template field as a value the channel accepts; a discounted item is “used” in Google.

    A card created from a price list gets the row's condition; loading a price list doesn't overwrite the condition of an existing card. How the app determines the condition and which values the channels get: Product condition.

    Weight unit and product unit

    • “Weight unit” comes from the system directory of weight units. It has two entries, “Kilogram” and “Gram”, and can't be edited in the interface. Choose a unit and enter the weight in it: 250 g is 0.25 in kilograms or 250 in grams; decimals are allowed.
    • “Unit” is the unit of the product itself, from the “Units of measurement” directory (“Directories” → “Base product catalog” → “Units”), which you can edit. How to merge “pcs” and “pieces” into one unit: see the article about units of measurement in import.

    Barcodes and SKUs

    The “Barcodes, product ID” group: “SKU”, “Manufacturer SKU”, “Supplier SKU”, “Supplier”, “EAN (European Article Number)”, “UPC (Universal Product Code)”, “GTIN”, “JAN (Japanese Article Number)”, “ISBN (International Standard Book Number)” and “QRCode”.

    You don't need to fill in all of them: day to day you need “SKU”, “Manufacturer SKU” and “EAN”. The rest are codes for a specific market or product type: UPC for North America, JAN for Japan, ISBN for books.

    Publishing, storefront and export flags

    The “Statuses and flags” section has sixteen switches in four groups. Each flag is read by a specific mechanism. The “Import protection” group is a separate topic: how to stop a price list from overwriting a price or a product.

    Publishing

    “Product enabled” is the main switch: turn it off and the product disappears from the storefront, which is called . Next to it are “Draft”, “Archived” and “Digital product”.

    Storefront

    “Popular Item”, “Best deal”, “New product”, “Sale product”, “Advertise”, “Gift”. These are labels for product collections on the website: the website decides what to do with them, and in the app itself they don't trigger anything. Turn them on only if your website can actually read them.

    Export

    “Export to file (to website)” is on by default. Turn it off when the product shouldn't be exported at all.

    You can't toggle “Exported”. It's a read-only system marker in the card, with the tooltip “Set by the export run: any product change clears it automatically”. Any card save resets the marker to zero, and the product goes into the next export. Once it's cleared, the app also resets it on all the product's photos and attributes.

    “Additional” and “Other fields”

    Both sections are collapsed by default; click the header to expand one.

    The “Additional” section contains:

    • “Status”: a directory of product statuses; the gear icon next to it opens the directory itself;
    • “Sort order”: a number you enter manually is locked (how this works);
    • “Points”, “Shelf life, days”, “Nutri-Score”, “Color (HEX)” with a live color swatch preview;
    • “Print template”: a read-only field with three icons (select, edit, reset); once a template is selected, a fourth one appears, print;
    • “Board”: a multiple choice of organizer boards, where the “---” item removes all links at once.

    Some fields are “just in case”: Nutri-Score, “Points”, “Shelf life, days”, “Color (HEX)”, “Delivery cost”, “Stock location”, “Min. order qty”. If you don't know why you'd need a field, you don't need it.

    “Shelf life, days” isn't a date but a number of days. The field is numeric and has no calendar: the app adds this number to the document date when it calculates the batch's expiry date (with no value, it uses 360 days). There's only one real date field nearby: “Date Available”.

    The “Other fields” section is built by the itself. It has two groups: “System fields outside sections” and “Custom fields”.

    • When you create your own product field, it appears here right away.
    • A field marked as read-only in the registry is shown locked; a custom field with the HTML editor turned on gets a full editor.
    • At the top there's a search by field caption: with a few dozen fields, it's faster than scanning by eye.

    How card completeness is calculated

    is the percentage in the right panel. It's calculated mechanically: the app takes the list of fields marked as required in the product grid settings, each has the same weight, and the filled-in ones are added up.

    By default there are nine such fields, so each one is worth 11.11%:

    • Name
    • Full description
    • Price
    • Manufacturer
    • Meta title tag
    • Meta description tag
    • Product URL
    • Photo (presence flag)
    • Attributes (presence flag)

    The sum is rounded up and capped at 100%. Then the number of empty required attributes is subtracted from the result: a product with all nine fields filled in but three empty required attributes shows 97%.

    • This subtraction has no lower limit: a product with an empty card and a dozen empty required attributes gets a negative percentage.
    • The set of required fields is configured per account, so in your app it may be different.
    • The percentage is recalculated on every save, but the new value appears in the right panel only after you reopen the card.

    The list under the progress bar is a different check and isn't part of the percentage: an empty meta description, a missing photo, an empty barcode, a language with no content fields filled in, and the info line “Photos: N · videos: N · files: N”. Each line is clickable and scrolls to the right section.

    Filling in a card for the first time

    Header, rail and bottom bar of the card

    The card is one long document, not a set of tabs. The overall layout is in the article about the product card; here are the details of each part.

    The header at the top: a thumbnail, the product name in large type, and below it SKU, MPN, ID, the manufacturer and the main category. The status badge (“On” or “Off”) sits in the same row as the codes. On the right: the “✦ AI” button, the “On site” button and the red “Delete” button.

    • Empty codes aren't shown: a newly created product has only the ID in its header.
    • Clicking any of the codes copies it to the clipboard and shows “Copied”.
    • The header name and the status badge change as you edit: type a new name and the title updates; clear the “Product enabled” checkbox and the badge goes grey.
    • “On site” opens the product page: the site address from your company details or from an export, plus the “SEO URL”, and also direct links to marketplaces. If there are several links, the button opens a list.

    The “✦ AI” button opens the consultant chat with questions about this particular product: “Where does this price come from?”, “How the product goes to the export”, “Supplier offers”, “Formula for a field”. Details are in the article on phrases for the AI consultant.

    An orange number on the button means the card has found a problem on its own:

    • the price is 0 for a product that goes to an export;
    • a product that goes to an export has no photo or description;
    • no supplier has it in stock;
    • the selected supplier's price list hasn't been updated for more than 14 days.

    A click sends the analysis to the chat, and the number turns grey. The product preview to the right of the catalog grid doesn't have this button — only the card opened in its own window does.

    The AI button in the product card header with a tooltip describing the problem found
    1AI button with problem counter
    2Tooltip with the problem
    1. AI button — the badge shows how many problems AI found in the card.
    2. Tooltip on hover — names the problem and invites a click to sort it out.

    The anchor bar under the header: Content · Media · Prices · Attributes · Inventory · Relations · · Statuses and flags · Additional · Activity. The bar is sticky and highlights the section you're reading.

    Some items don't always appear: “Variants (options)” — only if the product has variants; “Other fields” — if there's a field outside the sections or your own custom fields; the item for the product's page on the site — only for an Elbuz CMS store.

    The right rail runs next to the document and doesn't scroll with it. It has four cards, or five with the module that tracks the product on the site:

    • Status — the status badge and four dates: “Modified”, “Created”, “Date updated (price)”, “Stock status date”. An empty date shows as a dash.
    • Completeness — a percentage, a progress bar and a clickable list of what's missing. Clicking a line scrolls the document to that section.
    • Organization — “Manufacturer” (a dropdown directory with search; you can add a new manufacturer right here) and “Categories”: up to eight chips, the main one marked with a star, and a pencil that opens the categories window.
    • Identifiers — “Product ID (number)”, “Product ID (UUID)”, “Product ID on site” if filled in, and “Number of views”. The first three can be copied with an icon.
    Right rail of the product card: status, completeness, organization and identifiers
    1Completeness percent and progress bar
    2Clickable checklist
    3Manufacturer dropdown
    4Copy icon
    1. Completeness percentage and progress bar.
    2. Checklist under the bar — each row scrolls the document to its section.
    3. Manufacturer dropdown from the directory.
    4. Copy icon next to an identifier.

    The bottom bar is pinned to the bottom of the window: on the left, the save status; on the right, the “Print”, “Duplicate” and “Operation history” buttons. The last one opens the change log for this product.

    The “Media” and “Attributes” sections load as you approach them — about one screen before they come into view. That's why a card with a hundred specs opens as fast as an empty one.

    How exactly the card is saved

    The card has no “Save” or “Save and close” buttons — they were removed in the redesign. Instead, the bottom bar shows a label with three states:

    LabelWhat it means
    SavedThe server accepted the request; the time is added next to it: “Saved · 14:32”. This isn't the same as “all fields made it into the database” — see the difference in the tip below
    Saving…The form has gone to the server and there's no response yet. A dropped connection switches the label to “Save error”, so it doesn't hang in this state for long
    Save errorSome of the data didn't make it into the database. Full text: “Save error: some data was not written (code N). Reload the page and try again; if it persists, contact support.” The same state appears when no response came from the server at all — the connection dropped

    The rules are simple, but it's worth knowing them exactly.

    1. The countdown starts when you leave a field, not on every keystroke. While the cursor is in the “Name” field, nothing happens: you can type a paragraph for as long as you like.
    2. The pause is 1.2 seconds. Each new change restarts the countdown, so ten fields changed in a row go in one request, not ten.
    3. The whole form is sent, not a single field. A cleared checkbox is sent too — that's why you can't “partially save” the card.
    4. When you close the window, the card sends any unsaved edit. If the last change is still waiting for its pause, closing sends it without waiting. If everything is already saved, closing sends nothing.
    5. Media and attributes aren't part of autosave. They have their own requests and their own buttons inside the sections.
    Bottom bar of the product card window with the save status and action buttons
    1Autosave status
    2Print button with template arrow
    3Duplicate button
    1. Autosave status — reads Saved when all changes are written.
    2. Print button and the arrow for choosing a template.
    3. Duplicate button — creates a copy of the product.

    “Saved” means the database rejected none of the save requests, not that exactly what you expected was written. One save runs over twenty requests; if the database rejects even one, the card shows “Save error” with a code. But what's already written isn't rolled back — the save stays partial on purpose: it uses temporary tables that ROLLBACK doesn't restore.

    So after a “Save error”, reopen the card and see what was actually written. Another way to check is the “History” tile in the “Activity” section: it lists only the fields that really changed in the database.

    The second cause of a “Save error” is a dropped connection or an expired session. Then a “Session ended” window appears over the card with a “Sign in again” button. Sign-in opens in a new tab; the data in your form is still there, but it isn't written to the database.

    Sign in, return to this tab, change any field again and wait for “Saved”. If you close the window before the bar says “Saved”, the edit is lost.

    What Elbuz does when the card is saved

    One save isn't a single “write the fields” request. More than twenty steps run behind it, and you don't start any of them separately. Here are the ones whose effects you can see:

    • Product fields are written, along with texts in all languages; default-language texts are copied to the main table, where the product list reads them from.
    • The SEO URL is built. If the “SEO URL” field is empty, the program generates the address; if it's filled in, yours stays.
    • Price and quantity are copied to the default store — that's where the storefront reads them from.
    • Catalog field formulas are applied, if you have any. The “Apply formulas when editing” setting is on by default.
    • SEO generator templates in “Fixed text” mode fill empty fields — descriptions, meta fields, , tags — if an active template exists for the product's main category or for all categories. A template skips fields you filled in by hand, so it won't overwrite a manual edit. Except tags: with tag generation on in the template, they're rebuilt on every save.
    • Completeness is recalculated and the “Modified” date is updated.
    • The change log is written: the program compares the product before and after and stores the difference for each field. This is what the “History” tile in the “Activity” section shows.
    • The search index and duplicate-detection fingerprints are rebuilt, and the store for this product is cleared.

    A practical takeaway: saving a card with many fields and formulas turned on isn't instant. “Saving…” may stay for a second or two, and longer on a large card — that's normal. A failed save looks different: the label changes to “Save error”.

    Separately: just opening the card is also recorded in the work log as “Product card opened”. So the log shows who viewed the product and when, even if they didn't change anything.

    What goes into the copy, how the card is printed and what disappears with the product

    The “Duplicate” button in the bottom bar asks “Create a copy of this product?”, shows “Processing data, please wait...” and opens the copy's card in its own window.

    • The copy gets a name with the “copy_” prefix.
    • Categories, stores, warehouses, attributes and photos are carried over with it, as well as promotions, discounts, files, videos, related and recommended products, and the specification.
    • “SKU”, “Manufacturer SKU”, EAN and the flags, including “Fixed Price” and “Do not update”, are carried over from the original as is; only “Exported” is cleared. Change the codes and the name in the copy.
    • The copy's SEO URL is the original's address with the copy number.
    • “Product ID on site” and the link to the price list and its row are cleared, and the copy gets a new “Product ID (UUID)” — imports and exports to the site treat it as a separate product.

    Photos are copied as files, so a product with a dozen images takes noticeably longer to duplicate than an empty one — the copy's window will open by itself.

    The “Print” button has two parts:

    • clicking the button itself prints the product to PDF with the template selected in the “Print template” field; if no template is selected, the “Standard card” is printed in ;
    • the arrow next to it opens a menu: “Standard card” (checked if no template is selected), all product print templates, and “Select print template”.

    Each template's format comes from its settings; PDF by default.

    The red “Delete” button in the header asks “Delete entry?” and shows the product ID. After you confirm — “Record deleted”, the card window closes by itself, and the list behind it refreshes.

    Deletion is permanent. There's no Trash and no undo. More than twenty kinds of data disappear with the product:

    • descriptions in all languages, links to categories, stores and warehouses;
    • attributes, photos together with their files, videos;
    • related products, reviews, Q&A, product sets, SEO URLs, promotions and discounts;
    • this product's variants — each such variant is a separate .

    The service keeps nightly copies of the whole database for the past week, but that's no “undo”: restoring one rolls the whole database back a day, including orders and edits made since. It's started manually: “Account” → “System settings” → “Other settings” → “Restore DB backup” tile. The copy has no photos — the files are gone for good.

    The product is also deleted on a website connected via a tunnel, and drops out of any sets it belongs to.

    What isn't deleted is price list rows. They're only unlinked: the match is removed, and on the next update these items become unmatched. So after deletion the product may come back from the price list — without your edits.

    What to do when a field doesn't behave as expected

    Common problems
    What you seeWhyWhat to do
    The bar says “Saved”, but the fields went back to their previous values Your group doesn't have the “Edit” right for these fields: the server accepts the request but returns the old values to restricted fields Ask the account owner for the right — the “Tables” tab in “Group permissions”, product grid (access)
    “Saving…” stays for more than a few seconds The server is still working: a save runs more than twenty requests, and field formulas add their own. A dropped connection would switch the label to “Save error” Wait for “Saved” and don't close the window until the label changes (autosave)
    Cost price can't be edited The field is locked on purpose: the card doesn't save it, and the value comes from a price list, the bundle composition or a goods receipt Change the purchase price at the source: in the price list, in the bundle composition, or by posting a goods receipt with the new price (prices)
    Margin shows “no data” Cost price is empty or zero, so there's nothing to calculate from The value appears once the product gets a cost price from a price list (prices)
    The “Exported” flag cleared itself after an edit This is by design: saving the card resets the export marker, and once it's cleared, it's also reset on photos and attributes Nothing; the product simply goes into the next export (flags)
    There's no “Reserved / Available” line under the quantity Warehouse inventory is turned off Warehouse inventory is turned on in the Documents module settings, not in the card (stock)
    You inserted a photo into the description and closed the card, and the image (or the whole description) is missing The image is uploaded to the server in a separate request; the card was closed while the bar showed “Saving…”, or the upload failed and the editor removed the preview Insert it again, wait for “Saved” and only then close the card. With “Invalid file format”, save the image as jpg, png, gif or webp; with “File is too large”, compress it to 4 MB (photos in the description)
    You filled in a field, but the completeness percentage didn't change The right panel is drawn once, when the card opens Reopen the card (completeness)
    “Select a product category!” The card is being opened with no product and no category — nothing is selected in the tree on the left Select a category in the product list tree and try again
    “Select a product category” or “Enter a product name” in the “Add product” dialog Both dialog fields are required Fill in the category and the name; you can create the category right in the dialog with the “Create category” link (creating a product)
    “Enter a category name” The “Category name” field in the category creation panel is empty Enter a name or pick an existing category from the list (creating a product)
    “Select a manufacturer from the list!” The select button was clicked, but no row is highlighted in the manufacturer directory Highlight a row in the dropdown directory and confirm your choice
    “Manufacturer name required!” The name field in the new manufacturer dialog is empty Enter the manufacturer name
    “Processing data, please wait...” doesn't go away for a long time after “Duplicate” Copying carries photos over as files, and the response comes only at the very end Wait: the copy's card will open by itself (duplicating)
    “Record deleted” — and the product's variants disappeared with it Deleting the main product also deletes all its option products There's no recovery. Before deleting a product with variants, make sure you don't need the variants (deletion)
    The card has no “Delete” button No right to the “Delete product” button in the “Products” window Ask the account owner for the right: deleting from the product list is closed by the same right. The preview next to the grid never has the button — open the card in its own window (access)
    The card has no “On site” button The product has no links at all: your company's site address isn't filled in, and there are no active exports or direct marketplace links Fill in the site address in your company details or set up an export
    The anchor bar has no “Variants (options)” item The product has no child products That's expected: the section appears only for a main product with variants (card layout)

    FAQ

    Which product weight unit should I choose, and where do I set it?

    Next to the “Weight” field in the “Inventory and logistics” section there's a “Weight unit” list with two entries: “Kilogram” and “Gram”. Enter the weight in the unit you chose: 250 g is 0.25 kg or 250 g (units).

    I insert a photo into the description and close the editor, but the description isn't saved. Where's the “Save” button?

    There's no button; the card saves itself. After inserting, wait for “Saved” in the bottom bar and only then close the card (photos in the description).

    How do I quickly fill in the Ukrainian version of a description if there's only a Russian one?

    In the header of the “Ukrainian” language, click the “Translate all from ‹default language›” icon. This works if Russian is the default language; otherwise use bulk translation (translation).

    How can I tell where a field's value came from: a price list, a formula or a person?

    The card itself doesn't show this. Open the “History” tile in the “Activity” section: it shows every change to the field.

    Can I enter my own cost price manually?

    No, the field is read-only. Cost price comes from a price list, the bundle composition or a goods receipt (prices).

    Where to find it and who has access

    Menu
    Directories → Base product catalog → Products → product card
    Access right
    the “Products” window in “Group permissions”
    Field permissions
    the same as for the product grid: the “Tables” tab in “Group permissions”

    A field without the “View” right isn't shown in the card at all, and a field without the “Edit” right opens read-only. There's no separate set of permissions just for the card. How to open the card and how it saves is covered in the article about the product card.

    • The card also opens from catalog analytics, the organizer board and AI consultant replies, and from the card itself — via “Duplicate” and the “Card” link in the “Variants (options)” section.
    • A field without the “View” right isn't shown in the card; a field without the “Edit” right is read-only. On save, the server returns the previous values to restricted text fields.
    • AI text generation buttons next to fields are visible right away; in a demo account — until the daily AI spending limit is used up.
    • When you close a card opened from a list, the list refreshes by itself.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free