Shipping integration

USPS WMS Integration

Cybership connects USPS to the warehouse workflows the integration supports. This page defines the connection method, data direction, synchronization pattern, setup, limitations, and troubleshooting ownership so operators can evaluate a real implementation rather than a logo checklist.

Who Cybership is for

  • You need a supported USPS connection within Cybership
  • The integration has a named business owner and a testable warehouse workflow
  • Setup, data ownership, exceptions, limitations, and troubleshooting responsibilities will be documented

When to choose another approach

  • A logo-level connection is enough without testing the required data and exception paths
  • No one owns credentials, source-system configuration, or downstream behavior
  • The implementation assumes unsupported data or actions without written confirmation

What connects and how data moves

Direct Cybership integration using authorized USPS platform and customer credentials.

Shipment and package data is sent for supported rate and label operations; service, label, tracking, and shipment results return to Cybership.

Synchronization and setup

Rating and label requests run during warehouse execution; tracking events arrive according to the configured USPS workflow.

Complete USPS account authorization, confirm payment and mailing identifiers, configure packages and services, and validate domestic, international, label, tracking, void, and refund scenarios that apply.

Limitations and support ownership

Service eligibility, account approval, payment setup, mail classes, destinations, package rules, and USPS API behavior affect available workflows.

Cybership owns WMS-side request and response diagnostics. USPS owns account approval, payment, service eligibility, and carrier-network events.

Buyer questions

Does Cybership integrate with USPS?

Direct Cybership integration using authorized USPS platform and customer credentials. Confirm the exact required data, actions, account configuration, and exception paths before implementation.

What should we test for the USPS integration?

Test authorization, representative data, normal workflows, cancellations or reversals, duplicates, retries, permissions, error evidence, reconciliation, and ownership. Service eligibility, account approval, payment setup, mail classes, destinations, package rules, and USPS API behavior affect available workflows.

Who owns integration troubleshooting?

Cybership owns WMS-side request and response diagnostics. USPS owns account approval, payment, service eligibility, and carrier-network events.