What's new in WLD.

WLD 2.1.0 — prices for the quantity you buy, and a BOM you can walk through

A BOM costed at the price of a single part is a BOM costed wrong. When a line needed two hundred resistors, WLD's ranking used to ask the distributors for the part and take the first price they gave, which for most of them is the price of one. It now asks for the quantity the build actually needs. DigiKey is asked for the price at that quantity, and, when the company's DigiKey account is entered in WLD, for the company's own price rather than the list price. Mouser, Arrow, Future and Farnell are each priced by their own published price breaks. Where a distributor will only sell a minimum quantity or a full reel, the comparison is made on what covering the need really costs, so a cheap reel of three thousand no longer beats ten pieces of cut tape. The draft purchase order still orders what the BOM needs, at the distributor's real price, and says so on the line when that price was for more.

The Multi-level BOM editor can now be walked. A child on a BOM line is a link: a sub-assembly opens its own structure in the same page, with a breadcrumb back to the top and the browser's Back and Forward working the way they do everywhere else, and a part opens a window with its item details, editable in place, with a link to the full Item Master and a button that starts its structure when it should have one. Which revision is being looked at also follows one rule now: screens show the newest approved revision, or the newest draft when nothing is approved yet, and everything that buys, builds, picks or costs uses approved revisions only. An import never writes into an approved revision.

The first two connections to engineering vaults are in this release, for Autodesk Vault and SOLIDWORKS PDM Professional. Each reads a released assembly and its bill of materials through the vendor's published API and turns it into a draft revision in WLD, through the same review an imported file gets. Both are switched off, and both have so far been tested only against answers built from the vendors' documentation, not against a customer's vault. If you run either and would like to be the first to connect it, we would like to hear from you.

Auto Arrange now plans night shifts. A shift from 22:00 to 06:00 belongs to the evening it starts and runs into the next morning, so work is placed through the night, and on the nights the clocks change it gets the hour it really has: nine in October, seven in March. A job that cannot be placed is left unplanned and named, together with the jobs waiting on it, instead of stopping the whole arrangement, and a machine marked out of service for years is passed in a single step. The capacity report counts the same hours Auto Arrange places work in.

Dates now follow the clock on the wall. Between midnight and three in the morning, Finnish time is already tomorrow while the server's clock is still on yesterday, and in a number of places WLD took the server's day: an expired lot read as good until three, a complaint's deadline came out a day early, the first document number of New Year's night continued last year's series. Every one of those places reads the local date now.

Much of the rest of this release is work that should never be noticed. A double click records one payment, not two. Two people saving the same BOM line keep both their changes, or the second is told the line changed under them, rather than one silently undoing the other. Deleting a record takes its attached files with it, while documents the law requires us to keep stay. Uploaded files are read within stated limits, an error from a distributor, an accounting service or any other outside service never repeats its address or a key, and stylesheets and scripts carry the version number, so a browser never runs last release's code after an update.

It is also a security release. Who may change a colleague's access and sign-in details is checked more strictly, the customer portal can no longer be used to affect a staff account, and pages you have seen signed in are never kept by the browser after you sign out. Customers are told the details directly. We recommend installing 2.1.0 promptly.

Zoho CRM, both directions

Companies that already keep their customers in Zoho CRM have no wish to keep them twice. WLD now treats Zoho as the master for customer information: Accounts arrive as customers, Vendors as suppliers, and Contacts as the named people at each customer — the buyer, the engineer, the invoicing clerk — with their role read from their job title so that a delivery note reaches goods-in and a quote reaches the person who asked for it.

It works in both directions. An edit made in WLD is sent back to Zoho, but never while somebody is waiting: a save leaves a note in a queue and the next sync delivers it, so a slow or unreachable CRM can never make saving a customer fail. A sync sends what it owes before it accepts what Zoho holds, and an edit that has not yet been accepted is left alone rather than overwritten — a change made here is not lost because someone else's system was down when it was made.

Reading and writing are separate switches, and both are off until they are turned on. Whether Zoho is connected at all is a setting: with it off, customers, suppliers and contacts are maintained in WLD exactly as before, and nothing in the application reaches for an integration that is not there.

WLD 1.1.0 — the reporting pass, and deliveries that say how they travelled

