# Tremol / ZFPLab settings audit
| Input | Persistence | Runtime consumer | Status |
|---|---|---|---|
| `tremol_enabled` | `FiscalDevice.is_active` | Active-device checks, fiscal payment jobs, Tremol client injection | Implemented |
| `tremol_platform` | Device config and per-platform profile | Selects Windows/Android profile in `tremolConfig()` and Company Fiscal API/client | Implemented |
| `tremol_connection_mode` | Device `connection_type` plus profile config | Client injection and fiscal API validation/claim configuration | Implemented |
| `tremol_server_host`, `tremol_server_port` | Profile config | Browser Tremol client and Fiscal API configuration | Implemented |
| `tremol_serial_port`, `tremol_baud_rate`, `tremol_keep_port_open` | Profile config | Browser client configuration | Implemented in the client path |
| `tremol_bluetooth_name` | Profile config (also used as fallback serial number) | Browser Android client configuration | Implemented |
| `tremol_device_ip`, `tremol_device_port` | FiscalDevice columns and profile config | Device/client and Fiscal API configuration | Implemented |
| `tremol_device_password` | FiscalDevice password and profile config | Fiscal API configuration | Partial: the settings form writes an empty password over the existing secret when left blank |
| `tremol_operator_number` | Profile config | Browser client and Fiscal API receipt job configuration | Implemented |
| `tremol_operator_password` | Profile config | Browser client and Fiscal API configuration | Partial: the settings form writes the default/empty value instead of preserving the existing secret when not re-entered |
| `tremol_vat_class` | Profile config | Fiscal API receipt item and browser client | Implemented in the current Company Fiscal path |
| `tremol_cash_payment_type`, `tremol_card_payment_type` | Profile config | Fiscal API payment-method mapping and browser client | Implemented |
The legacy `TremolFiscalService` still reads the global `config('fiscal.*')` settings and uses hard-coded operator/VAT defaults, so older reservation/receipt callers do not use the company device profile. The current Company Fiscal API and browser client do use the profile saved by this tab. The UI also exposes only cash/card mappings while the API supports additional mappings such as bank transfer, PayPal, and other.
## Fixes applied
- Blank device/operator password inputs preserve the existing stored secret during settings saves.
- Legacy TremolFiscalService now resolves the active company FiscalDevice profile for operator credentials and VAT defaults, with global config retained only as a compatibility fallback when no company device exists.