Magento remains the source.
Product names, URLs, images, categories and additional product attributes come directly from Magento. Multiple SKUs are kept separate so that AI does not mix product information or invent facts.
Vermontas Ritus is the editorial control centre for Magento 2 and Hyvä. Product knowledge is collected, structured, developed with optional AI assistance, reviewed, approved, scheduled and published. A calm, traceable process for content that originates in the shop. All content can also be created and edited completely manually; AI assistance is optional.
Works without AI: Blog articles, SEO copy and social media content can be written and maintained entirely by hand.
Good content is not created by speed. It is created by order.
Ritus brings ideas, product knowledge, AI assistance, editorial decisions and publishing into one continuous flow. No frantic switching between the shop, notes, social platforms and separate content tools.
Ritus does not make content more arbitrary. It makes the path to publication traceable.
Ritus connects three areas that still live in separate tools in many companies.
Product names, URLs, images, categories and additional product attributes come directly from Magento. Multiple SKUs are kept separate so that AI does not mix product information or invent facts.
Ritus can create articles, teasers, SEO data, social media copy, CTAs and hashtags. AI generated fields remain identifiable. Manual changes are marked as Edited and remain traceable through version history.
After review and approval, content can be published to the Magento blog, Facebook, Instagram Feed, Instagram Stories and Telegram. Each channel has its own time and status.
Not a collection of isolated plugins, but one coherent editorial environment.
Blog overview, article pages, categories, search, filters, pagination, Store View assignment, featured images, related products, readable URLs, canonicals, metadata, preview and scheduled publishing. The frontend integrates seamlessly into the existing Hyvä layout and follows the shop’s existing design, without requiring time consuming adjustments to colors or the basic visual styling.
The Ritus blog includes structured data for BlogPosting, WebPage, BreadcrumbList, CollectionPage and ItemList. Search pages remain noindex and preview content is not indexed.
Topic, Store View, campaign, products, featured image, expert notes, additional AI instructions, article HTML, SEO fields, social media copy, CTA, hashtags and preview in one place.
Products are selected through a Magento Admin modal and grid. The first SKU is the main product, while additional SKUs extend the context. Product chips clearly show SKU and name.
Ritus can create titles, teasers, articles, meta titles, meta descriptions, Instagram copy, Facebook copy, Telegram copy, CTAs and hashtags from the assigned Magento data.
All editorial content can be created and edited completely manually. Titles, teasers, articles, SEO fields, social media copy, CTAs and hashtags can be maintained without AI. Planning, blog, campaigns, calendar and publishing also work without an OpenAI connection.
Terra is the Ritus default and balances quality with economical API usage. Sol is available for particularly demanding content, while Luna is intended for fast and cost efficient generation at higher volume. The customer's own OpenAI API account is used.
Editorial guidelines and additional AI instructions control tone, focus and structure. Additional Magento product attributes can be explicitly released as AI context.
Ritus deliberately separates generation from publication. Content can be reviewed, edited and approved before publication becomes possible.
Earlier content states remain traceable. This makes it visible what AI created, what was changed editorially and how content developed before approval.
Content can be assigned to campaigns. Related blog and social media publications are visible together, including campaign based auto publish behaviour.
Scheduled and already published content becomes visible over time. Each social media channel can have its own publication date.
Facebook posts, Instagram feed posts, Instagram Stories and Telegram messages can be published directly from Ritus or scheduled through Magento Cron.
Temporary errors can be retried automatically. Each channel has its own status, publishing overview and traceable publication log.
Facebook, Instagram and Telegram can be tested directly in Ritus. Account, destination and basic availability are checked before scheduled content depends on them.
Before publishing, Ritus checks content, images, SEO fields, channel requirements, connections and publication status. Problems become visible before they become public.
Images can be prepared, cropped and adapted to suitable aspect ratios for Feed, Story and Blog without leaving the editorial workflow.
Product presentations, guides, news, promotions or seasonal content can be reused as content types with appropriate guidance, writing rules and CTA structures.
Ritus can automatically add unique source, medium, campaign and content information to published links. When a visitor enters the Magento shop through such a link, that visit can be attributed to the originating content and channel throughout the subsequent shop interaction.
The performance overview connects published content exclusively with measurable behaviour in the Magento shop. Visits, carts, orders, revenue and conversion can be attributed to content, campaigns and channels.
Connect OpenAI if desired, check social media channels, verify the blog and create the first piece of content. Onboarding guides the user through the few steps required to get productive.
Cards, status indicators, section navigation, a sticky action bar, focus mode, clear empty states, responsive layouts and a calm visual reaction during AI creation reduce distraction.
The Ritus Admin interface is translated for en_US, de_DE, de_CH, fr_FR and it_IT. The Swiss German translation consistently avoids ß.
AI generated article content is sanitized before use, reducing unwanted or technically unsuitable HTML structures in editorial content.
AI may accelerate. It must not replace responsibility.
Ritus marks AI generated fields, distinguishes editorial changes and deliberately keeps human approval in the process. The machine formulates. A person decides what gets published.
Ritus does not automate at any cost. The workflow shows where content currently stands and what is still missing before publication.
Since 2 August 2026, the transparency obligations in Article 50 of Regulation (EU) 2024/1689 on artificial intelligence apply. For AI generated or manipulated text published to inform the public on matters of public interest, Article 50(4) generally provides for disclosure.
The Regulation also includes an important exception: the disclosure requirement for such text does not apply when the AI content has undergone human review or editorial control and a natural or legal person holds editorial responsibility for publication.
Each channel remains independently controllable without content having to be copied back and forth between systems.
The strongest functions do not need to be the loudest. Ritus checks connections, images, publication readiness and tracking before content moves outward.
Ritus measures where impact becomes concrete for a Magento shop: inside the shop itself. Unique attribution on published links can show which content, campaign and channel led to visits, carts, orders and revenue.
Ritus does not read reach, likes, reactions, comments, impressions or other platform specific social metrics from Facebook, Instagram, Telegram or other services. The performance overview deliberately focuses only on measurable impact inside the Magento shop.
Ritus is intentionally built close to Magento. Commerce data and editorial work remain part of the same environment.
Ritus already includes the complete technical foundation. Integration, setup and handover are planned to fit your Magento and Hyvä environment.
If Ritus fits your environment directly, the content suite is integrated and configured accordingly. Where customizations are useful or desired, they are considered deliberately. Before work begins, you receive a transparent proposal for integration, setup and handover.
Scope and price depend on your shop environment and the concrete requirements. Ongoing maintenance, updates and personal support can be agreed separately where required. External usage costs, for example for OpenAI or connected platforms, are not included.
Vermontas Ritus is a premium content suite for Magento 2 and Hyvä. It combines Magento product data with either fully manual or AI assisted content creation, its own blog, campaigns, calendar, approval workflow and social media publishing in one editorial environment.
No. Ritus can be used as a complete editorial content suite without an OpenAI connection. Articles, teasers, SEO fields, social media copy, CTAs and hashtags can all be written and edited manually. Planning, campaigns, blog, calendar, approvals and publishing work independently of AI generation.
Ritus offers GPT-5.6 Terra, GPT-5.6 Sol and GPT-5.6 Luna. Terra is the default and provides a balanced combination of quality and API cost. Sol can be selected for particularly demanding content, while Luna is intended for fast and cost efficient generation at higher volume. The customer's own OpenAI API account is used.
Ritus can create titles, teasers, articles, meta titles, meta descriptions, Instagram copy, Facebook copy, Telegram copy, CTAs and hashtags. The basis is the assigned Magento product data, expert notes, writing guidance and additional editorial instructions.
Product data from multiple SKUs is kept separate. AI receives structured product information from Magento and is instructed not to invent product facts or mix facts between products. Human editorial approval remains part of the workflow.
Ritus supports Facebook posts, Instagram feed posts, Instagram Stories and Telegram messages. Each channel has its own publishing time, status and log entry.
Yes. Ritus includes its own Magento 2 and Hyvä blog with categories, search, filters, pagination, Store View assignment, featured images, related products, readable URLs, canonicals, metadata, preview, scheduled publishing and structured data.
Yes. Approved content can be published immediately or scheduled. Magento Cron handles scheduled publishing. Social media channels have automatic retries for temporary errors and an individual status per publication.
Before publishing, Ritus checks important requirements such as content, images, SEO fields, channel connections, image requirements and publication status. Issues are made visible before content goes public.
The media workspace prepares existing images for the intended channels. This includes cropping, suitable aspect ratios and previews for the blog, Instagram feed and Instagram Stories.
Not for the Ritus workflow. Product knowledge, editorial content, planning, blog and the supported social media publications are managed directly from Magento.
Yes. The commercial version of Ritus is deliberately designed for Magento 2 with Hyvä, allowing the frontend integration to stay focused without additional compatibility layers.
Article 50(4) of Regulation (EU) 2024/1689 generally requires disclosure for certain AI generated or manipulated text published to inform the public on matters of public interest. That disclosure requirement does not apply to such text when it has undergone genuine human review or editorial control and a natural or legal person holds editorial responsibility. Ritus supports this human review and approval process. AI generated fields remain marked internally in the Admin, are deliberately approved after substantive review, and are not automatically published with a visible 'AI generated' label. The publication check supports the process technically but does not replace human review.
Yes. The Ritus blog includes Schema.org markup for BlogPosting, WebPage, BreadcrumbList, CollectionPage and ItemList. Search pages remain noindex and unpublished previews are not indexed.
Ritus is integrated as a complete technical foundation into the existing Magento and Hyvä environment. Scope and price therefore depend on the shop environment, the required channels and the concrete setup or customization requirements. A transparent proposal is provided before work begins.
A content system for Magento shops that are no longer looking to simply produce more content, but want a reliable path from knowledge to publication.