Twelve reports now answer the questions a manufacturer actually asks at month end: aged receivables and payables stated at a date, the VAT return and EU sales list, the general ledger, a cash flow forecast, capacity against load week by week, stock valuation and turns, delivery performance for us and for our suppliers, quoted margin against what a job really cost, purchase price variance, quote hit rate, and quality as numbers rather than anecdotes. Each one exports to PDF and to a spreadsheet.

Every report drawn from WLD's own journals now says so, on screen and inside the exported file. WLD sends invoices and journals to the accounting system and nothing comes back, so anything an accountant books directly there — depreciation, accruals, year-end adjustments — is not in WLD's figures. The reports are for running the business; the statutory position stays in the ledger that holds it. A file that leaves the building carries that sentence with it.

Deliveries gained carrier, tracking number, package count and gross weight as fields of their own. They were being typed into the delivery's notes box — the placeholder asked for them — which meant no delivery could be found by its tracking number and the delivery note printed them only if somebody remembered. Delivery terms are now snapshotted onto the note when it goes out, so a later change to the customer's terms cannot rewrite what was already sent.

Several contacts per account, each with the role they hold

A customer record held one name, one email address and one phone number. In business-to-business work that is rarely enough: the buyer who places the order, the engineer who answers a question about a drawing and the clerk who needs the invoice are three different people, and sending all three to the same address is how a quote goes unanswered.

Customers and suppliers now carry as many named contacts as they need, each with a role — sales, purchasing, engineering, quality, logistics, invoicing, management — a job title, and an active flag, because people leave and documents already sent should keep showing who received them. The contact on the account itself stays exactly where it was and remains the main one, so nothing that worked before behaves differently.

The roles are not decoration. A sales order confirmation is offered to the customer's sales contact and a delivery note to their goods-in desk, each falling back to the account address when no such contact exists. An account with one person to talk to works exactly as it did.

WLD 1.0.8 — documents leave the system

Seven documents could be generated but not sent: you downloaded the PDF and attached it to an email yourself. Purchase orders, purchasing enquiries, quotations, sales invoices, delivery notes, consignment agreements and engineering changes now go out from the page that produced them, with the file attached rather than a link to fetch it. Where a document travels with drawings or specifications already filed against it, those are offered beside it and you pick which ones go.

One of them was worse than missing. Send Quote rendered the quotation, filed it and set the enquiry to Sent — with a timestamp — while emailing nobody at all. An RFQ could sit in the Sent column having never reached the customer. It now sends, and the rule is the same everywhere: nothing is recorded as sent until the mail server has accepted the message. A refusal, a missing address or an unconfigured server leaves the document exactly where it was.

The sales invoice needed a route rather than a button. Its delivery channel offered no sending or electronic invoice, so a customer who does not accept e-invoices could not be served at all; email is now a third channel, and for those customers sending is the delivery. Purchase orders also gained revisions: change an order after the supplier has it and the number moves, the document and the file name say so, and the page marks the order as changed since it was sent.

Where the translations stand

The interface is finished in every language WLD sells into. Seventeen are configured — English plus sixteen European languages — and each of the sixteen carries the full catalogue of 4,437 strings: just under 71,000 translated strings in total, covering every page, field label, button, setting, confirmation, error message and printed document. None of them is partial. A language appears in the picker only once its catalogue is complete, so there is no screen where the platform changes language halfway down.

The guided help behind each screen is the larger job and moves at its own pace. It runs to 152 topics covering the end-to-end process, and it is complete in seven languages — Finnish, Swedish, Danish, German, Polish, Czech and Estonian — which is 1,064 translated topics, and which puts the three largest EMS manufacturing bases in Europe alongside the Nordics and the Baltics. The other nine fall back to English topic by topic, and the help drawer tells the reader when a topic it is showing has not been translated yet rather than letting them assume it has.

Latvian, Lithuanian, Slovak, Dutch, French, Italian, Spanish, Romanian and Hungarian are what remains. The standing caveat has not changed: these are machine-assisted translations, consistent with the terminology already in each catalogue, and no native speaker has read them end to end. Corrections from customers in each market are welcome and go in under normal change control.

Translations, phase one: all seventeen languages complete

