Real-time
Two-way sync
Changes in Box or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ ERP
Box to Epicor ERP integration — real-time, two-way sync
Keep Box 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 Box and Epicor ERP
Move the documents and data that Epicor ERP produces into Box as files, and let files stored in Box update the records they belong to in Epicor ERP, continuously and without exports or manual filing.
Epicor ERP runs the business on structured records: Bills of materials, Customers, Suppliers, Parts. Box holds files and the metadata that describes them: Tasks, Events, Files, Folders. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Epicor ERP touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Box, from signed contracts to vendor bills to receipts, describe a transaction Epicor ERP needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.
Stacksync keeps Bills of materials, Customers, Suppliers, Parts in Epicor ERP and Tasks, Events, Files, Folders in Box in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Box already labeled and filed, and metadata captured against a stored file can create or update the matching record in Epicor ERP. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.
The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Epicor ERP and the file in Box never describe two different versions of the same document.
Common use cases
- 01 Sync shipment confirmations out to commerce platforms and customer portals as jobs complete.
- 02 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
- 03 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
- 04 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
Common sync patterns
An archive that stays current
As records change in Epicor ERP, the corresponding files and metadata in Box are kept in step, so a stored document reflects the latest version rather than a stale one-time export.
Audit-ready retention
Every transaction's supporting file lives in Box beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Epicor ERP.
Documents filed with their context
Files that Epicor ERP produces land in Box labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.
What you can sync between Box 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.
| Box objects | Epicor ERP objects | How this pairing syncs | |
|---|---|---|---|
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | Events is specific to Box and Jobs to Epicor ERP — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | Quotes Estimates that pair with CRM opportunities during the sales cycle. | Files is specific to Box and Quotes to Epicor ERP — each maps to any object or custom field on the other side. | |
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | AR invoices Billing records surfaced in CRM or finance tools for collections visibility. | Folders is specific to Box and AR invoices to Epicor ERP — each maps to any object or custom field on the other side. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Shipments Fulfillment confirmations synced to customer portals and commerce systems. | Metadata is specific to Box and Shipments to Epicor ERP — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Bills of materials Methods of manufacturing read for costing and planning integrations. | Collaborations is specific to Box and Bills of materials to Epicor ERP — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. | Users is specific to Box and Customers to Epicor ERP — each maps to any object or custom field on the other side. |
How changes propagate between Box 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.
Box Epicor ERP Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is written to Epicor ERP through its API, with automatic retries and rate-limit backoff.
Epicor ERP Box 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 Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
- Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
What ships with Box ⇄ Epicor ERP
Connect Box and Epicor ERP for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Epicor ERP connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box 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 Box or Epicor ERP record.
Observability
Monitoring
Track your Box ⇄ 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 Box and Epicor ERP.
How the Box and Epicor ERP connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
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 Box 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.
- 01
Connect your apps
Authenticate Box 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.
Box
connected
Epicor ERP
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box 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.
objects · Box ⇄ Epicor ERPCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Box Epicor ERPCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Epicor ERP integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Epicor ERP: authenticate both systems, choose the objects to sync (such as Box's Events and Files), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Box and Epicor ERP records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Epicor ERP connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Epicor ERP integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and Epicor ERP. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Box: V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed. On Epicor ERP: Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Epicor ERP side: Bills of materials, Customers, Suppliers, Parts, plus custom fields where Epicor ERP exposes them. On the Box side: Tasks, Events, Files, Folders. Stacksync auto-detects both schemas and converts types between the two systems.
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 501 integrations available for Box and Epicor ERP.
Popular · 5 of 501
No integrations match .
