The Spanish version is the authoritative reference. View in Spanish
📊 xPOS-Core Dashboard
The Dashboard is the web interface that runs on the same machine as xPOS-Core. It lets you review the service's operational status, query processed documents, manage folios and run maintenance tasks on the installation.
This page describes the local console, the one running on the store machine. Centralized administration of the whole device fleet — Pool, Monitor, Versions, Logs — lives in the Customer portal (xPOS Gadget), which is a separate product and runs in the cloud.
🔐 Dashboard access
- Open a web browser on the machine where xPOS is installed.
- Go to the following address:
http://localhost:3200/dashboard/
- Sign in with the installation credentials.
| Field | Example value |
|---|---|
| Username | admin |
| Password | 1234 |
The credentials shown are examples: the real ones for your installation are provided during onboarding with the Gosocket team.
For xPOS-Core versions v2.X.X or higher:
For xPOS-Core versions v1.X.X or lower:
Once authenticated, you reach the main Dashboard:
Need to access it from another machine? See Remote access to xPOS-Core.
🆔 xPOS information
The top of the dashboard shows a summary of the main data of the installed xPOS:
- Version: version of the executable X.XX.X.
- xPOS name.
- UUID: unique identifier of the xPOS.
- Environment: Sandbox (SBX) or Production (PRD).
- Status:
- 🟢 Active: the xPOS can process documents.
- 🔴 Blocked: the xPOS cannot operate due to a block applied by the user from the administration portal or the xPOS Gadget.
- 🔴 Financial block: the xPOS cannot operate due to a block requested by Gosocket's finance and/or commercial team.
- 🔴 Expired version: the xPOS cannot operate because the version is discontinued and will not be supported.
🏢 Issuer selector (multiroot)
From xPOS-Core 2.6.0 onwards, a single device can have several issuers installed (several onboardings, each with its own certificate, credentials and folios).
When there is more than one issuer, the sidebar includes a selector that determines which issuer you are working with. It shows the current issuer highlighted, allows searching by name or identifier, copying the identifier and adding a new issuer.
Every dashboard view shows only the data of the selected issuer. The filter is applied on the server, not in the browser.
The issuer used to process each sale is determined by the origin parameter the POS sends in the API call — see Multiroot. The dashboard selector only decides what is displayed on screen.
📥 Home module
Summarizes the document transactions sent to the xPOS.
Metrics shown
- Processed documents ✅ — total documents generated correctly.
- Contingencies 🕓 — transactions performed in contingency mode.
- Failed documents ⚠️ — documents with errors during creation or sending.
- Queued documents ⏳ — documents pending delivery to the tax authority or to the Inbox portal.
📑 Documents module
Lets you explore the history of processed documents.
Available submodules
- Processed documents: documents processed correctly, with access to the generated output XML files.
- Contingencies: documents processed during a contingency, with access to the generated output XML files.
- Failed documents: documents that had an error, either during processing or due to rejection by the tax authority.
Information table
| Field | Description |
|---|---|
| UUID | Unique internal ID generated by xPOS. |
| Document type | Invoice, receipt, credit note, etc. |
| Folio | Folio number of the document. |
| PartnerFolio | Folio number assigned by the tax authority or the PAC. Only enabled for Guatemala. |
| Date | Document creation date. |
| Status at the tax authority | Final status of the document according to the tax authority's response: Accepted, Rejected or Pending (waiting to be processed or to have its final status updated). |
| Status in Inbox | Synchronization status with the Gosocket/Inbox portal: Pending or Synchronized. |
| Status in Kiosk | Synchronization status with the Kiosk product: Pending, Synchronized or Rejected. |
Sorting and filters
Up to the previous version, sorting and some filters operated only on the rows already loaded on screen. From 2.6.0 they apply to the full set of documents, resolved on the server.
- Sort by column: date, document type, document number, folio, partner folio and error stage. The header indicates which column is active and in which direction (ascending → descending → unsorted).
- Filters: document type, status before the authority (Accepted / Rejected / In process, plus Conditionally accepted in the Dominican Republic), error stage (only in Failed documents) and date range with presets (Today, 3 days, 7 days, custom range).
- Search by document number: also searches by transaction identifier.
- Active filters are shown as individually removable chips, with a Clear filters button.
Status columns are not sortable, because they are derived fields; to narrow them down, use the corresponding filter.
Available actions
- Copy ID: copies the document's UUID (transaction ID) in xPOS.
- View document: displays the tax XML or JSON, with a download option.
Available only in versions 1.XX.X.
Available from versions 2.1.X onwards.
- View tax authority response: displays the XML or JSON of the tax authority's response, with a download option.
Available from versions 2.1.X onwards.
🧾 Folios module
Displays the available folios and the subranges assigned by Folio Manager 3.0.
General actions
- Reload folios: requests folio subranges from FM 3.0 for all xPOS documents.
Actions at folio range level
- Release folios: releases the range from the current folio up to the established limit.
From version 2.6.0 onwards, both actions operate on the selected issuer and report the actual result of the operation, including the case where the reload threshold was not reached.
⚙️ Configurations module
Lets you run technical and administrative tasks on the xPOS.
Available actions
| Action | Button | What it does |
|---|---|---|
| New onboarding 🆕 | + TaxID | Opens the onboarding wizard to register a new organization (TaxID) on the device, allowing multiple onboardings. |
| Send logs | Enviar | Manually syncs and sends the local logs to the Portal for technical support analysis. |
| Reload configuration | Recargar | Forces the download of updated validation schemas, certificates and templates from the xPOS cloud. |
| Compact database 🆕 | Compactar | Returns to disk the space that the purge freed inside the file. The xPOS does not respond while it runs. |
| Healthcheck | Checklist | Runs a connectivity and integrity diagnostic to verify the state of the xPOS links and configuration. |
| Update version 🆕 | xUpdater | Checks the availability of security patches and software updates through xPOS-Updater. |
| Manual contingency | ON / OFF | Offline mode: holds documents locally without sending them to the tax authority. When deactivated, the automatic transmission queue resumes. |
| Reset xPOS | Reiniciar | Factory reset: removes all local configuration, revokes the credentials and unlinks the terminal's UUID. |
🆕 = available from version 2.6.0.
New onboarding (+ TaxID)
Registers another issuer on the same device, without uninstalling or affecting the ones already installed. It opens the onboarding wizard for the new tax-id, including its verification step.
Compact database
The nightly purge deletes old rows, but the space it frees stays inside the database file: the file does not shrink on its own. Compacting is what returns that space to disk.
When it finishes, the action reports the size before and after the operation and how long it took.
While compaction is running the xPOS does not respond: it does not process documents. Run it outside the store's operating hours. That is why the action reports how long it took — it helps size the window needed for subsequent runs.
Compacting reclaims space. It does not repair a damaged database. If you suspect an integrity problem, escalate to Gosocket instead of compacting.
Healthcheck
It is the same verification that runs as a mandatory step during installation — see Installation verification. From the dashboard it can be re-run at any time to diagnose an already operational device.
Update version (xUpdater)
Checks whether security patches or new versions are available, and opens the Updater dashboard without having to start the service manually on the machine.
Manual contingency
A switch that activates offline mode on the device: documents are issued and held locally, without being sent to the tax authority. When switched off, the automatic transmission queue resumes and the held documents are sent.
On activation, mandatory data for the responsible person and the reason is requested, and while it is active a warning banner is displayed on screen.
Reset xPOS
Factory reset: removes all local configuration, releases the folios to FM 3.0 (if applicable), revokes the credentials, restores the local database with no data and unlinks the terminal's UUID, leaving it in "inactive" state.
Resetting the xPOS deletes the installation's local data. On a device with several issuers, verify which one you are operating on before running it.