Common questions we get about Ovesio, translations, integrations, pricing and support.
Ovesio is an AI-powered translation and content-generation platform that combines multiple translation engines (DeepL, Google, Microsoft, OpenAI and others) and an internal quality layer to pick the best result, so you get fast, high-quality translations and SEO-ready product copy automatically.
Merchants and teams that need to localise large product catalogs, agencies, and content teams who want automated multilingual SEO and product descriptions, in short, e-commerce stores and sites that need scale and quality.
Ovesio supports translation into 29+ languages. Here is the full list of supported languages.
The AI Inspector is Ovesio's built-in quality control layer, it compares outputs from multiple engines and applies selection/heuristics so the final text is closer to human quality while staying automated. This reduces manual corrections and improves consistency.
Create an account on Ovesio, choose a plan or trial, then follow the platform's setup wizard to connect your store (API keys, plugin or platform integration). The docs include step-by-step guides for common platforms.
Yes, Ovesio offers a WooCommerce/WordPress plugin that enables one-click translation of products, posts and pages without code. It's designed for no-code setup and integrates with common multilingual plugins.
Yes, Ovesio supports bulk and automatic catalog translation (it can detect new products and translate them automatically after setup). Use the one-click imports for platforms like Shopify, WooCommerce and Magento.
Yes, after automatic translation, you can review and manually edit results in the platform or via your CMS; Ovesio also provides tools and the AI Inspector to reduce the need for manual fixes.
Ovesio runs multiple engines (Google Translate, DeepL, Microsoft Translator, OpenAI/GPT and others) in parallel and uses the AI Inspector to choose the best output for each string.
Ovesio provides connectors and plugins for major platforms (Shopify, WooCommerce, Magento, and more). If you have a custom platform, Ovesio exposes an API for integration.
Yes, Ovesio documents API endpoints for authentication, translation jobs and catalog sync so developers can automate workflows and integrate bespoke platforms. See the docs for full API details.
Ovesio offers tiered subscription plans and credit-based usage; billing is automatic and monthly by default. Exact pricing and plan comparisons are listed on the Prices page, and there's a cost estimator to calculate credits for your project.
Subscription credits are tied to your subscription; separately purchased credit packs typically have a validity period (check your plan). If you run out of credits you can buy additional packages from the dashboard to continue processing.
Ovesio publishes entry-level plans and occasionally trial periods, check the Prices page or contact sales for the latest offers and a tailored quote.
Ovesio provides privacy and cookie policies detailing how text and metadata are processed; sensitive data handling and retention are described in those policies, review the Privacy Policy for full details or contact support for GDPR-related questions.
Ovesio offers support via the contact form and documentation; for account or integration help use the Contact page in your dashboard or the site contact form. For urgent or enterprise enquiries, reach out via the contact form to get a direct reply.
First, check the 'Billing' section in your Ovesio account. If the invoice or license email is missing, open a support ticket via the Contact page with your account email and order ID, support will re-send invoices/licenses.
The API provides endpoints for sending translation requests (/translate/request
), checking their status (/translate/status/{id}
), and getting supported languages (/translate/languages
). Responses are standardized in JSON.
More details about the API can be found in the documentation section.
All requests require a header X-Api-Key
, which is unique to each project. The API key can be generated and managed from the "Settings" section of the platform.
Applications must include the following parameters:
from
(source language),to
(target language),content
(text to be translated).Use the GET /translate/status/{id}
endpoint to get information about the status of the request (Pending, Started, Completed, etc.).
Use the GET /translate/languages
endpoint, which returns an array of the supported language codes and names.
Workflows define how requests are processed, including the translators used, AI enablement, and callbacks. The configuration is done from the "Workflows" section of the platform.
Context helps to obtain more accurate translations by specifying additional details (e.g. "economic terms" or "electronic products").
The system automatically detects duplicate requests and reuses existing translations. The option can be disabled in the workflow.
Feeds allow automatic uploading of data for translations on a daily basis, without using the API. Users can set up feeds for categories, products, or other information.
Large texts are automatically divided into subtasks and translated into fragments. Once completed, the texts are brought together in a coherent format.
The AI evaluates translations based on criteria such as accuracy, coherence, and context. The translation with the highest score is selected.
The "Search and Replace" feature allows users to edit translations and resubmit them via API or callback.
Users can create projects from the "Projects" section, with each project having customized settings for workflows and translations.
Translations associated with a deleted project are permanently lost. It is recommended to keep important projects to avoid additional costs.
The graphs and reports in the "Statistics" section show your daily, weekly, or monthly consumption, along with your total costs.
In the statistics tab, you can see the translators that delivered the most accepted translations. Based on this you can either remove or add more translators to your project.
Every page has its own url, so if you have a tool like Google Analytics or Microsoft Clarity installed, you will be able to see the page visits for each translation.
Subscriptions include access to APIs, workflows, dictionaries and feeds. Each subscription offers different options depending on the price plan you choose. More subscription deals can be found in the pricing section
Credits are used for translations and are valid for one year. They can be topped up separately but require an active subscription.
The system resubmits the application up to three times. If the failure persists, the request is marked with a status of "ERROR".
Details about failures can be found in the "Translations" section or in the error reports in the API.
Do you have any questions? Contact us