Does gPdf manage warehouse inventory?

No. Your WMS or ERP owns inventory state, locations, SKUs, lots, and process rules. gPdf renders the label PDF from final data.

Can warehouse labels use GS1 or SSCC barcodes?

Yes, gPdf can render supported barcode formats in PDF output. Your system owns the barcode payload and scanner acceptance.

Should repeated warehouse labels use templates?

Usually yes. Template Render gives print stations a stable template_id and data contract after the label layout is approved.

How should reprints work?

Store source label data or the generated PDF with your warehouse record, then render or retrieve the same label using the original operational IDs.

Logistics and labels

Warehouse label API for WMS and ERP print workflows

Generate pallet, case, bin, inventory, and warehouse-operation label PDFs from WMS or ERP data with deterministic reprints.

PRIMARY API JSON Render

ENDPOINT /api/v1/pdf/render

SYSTEMS WMS / ERP / warehouse print service / inventory workflow

Try in Playground → Read the docs

Job to be done

Render warehouse labels from WMS or ERP data for pallets, cartons, bins, assets, locations, and inventory movements, while keeping inventory state, picking rules, and warehouse operations in the caller's system.

When to use this API

You need pallet, carton, bin, location, inventory, or asset labels as PDFs.
Your WMS or ERP already owns SKU, lot, location, SSCC, and inventory data.
You need deterministic reprints when a label is damaged or a station retries a job.
You want approved label layouts to be reused through Template Render.

What it does not replace

You need gPdf to manage inventory, allocate locations, or run warehouse workflows.
You need a scanner app, print-station agent, or label-routing system from gPdf.
You need GS1 certification instead of barcode rendering.

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/pdf/render - pallet label with SSCC barcode data.

{
  "pages": [
    {
      "size": "label_4_6_in",
      "elements": [
        {
          "type": "text",
          "x": 6,
          "y": 8,
          "content": "PALLET LAX-01-2026-00042",
          "style": { "font_size": 12, "font_family": "NotoSans-Regular" }
        },
        {
          "type": "barcode",
          "format": "sscc-18",
          "content": "012345678901234567",
          "x": 6,
          "y": 30,
          "width": 88,
          "height": 26,
          "barcode_text": { "enabled": true, "position": "bottom" }
        },
        {
          "type": "text",
          "x": 6,
          "y": 70,
          "content": "SKU: CASE-001\nQTY: 48\nLOCATION: A-14-02",
          "style": { "font_size": 10, "font_family": "NotoSans-Regular" }
        }
      ]
    }
  ]
}

What gPdf handles

PDF labels for warehouse print workflows.
Vector barcodes, text, boxes, label page sizes, and template binding.
Deterministic output for reprint and audit workflows.
JSON Render for custom layouts and Template Render for approved label contracts.

What your system owns

Inventory state, SKU data, lot/serial data, SSCC values, and location semantics.
Printer routing, station setup, scanner validation, and warehouse process rules.
Template selection, retries, and storage of rendered PDFs or source data.

Production checklist

Validate label dimensions against the actual printer and label stock.
Scan every barcode format used by the warehouse process.
Keep WMS/ERP state authoritative and send only final label data to gPdf.
Use Template Render for labels that multiple systems or stations print.
Log source document IDs and request IDs for reprint traceability.

Claim boundaries

gPdf renders warehouse label PDFs; it does not manage inventory or warehouse state.
The caller owns barcode payload semantics and scanner acceptance.
Template Render can stabilize label layouts, but it does not replace WMS rules.

Warehouse labels are operational records

Warehouse labels identify pallets, cases, bins, assets, inventory movements, and locations. They are tied to operational state in your WMS or ERP. gPdf should receive the final label data and render it; it should not decide inventory meaning or warehouse process state.

Template Render keeps print stations simple

For labels used across multiple stations, publish the approved layout as a template. Print services can then send template_id plus WMS data instead of rebuilding coordinates in every caller.

Reprint determinism

Warehouses reprint labels. A damaged label, jammed printer, or station retry should not create a slightly different document. Keep source label data tied to the warehouse record and use deterministic render inputs for reprints.

FAQ

Does gPdf manage warehouse inventory?: No. Your WMS or ERP owns inventory state, locations, SKUs, lots, and process rules. gPdf renders the label PDF from final data.
Can warehouse labels use GS1 or SSCC barcodes?: Yes, gPdf can render supported barcode formats in PDF output. Your system owns the barcode payload and scanner acceptance.
Should repeated warehouse labels use templates?: Usually yes. Template Render gives print stations a stable template_id and data contract after the label layout is approved.
How should reprints work?: Store source label data or the generated PDF with your warehouse record, then render or retrieve the same label using the original operational IDs.