SIGNALS Docs
Reader View

Seeder reference

What each boot-start, starter-content, demo and volume seeder creates, the demo-data clearing rules, and how every seeder behaves when it is run again.

Overview

This is the per-seeder reference behind Seeders and Demo Data, which explains the four seed tiers and how to run them. Seeders can also be run from Database Seeders.

CanonicalApprovalChainSeeder

Publishes the immutable v1 approval definition used by the first internal order confirmation attempt (approval guard identity rental.transition.order): the rental.state_changed event filtered to from: quote and to: order, one unconditional owner_manager stage with all quorum, a 10080-minute expiry, auto_reject, and the Operations Manager fallback. It creates the canonical row only when that chain identity is absent; malformed or inactive existing definitions remain closed to conversion rather than being rewritten.

REST callers request this transition with POST /api/v1/rentals/{rental}/transitions and {"to": "order"}, using rentals.edit and rentals:write.

CountrySeeder

Loads all ISO 3166-1 country records from database/data/countries.json — 250 countries, each with a code, name, currency code, phone prefix, and default timezone. Uses updateOrCreate keyed on code — safe to re-run.

LanguageSeeder

Creates the single default language record, English (UK) (en), marked default and active. Every language string falls back to this record.

LanguageTranslationSeeder

Adds the optional UI languages alongside the default and upserts their translated string packs:

Code Language
en-srf English (UK) - SRF Opinionated
fr French (Français)
de German (Deutsch)
it Italian (Italiano)
es Spanish (Español)
pt Portuguese (Português)
zh Chinese (中文)

String packs are upserted on language_id + key and never overwrite a string that has already been translated in the UI — safe to re-run.

ListsSeeder

Creates the system-managed lists used throughout the platform (Admin → Option Lists). The editable contact and CRM lists are:

List Values
Address Type Billing, Shipping, Primary, Registered
Email Type Work, Personal, Billing, Support
Phone Type Work, Mobile, Home, Fax
Link Type Website, LinkedIn, Facebook, Instagram, X (Twitter), YouTube
Relationship Type Employee, Director, Contractor, Agent
Location Type Internal, External
Rating None, 1–5 Stars
Invoice Term Due on Receipt, Net 7/14/30/45/60/90, End of Month
Locale 17 locale codes (en-GB, en-US, fr-FR, de-DE, and others)
File Category Contract, Invoice, Quote, Purchase Order, Certificate, and 8 others
Vehicle Type Van, Truck 7.5t, Artic, Trailer, Car
Vehicle Assignment Role Delivery, Collection, On-site, Standby

It also seeds the read-only status and classification lists that mirror application enums, so reports and filters can label them: Activity Type, Credit Note Status, Invoice Status, Rental Status, Repair Status, Repair Reason, Stock Check Status, Stock Check Discrepancy Resolution, Warehouse Transfer Status, Asset Cost Type, Asset Retirement Reason, Usage Metric, Import Batch Status, Import Plan Status, Import Conflict Strategy, Import Source Format, Export Format, and Export Job Status.

All values are marked is_system = true and use updateOrCreate — safe to re-run.

CurrencySeeder

Inserts the missing codes of the full ISO 4217 catalogue (over 200 currencies) from brick/money, including each currency's name, symbol, and decimal places. Only GBP, USD, and EUR are enabled; everything else is disabled and can be switched on in settings. Uses insertOrIgnore keyed on code, so a re-run never changes an existing currency — safe to re-run.

ExchangeRateSeeder

Seeds two indicative manual rates effective 2026-01-01 so a clean install can price in more than one currency: GBP→USD at 1.27000000 and GBP→EUR at 1.18000000, each with its inverse. These are placeholder figures, not live market data — replace them before quoting in foreign currency.

WarehouseSeeder

Creates a default warehouse called Main Warehouse (GB, marked default) if no warehouses exist. It is starter content rather than boot-start reference data and runs before CatalogueItemSeeder when invoked through signals:seed-starter-content.

Note

The setup wizard (php artisan signals:setup) creates the operator's chosen warehouse instead. This seeder is primarily useful for automated development environments.

