Skip to main content

Common Use Cases

Use this page to decide quickly whether Doqlo Bulk Fill fits your workflow. Bulk Fill is strongest when you have one recurring PDF layout, structured data, and a recurring need to generate many finished PDFs with predictable output.

When Bulk Fill Is A Good Fit

Bulk Fill is usually a good fit when:

  • you already have a source PDF you want to keep using
  • the output layout stays stable across rows
  • the variable values already exist in CSV data today
  • you want to preview representative rows before you run the batch
  • you may want to automate the same validated workflow later with the API

Common Workflow Examples

Invoices

Use Bulk Fill when you export invoice rows from another system and need the same customer-ready invoice layout every time.

Certificates

Use Bulk Fill when the same certificate layout needs names, dates, IDs, or codes merged in from structured data.

Letters And Notices

Use Bulk Fill when you send a recurring letter format to many recipients and want to preview a few rows before you run the full batch.

Internal Forms

Use Bulk Fill when one approved form layout is reused for recurring internal paperwork or acknowledgements.

Packing Slips And Shipping Documents

Use Bulk Fill when operational data already exists elsewhere and you need a predictable PDF output for each row.

Operational Batch Documents

Use Bulk Fill when the same PDF pattern is reused for recurring notices, confirmations, or internal document runs.

When Bulk Fill Is Not A Good Fit

Bulk Fill is probably not the right tool when:

  • every document needs a different visual design
  • you need a full PDF editor or document authoring suite
  • the source content is unstructured and must be discovered automatically
  • the workflow is mostly one-off manual editing instead of repeatable output

In those cases, prepare the PDF elsewhere or use a different class of tool.

When To Use The Web App

Use the web app when you need to:

  • upload the source PDF
  • upload the CSV
  • place and map fields visually
  • preview representative rows
  • validate that the output looks right before export

When To Use The API

Use the API after the web workflow is validated and you want another system to:

  • execute the same packaged workflow repeatedly
  • trigger jobs from your own application or automation system
  • keep visual setup separate from repeatable runtime execution