One Action, Every Language, One Supplier
If you run multilingual Codyt projects, you are going to feel this one immediately. You used to assign each language pair separately, which got painfully slow on a project with a dozen languages. Now you select multiple Codyt jobs across different language pairs and task types and assign them all to the same supplier in one action. The redesigned Assign Jobs screen adds a Select Supplier mode: pick the supplier, optionally set a specific worker, and apply it across every selected job at once.
It is a small change in clicks and a big change in how staffing a launch feels, which is exactly why LSPs juggling large rosters told us they wanted it.
Quality Checks That Speak More Languages
Your quality gate just got smarter where it counts. The Forbidden Terms QA rule now detects banned terms in Chinese, Japanese, and Korean. These languages do not put spaces between words, so the rule could quietly miss a forbidden term sitting in plain sight. It now applies the right matching method per language, so the check works the same whether the content is English or Japanese. If you ship into Asian markets, this closes a gap that was easy to miss and expensive to let through.
Translation Memory That Scales With You
Two changes make translation memory steadier at volume. The Translate Files API now takes up to 100 files at once in a ZIP archive, and a new parameter turns on MT consolidation, so machine-translated segments save into a memory automatically and the next job reuses them instead of paying for the same MT twice. Separately, the consolidation that merges project segments into memories now uses far less memory on large datasets, which heads off the slowdowns and failures that enterprise-scale memories used to risk.
An Analytics Engine That Recovers on Its Own
The most important fix here is one you will probably never see, and that is the point. The Business Analytics engine could crash mid-calculation if a record was being edited at the same time, and when it did, the whole day of data for that account stopped processing, then got marked complete and skipped for good. Now failed calculations retry on their own, and a single failure no longer blocks the rest of the day. The reporting you make decisions on stays whole.
Also in This Release
The refinements clean up the edges everywhere you look. Invoices are now tracked in the admin audit trail through the Traces API, so a created, changed, or deleted invoice is recorded with who did it and when, which makes chasing an accidental deletion simple. The Failed Login Attempts report now tells a seat-limit block apart from a wrong password, with a specific code pointing to which user type ran out of licenses. The Job Reference column is now optional, so teams who work by Job ID get a cleaner list. The R200 access right description now spells out its full scope, including that it gates client quotes and invoices, so admins assign it with confidence. And the Client Portal now pulls its logos and banners from your central Look and Feel settings, so branding lives in one place and existing portal branding is preserved.
The fixes go deeper than a typo, though there is one of those too: the Arabic language label in French no longer reads "Aarabe." A multi-file upload counts as one API call against your rate limit instead of one per file. The job status popup shows the requester and company from the order that actually created the job. Excel files using context or key column extraction no longer leak source markup into the key column. And translation memory hits exported to Excel from the editor now read as clean, color-coded text instead of raw data.
A quieter release on the surface, with real muscle underneath. The full technical notes for 2026.1.10.0 live on help.wordbee.com. If multilingual assignment or quality checks for Asian languages fit how your team works, talk to us and we will help you put them in place.