Can you integrate Campfire with Epicor ERP?

Explore a Campfire and Epicor ERP integration with a Stacksync engineer. Stacksync support for Epicor 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.

Can Campfire and Epicor ERP sync in both directions?

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.

What should be ready before the Campfire and Epicor ERP initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Create an API user with a Super User role in Campfire Settings > API Keys and generate its secret. Identify the Epicor ERP account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Campfire to Epicor ERP sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

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.

How do I map Campfire fields to Epicor ERP?

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.

What should I do if a record fails to sync?

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.

What does a Campfire and Epicor ERP integration cost?

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.

Which records should the Campfire and Epicor ERP pilot start with?

Start by reviewing Invoice in Campfire and AR invoices in Epicor 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.

Business productivity / ERP · Two-way sync platform

Campfire and Epicor ERP integration

Plan how Campfire and Epicor 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

Integration planning

stacksync.com

Campfire

Epicor ERP

Review the integration scope

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

Customer invoice sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving Campfire Invoice or Epicor ERP AR invoices needs a defined result in the other system.

Start with Campfire Invoice and Epicor ERP AR invoices. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
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 posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between Campfire and Epicor ERP
Campfire record	Epicor ERP record	Record matching	Field ownership
InvoiceDocumented record: Incremental: ; historical: ; delete detection:Record matching	AR invoicesProposed record; confirm Stacksync object support.	Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.	The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.
BillDocumented record: Incremental: ; historical: ; delete detection: Every 24hRecord matching	Bills of materialsProposed 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.
InvoiceDocumented record: Incremental: ; historical: ; delete detection: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.

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.

Campfire

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Invoice Debit Memo Credit Memo Bank Account Bank Transaction Journal Entry Intercompany Journal Entry Chart of Accounts Chart Transaction Fixed Asset Fixed Asset Class Budget Transaction Match Vendor Tag Cost Allocation Custom Field File Contract Contract Customer Product Product Bundle Revenue Transaction Customer Currency Reconciliation Report Webhook	Incremental: ✅; historical: ✅; delete detection: ✅. Confirm field permissions and sync direction.
Bill Fixed Asset Automation Rule Vendor Custom Field Department Entity Tag Group	Incremental: ✅; historical: ✅; delete detection: ✅ Every 24h. Confirm field permissions and sync direction.
Fixed Asset Automation Match Vendor Summary	Incremental: ✅; historical: ✅; delete detection: N/A (cannot be deleted). Confirm field permissions and sync direction.

Read the Campfire connector guide

Epicor ERP

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Customers Suppliers Parts Sales orders Purchase orders Jobs	Confirm support for this record type and the direction you need.

Discuss Epicor ERP requirements

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	Campfire	Epicor ERP
Integration interface	HTTP endpoints for bot integrations on a self-hosted instance	REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
Authentication	API key	Confirm the credentials, API plan, and permissions required for Epicor ERP.
Change detection	Historical backfill and incremental change tracking are documented.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Available for supported records	Confirm with Stacksync
Write access	Available for supported records	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance 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 guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Campfire

Integration interface: HTTP endpoints for bot integrations on a self-hosted instance
Authentication: API key — create an API user with a Super User Role in Campfire (Settings -> API Keys), generate an API Key secret, and provide it in the Stacksync connection setup
Change detection: Historical backfill and incremental change tracking are documented. Delete detection varies by object.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Create an API user with a Super User role in Campfire Settings > API Keys and generate its secret.
Review the supported-object table for incremental sync and deletion behavior before selecting entities.

Limitations to check

Incremental sync and delete detection vary by object; some deletions are checked only every 24 hours.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Campfire setup guide

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.

Prepare Campfire and Epicor 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.

Campfire setup checklist

Create an API user with a Super User role in Campfire Settings > API Keys and generate its secret.
Review the supported-object table for incremental sync and deletion behavior before selecting entities.

Setup guides: Authorize Campfire Connection

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.

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 Campfire and Epicor ERP planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

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

Invoice / AR invoices

Compare whether Campfire Invoice and Epicor ERP AR invoices describe the same customer invoice in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Campfire: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Epicor ERP: Object support to establish
Record identity: Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Field ownership: The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.

Fields to include

Source invoice ID
Customer or supplier reference
Line totals
Currency
Posting/payment status

Record dependencies: Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Validation: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Recovery: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

References: Campfire: Invoice documentation

Record matching

Bill / Bills of materials

Compare whether Campfire Bill and Epicor ERP Bills of materials describe the same supplier bill in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Campfire: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅ Every 24h
Epicor 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.

References: Campfire: Bill documentation

Business process

Invoice / Sales orders

Order-to-invoice handoff: Epicor ERP Sales orders provides context for Campfire Invoice. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Campfire: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Epicor 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.

References: Campfire: Invoice documentation

Record matching

Vendor / Suppliers

Compare whether Campfire Vendor and Epicor ERP Suppliers describe the same supplier or vendor in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Campfire: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Epicor ERP: Object support to establish
Record identity: Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Field ownership: Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.

Fields to include

Source supplier ID
Legal name
Entity reference
Payment terms
Active status

Record dependencies: Resolve business-unit and payment-term references before purchasing transactions.
Validation: Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
Recovery: Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.

References: Campfire: Vendor documentation

Record matching

Product / Bills of materials

Compare whether Campfire Product and Epicor ERP Bills of materials 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.

Campfire: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Epicor 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.

References: Campfire: Product documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Invoice / AR invoices 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 invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. 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 Campfire and Epicor 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 Invoice / AR invoices, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Invoice / 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 Campfire / Epicor 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

Customer invoice sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Invoice or AR invoices record needs a defined result in the other system.

Start with Campfire Invoice and Epicor ERP AR invoices. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
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 posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

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 Bill or Bills of materials record needs a defined result in the other system.

Start with Campfire Bill and Epicor ERP Bills of materials. 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 Invoice or Sales orders record needs a defined result in the other system.

Start with Campfire Invoice and Epicor 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.

Reconcile Campfire business records with Epicor ERP

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Campfire needs operational visibility through Customers or Suppliers.

Select Bill or Invoice with the correct legal entity, period, and currency.
Define a reporting relationship in Epicor 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.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated customer invoice change

Investigate

Inspect Campfire Invoice and Epicor ERP AR invoices, their IDs, and the destination error.

Next action

Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Rejected or repeated supplier bill change

Investigate

Inspect Campfire Bill and Epicor ERP Bills of materials, 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 Campfire Invoice and Epicor 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.

A record type or update is unavailable

Investigate

Check the Campfire and Epicor 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 Campfire and Epicor ERP

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Campfire Epicor ERP Direction requires confirmation

Detect changesHistorical backfill and incremental change tracking are documented. Delete detection varies by object.

Apply updatesConfirm that Stacksync can create or update the records you need in Epicor ERP.

Epicor ERP Campfire 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 Campfire.

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.
Incremental sync and delete detection vary by object; some deletions are checked only every 24 hours.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