# POS settings tab wiring audit
The POS tab is persisted through `SettingsHelper` in the `pos` group and rendered from `config/pos-settings.php`.
## Wired or backed by existing components
- Fiscal printer settings are represented by the Tremol/fiscal device components and receipt controllers.
- Receipt generation and barcode/QR rendering exist in invoice and booking PDF controllers.
- Products and inventory have barcode fields and low-stock reporting paths.
- POS payment forms support cash/card and fiscal receipt processing through the existing payment services.
- Shift, cash drawer, and cashier workflows exist in Filament POS pages and related components.
## Partial or configuration-only
- The non-Filament company-admin POS settings form saves all keys, but most POS runtime screens read their own Filament `pos` settings or fiscal settings and do not consistently resolve these company values.
- `auto_print_receipt`, printer paper size/copies, receipt footer/logo, customer display settings, and barcode auto-add are not applied uniformly across every receipt/scanner path.
- `accept_mobile_payment`, `accept_vouchers`, and `split_payment_enabled` are not enforced in every checkout/payment endpoint.
- `auto_update_inventory`, `prevent_negative_stock`, and `low_stock_threshold` are not globally enforced by all inventory mutation paths.
- Shift start/end, supervisor approval, PIN controls, and daily report/email settings require the corresponding POS workflow; legacy admin endpoints do not consistently check them.
PHP syntax checks for the settings form and related POS components pass.