Ecommerce data operations desk with SKU, warehouse, pricing, and tax mapping displays

An ecommerce integration succeeds or fails at the field level. Before an Acumatica item is exposed to a storefront, a team must decide which system owns its SKU, how each variant maps to a stock item, which warehouse supplies available quantity, which price is published, and how tax categories are interpreted. A connector moves records; it cannot settle contradictory ownership rules. This guide gives ecommerce and ERP teams a practical mapping worksheet, test cases, and release checklist for Shopify, WooCommerce, and BigCommerce projects. Connector behavior differs, so validate every proposed mapping against the installed product and version before enabling synchronization.

The practical answer is to define a single owner for each field, document any transformation and fallback, and test the full order and inventory cycle with representative records. Treat price, availability, and tax as separate decisions. A clean SKU match alone does not prove that a channel will display the right quantity or charge the intended amount.

Table of Contents

  1. Why master data comes before synchronization
  2. Key points
  3. Choose the record of truth by field
  4. Map SKUs, variants, and alternate identifiers
  5. Map warehouses, locations, and available quantity
  6. Check units of measure and pack sizes
  7. Set price ownership and precedence
  8. Define tax data boundaries
  9. Use a mapping worksheet
  10. Test changes before synchronization
  11. Control launch and ongoing exceptions
  12. Frequently Asked Questions
  13. Next step: a data readiness assessment
  14. Sources

Why master data comes before synchronization

A storefront product is a commercial presentation; an ERP stock item is an operational record. A parent product might contain color and size variants, while Acumatica may maintain one stock item per sellable combination. The storefront may display a single price, a promotional price, or a customer-specific price. An order can be paid in one channel and fulfilled from a different location. Each step has different data rules.

Start with the transaction you need to preserve: a customer sees the correct sellable variant and quantity, places an order at the intended price, and receives it from an eligible location. The ERP receives a resolvable item, unit, location, customer, and tax treatment. Later inventory and shipment updates return to the right storefront records. A field mapping should be evaluated against this end-to-end sequence, not just against a successful product export.

Biz-Tech’s Shopify connector and WooCommerce connector describe different controls. Acumatica’s own commerce integrations have their own entities and synchronization settings. Name the exact connector, release, and direction of each flow in the design. A rule documented for one integration should not be silently applied to another.

Back to TOC

Key points

  • One owner per field. Decide who creates and edits each SKU, product ID, quantity, price, and tax classification. Give two-way flows a conflict rule.
  • One match per sellable variant. Verify that every storefront variant resolves to the intended Acumatica item, unit, and external ID. Treat blanks, duplicates, and renames as explicit exceptions.
  • Only eligible stock counts. Select the Acumatica quantity basis and the warehouses that can actually fulfill the channel. Test allocations and excluded locations.
  • Price and tax need separate rules. Document price-list and promotion precedence, then have a tax reviewer approve the classification and calculation flow.
  • Test the full order cycle. Confirm storefront display, checkout, order import, fulfillment, shipment update, and reconciliation with representative records.
  • Make failures visible. Give unmapped records an exception queue, an owner, and a safe retry path before broad synchronization.

Back to TOC

Choose the record of truth by field

“Acumatica is the source of truth” is too broad to implement. An ERP may own item identifiers and standard prices while a storefront owns product copy, merchandising categories, images, and temporary promotions. Another business may create products in the storefront first and import them. Both patterns can work if the owner and direction are explicit.

For every field, record: owner, allowed editors, synchronization direction, transformation, fallback, approval, and reconciliation rule. “Bidirectional” needs a conflict rule. If both applications change the same value between runs, which wins? How are rejected updates reported? What happens if a product exists on only one side? These decisions should be made before enabling an automated job.

Give each mapped record an immutable integration identifier where the connector supports one. Human-readable SKU remains important for operations, but renaming it must not accidentally create a second product. Check whether your chosen integration matches on SKU, stock ID, alternate ID, a stored external ID, or a combination. Acumatica’s native Shopify order synchronization guidance discusses stock and alternate ID matching; that is a reference for the native integration, not a guarantee for every third-party connector.

