Packing slip PDFs in Node.js

Why packing slips become PDFs

A packing slip is printed and physically placed in a box. It exists to be paper. That is the difference between a document and a view of a database, and it is why warehouse and fulfilment teams keep asking for this.

What a packing slip has to carry

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

• the order reference, which the picker checks against the pick list
• each line with SKU, description and quantity shipped
• backordered lines shown explicitly rather than omitted
• the ship-to address as it will appear on the carton
• the carrier reference or tracking number where it exists

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("/packing-slip/:id.pdf", async (req, res) => {
  const html = await renderPackingSlip(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 packing slip never sits in memory.
  upstream.body.pipe(res);
});

The CSS that makes a packing slip page correctly

The layout problem specific to this document is that it must print correctly on the label and A5 stock warehouses actually use, not just on A4. These rules handle it.

/* Warehouses print on A5 and label stock, not A4. */
@page {
  size: A5;
  margin: 8mm;
}

.signature {
  break-inside: avoid;
  margin-top: auto;
}

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 packing slip lives afterwards

Rendering is the short part. The packing slip is thrown away when the box is opened. It has essentially no retention requirement, which is unusual on this list and worth knowing: the document does not need to be stored, only printed correctly the first time.

Getting the document right

• Check the order reference and quantities, which a picker checks against the physical goods.
• Generation is triggered by an order moving to fulfilment, so size the timeout for that path rather than for a health check.
• Volume arrives in bursts, so queue the render rather than doing it inside the request that triggered it.
• 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 packing slip in other stacks.