Two-way sync
Changes in Epicor ERP or Gatekeeper instantly reflect in both systems. No stale data, no manual imports.
Keep Epicor ERP and Gatekeeper in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Gatekeeper is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Stacksync syncs Workflow form data, Custom data groups, Users, Categories in Gatekeeper with Parts, Sales orders, Purchase orders, Jobs in Epicor ERP bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Worker and organization data from Epicor ERP stays current in Gatekeeper, so the tools people use daily reflect the org as it actually is.
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
Order, invoice, or account status from Epicor ERP appears alongside the customer in Gatekeeper, so front-line teams answer from live data.
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.
| Epicor ERP objects | Gatekeeper objects | How this pairing syncs | |
|---|---|---|---|
| Sales orders Created from won CRM opportunities; status and line changes sync back out. | Vendors (Suppliers) Company records for counterparties and suppliers with onboarding status, compliance, risk, contacts, and spend; read and written to keep vendor master data aligned with a CRM or ERP. | Sales orders is specific to Epicor ERP and Vendors (Suppliers) to Gatekeeper — each maps to any object or custom field on the other side. | |
| Purchase orders Synced with procurement systems and matched against receipts. | Files Document files attached to contracts and vendors - executed PDFs, certificates, and compliance evidence; read to pull signed files and evidence out, or written to push generated documents in. | Purchase orders is specific to Epicor ERP and Files to Gatekeeper — each maps to any object or custom field on the other side. | |
| Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | Workflow form data The structured data captured on Gatekeeper workflow forms (intake requests, vendor onboarding, risk assessments); exposed by the API since 2025 so form results sync into an operational database, not only contract and vendor records. | Jobs is specific to Epicor ERP and Workflow form data to Gatekeeper — each maps to any object or custom field on the other side. | |
| Quotes Estimates that pair with CRM opportunities during the sales cycle. | Custom data groups Customer-configured custom fields and data groups; because the JSON:API and its docs are dynamic, any custom data added in Configuration exposes the same read/write endpoints as the standard objects and syncs the same way. | Quotes is specific to Epicor ERP and Custom data groups to Gatekeeper — each maps to any object or custom field on the other side. | |
| AR invoices Billing records surfaced in CRM or finance tools for collections visibility. | Users Gatekeeper user and team records governed by role-based access; read to map contract and vendor owners, approvers, and internal contacts to CRM or HR records. | AR invoices is specific to Epicor ERP and Users to Gatekeeper — each maps to any object or custom field on the other side. | |
| Shipments Fulfillment confirmations synced to customer portals and commerce systems. | Categories The classification taxonomy applied to contracts and vendors (type, department, business unit); synced so categorization stays consistent between Gatekeeper and downstream reporting or ERP dimensions. | Shipments is specific to Epicor ERP and Categories to Gatekeeper — 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.
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 Gatekeeper through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Gatekeeper for changes on an incremental schedule, reading only records changed since the previous pass. No native developer webhook subscription API and no database change-data-capture log.
DeliveryEach detected change is written to Epicor ERP through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Epicor ERP–Gatekeeper connection.
Changes in Epicor ERP or Gatekeeper instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Epicor ERP or Gatekeeper data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Epicor ERP or Gatekeeper record.
Track your Epicor ERP ⇄ Gatekeeper sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Epicor ERP and Gatekeeper.
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 Epicor ERP and Gatekeeper 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 Epicor ERP and Gatekeeper 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 Epicor ERP and Gatekeeper: authenticate both systems, choose the objects to sync (such as Epicor ERP's Sales orders and Purchase orders), 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 Epicor ERP and Gatekeeper: Where Epicor ERP is the HR or people system of record; Master data corrections travel; Where Gatekeeper faces customers and Epicor ERP carries account records. Worker and organization data from Epicor ERP stays current in Gatekeeper, so the tools people use daily reflect the org as it actually is.
Epicor ERP: 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. Gatekeeper: RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant. Authentication: API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently. Stacksync manages authentication, retries, and rate limits on both sides.
Gatekeeper: There is no native developer webhook subscription API and no database CDC log; change detection is polling by updated-at. Event-driven automation lives in Gatekeeper's Workflow Engine and Interconnect, inside the platform. Epicor ERP: The REST surface wraps Epicor business objects, so API writes pass through the same validation and business logic as the client UI. Stacksync's field mapping accounts for these differences between Epicor ERP and Gatekeeper 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 Epicor ERP and Gatekeeper 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 411 integrations available for Epicor ERP and Gatekeeper.