Skip to content
E-commerce ⇄ ERP

Easypost to Epicor ERP integration — real-time, two-way sync

Keep Easypost and Epicor ERP in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Easypost and Epicor ERP

Keep the storefront in step with the back office: Easypost and Epicor ERP share products, inventory, and orders in real time, in both directions.

Easypost runs the storefront and takes the orders; Epicor ERP owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.

Stacksync syncs Shipment, Address, Parcel, Rate in Easypost with Shipments, Bills of materials, Customers, Suppliers in Epicor ERP field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Epicor ERP, order and customer detail from Easypost — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Verify and normalize customer Addresses through EasyPost before they are saved to the CRM or OMS to cut failed deliveries and carrier address-correction surcharges.
  • 02 Sync CarrierAccount configuration and negotiated rates so shipping options stay consistent across the storefront, ERP, and 3PL systems.
  • 03 Push won opportunities from the CRM into Epicor as sales orders and sync order status back.
  • 04 Mirror parts, on-hand inventory, and job status into a reporting database for shop-floor dashboards.

Common sync patterns

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where Epicor ERP is the inventory system of record: stock stays accurate

Available quantities from Epicor ERP publish to Easypost, so the store shows what can actually ship and stops overselling.

New orders reach the back office

An order captured in Easypost creates the matching record in Epicor ERP with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

What you can sync between Easypost and Epicor ERP

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 Epicor ERP objects How this pairing syncs
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. Shipments Fulfillment confirmations synced to customer portals and commerce systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
CarrierAccount Carrier credentials and settings that control which carriers and negotiated rates are available; create, update, and delete to manage enabled carriers across accounts. Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. CarrierAccount is specific to Easypost and Jobs to Epicor ERP — each maps to any object or custom field on the other side.
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. Quotes Estimates that pair with CRM opportunities during the sales cycle. Webhook is specific to Easypost and Quotes to Epicor ERP — 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. AR invoices Billing records surfaced in CRM or finance tools for collections visibility. Address is specific to Easypost and AR invoices to Epicor ERP — 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. Bills of materials Methods of manufacturing read for costing and planning integrations. Parcel is specific to Easypost and Bills of materials to Epicor ERP — 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. Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. Rate is specific to Easypost and Customers to Epicor ERP — each maps to any object or custom field on the other side.

How changes propagate between Easypost and Epicor ERP

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.

Easypost Epicor ERP Sub-second propagation

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 Epicor ERP through its API, with automatic retries and rate-limit backoff.

Epicor ERP Easypost Interval-based propagation

DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.

DeliveryEach detected change is written to Easypost through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Easypost: Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests.
  • Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
What ships with Easypost ⇄ Epicor ERP

Connect Easypost and Epicor ERP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Easypost–Epicor ERP connection.

Real-time

Two-way sync

Changes in Easypost or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Easypost or Epicor ERP data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Easypost or Epicor ERP record.

Observability

Monitoring

Track your Easypost ⇄ Epicor ERP sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Easypost and Epicor ERP.

How the Easypost and Epicor ERP connectors work

Easypost

Integration surface
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
Change detection
Webhooks deliver an Event via HTTP POST on object changes (e.g. tracker.updated); historical pulls via list/index endpoints using before_id/after_id cursor pagination
Capabilities
read · write · webhooks
Rate limits
Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests
Easypost setup guide

Epicor ERP

Integration surface
REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
Authentication
API key combined with basic or token authentication, depending on version and deployment
Change detection
Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments
How it works

How to connect Easypost to Epicor ERP — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Easypost and Epicor ERP with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Easypost connected
    Epicor ERP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Easypost and Epicor ERP 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Easypost ⇄ Epicor ERP
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Easypost Epicor ERP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Easypost and Epicor ERP integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 468 integrations available for Easypost and Epicor ERP.

Popular · 7 of 468
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.