Can you integrate BigCommerce with Epicor ERP?

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

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the BigCommerce account, edition, environment, and business objects the integration must access. 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 BigCommerce 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 BigCommerce 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 BigCommerce 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 BigCommerce and Epicor ERP pilot start with?

Start by reviewing Orders in BigCommerce 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.

E-commerce / ERP · Two-way sync platform

BigCommerce and Epicor ERP integration

Plan how BigCommerce 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

BigCommerce

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

Sales order process handoff

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

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

Start with BigCommerce Orders and Epicor ERP AR invoices. 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.

What to verifyTest a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.

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 BigCommerce and Epicor ERP
BigCommerce record	Epicor ERP record	Record matching	Field ownership
OrdersProposed record; confirm Stacksync object support.Business process handoff	AR invoicesProposed 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.
OrdersProposed record; confirm Stacksync object support.Business process handoff	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.
CustomersProposed record; confirm Stacksync object support.Record matching	CustomersProposed record; confirm Stacksync object support.	Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.	Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

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.

BigCommerce

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Products Variants and SKUs Orders Customers Categories Brands	Confirm support for this record type and the direction you need.

Discuss BigCommerce requirements

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	BigCommerce	Epicor ERP
Integration interface	REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs	REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
Authentication	Confirm the credentials, API plan, and permissions required for BigCommerce.	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.	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 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

BigCommerce

Integration interface: REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs
Authentication: Confirm the credentials, API plan, and permissions required for BigCommerce.
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 BigCommerce account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for BigCommerce, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for BigCommerce and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Technical documentation

BigCommerce vendor API documentation

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 BigCommerce 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.

BigCommerce setup checklist

Identify the BigCommerce account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for BigCommerce, including read/write support, authentication, and initial-load limits.

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 BigCommerce 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

Business process

Orders / AR invoices

Order-to-invoice handoff: BigCommerce 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.

BigCommerce: Object support to establish
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: BigCommerce: Orders documentation

Business process

Orders / Shipments

Order-to-fulfillment handoff: BigCommerce Orders provides context for Epicor ERP Shipments. These are related records, not equivalent entities.

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

BigCommerce: Object support to establish
Epicor 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.

References: BigCommerce: Orders documentation

Record matching

Customers / Customers

Compare whether BigCommerce Customers and Epicor ERP Customers describe the same customer in your business.

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

BigCommerce: Object support to establish
Epicor ERP: Object support to establish
Record identity: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership: Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

Record dependencies: Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: BigCommerce: Customers documentation

Record matching

Orders / Sales orders

Compare whether BigCommerce Orders and Epicor 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.

BigCommerce: Object support to establish
Epicor 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.

References: BigCommerce: Orders documentation

Record matching

Products / Bills of materials

Compare whether BigCommerce Products 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.

BigCommerce: Object support to establish
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: BigCommerce: Products documentation

Record matching

Shipments / Shipments

Compare whether BigCommerce Shipments and Epicor ERP 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.

BigCommerce: Object support to establish
Epicor 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.

References: BigCommerce: Shipments documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Orders / 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: Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order. 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 BigCommerce 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 Orders / AR invoices, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Orders / AR invoices 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 BigCommerce / 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

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 Orders or AR invoices record needs a defined result in the other system.

Start with BigCommerce Orders and Epicor ERP AR invoices. 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 Orders or Shipments record needs a defined result in the other system.

Start with BigCommerce Orders and Epicor ERP 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.

Customer sync test

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

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

Start with BigCommerce Customers and Epicor ERP Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
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 an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Reconcile Epicor ERP business records with BigCommerce

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

Starting event: A finance-owned record in Epicor ERP needs operational visibility through Products or Variants and SKUs.

Select Customers or Suppliers with the correct legal entity, period, and currency.
Define a reporting relationship in BigCommerce; 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 sales order change

Investigate

Inspect BigCommerce Orders and Epicor ERP AR invoices, 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 BigCommerce Orders and Epicor ERP 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.

Rejected or repeated customer change

Investigate

Inspect BigCommerce Customers and Epicor ERP Customers, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

A record type or update is unavailable

Investigate

Check the BigCommerce 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 BigCommerce 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.

BigCommerce 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.

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

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