TaxTypeSeeder

Creates the default tax profile and item tax code records:

  • Customer tax profile: Standard (default)
  • Item Tax Codes: Standard (default), Exempt

It also writes the default item tax code into tax.default_item_tax_code_id when that setting is still unset. Uses updateOrCreate — safe to re-run.

TaxZoneSeeder

Creates the four tax zones used by zone-matching rules and attaches country memberships to each:

Slug Zone Account countries
uk United Kingdom GB
eu_account EU Account States Current EU account countries
eu_other EU Other CH, NO, IS, LI, AD, MC, SM, VA
world Rest of World Catch-all for every country not mapped above

If a default warehouse exists and has no zone, it is attached to the UK zone. Uses updateOrCreate keyed on slug — safe to re-run.

TaxCategorySeeder

Creates the four catalogue item tax categories used to classify catalogue items: Standard (default), Reduced, Zero Rated, and Exempt. Uses updateOrCreate keyed on slug — safe to re-run.

TaxRateSeeder

Creates three default tax rates suitable for UK VAT:

Name Rate
Standard 20%
Reduced 5%
Zero 0%

Uses updateOrCreate — safe to re-run.

TaxRuleSeeder

Creates the single class-map rule that ties the default customer tax profile and default item tax code to the Standard rate. Without it, TaxCalculator falls back to zero tax for an otherwise ordinary catalogue item/company pairing. Depends on TaxTypeSeeder and TaxRateSeeder.

TaxZoneRuleSeeder

Creates the UK-seller zone-matching rules used for cross-border scenarios. Higher priority wins; a null buyer type or tax-ID flag acts as a wildcard.

Priority Rule Result
110 Tax exempt supply (government) Exempt
110 Tax exempt supply (charity) Exempt
100 UK domestic Standard
90 UK to EU B2B reverse charge (validated tax ID) Reverse charge
80 UK to EU B2B without tax ID Standard
70 UK to EU B2C Standard
65 Outside scope supply (business, validated tax ID) Outside scope
60 UK export zero rated Zero rated

Uses updateOrCreate keyed on name, zones, buyer type, and tax-ID flag — safe to re-run.

RevenueAccountSeeder

Creates four revenue accounts used for categorising rental line items:

  • Dry Hire
  • Wet Hire
  • Sales
  • Services

Uses updateOrCreate — safe to re-run.

CostCategorySeeder

Creates five cost categories used for categorising rental costs:

  • Equipment Sub-Hire
  • Crew Sub-Hire
  • Transport
  • Consumables
  • Equipment Purchase

Uses updateOrCreate — safe to re-run.

CatalogueItemGroupSeeder

Creates 13 default catalogue item groups with sort order:

Audio, Lighting - Generic, Lighting - Moving Heads, Lighting - Battens, Lighting - Strobes, Lighting - Related items, Video, Staging, Power, Rigging, Furniture, Transport, Consumables.

Uses updateOrCreate — safe to re-run.

PermissionSeeder

Creates every permission used by the role-based access control system — over 200 keys following the resource.action naming convention. Most domains follow the same shape: an .access key that opens the UI area, a .view key that grants read, and then the write and workflow actions.

Area Domains
Administration settings.*, users.*, roles.*, numbering.*, email-templates.manage, notifications.manage, custom-fields.*, live-filters.manage_global, option_lists.*, tax-types.*, static-data.*, languages.*, webhooks.manage, events.read, plugins.manage, action-log.view, evidence.view, workflows.* (including publish)
CRM accounts.*, addresses.*, activities.*, conversations.*
Customer communications communications.draft (compose for review), communications.approve (approve, discard, and send)
Approvals approvals.view, approvals.act, approvals.manage
Sales rentals.* (including unlock_rates and dispatch_add_lines), projects.*, shortages.*, documents.*, document_templates.*
Finance invoices.* (including issue, billing-run, void, credit), credit-notes.apply, payments.record, costs.view
Purchasing purchase_orders.*, virtual_stock.*, virtual_assets.*
Catalogue catalogue-items.* (including suppliers), kits.*, rates.*, pricing.*
Warehouse assets.*, availability.view, flightcases.*, repairs.*, stock_checks.*, warehouse_transfers.*, dispatch.*, returns.*, scanning.*
Assets & compliance equipment_tests.* (including override_dispatch), equipment-test-results.*, equipment-test-certificates.*, usage-readings.*, asset-costs.*, asset-retirements.*, vehicles.*
Scheduling facilities.*, services.*, resource-assignments.*, scheduling-conflicts.*
Data & reporting reports.*, imports.* (including undo), exports.*
Interfaces api.*, cli.access, mcp.access, system.read, schema.read

