Is this page different from the shipping label page?

Yes. This is the broad logistics document page. Shipping labels and warehouse labels have narrower pages with more specific label and barcode guidance.

Does gPdf call carriers?

No. Your logistics stack handles carrier APIs, postage, shipment rating, and routing. gPdf renders PDFs from the data it receives.

Which endpoint fits logistics documents?

Use JSON Render for custom layouts and Template Render for approved repeated documents such as packing slips or warehouse labels.

Can logistics pages include barcodes?

Yes. gPdf renders barcode elements in PDFs, but your system owns the encoded payload and operational validation.

Logistics and labels

Logistics PDF API for labels, slips, and warehouse documents

Generate structured logistics PDFs such as labels, packing slips, waybills, manifests, and warehouse documents from WMS, OMS, and 3PL data.

PRIMARY API JSON Render

ENDPOINT /api/v1/pdf/render

SYSTEMS WMS / OMS / 3PL backend / carrier operations

Try in Playground → Read the docs

Job to be done

Render operational logistics documents from structured WMS, OMS, 3PL, and fulfillment data, while keeping carrier transactions, shipment routing, warehouse state, and business rules in the caller's systems.

When to use this API

You need PDFs for labels, packing slips, manifests, waybills, or warehouse paperwork.
Your logistics systems already know shipment, order, inventory, route, and carrier data.
You need deterministic reprints and high-volume API rendering.
You want a broad hub page that routes users to narrower label and warehouse workflows.

What it does not replace

You need gPdf to rate shipments, buy postage, or talk directly to carriers.
You need WMS, OMS, TMS, or inventory-management features.
You need native EDI, customs filing, or freight-broker workflows outside PDF generation.

Which endpoint to call

PRIMARY

/api/v1/pdf/render

JSON Render is the default path for this workflow.

SECONDARY 1

/api/v1/template-render

Use this when the workflow needs the related API path, template contract, or capabilities lookup.

Minimal request

POST /api/v1/template-render - repeated logistics document from structured data.

{
  "template_id": "packing_list",
  "data": [
    {
      "order_number": "SO-8421",
      "warehouse": "LAX-01",
      "ship_to": "Example Retailer, 88 Harbor Rd, Long Beach, CA",
      "items": [
        { "sku": "CASE-001", "description": "Widget case", "quantity": 4 },
        { "sku": "CASE-002", "description": "Replacement kit", "quantity": 1 }
      ]
    }
  ]
}

What gPdf handles

PDF rendering for structured logistics documents.
Label-sized pages, A4/letter documents, barcodes, tables, address blocks, and metadata.
Template Render for approved warehouse and fulfillment document layouts.
Deterministic output for reprints and audit records.

What your system owns

Shipment state, carrier service, routing rules, inventory state, and document eligibility.
Business data mapping from WMS, OMS, TMS, ERP, or 3PL systems.
Printer routing, storage, delivery, retry logic, and operational exception handling.

Production checklist

Decide which documents are direct JSON Render and which are templates.
Validate barcode, address, and table overflow cases for each document type.
Store the source data or PDF according to reprint and audit requirements.
Keep carrier API calls and render API calls as separate integration steps.
Link narrower pages for shipping labels and warehouse labels instead of duplicating their content.

Claim boundaries

gPdf generates logistics PDFs; it is not a carrier, WMS, OMS, TMS, or postage provider.
Shipment rating, label purchase, inventory state, and carrier operations remain outside gPdf.
This broad page should link to narrower solution pages for exact workflow intent.

Logistics documents are a cluster

Logistics PDF generation covers multiple document types: shipping labels, warehouse labels, packing slips, manifests, waybills, pick tickets, and internal handoff documents. This page is the broad entry point. Narrow pages should own exact search intent for labels and barcode-heavy workflows.

API usage pattern

Most logistics documents use either JSON Render or Template Render. JSON Render fits generated layouts or special documents. Template Render fits repeated documents where operations teams expect a stable layout and a small set of data fields.

Keep operational systems authoritative

Your WMS, OMS, TMS, 3PL platform, ERP, or carrier integration remains the source of truth for shipment state and business rules. gPdf receives the final document data and produces PDF output.

FAQ

Is this page different from the shipping label page?: Yes. This is the broad logistics document page. Shipping labels and warehouse labels have narrower pages with more specific label and barcode guidance.
Does gPdf call carriers?: No. Your logistics stack handles carrier APIs, postage, shipment rating, and routing. gPdf renders PDFs from the data it receives.
Which endpoint fits logistics documents?: Use JSON Render for custom layouts and Template Render for approved repeated documents such as packing slips or warehouse labels.
Can logistics pages include barcodes?: Yes. gPdf renders barcode elements in PDFs, but your system owns the encoded payload and operational validation.