Skip to content
    Changelog

    What's new and improved in Monokaido

    Every entry comes here straight from the production release — with its date, module and type of change.

    Filters· 632 entries
    Module
    New featureE-commerce6 May 2026

    Prices in Hungarian forint (HUF) — shown without decimals

    Prices in Hungarian forint are now shown without decimal places, as is usual in Hungary. The forint has no unit smaller than 1 forint, yet prices used to appear as, for example, “4,990.00 Ft”, which looks wrong to Hungarian readers — the correct form is “4 990 Ft”. Decimals are now left out automatically for HUF and other currencies without them, across the admin, the shop and the feeds. It helps anyone selling on the Hungarian market.

    New featureVendors6 May 2026

    Trek — product feed and availability feed in a single vendor

    Trek, one of the largest bike suppliers, sends two separate feeds: one with product data (names, descriptions, photos) and one with availability and prices. Until now this meant two separate vendors in Monokaido, both of which you had to maintain — duplicated settings and the risk that one imported while the other did not. Now a single vendor handles both feeds: the product feed imports products, variants and photos, and the availability feed then only updates availability and price on the same variants. If the availability feed does not run before the next product sync, the import gets the “Partial” status — so you see exactly which feed ran when and with what result. Existing pairs of Trek vendors are merged gradually at the next sync.

    FixERP and transfers5 May 2026

    Fixes — feed prices, photos and descriptions in the Grandus transfer, pagination

    A round of fixes to feed prices, Grandus transfers and lists. (1) Supplier feed prices — for the Level Sport Koncept feed, which sends VAT-inclusive prices without a VAT rate, VAT is now deducted using the vendor’s fallback rate; price mapping for Level Sport Koncept, Davorin and ProfiBike is more reliable, the Vavrys retail price (MOC) is used as the selling price, and CTM feed price processing has been reworked. (2) Vavrys variants — deactivating variants is fixed. (3) Photos in the Grandus transfer — colours are converted to sRGB, photos with a wrong type or extension are converted correctly, other formats become JPEG before upload, and cancelling a transfer also works during retries. (4) Descriptions and category icons in Grandus — the long description goes to the right field and category icons have the correct address. (5) Grandus credentials — if the stored credentials cannot be read, the transfer shows a warning instead of a silent “OK”. (6) Long ERP transfers — a long-running transfer is no longer wrongly flagged as stuck, and only one transfer of each type runs per configuration. (7) Custom statuses and pagination — filtering by custom statuses is fixed and pagination respects the maximum of 200 rows per page. (8) Products with several templates — template compliance takes all of a product’s templates into account.

    ImprovementProducts5 May 2026

    Improvements — templates, parameters, Grandus transfer and shop dashboards

    A round of reliability improvements across the catalogue, transfers and the shop. (1) Products with several templates — template compliance now correctly takes all of a product’s templates into account, and saving many template parameters at once is faster. (2) Bulk parameter saving — a bulk save no longer blocks other users editing at the same time. (3) Photos in the Grandus transfer — you see every problematic photo of a transfer in one overview, and parallel transfers no longer overload each other while compressing photos. (4) Categories in Grandus — transferring categories is more reliable thanks to checks before sending and the adjustment of characters Grandus cannot store. (5) File uploads and sub-vendors — simultaneous uploads for the same vendor no longer collide, and sub-vendor matching is faster. (6) Shop dashboards — key figures are the same size on every dashboard, and currency analytics copes with missing or invalid exchange rates.

    New featureProducts5 May 2026

    Product excluded from the storefront — now also left out of every export feed

    A product marked as excluded from the storefront is now automatically left out of every export feed too — Heureka, Google Shopping, Facebook and the sitemap. Until now it only disappeared from the shop but was still exported to price-comparison feeds, so Heureka, for example, listed a product you did not offer in your shop. It is also hidden from listings, search and its product page in the shop — anyone opening a direct link gets a “not found” page instead of an unfinished draft.

    New featureVendors5 May 2026

    CSV or Excel upload — for suppliers without a feed URL

    A supplier that has no feed URL and emails you its catalogue as an Excel or CSV file can now be added as a new vendor type with manual file upload. You upload the CSV or XLSX file directly in the app. You set up the column mapping only once — every later upload replaces the previous file and starts a normal sync. The import then runs exactly as it does for vendors with a dynamic XML, JSON or CSV feed. Simultaneous uploads for the same vendor are processed one after another.

    New featureVendors5 May 2026

    ETIM (BMEcat 5.0) — new vendor type with a feed URL or file upload

    A new ETIM vendor type supports the industrial BMEcat 5.0 standard. BMEcat is an international XML format used mainly for electrical and electrical-installation materials (transformers, circuit breakers, cable trays) — suppliers use it to send products with ETIM classification, that is a category plus technical features in standardised units. The catalogue can come from a URL (fetched at every sync), or you can upload it as a file when the supplier sends it by email. The catalogue may be gzip-compressed, and you can upload files of up to 200 MB. A setup wizard guides you when you add the vendor — there is no mapping to write by hand, because the ETIM structure is fixed by the standard.

    New featureAI5 May 2026

    AI activity on the product detail — the AI history of a single product

    The product detail now has an “AI activity” block showing the history of every AI task run for that product — description generation, translations, parameter extraction, template matching, scene generation and more. Until now AI logs were only available on the shared AI logs page, where you had to filter your way to the product. When you look at a product, you now see straight away which AI services were applied to it, how many tokens they used, what went in and what came out, and when they ran.

    New featureCategories5 May 2026

    Category and template — subcategories inherit the template from the nearest parent

    You can now optionally link a parametric template to a manual category. Subcategories inherit it automatically from the nearest parent category that has a template. Vendor categories cannot have a template, so category trees imported from vendors do not start assigning templates on their own. The flow action “Apply Category Template” assigns a product the template derived from its category; such an assignment is marked as made by category, so AI re-matching does not overwrite it. When you delete a template, the link is removed automatically and the category itself stays in place.

    New featureAI4 May 2026

    AI template matching — products get one or more parametric templates automatically

    AI can automatically assign a parametric template to products, or several templates ranked by how well they match. First AI writes a short summary of each template once (purpose, product types, tags, keywords, brands), then it summarises each product in the same way from its name, description, parameters and category, and finally Monokaido compares the two and picks the best matches. A product can have several templates in a set order, and each records whether it was assigned by a person, by AI or by category, together with a confidence level. Parameter completeness is calculated across all of a product’s templates. When you change a template’s name, description or parameters, Monokaido flags it, so you know exactly which summaries need regenerating. You can view the AI summary in a collapsible card on the template and check that AI understood it correctly before you run matching.

    New featureProduct Flows4 May 2026

    Product flows — a condition on template completion instead of “has a template”

    The condition in product flows could previously only check whether a product had a parametric template assigned. It has been replaced by two richer fields: “Template Completion” (no template, incomplete, complete) and “Template Completion %”, the share of required parameters that are filled in. You can now build a rule such as “if a product has a template and at least 80% of its required parameters are filled in, switch it to published” — which was not possible before. Existing flows were converted automatically to the closest equivalent, so your old rules behave exactly as before without any manual changes.

    New featureProducts30 April 2026

    Product detail — delivery time under availability and a “Transferred” badge

    The product detail now shows the delivery time from the feed under availability (for example “2–5 days” or “In stock”), so you no longer need to open the variant detail to see a delivery estimate. A product that was successfully transferred to at least one ERP system gets a “Transferred” badge with a tooltip showing where and when it was last sent. In the product list you can see at a glance which products are already in the ERP and which are still waiting to be transferred.

    New featureVendors30 April 2026

    CTM — text availability from the feed is converted into stock levels

    The CTM feed sends availability as text, such as “In stock”, “In transit” or “On demand”. The import now always converts these values into stock numbers the same way: “In stock” becomes a high stock level, “In transit” a level in the low-stock range, and “On demand” zero with an on-demand flag. CTM products no longer appear as unavailable in the shop when the feed says they are in stock.

    New featureERP and transfers29 April 2026

    ERP transfer — optional automatic re-sync of changed products every 5 minutes

    Transfer settings have a new “Automatic product re-sync” toggle, off by default. When it is on, Monokaido sends products changed since the last run to the ERP every 5 minutes, without you having to start the transfer by hand. The check never runs twice at the same time. Only products that have actually changed are sent, so Grandus, for example, receives no needless updates of unchanged products.

    New featureVendors28 April 2026

    Vavrys — variants that disappear from the feed are deactivated automatically

    The vendor Vavrys only sends currently available variants in its feed. Until now old variants stayed active and had to be removed by hand. On every sync the import now marks every variant missing from the current feed as inactive and sets its stock to 0. The shop stops offering these variants automatically, while the product itself stays active as long as it has at least one active variant.

    New featureProducts28 April 2026

    Product detail — transfer to your ERP straight from the product, with cancel

    The product detail has a new block for transfers to your configured ERP systems. The block adapts to each system — Cybersoft i6 shows its own actions, Grandus E-commerce shows different ones. If you click Cancel while a transfer is running, it stops immediately instead of waiting 30 seconds. Once a transfer starts, the block shows its progress live.

    New featureCategories27 April 2026

    Manual categories — drag and drop between parent categories too

    In Manual Categories you can now drag a category under a different parent, not just reorder it within the same one. The move happens in one go: the category lands under its new parent at the chosen position, and the other categories in both the old and the new parent shift so the order stays without gaps. Every move is recorded in the audit log.

    New featureERP and transfers27 April 2026

    Transfer to Grandus — only products from selected categories

    Transfers to Grandus have another filter: a list of allowed categories. You select some categories from your tree, and only products in those categories and their subcategories are sent to Grandus. This is useful when you manage a broader catalogue but want a particular Grandus shop to receive only part of it, for example bikes only, without accessories and clothing.

    New featureERP and transfers27 April 2026

    Transfer to Grandus — filter by product status

    When setting up a transfer to Grandus you choose which product statuses should be transferred. Most teams pick only active or for-sale products, so Grandus is not flooded with unfinished drafts or deactivated products. If you select no status, nothing is transferred; an empty selection does not mean “everything”.

    New featureERP and transfers27 April 2026

    Grandus E-commerce — send products and categories back to Grandus

    Monokaido no longer only imports from Grandus — it can now also write products and categories into it. The first transfer creates the product in Grandus and later ones update it. Products that have not changed since the last successful transfer are skipped, so a full sync of 67,000 products takes minutes instead of 74 hours. Products that Monokaido itself sent to Grandus are skipped when importing from the same Grandus, so a two-way sync creates no duplicates. Only one transfer of a given type runs per configuration at a time, so a scheduled run never clashes with a manual start, and long transfers of large catalogues are no longer wrongly flagged as stuck. Categories are checked before sending and their names adjusted so that Grandus accepts them, and photos larger than 2 MB are compressed before upload.

    FixE-commerce26 April 2026

    Fix bundle — VAT in feed prices, cart and checkout, loyalty points

    We fixed several bugs that could affect prices, the cart and loyalty points. (1) VAT in feed prices — For feeds with a custom mapping, VAT was not deducted from prices even when the feed required it, so products appeared 20–23% too expensive in the shop; we also checked imports whose default VAT rate is not 20%. (2) LSK availability — The availability sync no longer resets the VAT rate to zero or deletes the purchase price. (3) Cart and checkout — Rapid clicking no longer creates duplicate carts; stock reservations, coupon usage and customer statistics (order count, total spent) are recorded reliably, and simultaneous payment events from Stripe are processed one at a time. (4) Loyalty programme — When an order status changes, points can no longer be awarded or reversed twice, and points expiring while being redeemed in the cart no longer corrupt the balance. (5) Shop limits — A cart holds at most 200 items and a customer can save at most 50 addresses. (6) Account protection — We strengthened the protection of sign-in and customer accounts.

    ImprovementInfrastructure26 April 2026

    Reliability across the app — simultaneous edits, clear errors, new password pages

    A large wave of reliability improvements you will notice throughout the admin. (1) Simultaneous edits — Two admins can edit the same record at the same time without overwriting each other’s changes; this covers products, variants, categories, vendors, translations, pages and banners, payment and shipping, exports, flows and more. (2) Scheduled jobs without duplicates — Automatic translations, exports and ERP synchronisation no longer start twice at once, so AI is not charged twice and exports are not duplicated. (3) Value checks — Money amounts and stock can no longer be negative, and ranges such as the minimum and maximum order total must make sense. (4) Clear error messages — When saving fails, for example because of a duplicate or invalid value, you see a readable message instead of a technical error. (5) Categories in Grandus — Creating categories in Grandus is more stable, including correct handling of hidden parent categories. (6) Password and sign-in pages — The “Forgot Password” and “Reset Password” pages have a new look, form validation messages are fully translated, and the 404 page and the error page follow your system’s light or dark mode.

    New featureProducts25 April 2026

    Sell at cost — a deliberate zero with a “Manual” badge

    Selling at cost is now supported. An admin can clear the purchase price or deliberately set it to 0, and Monokaido tells the two apart everywhere: an empty value means the purchase price is unknown, while zero means you are deliberately selling at zero. On the product detail such a price shows as €0.00 with a “Manual” badge, so you can see at once that the value is intentional and not an import error.

    New featureVendors25 April 2026

    Default margin for vendors and brands — plus the origin of every purchase price

    Vendors and brands now have an optional “Default margin (%)”: when the feed has no purchase price, Monokaido derives it from the selling price using this margin. Every purchase price also records where it came from — the feed, calculated from the margin, set by hand by an admin, or unknown. On the product detail you can see the origin of the value, and when reviewing prices you know exactly what was recalculated and what came straight from the vendor. We also fixed a bug where a cleared margin was saved as 0; a margin of 0 is now respected.

    New featureVendors25 April 2026

    VAT fallback region — correct prices even from feeds without a VAT rate

    You can now set a VAT fallback region on a vendor. When a feed has no VAT rate or sends it empty, Monokaido uses the VAT rate of the selected region instead of guessing. This solves a long-standing problem with feeds that did not send VAT — previously the shop showed the wrong price including VAT. A company can have exactly one default region.

    Let's try it on your own catalogue

    We'll walk through your feeds, categories and parameters live.