Skip to main content
The JTL Cloud platform is the developer surface for JTL Software’s ERP and commerce suite. It exposes core merchant systems (products, inventory, orders, and marketplace connectors) through APIs, a messaging layer, a manifest-based app model, and an App Store. For hands-on setup, see Get Started. For implementation detail on a specific app type, see Cloud Apps Architecture.

​
Platform Capabilities

CapabilityWhat you getReference
Integration surfacesRender inside ERP Cloud, launch from a JTL Hub tile, or run headlessIntegration Surfaces
Data accessRead and write merchant data (orders, products, customers, invoices) over REST and GraphQLUsing Platform APIs
AuthenticationOAuth 2.0 client credentials for your backend, short-lived session tokens for your frontendSecurity & Compliance
AppBridgeTwo-way messaging between your app and ERP Cloud for exchanging data and triggering events,App Shell & UI Integration
Design systemPlatform UI, a React component library matching the JTL look and feelApp Shell & UI Integration
DistributionRegister in the Partner Portal, publish to the App Store, install via JTL HubGet Started
MonetizationConfigure pricing plans for your app. JTL handles invoicing, billing, and payouts on your behalf. (Coming soon.)—
Marketplace syncConnect a marketplace channel via SCX, a separate platform that integrates with JTL-WawiMarketplace Channels

​
Integration Surfaces

A Cloud App declares its integration surfaces in the manifest.json. Four types are available, and a single app can use any combination.
TypeWhere it rendersCommunicationTypical use
Hub-LinkCard in JTL-Cloud Hub; clicking redirects the merchant to your URLNone (redirect only)Entry points to external tools and dashboards
ERP-iFrameMain content area of ERP Cloud, reached from the ERP sidebarAppBridge messagingRich interactive UI inside the merchant’s ERP workspace
PaneSidebar panel on specific ERP Cloud viewsAppBridge messaging; context-awarePanels that react to the current customer, order, or product
HeadlessNo UIBackend-to-backend via the ERP APIScheduled sync, webhook processors, automation
All four require app registration in the Partner Portal and OAuth 2.0 client credentials for backend API access. The UI-bearing types (ERP-iFrame, Pane) render as iframes and have full AppBridge access; the difference between them is placement. Hub-Link is a redirect, not an iframe. Headless apps run without any UI surface at all. See Cloud Apps: Architecture for more details.

​
Developer Lifecycle

Building on JTL follows a consistent lifecycle, regardless of the integration surface. You register your app in the Partner Portal and receive client credentials. You build and test against a sandbox tenant inside the ERP shell. When ready, you create an App Store listing and attach a pricing plan. Approved apps become available for merchants to buy and install. Each step is covered in Get Started.

​
What’s Next

Get Started

Set up accounts and ship your first app.

Cloud Apps Architecture

How a Cloud App is structured and communicates with JTL.

Essentials

Auth, errors, pagination, webhooks, versioning.

API Reference

OpenAPI reference for the Cloud API.