PHPackages                             jeffersongoncalves/laravel-erp-support - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. jeffersongoncalves/laravel-erp-support

ActiveLibrary[Utility & Helpers](/categories/utility)

jeffersongoncalves/laravel-erp-support
======================================

ERP support — issues, service level agreements and warranty claims for the Laravel ERP ecosystem

10PHP

Since Jun 27Pushed todayCompare

[ Source](https://github.com/jeffersongoncalves/laravel-erp-support)[ Packagist](https://packagist.org/packages/jeffersongoncalves/laravel-erp-support)[ RSS](/packages/jeffersongoncalves-laravel-erp-support/feed)WikiDiscussions main Synced today

READMEChangelogDependenciesVersions (1)Used By (0)

Laravel ERP Support
===================

[](#laravel-erp-support)

ERP support — issues, service level agreements and warranty claims for the Laravel ERP ecosystem.

This package is the support (helpdesk) module of an ERPNext-native rebuild. It owns the post-sales service documents: support issues, the service level agreements (SLAs) that govern them, and warranty claims raised against sold serial numbers. The customer and serial number are referenced as dynamic links (`party_type`/`party_id`, `serial_no`), so the package depends only on [`jeffersongoncalves/laravel-erp-core`](https://github.com/jeffersongoncalves/laravel-erp-core) — there is no hard dependency on the selling or stock modules.

Features
--------

[](#features)

- **Support masters** — Issue types and service level agreements (with a default priority, enabled flag and per-priority response/resolution times).
- **Issues** — A support ticket with a subject, party (dynamic link), priority (`Low`, `Medium`, `High`, `Urgent`) and a status workflow (`Open`, `Replied`, `On Hold`, `Resolved`, `Closed`). Optionally tied to an issue type and a service level agreement, with an SLA `agreement_status` (`First Response Due`, `Resolution Due`, `Fulfilled`, `Failed`, `Paused`) and first-response/resolution timestamps.
- **Warranty claims** — A complaint raised against a sold serial number / item, with its own status workflow (`Open`, `In Progress`, `Resolved`, `Closed`, `Cancelled`) and resolution details.
- **Customizable Models** — Override any model via config (ModelResolver pattern).
- **Translations** — English and Brazilian Portuguese.

Compatibility
-------------

[](#compatibility)

PackagePHPLaravel`^1.0``^8.2``^11.0 | ^12.0 | ^13.0`Installation
------------

[](#installation)

```
composer require jeffersongoncalves/laravel-erp-support
```

Publish and run the migrations (the core package migrations must be published too):

```
php artisan vendor:publish --tag="erp-core-migrations"
php artisan vendor:publish --tag="erp-support-migrations"
php artisan migrate
```

Publish the config (optional):

```
php artisan vendor:publish --tag="erp-support-config"
```

Dynamic Links
-------------

[](#dynamic-links)

Issues and warranty claims reference their customer through a polymorphic-style dynamic link (`party_type` + `party_id`) and the warranty claim references the sold unit through a plain `serial_no` string. This keeps the support module decoupled from the selling and stock packages while still allowing those records to be resolved at the application layer.

Database Tables
---------------

[](#database-tables)

All tables use the configured prefix shared across the ERP ecosystem (default: `erp_`): `issue_types`, `service_level_agreements`, `service_level_priorities`, `issues`, `warranty_claims`.

Testing
-------

[](#testing)

```
composer test
```

License
-------

[](#license)

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

###  Health Score

21

—

LowBetter than 18% of packages

Maintenance65

Regular maintenance activity

Popularity2

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity11

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/411493?v=4)[Jefferson Gonçalves](/maintainers/jeffersongoncalves)[@jeffersongoncalves](https://github.com/jeffersongoncalves)

---

Top Contributors

[![jeffersongoncalves](https://avatars.githubusercontent.com/u/411493?v=4)](https://github.com/jeffersongoncalves "jeffersongoncalves (1 commits)")

### Embed Badge

![Health badge](/badges/jeffersongoncalves-laravel-erp-support/health.svg)

```
[![Health](https://phpackages.com/badges/jeffersongoncalves-laravel-erp-support/health.svg)](https://phpackages.com/packages/jeffersongoncalves-laravel-erp-support)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)