Uses Permission::findOrCreate() — safe to re-run. The authoritative list is PermissionSeeder::permissions().

RoleSeeder

Creates the five system roles and assigns their default permission sets. Owner access is handled separately via the is_owner flag on users — it is not a Spatie role, and redundant Owner, Manager, Operator, or Viewer roles are deleted.

Role Cost visibility All warehouses Access level
Admin Yes Yes Every permission
Operations Manager Yes No Everything except settings.*, users.*, roles.*, numbering.edit, plugins.install, plugins.manage, and live-filters.manage_global, plus custom fields, import/export management, and the equipment_test dispatch override
Sales No No Rentals (not unlock_rates), projects, activities, conversations, invoices, purchase orders, virtual stock, payments, accounts and addresses, shortage view/resolve, quote and invoice documents, plus read-only catalogue items and reports
Warehouse No No Stock, catalogue items, flightcases, kits, repairs, stock checks, warehouse transfers, equipment_test results, usage readings, dispatch, returns, scanning, asset cost creation and retirements, plus read-only accounts, vehicles, equipment_tests, and reports
Read Only No No Every .view and .access permission except scanning, plus import/export viewing

All roles are marked is_system = true and cannot be deleted through the UI. RoleSeeder calls PermissionSeeder internally, so permissions always exist first.

DispatchStageSeeder

Creates the four outbound dispatch board stages, keyed and ordered:

Key Label Terminal
to_pick To pick No
picking Picking No
packed Packed No
loaded Loaded Yes

Uses updateOrCreate keyed on key — safe to re-run.

ReturnStageSeeder

Creates the four inbound returns board stages, keyed and ordered:

Key Label Terminal
due_back Due back No
receiving Receiving No
exceptions Exceptions No
closed Closed Yes

Uses updateOrCreate keyed on key — safe to re-run.

EmailLayoutSeeder

Creates the master Signals email layout in email_layouts — the branded chrome (shell, styles, header, body slot, footer) wrapped around every system email. It is a faithful conversion of the static Blade view resources/views/emails/layouts/signals.blade.php, which is retained as the hard fallback, so the two must stay visually in step.

Key Name Flags
signals Signals is_system, is_active, and is_default when no default exists yet

Re-running refreshes the name, description, and system flag but never overwrites an edited body, and it drops the cached default layout. See Email Layouts.

EmailTemplateSeeder

Creates the type-less global system email templates. Transactional and auth copy (magic-link, password reset, invitation, new-sign-in, digest) is seeded only as per-warehouse communication templates — see CommunicationTemplateSeeder and Notifications. Custom custom.* templates remain supported and are never overwritten.

Key Name Purpose
test_email Test Email Sent when testing email configuration from admin settings
embedding_budget_exceeded AI Embeddings Budget Exceeded Sent to administrators when the monthly AI token budget is reached

Templates support merge fields (e.g. {{ user.name }}, {{ company.name }}). Uses updateOrCreate keyed on key — safe to re-run.

NotificationTypeSeeder

Registers every notification type definition on the NotificationRegistry and syncs it to the notification_types table. Each definition carries a category, audience, available channels, default channels, default recipient rules, and a merge-field data schema used by the template editor.

