Test Your App

You’ve built your app and installed it in JTL Hub. Now let’s verify it’s actually running inside the ERP Cloud and connected to your tenant. Prerequisites: You’ve completed either the From Template or From Scratch quickstart, and your app is installed in JTL Hub.

1. Make Sure Your App is Running Locally

Your app needs to be running on your machine for the ERP Cloud to load it. If it’s not already running, start it based on your setup:

From Template
React + Node.js
React + .NET
React + PHP

cd my-jtl-app
npm run dev

Start the backend

cd my-jtl-app/backend 
npm run dev 

Start the frontend

Open a new terminal tab, then run:

cd my-jtl-app/frontend
npm run dev 

Start the backend

cd my-jtl-app/Backend 
dotnet run 

Start the frontend

Open a new terminal tab, then run:

cd my-jtl-app/frontend
npm run dev 

Start the backend

cd my-jtl-app/backend 
php -S localhost:5273 -t public 

Start the frontend

Open a new terminal tab, then run:

cd my-jtl-app/frontend
npm run dev 

2. Open the ERP Cloud

Go to ERP Cloud and log in. You’ll see the ERP-App dashboard. This is where your app runs inside the ERP interface. In the ERP sidebar, scroll down to the App section. You should see your app listed by the menu item name you set when you registered your app:

The menu item corresponds to what you configured in your app.json:

From Template
From Scratch

The template ships an app.json, and the CLI registers it for you:

"erp": {
    "menuItems": [
        {
          "id": "my-jtl-app-menu",
          "name": "my-jtl-app",
          "url": "http://localhost:3004/erp"
        },
        {
          "id": "my-jtl-app-graphql-demo",
          "name": "GraphQL Demo",
          "url": "http://localhost:3004/graphql-demo"
        }
    ]
}

You wrote this manifest and registered it in the Partner Portal:

"erp": {
    "menuItems": [
        {
          "id": "my-jtl-app-menu",
          "name": "My JTL App",
          "url": "http://localhost:5173/erp"
        }
    ]
}

The name is what appears in the sidebar, and the url is the matching route in your app.

4. Click your App

Click your app’s menu item in the sidebar. The ERP loads your /erp page inside its main content area and shows the items from your JTL-Wawi. From Template App: /my-jtl-app

/graphql-demo

From Scratch App:

If you followed the From Template quickstart, you’ll see the item list in the ERP page. If you followed the From Scratch quickstart, you’ll see the tenant details page showing your connected Tenant ID and list of items.

5. Verify the Connection

Your app is working correctly if:

Check	What to look for
✅ App appears in sidebar	Your menu item name shows under the App section
✅ App loads in the ERP	Clicking it renders your app’s UI in the main content area
✅ Tenant is connected	Your app displays a tenant ID, queried products from the JTL-Wawi or connection confirmation

If any of these fail, check the troubleshooting section below.

How it All Connects

Here’s what happens under the hood when you click your app: Your app is extending the ERP Cloud. It sits alongside the built-in modules (Articles, Customers, Sales, Stock, etc.) in the sidebar and has the same access to merchant data through the JTL-Wawi API. The only difference is that built-in modules are native, and your app loads from your URL via the App Shell.

Troubleshooting

App doesn't appear in the sidebar

Is your app installed in JTL Hub? Check Apps in development in the Hub.
Does your manifest include a menuItems entry under capabilities.erp?
Did the app registration complete successfully?

App shows a blank page or loading spinner in the ERP

Is your local dev server running? The ERP loads your app from localhost.
Check the menu item URL you configured during registration. Does the path match your running app?
Open browser DevTools (F12) → Console tab. Look for errors.
If you see a mixed content warning, make sure your URL protocol (HTTP vs HTTPS) matches what the ERP expects.

'Connecting to JTL Platform...' spinner stuck (From Scratch)

The AppBridge provider can’t connect:

If your app isn’t running inside the App Shell, it won’t work in a standalone browser tab
Check terminal output for backend errors
Verify CLIENT_ID and CLIENT_SECRET in your .env / .env.local
Restart the dev server after changing environment variables

App loads but shows an error

401 / Authentication error: Your client credentials are wrong or expired. Regenerate them in the Partner Portal.
CORS error: Your backend might not be accepting requests from the ERP’s origin. Check your API route’s response headers.
Network error: The ERP can’t reach localhost. Make sure no firewall or VPN is blocking local connections.

What’s Next?

Your app is running inside the ERP Cloud. From here:

Publish to the App Store

Ready to ship? Create your App Store listing and submit it for review.

App Shell & UI Integration

Go deeper with the App Shell: add panel views, custom tabs, and ERP context integration.

Get Started

1. Make Sure Your App is Running Locally

2. Open the ERP Cloud

3. Find your App in the Sidebar

4. Click your App

5. Verify the Connection

How it All Connects

Troubleshooting

What’s Next?

Publish to the App Store

App Shell & UI Integration

​1. Make Sure Your App is Running Locally

​2. Open the ERP Cloud

​3. Find your App in the Sidebar

​4. Click your App

​5. Verify the Connection

​How it All Connects

​Troubleshooting

​What’s Next?

Publish to the App Store

App Shell & UI Integration

1. Make Sure Your App is Running Locally

2. Open the ERP Cloud

3. Find your App in the Sidebar

4. Click your App

5. Verify the Connection

How it All Connects

Troubleshooting

What’s Next?