WLD carries a high-mix order from the customer's enquiry to the invoice — the quote, the BOM, live component prices, purchasing, planning, the shop floor and the quality evidence your customers audit — in one system.
Jalacons Oy, Finland, maps WLD to how your company really works, hosts it as your own dedicated installation, and runs it for you as a service.
EMS companies build for markets that audit their suppliers. WLD keeps the records those audits look for in the same system that runs the order, so the evidence is captured while the work is done rather than assembled afterwards.
An ISO 13485 compliance profile and its clauses in the audit register. Design and development changes run through controlled engineering changes, and a serialised unit is traced from receipt through production to delivery, and back again on a return.
Configuration control through engineering changes and an approved-manufacturer list per BOM line. First-article inspection with a ballooned first-article report, and an export-control classification (ECCN) field on every item.
IPC Class 2 or Class 3 recorded on the compliance profile each route works to. The UL Follow-Up Service topics in the audit register, the UL file number on the item, and results from ICT, AOI and flying-probe testers imported into the inspection record.
A measuring-equipment register with calibration history. Equipment found out of tolerance leaves service, and the inspection results recorded with it are listed for an impact assessment.
Whatever the market, the same base: ISO 9001 in practice, and on every item its RoHS status and exemption, REACH SVHC, conflict minerals and WEEE category, and for a moisture-sensitive part its J-STD-020 level and floor life.
Since WLD 2.0.0 the same system serves machining, laser, bending and welding subcontractors: welding procedures and welder qualifications, EN 1090 execution classes, and heat numbers with their EN 10204 material certificates.
Not a quality add-on beside the ERP: the quality records hang off the same purchase receipts, jobs and deliveries the rest of the company works on.
The clause explanations are WLD's own plain-language summaries; no licensed standard text is reproduced, and you can add clauses for further standards or a customer's quality agreement. WLD holds the operational records an auditor samples. Certification remains yours to earn.
ERP sold as a service usually means one application shared by many customers, and a standard process to fit into. WLD is built the other way round.
| Topic | The usual ERP SaaS | WLD |
|---|---|---|
| The application | One application, shared by many customers. | A dedicated installation for your company, hosted and operated by Jalacons, with EU data residency available. |
| What it is built for | Any business with items, orders and invoices; the fit for manufacturing often comes from add-ons and partners. | High-mix EMS: RFQs, customer BOMs, MPNs and approved alternates, MOQ and MPQ, consignment, moisture-sensitive lots and DPMO per placement. |
| Your process | Adapted to the standard one. | Mapped first in an EMS Process Blueprint, then built and taken live in phases around how work really moves through your company. |
| Who answers for it | The software vendor for the service, and often a separate implementation partner. | One team designs, builds, operates and answers for it. |
| Change | On the vendor's release schedule. | Under explicit change control, with release notes that say what changed and, since 2.1.0, which versions a security fix affects. |
During the BOM import, a match the AI made carries an AI mark, and a line it is unsure of waits for a person. A board value the AI read from a document is not priced until somebody confirms it, and the market briefing says that the AI wrote it. The AI account is your own, and the model can run on your own network.
No outside connection — the distributors, the AI, your CRM, your accounting — sends anything until it is given credentials or an address, and each AI feature has its own switch. Writing back to your CRM is a switch separate from reading it.
First-pass yield counts inspections, not characteristics. DPMO for an item without an approved BOM is reported as not computable, never as zero. A market briefing drops any headline about a subject it was never told about.
WLD sends invoices and journals to Procountor and keeps its own statements as management views. The statutory accounts stay with your accountant, in the ledger that holds them.
Every step reads what the step before it recorded. Nobody retypes the order into the next tool.
Estimates per discipline, a PCB calculator that reads the board's files and lists what they did not state to ask the customer, and quotes sent and tracked.
The customer's BOM as it was sent, matched to your items and ranked by price, lead time or stock.
Supplier enquiries and quote comparison, purchase orders with revisions, consignment and its settlement.
Firm demand and safety stock netted against stock, with each requirement pegged to the demand behind it, the first 25 by need date.
Jobs placed on work centres and their shift calendars, night shifts included.
Routings, operator time, completions with scrap, and material collections picked with a scanner.
Inspection, NCR and CAPA, audits, calibration, and lot and serial genealogy.
Deliveries with tracking, invoices to your accounting, and each job's cost against its quote, where a quote matches the job.
And for your customers: a portal where named people at each customer follow the jobs made for them through production and download the signed certificate packs of their certified deliveries.
See the platform, module by moduleThe fastest way to lose trust in a system is to find out late what it does not do. So, up front:
A fixed-scope start, a phased build, and a managed service — one accountable team throughout.
A paid, fixed-price mapping of your real workflows. The output is a phased plan and a binding phase-one estimate.
Milestone-billed implementation with formal acceptance criteria. Quoting, inventory or quality can go live first.
Your own dedicated, cloud-hosted application with an SLA, contracted backups and continuous improvement.
Indicative monthly ranges are on the pricing page. The service fee starts when the first production module goes live, not before.
Ask for a demo, or start with an EMS Process Blueprint: two to four weeks, fixed price, ending in a binding estimate for phase one.