Category Types
Workflows workflow.internal
Users user.invited
System update.failed, queue.job_failed, password.reset, auth.magic_link, auth.new_sign_in, notification.digest
Rentals rental.created, .confirmed, .cancelled, .on_hold, .checked_out, .checked_in, .late_return, .quote_expiring
Conversations conversation.mentioned
Shortages shortage.escalated, .acknowledged, .resolution.confirmed, .waitlist.created, .waitlist.matched, .waitlist.expired
Invoicing invoice.created, .overdue, .payment_received, .credit_note, statement.emailed
Documents document.finalised, .emailed, .public_link_created, .portal_question, .approved, .declined, invoice.portal_payment_received
Approvals approval_request, approval_outcome, approval_external_link
Compliance repair.created, .updated, .released, equipment_test.completed, .failed, .due, .overdue, certification.expiring, stock_check.closed
Flightcases flightcase.contents_overrun
Virtual Stock virtual_stock.overrun
Data import_batch.committed, .failed, import_plan.completed, .undone, export.completed, export.failed
Reports report.scheduled_delivery, report.threshold_alert
Scheduling scheduling.conflict_detected, .conflict_resolved, .demand_unmet, .assignment_confirmed, .assignment_cancelled, .assignment_rescheduled (no types for created/started/completed — audit trail only)

Syncing is non-destructive: user channel preferences and edited recipient rules survive a re-run. The authoritative list is NotificationTypeSeeder::types().

DocumentTemplateSeeder

Seeds the system document template set for every existing warehouse, so each warehouse gets its own editable copy. Templates are keyed system-{type} and marked is_system, is_default, and is_active; the body, header, footer, styles, and page config come from SystemDocumentTemplates::definitions().

The set covers quotes, invoices, credit notes, deposit invoices, pro formas, statements, receipts, delivery notes, priced delivery notes (Delivery Note (with prices)), pick lists, return lists, purchase orders, asset and asset labels, equipment_test certificates and summaries, catalogue item spec sheets, virtual stock summaries, repair reports, stock check reports, warehouse transfer manifests, activity summaries, fleet vehicle summaries, scan session reports, and flightcase manifests.

It also runs any document template seeders registered by active plugins. Seeding is idempotent per warehouse (firstOrCreate on warehouse + slug), and CreateWarehouse calls the same seeder with a bulk-insert fast path when a brand-new warehouse is created. See Document Templates.

CommunicationTemplateSeeder

Seeds the customer-facing communication templates for every existing warehouse, one per notification type that can be sent to a customer — magic link, password reset, user invitation, notification digest, rental created/confirmed/cancelled/checked out/late return/quote expiring, shortage escalated/waitlist matched, virtual stock overrun, equipment_test failed/due/overdue, certification expiring, invoice created/overdue/payment received/credit note, statement emailed, document emailed, scheduled report delivery, report threshold alert, and scheduling demand unmet.

Each template links to its notification type key and supplies the subject, body, eyebrow, preheader, and footer context rendered inside the email layout. Idempotent per warehouse, with the same fresh-warehouse bulk path as document templates.

ViewSeeder

Creates system-managed live filters for each entity type. These views appear in the API and UI view selectors and cannot be deleted by users.

Entity Views created
Accounts All Accounts (default), Companies Only, Contacts Only, Active Venues, Inactive Accounts
Catalogue items All Catalogue items (default), Rental Catalogue items, Sale Catalogue items, Active Catalogue items, Inactive Catalogue items
Assets All Assets (default), Barcoded Stock, Loose Stock
Activities All Activities (default), Scheduled Activities, Completed Activities
Catalogue Item Groups All Catalogue Item Groups (default)
Rentals All Rentals (default), Drafts, Quotes, Orders
Shortage Resolutions All Shortage Resolutions (default), Pending Resolutions, Confirmed Resolutions

Uses updateOrCreate keyed on name + entity type — safe to re-run.

RateSpecificationPresetSeeder

Creates the 11 standard rate specification presets from RatePresets::all(): Daily Rate, Weekly Rate, Monthly Rate, Hourly Rate, Half Hourly Rate, Fixed Rate, Fixed Rate and Factor, Fixed Rate and Subs Days, Daily Multiplier and Factor, Hourly Multiplier and Factor, and Monthly Multiplier and Factor. Presets are identified by a preset_slug and use updateOrCreate — safe to re-run. See the Rate specifications page for details on each preset.

DiscountGroupSeeder

