Seeders and Demo Data
The reference data every installation gets, optional starter content, the demo dataset, and how to run seeders from the terminal or Admin → Database Seeders.
Signals separates seed data into four tiers:
| Tier | What it is | How to load it |
|---|---|---|
| Boot-start | Reference data every installation needs: countries, currencies, languages, lists, tax, roles and permissions, stages, and system templates | php artisan db:seed; setup runs it for you |
| Starter content | A default warehouse, groups, categories, rate presets, live filters, 14 sample catalogue items and the system reports | php artisan signals:seed-starter-content |
| Demo data | A curated, tagged working dataset of customers, rentals, invoices and operations | Load demo data in the setup wizard, signals:setup --demo, or php artisan signals:seed-demo |
| Volume | Bulk records for load testing only | php artisan db:seed --class=VolumeTestSeeder |
Running php artisan db:seed executes only the boot-start tier in dependency order, leaving warehouses, catalogue item groups, catalogue items, assets, plugins, customers, and transactions blank. Every seeder can also be run from Admin → System → Database Seeders, which shows whether each one has already run.
What Runs by Default
The DatabaseSeeder calls these seeders in order. The order comes from SeederPanelCatalog::bootStartClasses(), which also drives the admin seeders panel.
| # | Seeder | Purpose |
|---|---|---|
| 1 | CountrySeeder |
ISO 3166-1 countries with currency codes, phone prefixes, and default timezones |
| 2 | LanguageSeeder |
The default English language record |
| 3 | LanguageTranslationSeeder |
Additional UI languages and their translated string packs |
| 4 | ListsSeeder |
System-managed lists (Admin → Option Lists) |
| 5 | CurrencySeeder |
ISO 4217 currency definitions, with GBP/USD/EUR enabled |
| 6 | ExchangeRateSeeder |
Baseline GBP→USD and GBP→EUR rates for a clean install |
| 7 | TaxTypeSeeder |
Default customer tax profiles and item tax codes |
| 8 | TaxZoneSeeder |
Tax zones (UK, EU Account States, EU Other, World) and country memberships |
| 9 | TaxCategorySeeder |
Catalogue item tax categories (Standard, Reduced, Zero Rated, Exempt) |
| 10 | TaxRateSeeder |
Default tax rates (Standard 20%, Reduced 5%, Zero 0%) |
| 11 | TaxRuleSeeder |
Class-map rule tying the default tax types to the Standard rate |
| 12 | TaxZoneRuleSeeder |
UK-seller zone-matching rules for domestic and cross-border scenarios |
| 13 | PermissionSeeder |
All system permissions for role-based access control |
| 14 | RoleSeeder |
System roles with permission assignments |
| 15 | CanonicalApprovalChainSeeder |
The published v1 approval chain for rental quote-to-order conversion |
| 16 | DispatchStageSeeder |
Outbound dispatch board stages (To pick, Picking, Packed, Loaded) |
| 17 | ReturnStageSeeder |
Inbound returns board stages (Due back, Receiving, Exceptions, Closed) |
| 18 | EmailLayoutSeeder |
The master branded email layout wrapped around system emails |
| 19 | EmailTemplateSeeder |
Type-less system email templates (test mail, AI budget alerts) |
| 20 | NotificationTypeSeeder |
Notification type definitions with channel defaults |
| 21 | DocumentTemplateSeeder |
System document templates (quotes, invoices, and so on) for every existing warehouse |
| 22 | CommunicationTemplateSeeder |
System customer-communication templates for every existing warehouse |
In testing and conformance, DatabaseSeeder also creates the development owner [email protected]. In local, that account is created only when SIGNALS_SEED_DEV_OWNER=true; other environments always skip it. This prevents a known-password owner from silently blocking first-run setup on a real self-hosted installation.
Starter Content
Starter content is an explicit opt-in convenience tier defined by SeederPanelCatalog::starterContentClasses():
| Seeder | Content |
|---|---|
WarehouseSeeder |
Main Warehouse, created only when no warehouse exists |
RevenueAccountSeeder |
Revenue accounts (Dry Hire, Wet Hire, Sales, Services) |
CostCategorySeeder |
Cost categories (Equipment Sub-Hire, Crew Sub-Hire, Transport, Consumables, Equipment Purchase) |
CatalogueItemGroupSeeder |
13 sample catalogue groups used by the sample catalogue items |
ViewSeeder |
System-managed live filters for accounts, catalogue items, stock, and activities |
RateSpecificationPresetSeeder |
Standard rate specification presets |
DiscountGroupSeeder |
Default discount groups (Trade Discount, Preferred Customer, Staff) |
RateBandSeeder |
Default rate bands with tier multipliers (Trade Day 1 / Day 2+, Retail) |
CatalogueItemSeeder |
14 sample rental, sale, and service catalogue items with rates and stock |
ReportSeeder |
System reports for revenue, invoices, tax, pipeline, turnover, shortages, accounts, and catalogue |
Run all ten in their dependency order after boot-start seeding:
php artisan db:seed
php artisan signals:seed-starter-content
All ten remain available individually in Admin → System → Database Seeders. They are not run by db:seed, signals:setup --blank, or tenant:install.
What each seeder creates, how it behaves on a re-run and the full demo-data rules are listed in Seeder reference.
Demo data
A curated end-to-end demo dataset for development, evaluation, and demos — not a bulk load. It includes demo warehouses, customers, venues and contacts, rentals across every state, invoices and payments, sub-hire, flightcases, fleet, documents and dashboards. All demo records are tagged demo-data so they can be cleared later.
# Seed demo data
php artisan signals:seed-demo
# Remove eligible demo data
php artisan signals:clear-demo
Clearing is allowed in local and testing, and elsewhere only for a tenant explicitly flagged as demo. It refuses rather than touch non-demo or settled finance records. The full list of what is created, the clearing plan and every refusal are in Seeder reference → DemoDataSeeder.
Running Seeders
# Run all default seeders
php artisan db:seed
# Add the optional starter warehouse, catalogue groups, and 14 sample catalogue items
php artisan signals:seed-starter-content
# Run a specific seeder
php artisan db:seed --class=PermissionSeeder
php artisan db:seed --class=ViewSeeder
# Run in production (requires --force flag)
php artisan db:seed --force
php artisan db:seed --class=PermissionSeeder --force
You can also run seeders from the admin panel under Admin → System → Database Seeders, which shows the current status of each seeder and lets you run them individually.
Every seeder is safe to re-run except VolumeTestSeeder; the per-seeder keys are in Seeder reference → Idempotency.
Demo removal permanently deletes activities tagged demo-data, including archived activities. It leaves untagged activities outside that selection.