For software houses
You connect the ERP and prepare the data of the documents once. Then your customers' offices change logos, texts and columns themselves, and you stop spending afternoons moving a field by two millimetres.
Who does what
Each side does what it knows best, on the same template.
Your software house
Your customer
How it works
From its organization settings, with the workspaces you may open. The role is given only by invitation.
Connection, read-only queries, field catalog and mapping: or apply your catalog for that ERP in one click.
Its people see only readable field names and change the graphics, without SQL.
You and its designers can ask for publication; the decision stays with the customer.
What you get
Everything below is in the product today.
The data partner role opens only the workspaces the customer chooses: data sources, gateways, queries, datasets, field catalog and mapping. Never members, billing, license, settings or API keys, and no direct publication.
Prepare once the readable names of an ERP's columns, the mapping of the ready-made templates and the queries you reuse, then copy them into each customer's template.
Every change and every data access of your people appears in the customer's settings, with source, rows and outcome, never the values.
Your organization sees the customers that invited its people and the workspaces you can open: names only, each customer separate.
Your customer stays in control
Partner program
There is no self sign-up: tell us about your software house, the ERPs you work with and your customers, and we enable your organization as a partner. Conditions for partners are discussed case by case.
Databases supported today: Oracle and PostgreSQL.
Only the workspaces each customer opens for you. There you work on data sources, queries and the field catalog; you never see members, billing, license, settings or API keys.
Yes: a catalog per ERP keeps the readable names of the columns, the mapping of the ready-made templates and your reusable queries. You copy it into each customer's template; later changes do not propagate, and no customer data ever goes into the catalog.
No. You can ask for publication, like the customer's designers; the customer decides who approves, and the decision is recorded.
Yes. The software house activity lists every change and every data access of your people in that organization, with filters by workspace and person, also after access is removed.
Oracle and PostgreSQL, directly over TLS or from private networks through the outbound-only Prynt Gateway. SQL Server and MySQL are coming soon.
Contact us: Prynt enables partner organizations, there is no self sign-up. Even before that, any customer can invite one of your people as its software house.
Tell us which ERPs you work with and how many customers print documents from them.