Import the approved file
Use the .docx your company already maintains. dokus saves the original and creates an exact document version with its fonts, tables, headers, and numbering.
From the Word file you already use to the document your customer receives.
Import the file. Mark what changes. Your application sends the values each time, and dokus keeps the versions and the record.
- .docx in
- Typed data
- PDF or DOCX out
- Recorded origin
Your app
Units
QUOTATION
Quotation Q-1042
Date 21 September 2026
Valid for 30 days
Prepared for Northstar Logistics in Rotterdam. This quotation covers the supply of 12 AC-4 access controllers for two distribution hubs.
DescriptionQtyUnitAmount
AC-4 access controller12€1,240€14,880
Subtotal€14,880
Total€14,880
Scope of supply. Each controller ships with its mounting kit, firmware at the current release, and access to the management console for the sites named above. Configuration templates are prepared from the customer’s existing site list before delivery.
Prices exclude VAT. Delivery is 4 to 6 weeks from order confirmation. Hardware carries a 24-month warranty.
Accepted on behalf of Northstar Logistics
Date
- Customercustomer.nametext
- Quote datequote.datetext
- Line rowtarget.row("line")repeat
- Installation clauseshow when installationrule
Built for this page. In dokus the page is your own Word file, rendered by the same engine that creates the PDF.
From upload to finished document.
dokus keeps the file and its rules. Your application sends the business data. Every output records exactly what created it.
Mark each changeable part
Turn names, dates, and amounts into typed fields on the approved text. Name the rows that repeat and the paragraphs or tables that appear only under certain conditions.
Send the values
Your server sends the document version, the blueprint, and the data. dokus checks the data before it creates the requested PDF or DOCX.
Keep a complete record
Each output points to the document version, blueprint revision, and input that created it.
Who does what.
The people who hold the document and the people who hold the application work on the same model, each with their own tool.
Document owner · Studio
Imports the approved file, marks the fields, and names the rows that repeat and the sections that appear only under certain conditions. No code.
Engineer · TypeScript
Writes the blueprint that binds application data to those fields and rules, validates it against the exact version, and saves it through the API.
Your application · runtime
Sends the values, receives the finished PDF or DOCX, shows the document in the browser, and keeps the run reference next to its own records.
When the document changes.
Wording changes on the document owner's schedule, not on your release schedule.
A revised file becomes a new draft version
Published versions never change. The new draft sits next to them until it is published.
Blueprints stay pinned
Each blueprint is written for an exact version. A person rebinds it after a compatibility check. dokus does not guess from position or similar text.
Older outputs stay explainable
Every document already sent remains linked to the version, blueprint, and data that created it.
See what the integration looks like in code, or start with your own file.