Every language WLD sells into now has a complete interface. Seventeen are configured — English plus sixteen European languages — and each one carries all 3,970 translatable strings: every page, field label, button, setting, confirmation and error message. Polish, Czech, Slovak, Hungarian and Romanian were the last five and finished today. A language is only offered in the picker once it is actually finished, so nobody meets a half-translated screen.

These are machine-assisted translations, consistent with the terminology already in each catalogue, but no native speaker has read them end to end yet. Treat phase one as a first pass to review rather than a finished translation — corrections from customers in each market are welcome and go in under normal change control.

467 strings that had never been translatable

Finishing phase one made the gaps visible. A sweep of every template found text that had never been marked for translation at all — it was English in the source and English on the screen, no matter which language you picked. The printed PDF documents were the largest group: purchase orders, requests for quotation, delivery notes, order confirmations, credit notes and the financial reports. The country list on the customer and supplier pages was the next, at 195 names. The quality menu, the two-factor authentication screens, the work time entry page and the incoming purchases report followed.

The catalogue went from 3,970 strings to 4,437, and all sixteen languages were brought back to complete rather than left partial — 467 new strings each, 7,472 in total. A document that leaves your building now leaves it in the language it was addressed in.

Phase two: the in-app help follows

The guided help behind every screen — 148 topics covering the end-to-end ERP process — is a much larger body of text than the interface itself. Finnish, Swedish and Danish were complete; German, Polish and Czech followed, which puts the help of the three largest EMS manufacturing bases in Europe alongside the Nordics. The remaining ten languages are what phase two is for. A language that has not been reached yet falls back to English topic by topic, and the help drawer says so when it does. The printed documents and the country list, named here earlier as still outside the catalogue, went in the same day and are translated everywhere.

A purchase order remembers where it came from

Convert a quote on a Purchasing RFQ into an order and the two stay linked in both directions. The purchase order shows the RFQ it came from as a live link beside its status, and a closed RFQ lists the orders it produced. Buyers who want the competing quotes behind a price no longer have to search for them.

Also landed

The NPI lead-time KPI now measures a real window under an honest name, and you can set a target and see it drawn across the chart. The BOM calculator can create the item a new product needs instead of stopping at the missing code. The Purchasing module film has been recut around the RFQ-to-stock path, and the job pipeline film sits on the front page. Demo visits are counted without recording who the visitor is — a daily hash, an organisation name resolved from the network, and no cookies or addresses kept.

Procountor API

Added an API integration with Finago Procountor, an easy-to-use and reliable financial management platform trusted by over 100,000 companies and 1,400 accounting firms. Development of integrations with Xero, Exact Online, Fortnox, e-conomic, DATEV, Visma eAccounting, Visma.net, Netvisor, and Talenom is ongoing.

Update, 16 October 2026: none of those connectors has been built. Procountor is still the only accounting system WLD connects to; if another is built, it will be announced here.

WLD 1.0.1 released

The platform now speaks the customer's language. Each person's choice is stored against their account and follows them to the next session and any other machine. Seventeen languages are configured — one per market WLD sells into — and Finnish, Swedish and Danish are complete: every page, setting and confirmation message. Existing customers are updated as part of the managed service, under explicit change control as always.

WLD speaks your language — translation work ongoing

The WLD interface is being translated into 16 European languages alongside English — one per market WLD sells into — and every user keeps the language they chose. Finnish, Swedish and Danish are complete; the rest are under way. The language translation work is ongoing: more screens and refinements land continuously as the platform evolves.

Heavy AI investment in BOM and PCB scrubbing

Lots of AI work is going into the BOM and PCB scrubbing functions right now. The AI maps, classifies and enriches imported BOM lines, with a human review queue exactly where judgement is needed. BOM imports are Excel-only, so there is one clean, predictable path from a supplier spreadsheet to a controlled BOM.

WLD 0.6.0 released

The latest release of the EMS operating platform is live. Existing customers are updated as part of the managed service — under explicit change control, as always.

What should a board cost? Ask WLD

New PCB price estimation: estimate what a board should cost from your own purchasing history combined with current market data. It gives buyers and quoters an evidence-based target price before they negotiate — and feeds sharper numbers into every RFQ.