erpclaw-setup_skill

Overview

This skill provisions company setup and master data for ERPClaw ERP. It creates companies, configures currencies, payment terms, units of measure, and regional defaults that all other ERPClaw skills consume. It stores data locally in a single SQLite file and is designed for first-time setup and repeatable seeding of defaults.

How this skill works

All operations run through a single Python CLI script that exposes discrete actions (setup-company, seed-defaults, add-currency, etc.). The skill writes to a local SQLite database, uses parameterized queries, and emits JSON output for consumption by UIs or other skills. Backup, restore, and exchange-rate fetching are supported; most actions are offline and require no external credentials.

When to use it

• On first install to initialize the ERP database and create your company.
• When you need to add or enable new currencies and exchange rates.
• To define payment terms, units of measure, or UoM conversions for items.
• Before installing downstream skills (GL, Inventory, Selling) to ensure foundational data exists.
• To backup, verify, or restore the ERPClaw database during maintenance.

Best practices

• Run initialize-database if you see “no such table” errors before other actions.
• After setup-company, run seed-defaults to load currencies, UoMs, and payment terms for faster onboarding.
• Validate account IDs referenced on company updates against the GL skill’s account table.
• Use encrypted backups with passphrases for off-site storage and regularly verify backups.
• Prefer the provided CLI actions; never construct raw SQL—use db_query.py with --action to ensure validation and joins.

Example use cases

• Create a new company with base currency USD and fiscal year start: setup-company then seed-defaults.
• Add a new currency and immediately add a today’s exchange rate for multi-currency reporting.
• Define Net 30 payment terms and assign them to customers via selling workflows.
• Add a UoM and a conversion (e.g., 12 pieces = 1 dozen) for inventory tracking.
• Backup the SQLite database before performing imports or upgrades, then verify the backup file.