Epicor ERP
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
ERP · Two-way sync platform
Epicor ERP and Rootstock ERP integration
Plan how Epicor ERP and Rootstock ERP should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
Built for teams where self-serve, reliability and scale matter
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
Proposed workflow
Supplier bill sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving Epicor ERP Bills of materials or Rootstock ERP Bills of Material needs a defined result in the other system.
Start with Epicor ERP Bills of materials and Rootstock ERP Bills of Material. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Review records and field ownershipProposed record relationships
Records to connect
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| Epicor ERP record | Rootstock ERP record | Record matching | Field ownership |
|---|---|---|---|
| Bills of materialsProposed record; confirm Stacksync object support.Record matching | Bills of MaterialProposed record; confirm Stacksync object support. | Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. | Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice. |
| AR invoicesProposed record; confirm Stacksync object support.Business process handoff | Sales OrdersProposed record; confirm Stacksync object support. | Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order. | Finance owns invoice posting; the order system supplies the approved commercial context. |
| Sales ordersProposed record; confirm Stacksync object support.Business process handoff | Receipts and ShipmentsProposed record; confirm Stacksync object support. | Link the order and selected line IDs to separate fulfillment IDs; allow split shipments. | The fulfillment owner decides when an approved order can ship and how cancellations are handled. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Record coverage to review
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
Rootstock ERP
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Connection essentials
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | Epicor ERP | Rootstock ERP |
|---|---|---|
| Integration interface | REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints | Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects |
| Authentication | Confirm the credentials, API plan, and permissions required for Epicor ERP. | Confirm the credentials, API plan, and permissions required for Rootstock ERP. |
| Change detection | Confirm how Stacksync detects changes for this connector and the objects you need. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Confirm with Stacksync | Confirm with Stacksync |
| Write access | Confirm with Stacksync | Confirm with Stacksync |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
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
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:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Epicor ERP
- Integration interface
- REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
- Authentication
- Confirm the credentials, API plan, and permissions required for Epicor ERP.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Epicor ERP account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Epicor ERP, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Epicor ERP and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Rootstock ERP
- Integration interface
- Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects
- Authentication
- Confirm the credentials, API plan, and permissions required for Rootstock ERP.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Rootstock ERP account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Rootstock ERP, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Rootstock ERP and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare Epicor ERP and Rootstock ERP access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Epicor ERP setup checklist
- Identify the Epicor ERP account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Epicor ERP, including read/write support, authentication, and initial-load limits.
Rootstock ERP setup checklist
- Identify the Rootstock ERP account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Rootstock ERP, including read/write support, authentication, and initial-load limits.
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Epicor ERP and Rootstock ERP planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Record matching
Bills of materials / Bills of Material
Compare whether Epicor ERP Bills of materials and Rootstock ERP Bills of Material describe the same supplier bill in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Epicor ERP
- Object support to establish
- Rootstock ERP
- Object support to establish
- Record identity
- Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
- Field ownership
- Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.
Fields to include
- Source bill ID
- Supplier reference
- Entity
- Line amounts and currency
- Approval/posting state
- Record dependencies
- Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
- Validation
- Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
- Recovery
- Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
Business process
AR invoices / Sales Orders
Order-to-invoice handoff: Rootstock ERP Sales Orders provides context for Epicor ERP AR invoices. These are related records, not equivalent entities.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Epicor ERP
- Object support to establish
- Rootstock ERP
- Object support to establish
- Record identity
- Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
- Field ownership
- Finance owns invoice posting; the order system supplies the approved commercial context.
Fields to include
- Source record reference
- Destination record reference
- Approved handoff state
- Duplicate-detection key
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Business process
Sales orders / Receipts and Shipments
Order-to-fulfillment handoff: Epicor ERP Sales orders provides context for Rootstock ERP Receipts and Shipments. These are related records, not equivalent entities.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Epicor ERP
- Object support to establish
- Rootstock ERP
- Object support to establish
- Record identity
- Link the order and selected line IDs to separate fulfillment IDs; allow split shipments.
- Field ownership
- The fulfillment owner decides when an approved order can ship and how cancellations are handled.
Fields to include
- Source record reference
- Destination record reference
- Approved handoff state
- Duplicate-detection key
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Record matching
Sales orders / Sales Orders
Compare whether Epicor ERP Sales orders and Rootstock ERP Sales Orders describe the same sales order in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Epicor ERP
- Object support to establish
- Rootstock ERP
- Object support to establish
- Record identity
- Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
- Field ownership
- Decide which system approves the order and which can cancel or amend it after fulfillment begins.
Fields to include
- Source order ID
- Customer reference
- Line references and quantities
- Order status
- Currency
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Record matching
Bills of materials / Items / Products
Compare whether Epicor ERP Bills of materials and Rootstock ERP Items / Products describe the same product or catalog item in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Epicor ERP
- Object support to establish
- Rootstock ERP
- Object support to establish
- Record identity
- Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
- Field ownership
- Assign ownership for catalog content, price, and stock separately.
Fields to include
- Source product ID
- SKU or variant reference
- Description
- Unit of measure
- Price-list reference
- Record dependencies
- Resolve units, variants, categories, and applicable price lists before order lines.
- Validation
- Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
- Recovery
- Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Record matching
Shipments / Receipts and Shipments
Compare whether Epicor ERP Shipments and Rootstock ERP Receipts and Shipments describe the same shipment or fulfillment in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Epicor ERP
- Object support to establish
- Rootstock ERP
- Object support to establish
- Record identity
- Retain shipment/fulfillment and line IDs, order reference, and carrier context.
- Field ownership
- The fulfillment owner controls shipped quantities and cancellation eligibility.
Fields to include
- Source shipment ID
- Order/line references
- Carrier
- Tracking reference
- Fulfillment status
- Record dependencies
- Resolve order lines, delivery address, carrier, and any partial-fulfillment references.
- Validation
- Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
- Recovery
- Verify existing fulfillment before retrying creation; reconcile quantities against order lines.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Bills of materials / Bills of Material to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Stacksync managed sync
- Best fit
- Review compatibility with a Stacksync engineer using an example of the records and updates you need.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your Epicor ERP and Rootstock ERP record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Bills of materials / Bills of Material, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider explicit orchestration for the AR invoices / Sales Orders handoff.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
- Best fit
- Consider for a one-time Epicor ERP / Rootstock ERP migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Supplier bill sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Bills of materials or Bills of Material record needs a defined result in the other system.
- Start with Epicor ERP Bills of materials and Rootstock ERP Bills of Material. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
If it fails: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
Sales order process handoff
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected AR invoices or Sales Orders record needs a defined result in the other system.
- Start with Epicor ERP AR invoices and Rootstock ERP Sales Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Sales order process handoff
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Sales orders or Receipts and Shipments record needs a defined result in the other system.
- Start with Epicor ERP Sales orders and Rootstock ERP Receipts and Shipments. Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Reconcile Epicor ERP business records with Rootstock ERP
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Epicor ERP needs operational visibility through Sales Orders or Purchase Orders.
- Select Customers or Suppliers with the correct legal entity, period, and currency.
- Define a reporting relationship in Rootstock ERP; do not equate customer records, ledger accounts, and posted transactions.
- Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Bills of materials / Bills of Material
Test case
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Expected result
The expected supplier bill relationship is preserved with no duplicate action or unintended write.
AR invoices / Sales Orders
Test case
Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Sales orders / Receipts and Shipments
Test case
Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Sales orders / Sales Orders
Test case
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated supplier bill change
Investigate
Inspect Epicor ERP Bills of materials and Rootstock ERP Bills of Material, their IDs, and the destination error.
Next action
Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
Rejected or repeated sales order change
Investigate
Inspect Epicor ERP AR invoices and Rootstock ERP Sales Orders, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Rejected or repeated sales order change
Investigate
Inspect Epicor ERP Sales orders and Rootstock ERP Receipts and Shipments, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
A record type or update is unavailable
Investigate
Check the Epicor ERP and Rootstock ERP connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between Epicor ERP and Rootstock ERP
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Epicor ERP Rootstock ERP Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Rootstock ERP.
Rootstock ERP Epicor ERP Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Epicor ERP.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ
Epicor ERP and Rootstock ERP integration FAQ
-
Explore a Epicor ERP and Rootstock ERP integration with a Stacksync engineer. Stacksync support for Epicor ERP and Rootstock ERP is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
-
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Epicor ERP account, edition, environment, and business objects the integration must access. Identify the Rootstock ERP account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Bills of materials in Epicor ERP and Bills of Material in Rootstock ERP. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Choose a method around one example record and the update your business needs. Use Bills of materials / Bills of Material to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 412 integrations listed for Epicor ERP and Rootstock ERP.
Next step
Plan your integration with an engineer
Walk through your Epicor ERP and Rootstock ERP records, field mappings, and requirements with an integration engineer.
