Shipping integration

EasyPost WMS Integration

Cybership connects EasyPost 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 EasyPost 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 carrier-platform integration using an authorized EasyPost account.

Shipment details are sent for supported rating and label workflows; selected service, label, cost, tracking, and related shipment results return to Cybership.

Synchronization and setup

Rating and label requests run during warehouse execution; tracking updates depend on the connected carrier-platform workflow.

Connect the account, confirm carrier accounts and credentials, configure packages and shipping rules, and validate rates, labels, documents, tracking, voids, and refunds.

Limitations and support ownership

Carrier services, account contracts, hazardous materials, international documents, refunds, and tracking behavior vary by carrier and account.

Cybership owns the WMS request, mapping, and response diagnostics. EasyPost and the underlying carrier own account eligibility, rates, service availability, and carrier events.

Buyer questions

Does Cybership integrate with EasyPost?

Direct Cybership carrier-platform integration using an authorized EasyPost account. Confirm the exact required data, actions, account configuration, and exception paths before implementation.

What should we test for the EasyPost integration?

Test authorization, representative data, normal workflows, cancellations or reversals, duplicates, retries, permissions, error evidence, reconciliation, and ownership. Carrier services, account contracts, hazardous materials, international documents, refunds, and tracking behavior vary by carrier and account.

Who owns integration troubleshooting?

Cybership owns the WMS request, mapping, and response diagnostics. EasyPost and the underlying carrier own account eligibility, rates, service availability, and carrier events.