Generate packing slips from your order data

Design a packing slip template once (item table, recipient, order reference, your branding), then turn each order into a finished PDF. One API call, or a no-code step from your store or spreadsheet.

# 1. Generate the packing slip: POST order data as JSON
curl -X POST https://api.shippdf.com/v1/documents \
  -H "Authorization: Bearer $SHIPPDF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "template_id": "tmpl_example",
    "data": {
      "order_ref": "SO-10492",
      "recipient": "Acme Receiving, 120 Dock St, Columbus OH",
      "items": [
        { "sku": "VC65-GAN", "name": "VoltCore 65W Charger", "qty": 2 },
        { "sku": "CBL-C100", "name": "USB-C Cable 1m",       "qty": 5 }
      ],
      "notes": "Pack fragile. Include returns insert."
    }
  }'
# → 202 { "id": "doc_a3...", "status": "queued" }

# 2. Check status, repeat until completed
curl https://api.shippdf.com/v1/documents/doc_a3... \
  -H "Authorization: Bearer $SHIPPDF_TOKEN"
# → { "status": "completed", "pdf_url": "…/packing-slip.pdf" }

Use your published template ID and a workspace API token with documents:create and documents:read. ShipPDF renders the order into a branded packing slip and returns a hosted pdf_url. Read the document again for a fresh link. Follow the API quickstart for a complete example and pagination details.

What is a packing slip?

A packing slip is the document that travels inside or on a shipment and lists what the box contains: the order reference, the recipient, and a line-item table of SKUs and quantities. Teams also call it a pack slip or a packing list. It lets the warehouse pick accurately and the receiver check the delivery against the order.

Because every order shares that structure, a packing slip is a natural fit for a template. You design the layout once and bind the recipient, order reference, and item list to data fields. Each order then generates its own PDF from the same template, so a busy fulfillment day and a quiet one cost you the same design work.

Why generate packing slips this way

One template, every order. Design the layout once in the visual editor, then change it once and every future packing slip follows.
Item tables build themselves. Map an items list and the table renders with your styling, however many lines an order has.
Barcodes and branding. Add an order barcode and keep your logo, colors, and layout consistent across every shipment.
Nothing to operate. No headless browser to patch or scale. Rendering is a predictable API call.

Generate packing slips without code

Prefer not to touch the API? Add a render step in n8n, Zapier, Make, Airtable or Google Sheets and map your order columns to the packing slip template, and a new order row becomes a branded PDF. See the packing slip use case for the fields and layout.

Questions

How do I create a packing slip template?

Design it once in the ShipPDF visual editor: add your logo, an item table bound to a data field, the recipient and order reference, and any fulfillment notes. Publish it, and every packing slip you generate uses that layout.

How do I generate packing slips at scale?

POST each order’s data to the ShipPDF API, or add a render step in a no-code tool like n8n, Zapier, Make or Google Sheets and map your order fields. One published template serves every order and every channel.

Can ShipPDF read or extract data from existing packing slips?

No. ShipPDF generates packing slips from your order data, it does not parse or extract data from documents you already have. If you need to pull data out of received packing slips, pair ShipPDF with an OCR or document-parsing tool and send the extracted fields to ShipPDF to generate a clean, branded version.

What is the difference between a packing slip and a shipping label?

A packing slip lists the order contents for the warehouse and the recipient. A shipping label carries the delivery address and carrier barcode on the outside of the box. ShipPDF generates both from your order data.

← Back to home