Back to TOC

Map SKUs, variants, and alternate identifiers

Build a list of every *sellable* variant, not just parent products. Shopify recommends a unique SKU for each variant. BigCommerce also models variants as the sellable items in its catalog. Confirm whether the integration links a variant to an Acumatica stock item, matrix item, or another record type. Do not assume the parent product’s SKU is sufficient.

Create rules for blanks, duplicates, case, leading zeros, spaces, prefixes, and retired SKUs. An item that appears identical to a person may fail a literal match because `AB-001` differs from `AB001`. Conversely, normalizing every SKU can merge two legitimate products. Preserve the original identifier and record any normalized value as an explicit transformation. Reject unresolved duplicates before the first export.

Decide whether a storefront may create new ERP items. The Biz-Tech WooCommerce connector says importing items is optional and an order with an unmatched SKU is blocked when that option is disabled. The Biz-Tech Shopify connector describes controlled item creation and SKU numbering defaults. Those are configuration choices with operational consequences. A launch test should include both a known SKU and an unknown SKU, then confirm the resulting error, queue, or item creation behavior in the installed version.

Keep a crosswalk with the Acumatica stock ID, alternate IDs where used, storefront product ID, variant ID, channel SKU, lifecycle status, and last successful synchronization timestamp. That crosswalk makes a rename or channel migration auditable. For discontinued items, define whether the storefront product is hidden, unpublished, left visible but unavailable, or retained for replacement guidance.

Back to TOC

Map warehouses, locations, and available quantity

“Inventory” can mean on-hand, available, or available for shipment. The Biz-Tech WooCommerce connector explicitly offers these quantity bases. Acumatica’s availability rules affect what quantities are considered available. Record the selected basis and the conditions that reduce it, including allocations, open orders, holds, and inbound supply where relevant to your configuration.

Map each sellable storefront location to an Acumatica warehouse or an approved aggregation of warehouses. A Shopify location is not automatically equivalent to a fulfillment source; Shopify’s inventory and location guidance distinguishes inventory levels and fulfillment eligibility. Decide whether a local pickup location, drop-ship location, showroom, and main warehouse should all contribute to online availability. Never sum every warehouse by default.

Write down the formula in business language and in testable form. For example: “Publish available-for-shipment units from warehouses W1 and W2, excluding quarantined stock; cap negative results at zero.” Then test a variant held in W1, out of stock in W2, allocated to an open order, and available only at an ineligible location. Confirm both the number published and the location used when an order imports.

The Biz-Tech Shopify data-flow article notes that locations can map to warehouses and that its illustrated item mapping differs by flow direction. Treat that as a reason to inspect the actual import and export settings in your deployment, particularly when onboarding existing storefront products.

Back to TOC

Check units of measure and pack sizes

One storefront “unit” may represent one each, a box of 12, or a case. Acumatica stock items can have a base and sales unit of measure with conversion rules. A technically successful item match can still create a quantity error if the channel sells a pack but imports the order as an each.

For each channel variant, document the sellable unit, Acumatica sales unit, base unit, conversion factor, rounding rule, and whether partial units are permitted. Test orders of one, two, and the largest realistic quantity. Reconcile the imported order quantity, inventory decrement, fulfillment quantity, and customer-facing pack description. If the connector cannot express the desired conversion, create a distinct sellable item or adjust the commercial design before launch.

Back to TOC

Set price ownership and precedence

Price mapping is more than selecting a field. Establish the price source for each customer group, currency, market, variant, and effective date. Define how list price, sale price, discounts, shipping, and tax interact. Then decide which application calculates the final order value and which receives it as a record of the sale. A catalog export price and an imported order price can have different owners.

The Biz-Tech WooCommerce connector describes Default and MSRP price bases. BigCommerce supports variant-level price lists with catalog fallback, so a catalog price alone may not be the price a buyer sees. Shopify has its own product and variant pricing fields. For every channel, identify the actual effective price path in the installed integration and the storefront configuration.

