Settings

Enable and Monitor Desktop Connectors

Connectors are signed add-ons supervised beside the desktop till. They are not web-dashboard scripts, and a repeatedly failing connector parks itself without interrupting sales.

Menu path
Desktop app -> Manage -> Integrations -> Connectors
Verified from
Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence

Desktop connector UI and bridge behavior audited from current source 2026-09-04, frontend/modules/settings_write.html int-sub-connectors, frontend/static/script/js/modules/js/settings.js loadConnectors enableConnector disableConnector, Electron bridge connectors API

Desktop-only integration areaThe Connectors tab is added only when the Electron desktop bridge and connector runtime are available.
Choose the correct integrationUse webhooks for HTTPS change signals; use a published desktop connector only when an add-on must run beside the till.

When Connectors Appears

  • The tab is visible only in the desktop application when the Electron connector bridge is available.
  • It is intentionally hidden in the web dashboard and public demo browser.
  • Published connectors arrive through the till's normal update checks. If the list is empty, no connector package is currently installed.

Read Connector Status

StateMeaningOperator action
Not installedThe connector is known but its signed package is absent.Allow normal update checks; do not sideload an unverified package.
OffInstalled but disabled.Turn on only after confirming its purpose and data access.
RunningThe desktop supervisor has started it.Monitor its external service and expected results.
Parked / kept failingRepeated crashes caused the supervisor to stop restarting it.Inspect connector/runtime logs and configuration before re-enabling.

Enable a Connector

  1. Open the desktop app and go to Manage -> Integrations -> Connectors.
  2. Confirm the connector name and installed version.
  3. Click Turn on.
  4. Posnic creates a dedicated token and passes it directly to the desktop runtime; the plaintext is not shown for manual storage.
  5. Confirm the state changes to Running and perform one low-risk end-to-end test.
  6. Review API Tokens afterward so each enabled connector remains attributable.

Access and Failure Boundaries

  • The current enable flow mints a connector-specific customer Read and Write token for customer messaging, and nothing broader.
  • A connector runs beside the till, never inside the core sales process.
  • Connector failure must not stop checkout; repeated failures are parked for diagnosis.
  • Turning a connector off stops its runtime. Review and revoke obsolete connector credentials when permanently retiring it.

Troubleshooting

  • No Connectors tab: confirm this is the installed desktop till, not a normal browser, and restart after updates.
  • None installed yet: wait for a published connector through supported update checks.
  • Could not reach runtime: restart the desktop app and inspect local logs before changing tokens.
  • Could not mint token: verify authenticated shop context and integration API availability.
  • Parked: fix the connector's external credentials or crash cause before turning it on again.

Related Manual Pages

Settings API Tokens An API token is a standing machine credential. Its module permissions and the creating administrator's shop and branch context determine what the external system can reach. Settings Webhooks A webhook tells an external system that a selected entity changed. It deliberately carries no sale, customer or stock record; the receiver fetches details with its own scoped API token. Settings Integrations Integrations decide what can touch shop data from outside: tokens say who, webhooks say where signals go, analytics says what page visits are measured. Support Troubleshooting and Backup When something goes wrong, preserve evidence first: version, operating system, screen, sale, device, log, backup and exact step.