Creates the three default discount groups used to classify CRM pricing agreements: Trade Discount, Preferred Customer, and Staff. Uses updateOrCreate keyed on name — safe to re-run.

RateBandSeeder

Creates the two default rate bands with their day tiers:

Category Tiers
Trade Day 1 at ×1.0000, Day 2+ at ×0.8000
Retail Day 1 at ×1.0000

Uses updateOrCreate keyed on name — safe to re-run.

CatalogueItemSeeder

Creates 14 sample catalogue items across rental, sale, and service types to demonstrate the catalogue, along with a default rate for each and stock (barcoded assets or loose quantities) in the default warehouse:

Group Catalogue items
Audio Shure SM58, JBL EON615, Yamaha TF1 Mixing Console
Lighting - Moving Heads Robe Esprite, Martin MAC Aura XB
Lighting - Generic Chauvet COLORado Panel Q40, ETC Source Four 750W
Video Barco UDX-4K32, Samsung 55" LED Display
Staging Stage Deck 8x4, Stage Leg 1m
Power Power Distribution 63A 3-Phase
Consumables Gaffer Tape 50m Black (sale item)
(none) Lighting Technician (service item)

Rental and service catalogue items are priced against the daily-rate preset, sale catalogue items against fixed-rate. Catalogue items are created with firstOrCreate keyed on sku (rates on catalogue item + warehouse + transaction type, stock on asset number) — safe to re-run. It depends on CatalogueItemGroupSeeder, TaxTypeSeeder, RateSpecificationPresetSeeder, and a warehouse having run first.

ReportSeeder

Creates the thirty-four system reports every install starts with, built on the rentals, invoices, net_tax_facts, credit_notes, purchase_orders, accounts, catalogue_items, assets, equipment_test_results, and repairs report sources:

Report Key Source What it answers
Revenue by Warehouse revenue-by-warehouse invoices Posted ex-tax invoice revenue and invoice count per warehouse over the last twelve months, excluding proformas.
Outstanding Invoices outstanding-invoices invoices Posted unpaid gross balance and invoice count by invoice status, excluding proformas.
VAT Return vat-return net_tax_facts Signed posted invoice and effective credit tax by document currency and rate, last quarter; currency-separated subtotals, no grand total
Tax by Treatment tax-by-treatment net_tax_facts Signed posted invoice and effective credit tax by document currency and treatment, year to date; no mixed-currency total
Invoiced Revenue by Month invoiced-revenue-by-month invoices Posted invoiced, paid and outstanding totals per calendar month over the last twelve months, excluding proformas.
Payments Received by Month payments-received-by-month invoices Gross cash collected from posted invoices per calendar month, excluding proformas and windowed on when each invoice was paid.
Revenue by Currency revenue-by-currency invoices Posted ex-tax revenue accounted by billing currency but valued in base currency this year to date, excluding proformas.
Top Clients top-clients invoices Accounts ranked by posted, ex-tax invoice revenue over the last twelve months.
Pipeline by Stage pipeline-by-stage rentals Value and count of enquiries, quotes, and orders raised, last twelve months
Rental Turnover by Warehouse rental-turnover-by-warehouse rentals Charge value and job count per warehouse, by hire start date
Rental Revenue by Month rental-revenue-by-month rentals Charge value of rentals per calendar month, by hire start date
Revenue Mix by Warehouse revenue-mix-by-warehouse rentals Rental, sale, and service charge split per warehouse
Upcoming Shortages upcoming-shortages rentals Rentals starting in the next thirty days that are short of equipment, by warehouse
Uninvoiced Orders uninvoiced-orders rentals Orders that have started but carry no invoice yet, by account
Aged Receivables aged-receivables invoices Posted overdue gross balance and invoice count per account, excluding proformas.
Credit Notes by Status credit-notes-by-status credit_notes What was credited back to customers, by credit note status, last twelve months
Supplier Spend supplier-spend purchase_orders Purchase order value per supplier, by the date each order was placed
Fleet by Warehouse fleet-by-warehouse assets Non-virtual equipment held, allocated and unavailable at each warehouse, excluding assets retired by the reporting date.
Equipment Test Outcomes equipment-test-outcomes equipment_test_results Pass and fail counts per test, last twelve months, with subtotals
Repairs by Status repairs-by-status repairs Equipment in repair by status and the reason it was raised, with subtotals
New Accounts by Type new-accounts-by-type accounts Accounts added over the last twelve months by contact, company, and venue
Catalogue Composition catalogue-composition catalogue_items Item count per catalogue type, split by active state, with subtotals