Test a normal item, discounted item, customer-specific price if applicable, multiple currencies, and a price change during an open cart. Capture the displayed product price, cart price, captured order amount, imported ERP line price, and any later invoice difference. Define an exception threshold and owner for mismatches. If a promotion is owned by the storefront, do not overwrite it with a routine ERP export unless that behavior is intentional.

Back to TOC

Define tax data boundaries

Tax categories, tax classes, tax zones, tax status, and calculated tax amounts are not interchangeable fields. WooCommerce has product tax status and class; BigCommerce includes a tax class in product data; Acumatica uses its own tax configuration. A mapping must specify which field expresses product taxability, which determines jurisdiction, and which system calculates the amount for the transaction.

Separate *classification* from *calculation*. An ERP item tax category may map to a storefront tax class, but that alone does not establish the applicable rate, exemption, nexus, destination rule, or rounding behavior. If a storefront or external tax service calculates tax at checkout, document how the calculated amount and any tax identifiers are imported into Acumatica. If Acumatica recalculates, test how differences are handled. Have a tax reviewer approve the design; this article is an integration checklist, not tax advice.

The Acumatica native Shopify product settings describe tax category and code mapping for that native connector. Use the documentation for your actual integration before copying those settings into a Biz-Tech or custom connector project.

Back to TOC

Use a mapping worksheet

The worksheet below is a starting point. Replace the examples with the fields and behavior of the installed connector. One row should describe one field in one direction. Add columns for the real Acumatica screen, storefront API field, connector setting, release version, and evidence link.

Entity / field

Proposed owner

Direction

Transformation or fallback

Required test and approver

Variant SKU

ERP item master or approved channel crosswalk

ERP to store, or store to ERP at onboarding

Preserve original; reject blank or duplicate values

Known, duplicate, renamed, and unknown SKU; data lead

Product / variant ID

Storefront

Store to integration crosswalk

Persist external ID; do not infer from title

Reimport after rename; integration lead

Sellable unit

ERP and merchandising agreement

ERP to store plus order return

Define pack conversion and rounding

One pack and multi-pack order; operations lead

Inventory quantity

ERP inventory

ERP to store

Selected availability basis and eligible warehouses

Allocation and ineligible location; warehouse lead

Fulfillment location

Operations

Store order to ERP warehouse

Explicit location-to-warehouse map; error on unknown

Pickup, ship, split order; fulfillment lead

Catalog price

Chosen price owner

Usually ERP to store

Price list, currency, effective date, fallback

Standard and sale price; pricing lead

Order line price

Checkout system

Store to ERP order

Preserve agreed discount and currency semantics

Promotion and rounding; finance lead

Product tax classification

Tax policy owner

According to connector

Approved category/class crosswalk

Taxable, exempt, mixed cart; tax reviewer

Tax amount

Approved tax engine

Checkout to ERP or ERP calculation

Defined reconciliation tolerance

Destination and refund; tax reviewer

Include three sample records with real but non-sensitive values: a simple item, a variant family, and a pack-size item. Record the expected output for every row. A worksheet is useful only if a tester can tell whether a synchronization result passes or fails.

Back to TOC

Test changes before synchronization

Test in a nonproduction environment when available, using realistic data and a named connector version. Start with one record per edge case, then run a controlled batch. A useful minimum matrix covers creation, update, rename, deletion or retirement, duplicate, missing mapping, inventory allocation, price promotion, tax exemption, canceled order, refund, and retry after a failed job.

Use these five pilot checks as a release checklist:

  • Identity: Create one simple item and one variant family. Confirm unique matching on both sides, then rename a SKU without creating a duplicate.
  • Quantity: Place stock in an eligible and an excluded warehouse, allocate part of the stock, and verify the published quantity and fulfillment source.
  • Unit and price: Sell a pack-size item and a promoted item. Compare storefront cart values with the imported order and the ERP inventory decrement.
  • Tax: Test taxable and exempt items with an approved jurisdiction scenario. Reconcile the checkout amount and the Acumatica order or invoice.
  • Recovery: Force an unknown SKU and a temporary sync failure. Confirm that the records appear in an exception queue and that retry does not create a duplicate.

