← Integration Hub

PAXX P1

Action requiredSetup requiredMOCK

The internal fulfillment system: shipments, warehouse topology, pallets, inbound/outbound flow, returns, tickets.

How it connects
Configured on the server
Health
healthy
Integration status
connected
Credential
Not configured
Last sync
never
Connected
not yet

0 of 1 steps done

Setup

  1. P1 has to expose these reads, then a connector can use them

    You are hereNot done yet
    Administrator (once)Automatic

    Mock-only, and blocked a step earlier than the others: P1 publishes no API surface for shipments, warehouse topology or tickets today. BUSINESS_OPERATIONS.md §6 is written as the specification for that work. Nothing an administrator can paste shortens this.

Configured on the server

Connect

Nothing — the business cockpit runs on fixtures until a real connector exists.

Setup required

Mock-only, and blocked a step earlier than the others: P1 publishes no API surface for shipments, warehouse topology or tickets today. BUSINESS_OPERATIONS.md §6 is written as the specification for that work. Nothing an administrator can paste shortens this.

Live check

Connection test

This provider declares no connection test — it makes no external call, so there is nothing to probe and a green result here would mean nothing.

3 declared

Permissions

What PAXX asks the provider for. The provider's own consent screen is the authoritative grant — this list is what will be requested, and after connecting, what was actually returned.

  • readRead shipmentsnot requested yetShipment status, carrier, hand-over and delivery timestamps.
  • readRead warehousenot requested yetSites, storage locations, pallets and occupancy.
  • readRead ticketsoptionalnot requested yetCustomer tickets, status and SLA clocks.

Capabilities

What you get

  • Shipments

    readNot available

    Status, carrier, hand-over and delivery timestamps — the basis for every on-time and SLA figure.

    Available once this provider is connected.

    /paxx/operations/paxx/operations/carriers

  • Warehouse topology and occupancy

    readNot available

    Sites, storage locations, pallets and occupancy. P1 is the only system that plans outbound waves, which is why the wave figure is read from it and nothing else.

    Available once this provider is connected.

    /paxx/operations/warehouse

  • Tickets and SLA clocks

    readNot available

    Customer tickets with their status and SLA clock.

    Available once this provider is connected.

    /paxx/operations/exceptions/paxx/operations/customers

Requirements

Diagnostics

Administrator requirements

One-time work for whoever administers this PAXX instance.

  • P1 has to expose these reads, then a connector can use them

    Not satisfied
    Administrator (once)Automatic

    Mock-only, and blocked a step earlier than the others: P1 publishes no API surface for shipments, warehouse topology or tickets today. BUSINESS_OPERATIONS.md §6 is written as the specification for that work. Nothing an administrator can paste shortens this.

Your requirements

Per-person steps — the authorization is yours, not the deployment's.

None.