The rental reports window on starts_at — the date the kit goes out — except pipeline-by-stage, which asks when work came in and so windows on created_at. uninvoiced-orders and upcoming-shortages state their scope as filters in the definition (orders only, not yet invoiced; short of equipment) rather than leaving it to whoever reads the figures.

The two tax reports read net_tax_facts: signed posted invoice tax and already-signed effective Issued/Applied credit reversals. They never recalculate frozen tax or apply the sign twice. Both window on tax_point_at (invoice issue date or the credit tax row's own frozen date), group first by document currency, and disable grand totals and totals rows. Missing dates, unresolved prior posted voids and inconsistent retained evidence can refuse export; see VAT-return reports for exact scope and reconciliation.

Tax-report repair is conservative: ReportSeeder refreshes only exact, unmodified recognized system VAT Return/Tax by Treatment definitions. Customized or otherwise changed tax reports remain untouched for review; rerunning the seeder does not certify that every saved report uses the net source.

Upgrades do not run this seeder automatically. Run php artisan db:seed --class=ReportSeeder --force to refresh unchanged system tax reports. Edited or tenant-owned reports stay unchanged for maintainer review; report identities, pins and schedules are retained. See Seeded data when upgrading.

aged-receivables is the one report whose filter is relative rather than only its window: it asks for invoices due before {today}, resolved at execution in the company timezone, so "overdue" means overdue on the day someone runs it. The resolved instant is part of the result cache key, so it can never serve yesterday's list.

fleet-by-warehouse and repairs-by-status carry no money measure. An asset and a repair record no cost of their own — those figures live on asset_costs — so a spend-per-repair report is a question for a future source rather than one these can answer.

Each is seeded with visibility = system, so it is visible to every user, owned by nobody, and refused if anything tries to delete it. Definitions repository a relative date token (last_12_months) rather than fixed dates, so a seeded report still means "the last twelve months" a year from now.

Reports are addressed by their stable key, which is what lets a dashboard report widget — or a plugin — point at one without knowing its id. Uses firstOrNew on key — safe to re-run, and it restores a system report that has gone missing.

DemoDataSeeder

A curated end-to-end demo dataset for development, evaluation, and demos — not a bulk load. It creates:

  • 3 demo warehouses (London Warehouse, Manchester Depot, Edinburgh Office)
  • Roughly 10 companies, 10 venues, and 10 contacts with addresses, relationships, and notifications
  • Account enrichment: discount groups and rate bands with tiers, plus EU B2B, charity, tax-exempt, and rest-of-world tax variants
  • 13 standard catalogue groups, plus catalogue item enrichment: suppliers, kits, bundle rules, assets, repairs, stock checks, warehouse transfers, and a flightcaseable barcoded catalogue item with assets
  • Around 12 rentals across enquiry, quote and order states, including dispatched and returned orders — including agreed prices, surcharges, quantity breaks, quote versioning, costs, participants, and a multi-currency deal
  • Quote-to-cash: draft, paid, partial-with-refund-and-credit-note, deposit, pro-forma, and overdue invoices, plus billing runs and payments
  • Sub-hire: a draft purchase order plus a sent/received one with confirmed virtual stock intake
  • Flightcases, fleet vehicles and compliance, dispatch and returns workflows, generated and portal-approval documents, communication logs, webhooks, custom fields, and activities
  • Three dashboards for the demo owner — a blank My Dashboard (the active tab), plus Sales and Operations built from those role presets — created only when that user has no dashboard of their own

The lighting showcase catalogue step seeds a showcase of real catalogue items taken from the supplier catalogue item pages: 10 moving heads, 10 battens, and 4 strobes (the site lists only four strobes), plus the 35 clamps, safety bonds, power tails, PSUs, and brackets those pages list as related items. Fixtures are barcoded rental stock with serialised assets in the default warehouse, priced on the weekly-rate preset at the weekly list price published for the fixture — two of the 24 prices are estimates, flagged as "price_source": "estimate" in the source data. Related items use loose stock and cannot be added as standalone lines. They are linked to their fixture with Included and Included free enabled, so adding a fixture to a rental adds those related item rows at no extra charge. The catalogue is read from database/seeders/data/catalogue/lighting-showcase.json and the catalogue item photography ships alongside it in database/seeders/data/catalogue/images, uploaded through FileService::uploadIcon() on the first run. Everything is keyed on the DEMO-LTS- SKU prefix, so re-running the step never duplicates an item, an asset, a rate, or a related item link.

All demo records are tagged demo-data so they can be identified and cleared later. This seeder is not included in the default DatabaseSeeder. Use the Artisan commands below.

# Seed demo data
php artisan signals:seed-demo

# Remove eligible demo data
php artisan signals:clear-demo

signals:seed-demo records setup.demo_seeded_at and refuses a second run unless --force is supplied. The curated seeder reuses its tagged cohorts on a forced re-run; use signals:clear-demo when you want to remove the demo tier.

Clearing demo data is not a total reset after a billing run has been issued. Billing runs with any immutable issue-attempt evidence are retained, including historical attempts that are no longer active, and the command reports the number of retained demo runs. Eligible unissued demo runs can still be removed. Neither --force nor --force-demo-finance-purge bypasses this protection.

signals:clear-demo is refused outside local and testing unless the tenant is explicitly flagged as demo (instance.is_demo or flags.demo). This includes production and staging, even when no finance history exists. Force flags cannot bypass the environment/tenant refusal, which is audited. Self-hosted production installations have no tenant demo flag and cannot use this command to clear demo data seeded during setup.

For an allowed environment or demo tenant, the command removes the demo invoices and their append-only finance history in one database transaction. That history includes financial postings and posting lines, credit issue effects, billing issue effects, and protected invoice, payment and credit events:

  • It removes only the finance rows of the invoices it clears. The finance history of every other invoice stays unchanged.
  • Before it changes anything, it prints the plan: the invoice ids and the number of postings, posting lines, effects, and events it will remove. Inside the transaction it makes the plan again, locks the planned invoices, accounts, warehouses, rentals, and catalogue items, and stops and rolls back if the plan is different. It then deletes those records by their planned ids, so a record tagged demo-data after that point stays. On PostgreSQL it stops and rolls back when it waits more than 10 seconds for a lock, for example behind a user transaction.
  • It refuses and changes nothing when:
    • a non-demo record would be deleted or changed through a foreign key when the clear removes a demo record: a non-demo invoice on a demo account, warehouse, or rental; a non-demo invoice line that names a demo catalogue item or a demo rental line; a credit note of a non-demo invoice on a demo warehouse; a non-demo billing run item on a demo warehouse, or a demo billing run that also holds non-demo items; an asset cost that names a demo supplier account; a credit decision, reservation, or override of a non-demo account that names a demo rental; or a posting line outside the plan that names a demo account, warehouse, or rental;
    • the demo finance history is linked to data outside the demo tier (for example, a posting for a real invoice that names a demo event, or a demo event that is also on a non-demo record);
    • the demo invoices have settlement, write-off, settlement exception, or payment timestamp evidence;
    • an invoice with finance history, its account, or its rental has no demo-data tag (a DEMO-INV- reference or a return charge on a demo rental is not enough);
    • a planned row was written after setup.demo_seeded_at, or a planned event names a user who is not the demo owner ([email protected], else the first owner). Only user actors are checked; API, agent, workflow, plugin, and system actors are not. After an ownership transfer the seeded events name the original owner, so the clear refuses them.
  • It removes finance history only when setup.demo_seeded_at is set. An explicitly flagged demo tenant outside local and testing also needs --force-demo-finance-purge. This option confirms finance removal for an eligible demo tenant; it never grants production clearing to an ordinary tenant. In an interactive terminal the command still asks for finance confirmation, even with --force. For an eligible unattended run, supply --force --force-demo-finance-purge -n. Captured output without -n refuses instead of waiting for an invisible prompt.
  • The append-only protection stays in place. The command lets its own deletes through only for the row ids in the plan, only inside its transaction, and it closes that window before the rest of the clear runs. If a step fails, the transaction rolls back and all data stays, including the demo icon files, which it deletes only after the commit.
  • It writes one demo.finance_history_purged action log entry for each demo invoice whose finance history it removed, with the removed ids, a SHA-256 digest of each removed row, and the totals. Older action log entries that name a removed event keep their verb_event_id; the purge entry records how many there were.
# Local or testing, without prompts
php artisan signals:clear-demo --force -n

# Cloud: ONLY explicitly flagged demo tenants may clear outside local/testing.
# Each ordinary production/staging tenant refuses and is reported as failed.
php artisan signals:tenants:run "signals:clear-demo --force --force-demo-finance-purge -n"

The optional RentalDiaryDemoSeeder and AvailabilityDemoSeeder purge their own tagged fixtures inside a transaction. Retained accepted pricing manifests refuse deletion; the purge rolls back every change, including account history written by deleting observers. Matching search entries are removed in the same transaction with per-row search dispatch suppressed. A refusal restores prior deletions and search entries. Manifestless fixtures can still be removed. These fixture purges do not grant an exception to pricing-evidence retention.

VolumeTestSeeder

A load and performance testing tool, not an end-user demo, and hidden from the admin panel unless SIGNALS_VOLUME_SEEDER=true. It bulk-inserts 2,000 companies, 500 venues, and 3,000 contacts (configurable on the seeder class) with emails, phones, and relationships, to exercise list pagination, search, and N+1 behaviour. Records are tagged volume-test and are removed by signals:clear-demo alongside demo data.

Idempotency

Almost every seeder uses updateOrCreate, firstOrCreate, upsert, or findOrCreate and is safe to run repeatedly:

  • CountrySeeder — updateOrCreate on code
  • LanguageSeeder / LanguageTranslationSeeder — updateOrCreate on code; strings upserted without overwriting existing translations
  • ListsSeeder — updateOrCreate on list and entry name
  • CurrencySeeder — insertOrIgnore on code
  • ExchangeRateSeeder — updateOrCreate on currency pair and effective date
  • WarehouseSeeder — no-op once any warehouse exists
  • TaxTypeSeeder / TaxCategorySeeder / TaxRateSeeder — updateOrCreate on name or slug
  • TaxZoneSeeder — updateOrCreate on slug, memberships re-synced
  • TaxRuleSeeder / TaxZoneRuleSeeder — updateOrCreate on the rule's matching keys
  • RevenueAccountSeeder / CostCategorySeeder / CatalogueItemGroupSeeder — updateOrCreate on name
  • PermissionSeeder — Permission::findOrCreate()
  • RoleSeeder — Role::findOrCreate() and syncPermissions()
  • DispatchStageSeeder / ReturnStageSeeder — updateOrCreate on key
  • EmailLayoutSeeder — updateOrCreate on key; never overwrites an edited body
  • EmailTemplateSeeder — updateOrCreate on key
  • NotificationTypeSeeder — syncToDatabase() via the registry, preserving preferences
  • DocumentTemplateSeeder / CommunicationTemplateSeeder — firstOrCreate on warehouse + slug
  • ViewSeeder — updateOrCreate on name + entity type
  • RateSpecificationPresetSeeder — updateOrCreate on preset_slug
  • DiscountGroupSeeder / RateBandSeeder — updateOrCreate on name
  • CatalogueItemSeeder — firstOrCreate on sku
  • ReportSeeder — firstOrNew on key; restores a missing or soft-deleted system report
  • DemoDataSeeder — reuses tagged demo cohorts; the command requires --force after the first run
  • VolumeTestSeeder — not idempotent; use signals:clear-demo before re-seeding

Demo removal permanently deletes activities tagged demo-data, including archived activities. It leaves untagged activities outside that selection.