ERPlora SDK

Build modules for ERPlora — the modular POS system.

How It Works

The ERPlora SDK lets you create modules for ERPlora Hub locally on your machine, without needing access to the Hub source code. You develop against the SDK's dev environment (SQLite, built-in templates, PIN login), and your module code runs identically in production.

Install SDK → Create module → Develop locally → Push to GitHub → Available in Marketplace

Getting Started

1. Install the SDK

pip install erplora-sdk

2. Create a new module

erplora startmodule reservations

This generates a complete module scaffold:

reservations/
├── module.py              # Metadata: name, icon, navigation, permissions
├── models.py              # Django models (extend HubBaseModel)
├── views.py               # Views with @htmx_view, @with_module_nav
├── urls.py                # URL patterns
├── forms.py               # Django forms
├── ai_tools.py            # AI assistant tools
├── templates/reservations/
│   ├── pages/             # Full page templates
│   └── partials/          # HTMX partial templates
├── static/reservations/   # CSS, JS, images
├── migrations/
└── tests/

3. Start the dev server

erplora devserver

This automatically:

• Creates a SQLite database (zero configuration)
• Runs migrations for your models
• Creates a dev user with PIN: 1234
• Starts the server at http://localhost:8000

4. Develop your module

Edit your files — models, views, templates, AI tools — and see changes live at http://localhost:8000.

5. Publish when ready

git init
git add .
git commit -m "Initial module"
git remote add origin https://github.com/your-user/module-reservations.git
git push -u origin main

Register your module in the ERPlora Marketplace and it becomes available to all ERPlora Hubs via automatic sync.

What's Included

Import Compatibility

Your module code uses the exact same import paths as production ERPlora Hubs. The SDK maps them automatically:

# These work identically in the SDK and in production
from apps.core.htmx import htmx_view
from apps.core.models.base import HubBaseModel
from apps.accounts.decorators import login_required, permission_required
from apps.modules_runtime.navigation import with_module_nav
from assistant.tools import AssistantTool, register_tool

Write once, run anywhere — no code changes needed when your module goes to production.

View Pattern

Every module view follows this decorator pattern:

from apps.accounts.decorators import login_required, permission_required
from apps.modules_runtime.navigation import with_module_nav
from apps.core.htmx import htmx_view

@login_required
@permission_required('reservations.view')
@with_module_nav('reservations', 'overview')
@htmx_view('reservations/pages/overview.html', 'reservations/partials/overview.html')
def overview(request):
    from .models import Reservation
    return {'reservations': Reservation.objects.all()}

• Normal request (direct URL) → renders the full page template
• HTMX request (hx-get) → renders only the partial (SPA navigation)

AI Tools

Give your module AI capabilities by defining tools in ai_tools.py:

from assistant.tools import AssistantTool, register_tool
from .models import Reservation

@register_tool
class ListReservations(AssistantTool):
    name = 'reservations_list'
    description = 'List upcoming reservations'
    parameters = {
        'type': 'object',
        'properties': {
            'date': {
                'type': 'string',
                'description': 'Filter by date (YYYY-MM-DD)',
            },
        },
    }

    def execute(self, request, date=None):
        qs = Reservation.objects.filter(is_active=True)
        if date:
            qs = qs.filter(date=date)
        return {'reservations': list(qs.values('id', 'name', 'date', 'time'))}

Users can then interact with your module through the AI assistant: "Show me today's reservations".

module.py

Every module has a module.py that defines its metadata:

from django.utils.translation import gettext_lazy as _

MODULE_ID = 'reservations'
MODULE_NAME = _('Reservations')

MENU = {
    'label': _('Reservations'),
    'icon': 'calendar-outline',
    'order': 30,
}

NAVIGATION = [
    {'label': _('Overview'), 'icon': 'home-outline', 'id': 'overview'},
    {'label': _('Calendar'), 'icon': 'calendar-outline', 'id': 'calendar'},
    {'label': _('Settings'), 'icon': 'settings-outline', 'id': 'settings'},
]

PERMISSIONS = [
    'reservations.view',
    'reservations.edit',
    'reservations.delete',
]

Publishing to the Marketplace

1. Push your module to GitHub (your-user/module-name)
2. Register it in the ERPlora Marketplace
3. After review, it's available to all ERPlora Hubs
4. The sync pipeline automatically distributes updates when you push

CLI Commands

erplora startmodule <name>    # Create a new module scaffold
erplora devserver             # Start dev server (SQLite, PIN: 1234)
erplora version               # Show SDK version
erplora help                  # Show help

Requirements

• Python 3.12+
• Django 6.0+

Installed automatically: Django, djicons (icon template tags), Pillow (image handling).

Links

• ERPlora Website
• Developer Guide
• Module Marketplace
• Report Issues

License

MIT