Purchase order PDFs in Node.js

Why purchase orders become PDFs

A purchase order is the document a supplier's accounts team matches an invoice against, and it travels by email between two organisations that share no system. That is the difference between a document and a view of a database, and it is why procurement teams keep asking for this.

What a purchase order has to carry

Before any of the code below matters, the template has to produce a document that is actually a purchase order. These are the fields that make it one, and the ones a reader or an auditor will look for first.

• the PO number, which the supplier invoice must quote back
• the ordering entity and the ship-to address, which are often different
• the bill-to address and any cost centre or GL code
• each line with the agreed price, not the supplier list price
• the delivery date required, and the approval reference

The Node.js implementation

fetch ships with the runtime, so this adds no dependency. The render happens in a route handler that returns the response body directly, and you pipe the response body straight to res, so the PDF never lands in a Buffer.

app.get("/purchase-order/:id.pdf", async (req, res) => {
  const html = await renderPurchaseOrder(req.params.id);

  const upstream = await fetch("https://api.pdfpipe.xyz/v1/pdf", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.PDFPIPE_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      html,
      options: { format: "A4", printBackground: true },
    }),
  });

  if (!upstream.ok) throw new Error(`render failed: ${upstream.status}`);

  res.setHeader("Content-Type", "application/pdf");
  // Streamed, not buffered: a long purchase order never sits in memory.
  upstream.body.pipe(res);
});

The CSS that makes a purchase order page correctly

The layout problem specific to this document is that delivery and billing addresses sit alongside a line item table, and both must stay on the first page where a supplier looks for them. These rules handle it.

/* Backgrounds are dropped unless printBackground is set on the
   request, which is the usual reason a document renders in plain
   black and white when it looked right in the browser. */
@page {
  size: A4;
  margin: 18mm 16mm;
}

table { break-inside: avoid; }
h2    { break-after: avoid; }

What goes wrong in Node.js

Node buffers the whole response if you call res.send(await res.arrayBuffer()). On a 40-page report that is tens of megabytes held per concurrent request, and it is the usual reason a PDF endpoint takes down an otherwise healthy service under load.

What people try first

Most Node.js projects reach for puppeteer, which pulls a 300 MB Chromium download into your image and needs its own memory headroom on every instance. That works until it is running on more than one machine, at which point the browser becomes the thing you operate rather than the thing you use.

Where the purchase order lives afterwards

Rendering is the short part. A PO is retained alongside the invoice it authorised, because the pair is what an auditor matches. In practice it lives in the procurement system for as long as the supplier relationship does, which is longer than most teams plan for.

Getting the document right

• Check the PO number, because an invoice quoting the wrong one will not be paid.
• Generation is triggered by an approval completing in a procurement workflow, so size the timeout for that path rather than for a health check.
• These are produced one at a time by a person who is waiting, so latency is felt directly.
• Backgrounds are painted by default here, so a design that uses colour needs nothing set. Only an explicit print_background of false turns them off.

Frequently asked

Related

Other Node.js documents, and the same purchase order in other stacks.