The mid-market ERP a large slice of South African manufacturers already run — born in Johannesburg in 1978, purpose-built for discrete manufacturing and distribution. This is a context leaf, not a production skill: SYSPRO has no 2nth integration yet, but it is the incumbent in the local install base, so it's worth mapping its technology, its new ownership, and where a lighter system like ERPNext starts to compete.
SYSPRO is an enterprise resource planning system built specifically for discrete manufacturing and distribution. Founded in 1978 in Johannesburg, it now runs a dual headquarters in the UK and South Africa, employs roughly 400 people, and serves customers across six continents. For a meaningful share of SA factories — automotive components, food & beverage, metal fabrication, plastics, electronics assembly, industrial machinery — it is the system of record already on the floor.
It targets a specific band: businesses roughly $5m to $500m in revenue, 20 to 1,000+ users. That's deliberately narrower than the all-things-to-everyone suites. SYSPRO sells depth in costing, bills of material, work-in-progress, lot and serial traceability, and inventory — the parts of a manufacturing business where getting it wrong is expensive.
It is sold modular by licence: you buy the manufacturing and distribution modules you actually use and add more as you grow. That keeps an entry footprint smaller than a full-suite deployment, but it also means the "real" price depends entirely on which modules you switch on.
The other leaves in this sub-hub — ERPNext, Sage X3, Odoo, Shopify, WooCommerce, Oracle SCM — each back a working skill in the canonical 2nth-ai/skills repo. SYSPRO does not, yet. It's listed because it's the incumbent a South African manufacturer is most likely to already own, and because its integration shape would slot straight into the shared pattern the day a customer needs it. Treat everything here as a map of the territory, not a wired integration.
SYSPRO's architecture splits cleanly into database, business logic, and presentation — which is exactly why it survives the move from thick-client to browser and from on-prem to cloud without a rewrite.
The stack. SYSPRO runs on Microsoft technology — SQL Server for the database, a .NET business layer, and Windows hosting. Its three-tier separation means the same logic can be reached from the classic Windows client, the browser, or an API without losing integrity.
The interface. The modern UI is Avanti, a browser-based, responsive workspace with role-based dashboards and personalisation. It coexists with the long-standing Windows desktop client — most install bases run a mix.
The integration surfaces. Two matter:
| Surface | Shape | Use when |
|---|---|---|
| REST API | Modern HTTP/JSON | New integrations — the surface a 2nth skill would target first |
| e.net | COM / .NET business objects | The older, deeper layer — wraps SYSPRO transactions as callable objects; still load-bearing in many sites |
Deployment is a choice, not a lock-in. SYSPRO ships the same feature set across three models, and customers move between them as needs change:
The managed SaaS tier runs on hyperscaler infrastructure, and the region it lands in determines whether customer and production data sits inside or outside South Africa. For a POPIA-bound manufacturer that's not a footnote — it's the question that decides whether on-prem or private cloud is the safer default, and it's exactly where local or edge processing becomes a differentiator. Ask where the tenancy is before signing.
SYSPRO exposes business logic two ways, and that surface is what determines how cleanly an AI agent can reach it. The short version: the REST API makes it wrappable, e.net makes it deep, and neither ships as a first-party MCP server yet.
The REST API is the modern surface — HTTP/JSON over HTTPS, token-authenticated. It's what a new integration targets first, and it's the layer the Model Context Protocol is designed to sit on top of: MCP wraps an existing REST API as an AI-friendly tool layer, so an MCP server for SYSPRO is a build-on-top exercise, not a re-platform.
e.net is the older, deeper layer — SYSPRO transactions exposed as COM / .NET business objects. It reaches operations the REST surface may not, and it remains load-bearing in many sites. For an agent that needs to post a real costed transaction rather than read state, e.net is often where the write actually lands.
There is no first-party SYSPRO MCP server today. But MCP-readiness is a property of the API surface, and SYSPRO has the right one — a documented REST API that an MCP server can expose as runtime-discoverable tools for Claude, ChatGPT, or any MCP client. The pattern is identical to the production ERP leaves in this tree: wrap the REST endpoints, enforce auth and scoping in the wrapper, and write back through REST or e.net.
The vendor's own direction confirms the trajectory: in 2025 SYSPRO partnered with Versori, a UK-based agentic integration platform, to ship ~25 pre-built integrations and let partners build bespoke connectors in days. That's the agentic-ERP intent — though notably routed through a UK platform partner rather than a local one.
If a 2nth skill wired into SYSPRO, it would follow the same loop every ERP leaf here uses — and 2nth stays middleware, never system of record: read state, run the AI-assisted workflow, write only approved decisions back as first-class SYSPRO transactions.
One honest caveat. Rate limits, object availability, and which transactions are reachable over REST versus only over e.net are all deployment-dependent. Introspect the specific install before promising a workflow — what a current SaaS tenancy exposes differs from a ten-year-old on-prem build.
A short note, not a news roundup. The technology above is unchanged — but the company's growth attention has shifted toward the US and UK, and that opens a door locally.
SYSPRO was founded in South Africa and built its install base here, but since the 2024 change of majority ownership its growth focus has pointed at the larger US and UK markets — its newest AI-integration partnership, for instance, runs through a UK platform. None of that breaks the product. It does change the calculus for a local buyer.
The practical effect: some South African manufacturers weighing a new ERP — rather than those already settled on SYSPRO — are looking for two things the incumbent makes harder to guarantee as it chases offshore growth: focused local support from a vendor for whom SA is the priority market, and predictable ZAR-based pricing rather than dollar-denominated subscription that drifts with the exchange rate. That's the gap a lighter, openly-priced system can walk into — which is the subject of the side note below.
A separate aside, not the main story. SYSPRO owns the established mid-market manufacturer. But at the bottom of its target band — the 20-to-80-user shop weighing a first real ERP — an open-source system on the Frappe framework starts to compete on the things that matter most to a smaller business: cost, lock-in, and time to live.
This is the smaller-business question only — the SME at the edge of SYSPRO's range, not the $300m multi-site manufacturer where SYSPRO's depth is hard to match. For that smaller profile, the question isn't "which has more features" (SYSPRO wins on raw manufacturing depth). It's "which fits a business that needs to be live and cash-positive before the licence renews."
| Dimension | SYSPRO | ERPNext |
|---|---|---|
| Licence model | Modular, per-user; cloud subscription or perpetual + ~20% maintenance | Open-source, no licence fee; pay only for hosting and/or support |
| Entry cost | ~$75–$200 / user / mo + $75k–$200k implementation | Frappe Cloud from low tens of $/mo; self-host on a VPS; no per-user fee |
| Manufacturing depth | Deep — costing, WIP, lot/serial traceability, mature MRP | Strong for the size — BOMs, work orders, job cards, stock entries; backs real factories |
| Customisation | Configurable; partner-led; changes flow through the vendor channel | Metadata-driven doctypes — extend without a vendor; needs in-house or partner dev skill |
| Time to live | Months; partner-led implementation project | Days to weeks for a lean scope; longer if manufacturing is complex |
| Support | Vendor + established SA partner network; rated strong | Community + paid Frappe / partner plans; you choose the level |
| Lock-in / portability | Proprietary; data and logic sit inside the SYSPRO estate | Open-source, self-hostable; you can leave with your data and your stack |
| AI / agent integration | REST + e.net; deployment-dependent; no 2nth skill yet | Every doctype is a REST resource — already a production 2nth skill |
ERPNext competes hardest on cost, lock-in, and speed — the three things a 20-to-80-user manufacturer feels first. No licence fee, hostable anywhere, live in weeks, and already API-first for AI workflows. The trade is that you own the customisation and the operational responsibility: there's no single vendor to escalate to, and complex costing or traceability needs in-house or partner muscle.
SYSPRO still wins where depth and a managed relationship matter more than cost — mature MRP, deep costing, lot/serial traceability, and a dense local partner network that a smaller team can lean on instead of hiring. If the business is already on SYSPRO and stable, ripping it out to save licence fees is rarely the right call.
The honest dividing line: below roughly 50 users with straightforward manufacturing and a tolerance for owning your own stack, ERPNext is a genuine contender and often the cheaper path to production. Above that — or where traceability and costing are regulated and unforgiving — SYSPRO's depth earns its price. For the full ERPNext picture, see the ERPNext leaf.
It's a context node, not a wired skill — but it sits beside the production ERP leaves and points at the parts of the tree a real integration would lean on.
Vendor technology documentation. Any cost figures elsewhere on the site are third-party estimates — treat them as sizing, not quotes.