c ERPNext DocType Inspector — Explore ERPNext, Frappe & HRMS

ERPNext DocType Inspector

Simplify ERPNext customization by browsing comprehensive DocType details, fields, and relationships, and link with AI assistants for instant explanations.

Browse DocTypes across ERPNext, Frappe Framework, and HRMS — or connect your own instance for a live, real-time view.

Browse DocTypes Connect Your Instance  Coming Soon API Docs  Coming Soon
982
Total DocTypes
37
Modules
3
Applications
2
AI Assistants

Browse by Application

DocTypes are organised across three Frappe-ecosystem apps. Click any module tag to jump straight to that module's DocType list.

ERPNext

553 DocTypes · 20 Modules

The full ERP suite — accounting, inventory, manufacturing, CRM, purchasing, selling, projects, assets, and more.

Accounts (178) Stock (74) Manufacturing (43) CRM (27) Assets (26) Buying (20) Selling (17) Support (11) +12 more
Browse all ERPNext DocTypes

Frappe Framework

207 DocTypes · 11 Modules

The low-code web framework powering ERPNext — users, roles, permissions, workflows, email, desk config, and core utilities.

Core (92) Desk (52) Email (16) Automation (9) Workflow (9) Custom (7) Printing (7) +4 more
Browse Frappe DocTypes

HRMS

222 DocTypes · 5 Modules

Frappe's dedicated HR & payroll suite — employees, leaves, attendance, loan management, salary components, and telephony.

HR (115) Loan Management (62) Payroll (38) Telephony (5) Loan Origination (2)
Browse HRMS DocTypes

AI-Powered DocType Explanations

On every DocType detail page, the inspector generates a structured prompt containing field names, types, required flags, and relationships. You can copy it or deep-link directly into your preferred AI assistant — no manual copy-paste flow required.

Claude Claude
ChatGPT ChatGPT
Copy prompt
Try it on any DocType
Example generated prompt

Explain the Sales Invoice DocType in ERPNext.

It has 72 fields: 8 required, 12 read-only, 14 Link fields.

Key links: Customer → customer, Company → company, Item → items[].item_code...

Open in Claude Open in ChatGPT Copy

Two Ways to Use

Use this hosted version for instant, no-setup access, or run the Docker container locally to inspect your own ERPNext instance including custom DocTypes and private apps.

Live Version

You are here

Instantly browse 982 pre-indexed DocTypes from a reference ERPNext v15 instance. No account, no credentials, no setup needed. Perfect for exploring the schema before you build.

  • Browse all ERPNext, Frappe & HRMS DocTypes
  • Filter by module, field type, required, read-only
  • Export OpenAPI / Swagger specs for any DocType (Coming soon)
  • Deep-link to AI assistants for instant explanations
  • Generate TypeScript type stubs
  • Custom / private DocTypes not available
  • Local AI mode not available
Browse DocTypes

Run Locally with Docker

Full feature set Coming Soon

Point the inspector at your own ERPNext instance to inspect custom DocTypes, custom fields, and private apps. Unlocks live-sync mode and a locally fine-tuned AI via Ollama so your data never leaves your network.

  • Everything in the live version
  • Inspect custom & private DocTypes live
  • Always reflects your current schema (no static cache)
  • Fine-tuned local AI mode via Ollama
  • No data leaves your network
# run against your local instance
docker run -p 5000:5000 \
  -e MODE=erpnext \
  -e ERPNEXT_URL=http://your-site:8000 \
  -e ERP_API_KEY=your_api_key \
  -e ERP_API_SECRET=your_api_secret \
  doctype-inspector

How the Local Instance Connection Works

 Coming Soon

Setup Steps

  1. Generate API credentials in ERPNext under Settings → API Access
  2. Open the Connect page and enter your ERPNext URL, API Key & Secret
  3. The inspector validates your credentials against the Frappe REST API on every request
  4. Browse DocTypes — the list is fetched live from your instance so custom doctypes appear immediately
  5. Session expires gracefully: you'll be prompted to reconnect if the token is revoked

Requirements

  • ERPNext v13+ (v15 recommended)
  • API Key & API Secret (from your ERPNext user settings)
  • Network access to the ERPNext server from the Docker container

  • The user account must have System Manager or DocType read permissions

Tip: Running ERPNext locally with bench start? Use http://localhost:8000 as the URL and set MODE=erpnext in the Docker run command.

Privacy Policy

Last updated: March 27, 2026

1. Information We Collect

When you use the ERPNext DocType Inspector, we may collect and process information necessary to facilitate the connection to your ERPNext instances. This includes ERPNext URLs, API Keys, and API Secrets which are required to fetch DocType metadata.

2. How We Use Your Information

The credentials you provide are used strictly for communicating with your designated ERPNext instance. We use this access solely to read DocType structures, retrieve fields, and generate TypeScript interfaces or API documentation on your behalf.

3. Data Storage & Caching

To improve performance and limit repeated requests to your ERPNext instance, we temporarily cache the structure of fetched DocTypes (such as fields, descriptions, and types) using a local cache mechanism with a short Time-To-Live (e.g., 20 minutes). We do not permanently store your API credentials or any sensitive business data from your ERPNext system.

4. Third-Party Services

Our tool allows you to deep-link DocType metadata directly into external AI assistants (such as Claude or ChatGPT). When you use these features, the generated schema and prompts are handed over to the respective AI platforms. Please refer to their respective Privacy Policies to understand how they process this data.

5. Security

We are committed to securing your data. We use appropriate technical and organizational measures to protect your credentials during transmission. However, no internet-based service is 100% secure, and we advise against using production credentials if a test environment is available.

6. Changes to This Policy

We may update our Privacy Policy from time to time. Any changes will be posted on this page with an updated revision date.

If you have questions about this privacy policy, please contact the project maintainers or open an issue in the project repository.