How the Submission Process Works
The App Store submission follows this process:
Let’s go through each step.
1. Deploy your App
Your app currently runs onlocalhost and merchants can’t access that. You need to deploy it to a publicly accessible URL with HTTPS.
What you need:
- A hosting provider (Vercel, Railway, AWS, Hetzner, or any platform that runs Node.js)
- A domain or subdomain (e.g.
app.yourcompany.com) - HTTPS enabled (required because JTL loads your app in an iframe, and browsers block mixed content)
- Your frontend (the pages that render inside the App Shell)
- Your backend / API routes (the endpoints that handle auth and business logic)
2. Update your Manifest
Your manifest currently haslocalhost URLs. Update every URL to point to your deployed app:
- Use
https://(nothttp://) - Point to your production domain (not
localhost) - Be publicly accessible
Only the URLs need to change. The rest of your manifest (name, description, icon, locales, and legal URLs) stays the same. Make sure your support, privacy, and terms URLs point to real, accessible pages before submitting.
3. Register your App (if not already done)
If you already registered your app on the Partner Portal during the quickstart, you have your client credentials and the app exists in JTL’s system. If you’re registering for the first time with production URLs:- Open the Partner Portal
- Click + Create button
- Paste your updated manifest (with production URLs) into the Manifest Editor
- Click Register app button
- Copy your credentials immediately, as they’re shown only once
4. Submit your Listing Request
With your app deployed, your manifest updated, and the app registered, you can submit a listing request to the JTL partner team. Send your request to markus.fleischer@coduct.com using the template below. Fill in every field as incomplete submissions will delay your review.Submission Template
Copy the template above, fill it in, and send it as the body of your email.
- Open the Partner Portal and navigate to the Manage apps section.
- Click on the ellipsis (…) menu for your app and select Edit app.

- Copy the App ID from the URL.
https://partner.jtl-cloud.com/{TenantSlug}/{PublisherId}/app-edit/{AppId}
The App ID is the last segment of the URL.
5. JTL Reviews and Publishes
After you contact JTL, the team will:- Review your app and verify it’s working at the production URL
- Make your app visible in the App Store
- Notify you once the listing is live
Pre-submission Checklist
Before contacting JTL, make sure everything is in order:| Check | Status |
|---|---|
| App is deployed and accessible via HTTPS | ⬜ |
All manifest URLs point to production (no localhost) | ⬜ |
| App loads correctly in JTL Hub from production URL | ⬜ |
| Setup flow completes successfully (session token verification works) | ⬜ |
| App renders correctly in the ERP Cloud | ⬜ |
| Support URL in manifest leads to a real page | ⬜ |
| Privacy policy and terms of use URLs are live | ⬜ |
| App icon URLs are publicly accessible | ⬜ |
What to Expect After Listing
Once your app is live in the Extension Store:- Merchants can discover it by browsing or searching the store
- Installation triggers your setup flow: the same flow you tested locally
- You manage the app through the Partner Portal (credentials, payouts, updates)
- App updates are deployed through your hosting provider; if the manifest changes, coordinate with JTL
What’s Next?
What's Next?
Explore what to build next: deeper API integration, pane views,
marketplace channels, and more.
App Shell & UI
Add pane views, custom tabs, and deeper ERP integration to your app.