Shipping Integration APIDeveloper Portal
PAB Logistics › Developer API › Integrations
OMS - ERP - WMS - Ecommerce

Integration options

PAB provides a stable shipping interface between client order systems, warehouse operations and the carrier services enabled for each PAB account.

Available

Direct PAB API

Your server submits the canonical PAB shipment request and uses PAB shipment IDs for later tracking and labels.

Open implementation guides
Account specific

Managed source connector

PAB can read eligible orders from an approved order source, apply per-client service and packing rules, then present the order in the PAB customer workflow.

Available when enabled

CSV / XLSX import

Customers can upload a file, save mapping rules, validate the complete file and import valid orders into the PAB workflow.

Import walkthrough
Available when enabled

Pallet services

Pallet-enabled customers can book, label, track and review pallet consignments from the customer portal.

Pallet walkthrough
Managed Cin7 workflow

Typical Cin7 order flow

  1. PAB reads only orders that match the configured client status/date/customer filters.
  2. PAB maps the sale to the configured shipping service, shipment-note source and packing suggestion rules.
  3. Warehouse users confirm the actual parcel count and weights before labels.
  4. Label generation is the operational lock boundary for the shipment.
  5. Configured carrier/tracking/dispatch fields can be returned to Cin7 after the label exists.
Source system remains authoritative. PAB does not silently rewrite the customer's source order reference or use customer-facing provider-specific identifiers.

Handling missing delivery fields

For a managed pull connector, the source may not support a direct field-error response. PAB retains source identity and can apply a per-client opt-in city placeholder only where an attended correction process exists. A dot is not guaranteed to make a shipment fail allocation: it may print. Veeqo custom carrier integrations instead return the documented HTTP 400 {"errors":["Delivery city is required..."]} response, with no booking or fulfilment writeback.

Go-live pattern

Test before production

  1. Confirm the client account, credential model and enabled services.
  2. Validate sample orders and reference/idempotency mapping.
  3. Test one controlled live allocation and label.
  4. Confirm tracking/writeback behaviour where applicable.
  5. Enable scheduled sync or wider customer access only after the controlled test passes.