Your Workflow Can Now Read the Quality Score
This is the kind of automation that actually changes a project. A workflow step can now decide for itself whether it needs to run. Set a quality score threshold on a step, and when a translation clears it, a human review step cancels automatically. When it does not, the review stays exactly where it is.
That is the real promise of automation that respects quality: your strong content moves faster, and the work that genuinely needs another set of eyes still gets one. No blanket trade-off between speed and safety. Every job earns its own path.
Large documents stop being a chokepoint too. In Standard projects, a single big file splits automatically into smaller jobs based on a paragraph limit you set, so the work spreads across your team instead of stalling with one translator. You define the slicing in your Workflow and Suppliers configuration or override it when you mark documents, and the system keeps multi-step dependencies intact and applies safety limits to protect performance.
More Reach for the Developers Building on Wordbee
If your team builds on the platform, this release gives you less to do per result. New batch API endpoints let you download translated files for several documents as one archive and pull statistics for multiple documents in a single request, instead of looping call by call. The segment reports endpoint now accepts comma-separated target locales, so a multi-language report is one request rather than many, and existing single-locale integrations keep working untouched.
There is also a new webhook that fires when every job in a workflow has been cancelled, so a connected system knows the work stopped without polling for it. It is the sort of detail developers notice and appreciate.
Smoother From Login to Order
A run of refinements takes friction out of the everyday path. Log in with single sign-on and you land on the page you actually asked for, not the home page, so a deep link to a job opens that job. Target language selection in the order form is now a searchable checklist that stays open while you pick, with selected languages as removable tags, a counter, and a quick clear. Custom fields can carry help text that shows as a tooltip wherever the field appears, so fields get filled out right the first time. Project document uploads run up to five times faster, with live progress per file and clear errors beside anything that fails. And the orders page gains better keyboard navigation across tab order, dropdowns, search, and table focus.
Fixes That Pull Their Weight
A few corrections close gaps that mattered. The big one shipped in a quick follow-up: job dependencies in Standard projects were not always respected, so a revision step might not start after translation finished, and the automation that follows, including translation memory consolidation and saving translated files, could be skipped. Both the dependencies and the automation behind them are restored.
Beyond that, translated FrameMaker MIF files no longer corrupt and crash when they hold conditional text inside cross-references. Automatically generated invoices now honor your verbose pricelist settings and show the same detail as manual ones. Scheduled email notifications send once instead of duplicating when grouping is off. External users can open the Term Details window in the editor again when a termbase is attached. And deleting LLM credentials now asks for confirmation, since those credentials may be powering live MT connectors. The QA Issues Report also gains optional placeholders for segment IDs, resource IDs, and severity.
That is a release that makes the platform smarter and quieter at the same time. The full technical notes for 2026.1.7.0 live on help.wordbee.com. If quality-driven workflows or automatic job splitting could reshape how you plan a project, talk to us and we will help you set them up.