Forkiva Docs

Set Up Print Agent ​

This guide covers the current Forkiva print-agent flow. Forkiva does not ask you to enter an agent ID or secret anymore. Instead, each branch is connected to a local Qintrix service by saving:

  • an API Key
  • a Host
  • a Port

Forkiva uses that active branch connection when a user chooses Direct Print from POS.

Qintrix website: qintrix.tenvoro.app

Before you start ​

Make sure these items are ready first:

  • A local Qintrix service is already installed and running on the branch machine or local network.
  • If you need the Qintrix service or access details, start from qintrix.tenvoro.app.
  • You know the Qintrix API key.
  • You know the Qintrix host and port.
  • Your printers are configured in Forkiva with valid Qintrix ID values.
  • At least one POS register exists for the branch if you want to direct-print bill, invoice, or waiter documents.

1) Create the branch print agent in Forkiva ​

Open Admin Panel → Print Agents → Create and complete these fields:

  • Name: Friendly label for the branch connection.
  • Branch: Target branch. This field is hidden for users assigned to a single branch.
  • Active: Turn on the connection immediately.
  • API Key: Qintrix credential used for API calls.
  • Host: Hostname or IP only.
  • Port: Qintrix service port.

Host field rules ​

  • Enter only the hostname or IP address.
  • Do not include http:// or https://.
  • Do not include a path such as /admin or /api.
  • Do not include the port in the host field.

Examples:

  • Valid: 127.0.0.1
  • Valid: printer-box.local
  • Invalid: http://127.0.0.1
  • Invalid: 127.0.0.1:3366
  • Invalid: printer-box.local/api

2) Activate the correct agent ​

Forkiva keeps one active print agent per branch. If you activate another one for the same branch, it becomes the active connection used by POS direct-print operations.

Use separate agent records only when you intentionally want to switch a branch between endpoints.

3) Configure printers for direct printing ​

Open Admin Panel → Printers and make sure each printer that should receive direct jobs has:

  • the correct branch
  • an active status
  • a valid Qintrix ID
  • the correct paper size when required

If the printer does not have a Qintrix ID, Forkiva can still show print previews, but direct printing cannot target that printer through Qintrix.

4) Test from POS ​

  1. Open POS Viewer.
  2. Open or pay an order.
  3. Choose Print.
  4. Select the branch or register if the dialog asks for them.
  5. Use:
    • Preview Print to open the browser print dialog.
    • Direct Print to send the document to Qintrix.

What documents can be printed ​

Depending on the order state and printer mapping, the print dialog can include:

  • Bill
  • Invoice for paid orders
  • Waiter copy
  • Kitchen tickets for matching kitchens

Troubleshooting ​

  • Direct Print button is disabled
    • Check that the branch has an active print agent.
    • Check that the selected printer has a Qintrix ID.
    • For bill, invoice, and waiter copies, make sure a POS register is selected.
  • Preview works but direct print does not
    • Verify the API key, host, and port in the branch’s print-agent record.
    • Confirm the Qintrix service is reachable from the user’s browser network.
  • Kitchen print appears but other direct-print actions stay disabled
    • Select a POS register in the print dialog.
  • Host validation fails
    • Remove the protocol, path, and port from the host field.

Tenvoro

Copyright © Tenvoro