Factory.Online in Saudi Arabia: implementation and integration, assessed independently. We do not resell it and we hold no partner position with the vendor. The product is spelled with the dot, the way its makers spell it, and that is the level of care the rest of this page tries to keep.
The vendor describes factory.online as a cloud manufacturing platform where AI agents assist planning, costing and shop-floor decisions, putting sales, production and inventory in one real-time system, and positions it as plug-and-play for manufacturers. Read that carefully and the fit question appears: this is a system of record for how a factory runs commercially, not a sensor layer on the machines. If what you need is machine-level loss analysis, you are on the wrong page.
You are a small or mid-sized manufacturer running the business across spreadsheets and a general-purpose accounting package, and the seams show: what was promised to a customer, what is actually scheduled, and what is actually in stock are three different answers. You want one real-time system rather than an ERP programme. And your product and costing data, while messy, is recoverable — because that is what the platform runs on.
We do not recommend it when you already run a capable ERP; adding a second system of record for production is how organizations acquire two versions of the truth and a reconciliation job nobody wanted. We also advise against it when the problem is genuinely on the machines — downtime, micro-stops, quality losses — because that needs shop-floor instrumentation rather than a commercial platform. If the answer turns out to be instrumentation, our internet of things practice is the honest next stop; if it turns out to be neither, we will say that too.
From the vendor's own site, and no further: sales, production, supply chain, inventory management, planning, scheduling, costing, and master and product data, in one cloud system described as real-time and plug-and-play, with AI agents assisting planning, costing and shop-floor decisions. We deliberately do not claim shop-floor loss measurement for this product — its makers do not, and borrowing a term from a different category of tool is how buyers end up comparing things that are not comparable.
Three. "Plug and play" is a claim about setup, not about your data: the platform computes on your product records, routings and costs, and if those are wrong it will be wrong quickly and confidently. Second, AI assistance in planning and costing means recommendations, and recommendations need someone accountable for accepting them; decide who that is before go-live, not after. Third, as a system of record it will want to own things your accounting package currently owns, and that boundary has to be drawn on paper first.
Two constraints shape this work in the Kingdom. Any screen a production or warehouse team uses daily has to work in Arabic for the people using it — a real design and testing commitment. And what leaves the factory becomes a tax document: VAT is charged at 15%, and the Zakat, Tax and Customs Authority's E-Invoicing (Fatoorah) requirements have been in force since Phase 1 on 4 December 2021 and Phase 2 on 1 January 2023, so the path from a despatch to a cleared invoice has to hold. Because this platform carries sales as well as production, that path runs straight through it, which makes the invoicing boundary the first thing we scope rather than the last. See the manufacturing systems category and the manufacturing sector page.
We publish no price. The vendor does publish a pricing page and an ROI calculator of its own; use them as the vendor's figures, which is what they are, and bring the output to a conversation rather than to a decision. The model we build with you has four lines: the subscription as quoted to you; the master-data work to make products, routings and costs computable, which is the line that decides the project; the integration with accounting and the invoicing path; and the internal time to run a system of record you did not have before.
Three routes, honestly. A full ERP with a manufacturing module, when the organization is large enough to carry one. A focused cloud manufacturing platform such as this one, when it is not. Or keeping your accounting package and adding scheduling and inventory discipline around it, which is unglamorous and sometimes correct. We score them against your order book and your data, not against a feature grid; our independent software comparisons show that shape of work.
We start from where your answers disagree: promised versus scheduled versus in stock. That divergence, quantified, decides whether a platform is the fix. We take no margin on any licence and do not bid on implementations we scope, so "your problem is master data, not software" is a live outcome.
Accounting first, because the boundary between the platform's records and the ledger decides everything afterwards; then the invoicing and e-invoicing path; then any shop-floor data you already collect; then customer-facing channels if orders arrive digitally. We prove the accounting boundary before anything goes live.
Planners and sales staff carry this system, so training is built around the handover between them — the promise, the schedule, the stock — rather than around a screen tour. Where Arabic is the working language, training and the screens themselves are in Arabic. The first full month-end after go-live runs with us on call.
We publish no counters here. The outcome that matters is agreed with you before the work starts — usually on-time delivery and the gap between promised and actual lead time — and it is measured against your own baseline. A figure from another manufacturer tells you nothing about yours.
It tracks the state of your product, routing and costing data far more than the platform. We size it after the data review and put the assumptions in writing beside the estimate.
Subscription, master-data remediation, accounting and invoicing integration, and the internal time to operate a system of record. The vendor publishes its own pricing and an ROI calculator; we treat both as vendor inputs and model the rest with your numbers.
We make no compliance claim on any vendor's behalf. We establish where the data is hosted, obtain the vendor's own written statements for your compliance function, and test that sales documents leaving the platform can clear against ZATCA's published requirements. Compliance is a property of your deployment, not of a product name.
A full ERP with manufacturing, focused cloud manufacturing platforms, and the do-less option of tightening what you already run. Each is recorded in the assessment report with the reason it was kept or dropped.
Partly, and the honest answer is that a system of record always displaces something. Which records move and which stay is the boundary decision, and we draw it explicitly with an interface inventory and a written vendor confirmation per integration.
None of the kind that fits on a badge. The honest ones are not numbers: we take no licence margin, we do not bid on implementations we scope, and every engagement ends in a written recommendation you keep whether or not you hire us again.
We name organizations only with their consent and in direct conversation, never on a product page. Ask for references among manufacturers and we will arrange the calls.
No composite case study appears here. Relevant work is walked through attributably in a first conversation — the standard we suggest you hold every bidder to, ourselves included.
We publish no testimonial quotes on this page. Speak to our references directly; it carries more weight than a curated pull-quote.
Nobody, in the commercial sense, and that is the point of the page rather than a gap. We hold no reseller or partner position with the vendor and claim no accreditation in relation to this product. What qualifies the advice is method: a data review, an interface inventory, a written scope, and no financial interest in the outcome.
Continue with the manufacturing systems category, our independent software comparisons, the manufacturing sector page, or our internet of things practice if the answer turns out to be instrumentation.
Bring us a week of orders, schedules and stock figures and we will show you where they disagree. You will leave with a written position on whether a platform is the fix. Request a demo.
Unlimited support included.
One-on-one onboarding sessions.
Training videos, webinars, & demos.