Acumatica offers a native BigCommerce connector, but a successful launch depends on decisions that software cannot make for you: which system owns each field, how stock is calculated, which warehouse serves an order, how payments and refunds become accounting entries, and who responds when synchronization stops. A BigCommerce–Acumatica integration readiness review should settle those decisions before the first catalog export or order import. This guide gives commerce, operations, finance, and IT teams a practical checklist, an exception plan, and a go-live test sequence. It distinguishes documented platform capabilities from configuration choices that must be validated in your own environment.
What the native connector does
Acumatica describes its native BigCommerce integration as a way to synchronize items, inventory, customer information, orders, payments, shipments, returns, and refunds. Its BigCommerce Stores form reference shows that entities have activation, direction, and mapping settings; some directions are predefined. The connector is therefore a configurable integration surface, not a promise that every merchant workflow will work unchanged.
The distinction matters when a project involves a second warehouse management system, a separate payment gateway, a customized storefront, or a bespoke promotion rule. Acumatica's native integration overview describes multiple stores, selective exports, shipments, and returns. Your implementation still needs a written flow for each transaction and a test showing that the configured version behaves as intended.
This article concerns Acumatica's native connector. Biz-Tech Services publicly lists its own connectors for other commerce platforms and offers custom integration scoping; its marketplace does not currently list a Biz-Tech BigCommerce connector. Teams should confirm whether they will use Acumatica's native connector, a marketplace extension, or a separately scoped customization before assigning responsibility or buying services.
Confirm the product, edition, and version
Start with the actual Acumatica edition, release, enabled features, BigCommerce plan, storefront architecture, and any existing customizations. Acumatica says the BigCommerce Stores form is available when Retail Commerce and BigCommerce Connector are enabled. Its marketplace listing shows technically validated versions, but that list is a dated product record rather than a guarantee for every later release; verify your exact combination with the current vendor or implementation partner. See the feature reference and marketplace listing.
Record every customization that touches commerce entities or sync processors. Acumatica's 2026 R2 customization update says obsolete BigCommerce connector APIs were removed. It says this cleanup does not change standard functionality, yet custom code using removed APIs may require changes. A standard connector fit test and a customization compatibility test are different work items.
Ask the vendor or partner to document licensed features, supported release, connector build, payment path, and exclusions. A screenshot of a general product page is not a substitute for a version-specific implementation statement.
Name owners and systems of record
For each entity and field, nominate one primary owner: product identity, description, images, price, tax classification, stock, customer profile, order status, payment status, fulfillment, return authorization, and credit. Document which edits are allowed in the other system and what happens when both sides change before the next sync.
Acumatica's store settings allow entity-specific sync direction, and its documentation says the primary system takes precedence for a bidirectional conflict. That makes the ownership worksheet more than project paperwork: it determines which employee action will survive a conflict. Use a sample SKU and order to demonstrate the intended result rather than treating “bidirectional” as a universal setting. Acumatica BigCommerce Stores reference.
The practical deliverable is a field-level map with an owner, direction, transformation rule, null-value behavior, and escalation contact. Give finance explicit sign-off on amounts and statuses, and operations sign-off on stock and fulfillment.
Inventory: define the number shoppers see
“Inventory sync” is incomplete until the team defines the quantity being published. Is it physical on hand, available to sell after allocations, a safety-stock-adjusted value, or a channel-specific quantity? Decide how backorders, kits, preorders, returns awaiting inspection, and stock held for another sales channel affect that number.
BigCommerce's Inventory API example distinguishes `available_to_sell` from `total_inventory_onhand` at a location. These are different business quantities. In the project design, specify the ERP quantity source, any buffer, rounding or unit-of-measure conversion, and the storefront quantity expected for representative SKUs. This is an implementation recommendation, not a claim that the native connector applies a particular formula by default.
Test the unpleasant cases: an order arriving while a warehouse adjustment posts, two channels selling the last unit, a cancelled order, and a refund without physical receipt. If the storefront permits an oversell or backorder, document that business policy and the customer promise it creates.
Map warehouses to storefront locations
List every Acumatica warehouse and every BigCommerce location, including inactive, pickup, third-party fulfillment, and return-only sites. Decide which warehouses contribute to online availability and which one receives an imported order. Identify the routing rule for split orders and the location used for a returned item.
BigCommerce documents an important storefront limitation: its default Stencil behavior uses the default location for stock visibility, and aggregated stock is an alternate configuration available by request. It also notes that multi-location inventory is not fully supported end to end in native Stencil storefront flows. See BigCommerce Locations. A connector can send correct location data while a theme or checkout still presents an unexpected availability result. Test the buyer experience as well as the API records.
For each warehouse/location pairing, capture a real SKU, expected available quantity, storefront display, order source, pick site, and exception owner. Do not assume that a location name match establishes a functional mapping.
Clean products, variants, and identifiers
Before initial export, check SKU uniqueness, variant identifiers, units of measure, product type, category assignment, image ownership, inactive status, and descriptions. Decide whether a parent product, variant, kit, gift card, or digital item should sync and what represents its sellable unit in Acumatica. Acumatica's BigCommerce integration overview describes item and order synchronization; the scope of a particular merchant's product model still needs a sample-data test.
Choose a durable cross-system key. Names and descriptions change; IDs and SKUs require explicit collision and replacement rules. Prepare a small catalog set that includes a simple item, a variant family, an inactive item, an item with multiple images, and one deliberately bad mapping. Inspect both sides after the initial sync and after a second run. The second run reveals whether the process updates a record or creates a duplicate.
Do not export the entire catalog to production before resolving errors in the sample. A catalog-wide rollback can be harder than correcting a small controlled batch.
Set price, promotion, and tax rules
Identify the authority for base prices, customer-specific prices, discounts, coupons, shipping charges, gift wrapping, and tax calculation. Acumatica describes support for customer-specific pricing and promotions in its native BigCommerce integration, but each merchant must define which rules are evaluated in the storefront and which values are carried into the ERP document.
Use orders with a coupon, a customer-specific price, a tax-exempt buyer, freight, and a partial return. Compare the cart, captured payment, imported sales order, invoice, credit, and ledger totals. A one-cent discrepancy is a real reconciliation issue if it repeats at scale. Define rounding and currency conventions before testing, and have finance approve the result.
Avoid assuming that a promotional display price is the same as the accounting treatment of a discount. Record the original amount, discount, tax basis, and final charged amount separately in the mapping sheet.
Decide how customers and companies map
Specify whether a guest checkout creates a new ERP customer, uses a shared guest account, or follows another governed rule. Decide how email changes, duplicate addresses, tax IDs, B2B companies, contacts, and customer locations are matched. An email address alone may not be a safe identity key for a company with multiple buyers.
Acumatica documents company-account and customer synchronization for BigCommerce B2B Edition, while BigCommerce controls storefront roles and permissions. The two platforms have related but distinct responsibilities. Test company hierarchies, a buyer with two shipping addresses, a returning guest, and an existing ERP customer whose storefront details differ. Acumatica native integration; Acumatica BigCommerce Stores reference.
Define who may merge customer records and how historical orders remain traceable afterward. A duplicate customer is usually easier to prevent with a documented match rule than to unwind after invoices and credits exist.
Walk the complete order lifecycle
Draw one order from checkout through payment authorization, ERP import, allocation, picking, shipment, tracking, invoice, cancellation, and any return. Write the state transition and responsible system at each step. Mark the point at which an order becomes financially or operationally irreversible.
Acumatica documents synchronization of orders and shipments and support for separate packages and tracking numbers. That does not eliminate the need to test partial shipments, backorders, address edits, cancellations after allocation, and duplicate event delivery. Acumatica native integration.
Use the storefront order ID as a reconciliation reference in the test evidence, alongside the ERP order number and shipment number. Define what the support team tells a buyer if the storefront says “shipped” but the ERP shipment failed, or the reverse. The exception route should be clear before the first live order.
Separate payment, refund, and return events
A refund is a financial transaction; a physical return is an inventory event; a cancellation can be neither or both, depending on timing. Treat them as separate flows. The team must know which system initiates a refund, where gateway settlement is recorded, when a credit memo is created, and whether returned units are inspected before becoming sellable.
Acumatica's connector documentation includes payment and refund entities. BigCommerce's refund API documentation says an API refund cannot itself return items to inventory. Therefore, a successful refund message is not proof that stock was restored. Test a full refund, partial line refund, shipping-only refund, return to a different location, and refund after a split shipment. Reconcile the gateway transaction, storefront order, ERP payment, credit, and inventory receipt independently.
Keep a written matrix for who can approve and execute each action. If a payment integration or gateway changes, retest this section even when catalog and order sync remain unchanged.
Review security and integration access
Identify the API account, access scopes, credential owner, rotation process, and environments. Give the connector only the permissions required by its tested entities. BigCommerce's API account documentation identifies scopes for store inventory and locations; your actual connection may need more, depending on the flows you enable.
Separate test and production credentials, restrict who can edit mappings, and record where failed payloads or customer data can be seen. Verify that logs contain enough identifiers for diagnosis without exposing unnecessary personal or payment information. Agree who can pause a sync, replay a record, and change a credential during an incident.
Do not paste tokens into a runbook. Store the access procedure and accountable owner, then use your organization's approved secret-management process.
Plan sync timing, monitoring, and recovery
Document which entities are batch-synchronized, event-triggered, or manually initiated in your configured deployment. Define acceptable lag for stock and orders, and measure it in testing. “Real time” in a product overview is not a guarantee of zero latency for every storefront, API call, or exception queue.
BigCommerce provides webhooks that carry event identifiers and limited data; downstream processing may need to retrieve the full record. Its API rate-limit guidance explains how an integration can inspect remaining-call headers. If custom middleware uses these APIs, design retries with rate limits and idempotency in mind. Verify how the native connector handles these behaviors before adding separate custom listeners.
Create an operating dashboard or daily check covering failed entities, oldest pending record, order count by system, inventory discrepancy, payment exceptions, and retry outcome. Assign an owner and response time to each alert. A queue that eventually catches up can still leave buyers seeing wrong stock for hours.
Prove the design with test cases
Use a small but representative test set, not only a happy-path order. For every case, record source value, expected destination value, actual value, elapsed time, and the person who accepts the result. Include at least these scenarios:
- A simple item and a variant with distinct SKUs sync twice without duplicates.
- Stock changes after an order, warehouse adjustment, cancellation, and inspected return.
- Default-location stock is zero while another location has units; observe the actual storefront result.
- A guest order and a B2B company order map to the intended customers.
- A coupon and customer-specific price reconcile to the ERP document and payment.
- One order ships in two packages with separate tracking.
- A partial refund creates the intended financial records without silently restocking an item.
- An invalid SKU, expired credential, and temporary API failure reach an actionable exception queue.
- A repeated order event does not create a second sales order.
- A catalog edit on the non-owning side resolves according to the agreed conflict rule.
These are recommended acceptance tests synthesized from documented platform behavior and common integration failure modes. They are not a statement that the connector implements every edge case without configuration.
Use a controlled cutover and hypercare plan
Before go-live, freeze mapping changes, back up relevant configurations, record current open orders, and decide how historical data will be handled. Sequence the initial catalog, customer, inventory, and order loads so that shoppers cannot place orders against a partially mapped catalog. Assign one person to approve each transition.
For the first operating period, compare order counts, payment totals, and inventory exceptions frequently enough to catch a drift before it compounds. Establish a stop rule: for example, pause a particular entity when duplicate orders appear, while keeping unrelated flows available if the product and business process allow it. The exact threshold is a business decision, not a universal connector setting.
Prepare a rollback or containment plan that states what can be disabled, what data must be manually reconciled, and who authorizes customer-facing changes. Re-running a failed sync without understanding whether it partially succeeded can create duplicate records.
Define go-live acceptance criteria
The project is ready when the owners can show: verified version and features; signed-off entity and field map; inventory and warehouse rules; passing catalog, customer, order, payment, shipment, refund, and return tests; credential ownership; visible exception monitoring; reconciliation reports; and a cutover/runbook with named responders. Any excluded capability should be written beside the acceptance criteria so that it cannot become an implicit promise after launch.
The strongest business result is operational clarity. The connector transfers data; the team decides what the data means, which exceptions demand action, and how a buyer's order stays consistent from storefront to ledger. Biz-Tech Services can help scope Acumatica integration work around that design, including custom gaps where the native connector's verified behavior does not meet a documented requirement.
Frequently Asked Questions
Does Acumatica have a native BigCommerce connector?
Yes. Acumatica describes a native BigCommerce connector for commerce entities including items, customers, orders, inventory, payments, shipments, returns, and refunds. Confirm your edition, enabled features, and exact release before implementation.
Is the connector itself a complete rollout plan?
No. Teams still need ownership rules, field mappings, warehouse logic, payment and return treatment, tests, monitoring, and named exception owners.
Can BigCommerce show stock from multiple locations?
BigCommerce supports locations, but its documentation describes default-location storefront behavior and a separate aggregated-stock option. Test your actual theme and checkout path, especially when the default location is empty.
Does a BigCommerce refund put stock back automatically?
Do not assume so. BigCommerce states that its API refund cannot itself return items to inventory. Test the physical return and restock process separately from the financial refund.
Which system should own the product catalog?
Choose one primary owner for each field. Acumatica's connector has entity-specific direction and conflict behavior, so the choice should be documented and tested for your catalog model.
Can one BigCommerce order create multiple shipments?
Acumatica describes shipment synchronization with separate package tracking. Validate your split-shipment and partial-fulfillment cases in the configured environment.
How should guest buyers map to Acumatica customers?
That is a design decision. Test a shared guest account or individual account rule against tax, service, credit, and duplicate-record requirements before launch.
What should IT monitor after go-live?
At minimum, failed and oldest pending sync records, order-count differences, inventory discrepancies, payment/refund exceptions, and retry results. Assign a named responder to each alert.
Does Biz-Tech Services sell its own BigCommerce connector?
The current public Biz-Tech marketplace lists other commerce connectors and custom integration scoping, but not a named Biz-Tech BigCommerce connector. Confirm the proposed architecture and provider in the project scope.
What changes for an Acumatica 2026 R2 upgrade?
Acumatica says obsolete commerce APIs were removed without changing standard functionality. Customizations that call removed BigCommerce APIs may need updates, so include them in upgrade testing.
Sources
- Acumatica: BigCommerce Stores form reference
- Acumatica: Native BigCommerce integration
- Acumatica: Retail Commerce and BigCommerce feature reference
- Acumatica: Marketplace validated-version listing
- Acumatica: 2026 R2 customization update
- BigCommerce: Inventory at locations
- BigCommerce: Locations
- BigCommerce: Order refunds
- BigCommerce: API accounts and scopes
- BigCommerce: Webhooks
- BigCommerce: API rate limits
- Biz-Tech Services: Marketplace and custom integration scoping