Run the whole loop: item export → storefront display → cart and checkout → order import → allocation and fulfillment → shipment and inventory update → reconciliation. Check each system after each step. A green synchronization log only shows that a job ran; it does not confirm the buyer saw the right price or the warehouse shipped the right pack.

Make expected outcomes explicit. For an unknown SKU, should the order be held for review, should an item be created, or should the line fail? For a warehouse that has stock but is not eligible for online fulfillment, should published quantity remain zero? For a tax mismatch, should the imported order retain the checkout amount or trigger a review? Capture the result and the owner who approved it.

Back to TOC

Control launch and ongoing exceptions

Before launch, freeze uncontrolled master-data edits, run a full reconciliation, and set a rollback window. Compare counts of active sellable variants, unmapped SKUs, warehouse-location pairs, price exceptions, and tax classification exceptions. Publish an exception queue with a named owner and response time. If the connector can retry automatically, confirm it will not create duplicate items or orders.

At the launch gate, record the following evidence:

  • A signed field map with the connector name and version.
  • Passing pilot results for SKU, warehouse, unit, price, and tax cases.
  • A count and owner for every unresolved exception.
  • A rollback decision point and an accountable release owner.

After launch, monitor drift rather than relying on the first successful sync. Review new SKUs, renamed variants, inventory that differs between ERP and storefront, promotional prices that were overwritten, and tax classification changes. For each exception, retain the source value, destination value, timestamp, job ID, and corrective action. Periodically rerun the mapping test matrix after connector upgrades, storefront changes, new warehouses, and tax configuration changes.

The release gate is straightforward: every sellable variant resolves to one intended ERP item; every published quantity comes from eligible stock; every price follows a documented rule; every tax field has an approved owner; and every failure has a visible recovery path.

Back to TOC

Frequently Asked Questions

Should Acumatica always own the SKU?

No universal rule applies. Acumatica often owns operational item identifiers, but a storefront can create products first if the connector supports controlled item creation and a durable crosswalk. Choose one creation path and test unknown SKUs before launch.

Is a Shopify product SKU the same as a variant SKU?

Sellable variants need their own identifiers. Shopify recommends a unique SKU per variant. Confirm which Acumatica item or alternate ID each variant resolves to, rather than mapping only the parent product.

Can all Acumatica warehouses be summed for online inventory?

Only if every included warehouse is eligible to fulfill that channel and the availability basis is agreed. Pickup, quarantine, drop-ship, and wholesale-only stock may require separate treatment.

Which quantity should be published: on hand or available?

Use the quantity that matches the business promise and your connector’s supported options. The Biz-Tech WooCommerce connector describes On hand, Available, and Available for Shipment bases; test allocations and fulfillment eligibility with the selected setting.

What happens when a SKU changes?

The result depends on the connector’s matching key. Preserve external IDs and crosswalk history, and test a rename in both directions. Do not assume a title or SKU change will safely update the existing record.

Can a storefront promotion coexist with ERP pricing?

Yes, if price ownership and precedence are explicit. Decide whether ERP exports replace sale prices, whether checkout sends the final discounted amount, and how finance reconciles the imported order.

Is tax category mapping enough to ensure correct tax?

No. Classification is only one input. Jurisdiction, exemptions, the calculation engine, rounding, and the treatment of imported tax amounts all need an approved design and test.

What is the smallest useful pilot?

Use a simple stock item, a variant family, a pack-size item, two warehouse scenarios, a promotion, and a tax edge case. Run each through checkout, order import, fulfillment, and reconciliation.

Back to TOC

Next step: a data readiness assessment

Before connecting a full catalog, ask an Acumatica data lead, ecommerce architect, warehouse owner, pricing owner, and tax reviewer to complete the worksheet for a small representative sample. The deliverable should be a field map, exception policy, test evidence, and a clear launch gate. Biz-Tech Services can help assess the connector configuration and the data changes needed for a reliable rollout. Request an integration data readiness assessment with your channel, connector version, catalog size, and main mapping concerns.

Back to TOC

Sources

Back to TOC

Back to TOC

Privacy Preference Center