ERPNext POS · Integrations
ERPNext POS: plan the link between checkout and operations.
Using ERPNext? caisse.tn builds the connection on request with the first shop that needs it, then makes it available to everyone. These are the points we settle together: checkout, warehouses and business records.
Integration on request · built with the first shop
The role of each tool
ERPNext structures POS around profiles and business documents. caisse.tn is for shops seeking a direct route: choose products, set prices, prepare cashiers and sell. caisse.tn runs the counter alongside ERPNext; it does not replace its accounting or manufacturing functions.
The workflow to define
Start with a test company, shop and warehouse. Map item codes, units, price lists and taxes, then select the ERPNext documents expected for a sale, payment and return. The connection uses the Frappe REST API; we review your instance’s permissions, validation and customisations with you, then test it before opening it to other shops.
Questions for your project
- Which POS profiles, companies, warehouses and price lists are in scope?
- Are units, variants and taxes already normalised in ERPNext?
- Which document and payment account should receive each transaction?
- Who manages document submission, cancellation and reconciliation after sync?
Discuss your integration
Include the tool and version, your country, the data to exchange and a technical contact. Do not email passwords or API keys.
Each connection also depends on the provider’s API access and authorisation, and on availability in Tunisia: we check these at the start. Names belong to their respective owners. Inclusion does not imply affiliation, certification or endorsement.