Two-way sync
Changes in Easypost or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Keep Easypost and Kustomer in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Kustomer holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Easypost runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.
Stacksync links Companies, Custom Objects (Klasses), Users, Teams in Kustomer to Tracker, Batch, CarrierAccount, Webhook in Easypost with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.
The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.
A customer created in Easypost creates or updates the matching contact or account in Kustomer, so first-time and repeat buyers land in the relationship system without a manual import.
An email, phone, or shipping and billing address corrected in either system updates the other, so the next order and the next outreach both use current information.
Lifecycle stage, tier, or account owner set in Kustomer syncs onto the customer record in Easypost, so the buying side can act on how the relationship is classified.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Easypost objects | Kustomer objects | How this pairing syncs | |
|---|---|---|---|
| Webhook Event subscriptions delivering an Event via HTTP POST on object changes; full CRUD (create, retrieve, list, update, delete) and the mechanism for near-real-time change delivery to Stacksync. | Companies Organization records group customers and map to CRM accounts. | Webhook is specific to Easypost and Companies to Kustomer — each maps to any object or custom field on the other side. | |
| Shipment The central writable object: create with a to/from Address and Parcel, receive Rate options, then buy a label to get postage_label and tracking_code; retrieve and list with cursor pagination. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Shipment is specific to Easypost and Custom Objects (Klasses) to Kustomer — each maps to any object or custom field on the other side. | |
| Address Origin and destination locations; create, retrieve, and list, plus address verification (delivery and residential) to normalize and validate addresses before they are saved downstream. | Users Agent records map conversation ownership to people in other systems. | Address is specific to Easypost and Users to Kustomer — each maps to any object or custom field on the other side. | |
| Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. | Teams Team assignments support routing parity and reporting. | Parcel is specific to Easypost and Teams to Kustomer — each maps to any object or custom field on the other side. | |
| Rate Carrier service and price options EasyPost generates on a Shipment; read-only - you select a rate id and buy it, you do not create or edit rates directly. | Tags Labels on conversations and customers sync for categorization and analytics. | Rate is specific to Easypost and Tags to Kustomer — each maps to any object or custom field on the other side. | |
| Tracker Tracking for a shipment by tracking_code and carrier; create a Tracker to begin tracking, read status and tracking_details, and receive tracker.updated events via webhook as the parcel moves. | Notes Internal annotations carry context alongside synced conversations. | Tracker is specific to Easypost and Notes to Kustomer — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionEasypost notifies Stacksync of record changes through webhook events. Webhooks deliver an Event via HTTP POST on object changes (e.g.
DeliveryEach detected change is written to Kustomer through its API, with automatic retries and rate-limit backoff.
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryEach detected change is written to Easypost through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Easypost–Kustomer connection.
Changes in Easypost or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Easypost or Kustomer data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Easypost or Kustomer record.
Track your Easypost ⇄ Kustomer sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Easypost and Kustomer.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Easypost and Kustomer with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Easypost and Kustomer objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Easypost and Kustomer: authenticate both systems, choose the objects to sync (such as Easypost's Webhook and Shipment), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Easypost and Kustomer: New buyers become CRM records; Contact and address details stay consistent; Where Kustomer segments customers: status travels to the store record. A customer created in Easypost creates or updates the matching contact or account in Kustomer, so first-time and repeat buyers land in the relationship system without a manual import.
Easypost: REST API (EasyPost API v2, https://api.easypost.com/v2). Authentication: HTTP Basic auth with the API key as the username and an empty password (Bearer token also accepted); separate Test and Production keys. Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Stacksync manages authentication, retries, and rate limits on both sides.
Kustomer: Custom object types are called Klasses, and they are the standard mechanism for landing external data like orders and subscriptions where agents work. Easypost: Test and Production API keys are separate: test-mode calls do not create real labels or charges, so integration tests and dry-run backfills should run against the test key before touching production. Stacksync's field mapping accounts for these differences between Easypost and Kustomer without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Easypost and Kustomer records are not retained after a sync operation.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 376 integrations available for Easypost and Kustomer.