How to Map CommerceHub Store Codes and Customers in Acumatica

CommerceHub orders imported into Acumatica use a default customer associated with the store configuration. The connector documentation says the actual customer address from the imported order overrides the default address on the resulting sales order.

With the Biz-Tech Services CommerceHub Acumatica Connector, a store code provides the process context for that configuration. Check the selected store code, default customer, and resulting order address together to confirm that each order reaches the intended account.

What a CommerceHub Store Code Controls

The Biz-Tech Services Acumatica CommerceHub Connector uses store codes to organize distinct import and export configurations. The documentation lists Transaction Type, Description, Default Customer, and Document type among parameters that can differ by store. Confirm the values that apply to the purchase order import process before processing orders.

The manual says customers are not imported from CommerceHub during purchase order import. It does not describe a separate customer-to-trading-partner cross-reference, an automatic account matching algorithm, or a rule for creating a separate customer for each buyer.

CommerceHub Customer Mapping at a Glance

Review the intended store code and its purchase order import configuration in Mappings.

Check the Default Customer and Document type configured for the relevant process.

Open Import Purchase Orders and select the intended store code.

Process a representative order and find the resulting record in Sales Orders.

Compare the sales order customer and the address on its Addresses tab with the intended account and the source order.

Review errors and failed orders before deciding whether to repeat an import.

Choose the Store and Default Customer

The Mappings screen defines connector behavior for import, export, and synchronization. Store codes support distinct settings for different operations. Review the code used for order import and check its Default Customer against the Acumatica customer your business intends to use for that workflow.

A default customer on a sales order is an account assignment, not proof that the buyer from the CommerceHub order was created as a new customer. If different trading partners require different account treatment, review the intended configuration with the implementation team; the manual does not explain the full range of trading-partner mapping options.

Check the Order Address Separately from the Account

The Biz-Tech Services CommerceHub Acumatica Integration imports purchase orders by selected store code and creates records visible in Sales Orders. The documented behavior assigns a default customer while replacing the default address information on the Sales Orders Addresses tab with the actual customer address received from the order.

Compare the incoming order, the assigned customer, and the address on the resulting Acumatica sales order. The supplied guide does not identify every address field affected, the fallback when an address is missing, or a matching rule for existing customer locations. Confirm these details in your installed configuration before relying on an automated result.

Review Duplicates and Import Failures

The documentation describes processing selected purchase orders with Process or using Process All. It does not describe an automatic duplicate-customer or duplicate-order prevention rule, nor does it establish what happens if an already imported order is processed again.

Import CommerceHub purchase orders

Before a retry, review the source order and existing Sales Orders according to your organization's procedures. Import Failed Purchase Orders is described as the screen for orders that failed the initial import, selected by store code. Review the failure and existing records before retrying; do not assume every failure occurred before a sales order was created.

The Mappings Error Log shows errors related to order import and export. CommerceHub Errors displays errors received from CommerceHub for various processes. The manual does not provide a complete set of error messages or a specific customer-mapping error. Preserve information needed for investigation before using Purge Logs, which deletes all messages in the Error Log.

Where to Check Your Work

Use these checks when reviewing the Biz-Tech Services Acumatica CommerceHub Integration after a representative import:

CommerceHub workspace: confirm that the connector screens are available after publication.

Mappings: review the intended store configuration for the order import process.

Transaction Type and Description: compare the configured process context with the intended workflow.

Default Customer: verify the account expected on the sales order.

Document type: check the value configured for the process.

Import Purchase Orders: confirm the store code selected for the import.

Sales Orders: inspect the resulting order and assigned customer.

Sales Orders, Addresses tab: compare the received address with the source order.

Import Failed Purchase Orders: review orders that failed the initial import under the relevant store code.

Mappings Error Log and CommerceHub Errors: review available error details before retrying.

CommerceHub Customer Mapping: Frequently Asked Questions

Why does an imported order show a default customer?

The manual says customers are not imported from CommerceHub during purchase order import. The resulting sales order is assigned a default customer.

Does the customer address come from the default customer?

The Biz-Tech Services CommerceHub Acumatica Integrator documentation says the order address overrides the default address information on the sales order Addresses tab. Check the actual result and source order for your configuration.

Can different store codes have different settings?

Yes. The documentation describes individual store configurations with parameters such as Transaction Type, Description, Default Customer, and Document type. Verify the relevant values for each process.

Does the connector automatically match or create customer accounts?

The supplied guide says customers are not imported during purchase order import. It does not describe a general customer-matching algorithm, account-creation process, or trading-partner customer cross-reference.

What should I check if an order has the wrong customer or address?

Check the store code used for import and its default customer, then compare the Sales Orders Addresses tab with the address on the source order. The manual does not give a specific diagnostic message for this situation.

Does the connector prevent duplicate orders?

The manual does not establish an automatic duplicate-order prevention rule. Before retrying a failed import, review the original order and existing sales orders, then follow your organization's recovery procedure.

Work With Biz-Tech Services on CommerceHub

For the broader workflow, see "How to Import CommerceHub Purchase Orders into Acumatica." This customer-focused review helps you check account assignment and order addresses in the context of the selected store code.

To discuss your store and customer configuration, visit https://biz-techservices.com and ask Biz-Tech Services about the Biz-Tech Services Acumatica CommerceHub Integrator.


How to Map EZCom Trading Partners in Acumatica

Map EZCom EDI trading partners in Acumatica by retrieving the partners, configuring each Partner Code, and choosing either a default Customer ID or the documented Customer Ship To mapping for imported orders. Review the resulting customer, location, address, and warehouse on a representative sales order.

The Biz-Tech Services EZCom EDI Acumatica Connector keeps partner settings separate, so customer and fulfillment choices can be reviewed for each trading relationship. This guide focuses on partner and ship-to mapping rather than the full order-import process.

Before You Map an EZCom Trading Partner

The Biz-Tech Services Acumatica EZCom EDI Connector uses the General Settings screen for connection information. With Modify API Connectivity selected, enter the Account, API Key, Login, and Password provided for the connection. Use Actions > Test Credentials to check connectivity. The documentation describes this test as checking the connection to the Acumatica-Biz-Tech server; it does not describe it as a test of every partner mapping.

On Trading Partners, select Actions > Get Trading Partners to retrieve partners. Partner Code is the lookup identifying the partner whose settings you are configuring. Check the code before changing customer or warehouse settings, particularly if several partners use similar names.

EZCom Trading Partner Mapping Step by Step

Retrieve the trading partners and select the intended Partner Code.

In Partner Settings, review the default Order Type, EZCom Status, and the applicable date filters.

Select Customer ID as the partner default and decide whether the order shipping address should override the default ship address.

When using Customer Ship To, review the trading partner ship-to, customer, and location relationships for the source location number.

Review the default Warehouse ID and any intended warehouse cross-reference; the documented default has priority over a warehouse cross-reference.

Test a representative order for the partner and compare its customer, location, ship-to address, and warehouse with the source order and the intended setup.

Set the Default Customer for Each Partner

In the Trading Partners screen, Customer Information includes Customer ID. The guide says the integration imports customer information from EZCom into the Acumatica customer selected in this field. If Customer Ship To is not set up, that partner customer is used during EZCom order import.

EZCom trading partners

This default links the partner workflow to a configured Acumatica account. It should be checked against the intended trading relationship before an import. The guide does not say that a unique Acumatica customer is automatically created for each buyer or partner.

Use Customer Ship To for Location-Specific Matching

The Biz-Tech Services EZCom EDI Acumatica Integration can follow the Customer Ship To setup during order import. The guide describes a sequence in which the Location Number on the EZCom order is used to find a Trading Partner Ship To ID. It then describes looking for an Acumatica customer matching the Child Customer and Parent Customer, followed by a Customer ID and Location CD match in the customer location setup. If a matching customer is found, that customer is used to create the sales order.

Review the source Location Number and the intended parent, child, customer, and location records together. The manual references Customer Ship To on an "EZCom Store" in its description but does not clearly explain every field, setup screen relationship, or result when a match is missing or ambiguous. Confirm those details in your installed configuration before processing a large batch.

Decide Which Shipping Address and Warehouse to Use

The Override Ship Address Info from EZCom Order option imports the address of the location where the order will be shipped from EZCom. Compare the resulting ship-to details with the source order. The manual does not describe every address fallback when the option is cleared or the incoming address is incomplete.

Partner Settings also includes a default Warehouse ID for imported orders. If Use Cross Ref for warehouse is selected and the cross-reference is configured, the guide says the mapped value can be used during import. Its note adds that Default warehouse must be blank for the cross-reference value to be used. Decide which route applies and verify it on the order; do not assume that the address itself chooses the warehouse.

EZCom send routing request

Review Customer Accuracy and Duplicate Risk

Before importing, compare the partner code and source location number with the customer and location records intended for that relationship. After import, review the created sales order and its ship-to address. These are operational checks, not an automatic duplicate-prevention guarantee.

The source does not establish a complete rule for duplicate customer detection, duplicate order blocking, or the outcome of multiple matching Customer Ship To records. Test those cases with Biz-Tech Services and follow your own review process before enabling recurring processing. For the broader import steps, see "How to Import EZCom Purchase Orders into Acumatica."

Where to Check Your Work

Use these records to review the Biz-Tech Services Acumatica EZCom EDI Integration for the intended partner:

General Settings > Actions > Test Credentials: check the documented server connection test.

Trading Partners > Actions > Get Trading Partners: retrieve the partner list.

Trading Partners > Partner Code: confirm the partner whose settings are being reviewed.

Partner Settings > Customer Information > Customer ID: verify the default customer.

Partner Settings > Override Ship Address Info from EZCom Order: verify the address choice.

Customer Ship To: inspect the mapping for the order Location Number and intended customer and location.

Customers and customer location records: check the parent, child, Customer ID, and Location CD relationships described in the guide.

Partner Settings > Default Warehouse > Warehouse ID and Cross-Reference: review the chosen warehouse route.

Import Purchase Orders and the resulting sales order: compare the source partner and location with the customer, address, and warehouse produced.

Inbound Purchase Orders: inspect the EZCom order information for the corresponding partner.

EZCom Trading Partner Mapping: Frequently Asked Questions

How do I retrieve the EZCom trading partners?

On Trading Partners, choose Actions > Get Trading Partners. Select the appropriate Partner Code before configuring that partner.

Which customer is used when Customer Ship To is not set up?

The manual says the customer configured in Partner Settings is used during order import when Customer Ship To is not set up. Review Customer ID for the relevant Partner Code.

How does the system find a ship-to mapping?

With Customer Ship To configured, the documented process starts with the Location Number on the EZCom order to find a Trading Partner Ship To ID, then checks customer and location relationships. The manual does not fully specify unresolved or multiple-match behavior.

Why did an order use the default warehouse instead of the mapped warehouse?

Check Default Warehouse in Partner Settings. The guide says that field must be blank for the warehouse cross-reference value to be used. Also check the cross-reference option and mapping for the partner.

Does the connector prevent duplicate customers or orders?

The Biz-Tech Services EZCom EDI Acumatica Integrator manual does not document a general duplicate-customer or duplicate-order prevention rule. Check existing records and confirm the behavior for your implementation.

Why might the ship-to address differ from the customer default?

Check Override Ship Address Info from EZCom Order. When selected, the manual says the order shipping address is imported from EZCom. Compare that source address and the resulting order.

Work With Biz-Tech Services on EZCom Trading Partners

A partner review brings together the source location, the customer mapping, and the address and warehouse settings that determine what staff should check on an imported order.

For help reviewing the Biz-Tech Services Acumatica EZCom EDI Integrator for your trading partners, visit https://biz-techservices.com to contact Biz-Tech Services.


How to Map DSCO Trading Partners and Customers in Acumatica

DSCO orders imported into Acumatica use the default Customer selected on the DSCO Store record. The store is identified by Partner Code; the supplied documentation does not describe a separate trading-partner-to-customer mapping table or an automatic customer-matching rule.

The Biz-Tech Services DSCO Acumatica Connector lets a team configure the store and review orders before importing them. This guide focuses on choosing and checking the customer associated with that store, then verifying the result on a representative order.

Before You Assign a DSCO Customer

In the Biz-Tech Services Acumatica DSCO Connector, open DSCO Store and select the Partner Code that identifies the corresponding DSCO store. Enter the connection information on General Settings and use Test Credentials to check the connection. Confirm that you are editing the intended store before making order settings changes.

In Customer Information, select the Acumatica Customer to use by default when that store imports DSCO orders. Agree internally which account should receive the orders and confirm the setting against that decision. The documentation does not say that Partner Code itself is an Acumatica customer account.

DSCO Customer Setup Step by Step

Open the intended DSCO Store record and confirm its Partner Code.

Check the connection using Test Credentials on General Settings.

In Customer Information, select the default Customer for imported orders.

Review the import document type, Order Type, and eligible DSCO Status in Order Settings.

Review enabled Cross-Reference Options and complete any required warehouse mapping.

Retrieve a representative order, inspect it, and import the selected order.

Open the resulting Acumatica document and compare its customer and relevant order details with the expected result.

Understand Partner Code and Default Customer

Partner Code is a lookup that identifies the corresponding DSCO store. Customer is a separate selection in Customer Information: the guide says it is the default customer set on DSCO orders during import. Review both values together so that the store you are processing is associated with the intended Acumatica account.

The documentation does not specify a table that maps individual trading partners or buyers to different customer accounts. It also does not explain an override by buyer, a customer lookup key, or the behavior when an account is missing. Confirm any such requirements with Biz-Tech before relying on them.

DSCO Store test credentials

Review Cross References and Warehouse Requirements

The Biz-Tech Services DSCO Acumatica Integration includes Cross-Reference Options for entities to be matched between systems. The Cross-Reference tab shows only entities whose options are selected. The guide specifically describes warehouse cross-referencing, but does not define a customer or trading-partner cross-reference in the text.

When Use Cross Ref for Warehouse is selected, map the DSCO item warehouse to the Acumatica warehouse value on the Cross-Reference tab. The guide reports the error "Warehouse does not have value." when a required warehouse is not mapped. This is a warehouse mapping issue; the message does not establish that the default customer is wrong.

DSCO warehouse mapping

Inspect the Order and Resulting Customer

Order Settings controls the document type into which DSCO orders are imported, the default Order Type, and the DSCO Status eligible for import. The guide says the relevant order-status checkbox must be selected for an order to be retrieved and imported. Begin Order Date filters retrieval.

On Import DSCO Orders, select GET ORDERS to retrieve orders for the selected period. Select an Order Number to inspect its information. Import a selected order with IMPORT; IMPORT ALL processes the orders in the grid. For a first check, use a representative order and inspect the resulting document and customer before processing a broader batch.

The DSCO Orders screen displays associated sales order and invoice numbers after an order has been imported and an invoice created. Use the available document number to locate the resulting record. The guide does not give a complete ship-to or billing-address mapping rule, so compare those fields with the source order and confirm any discrepancies in your installation.

Avoid Duplicate Assumptions and Diagnose Errors

The supplied manual does not describe how the connector detects duplicate customers or orders, matches buyers to existing accounts, or resolves multiple possible matches. Before repeating an import, check the order and related Acumatica documents using your existing review process. Do not assume that the connector will merge records or block a duplicate.

If an order fails during processing, the import grid displays an error on the corresponding line; hover over the red cross for details. The manual also points to Tools > Trace for additional information. Investigate the reported error before retrying rather than changing customer or warehouse settings without evidence.

Where to Check Your Work

Use these records when reviewing the Biz-Tech Services Acumatica DSCO Integration:

DSCO Store, General Settings: Partner Code and Test Credentials.

DSCO Store, Customer Information: the default Customer.

DSCO Store, Order Settings: import document type, Order Type, and DSCO Status.

Order Settings: Begin Order Date and the selected order-status checkbox.

Cross-Reference Options: entities selected for cross-referencing.

Cross-Reference: warehouse values when Use Cross Ref for Warehouse is selected.

Import DSCO Orders: the retrieved order and any error shown on its line.

DSCO Orders and the resulting Acumatica document: associated document numbers and the customer assigned.

Tools > Trace: additional error information when processing fails.

DSCO Customer Mapping: Frequently Asked Questions

Which customer is used when a DSCO order is imported?

The DSCO Store Customer Information section lets you select a default Customer, which the manual says is set on DSCO orders during import. Check the setting on the intended store.

Does Partner Code identify an Acumatica customer?

The manual defines Partner Code as a lookup for the corresponding DSCO store. It identifies the default Customer as a separate setting; it does not define Partner Code as a customer account.

Can I map each trading partner to a different customer?

The supplied guide does not document a per-trading-partner customer mapping table. Ask Biz-Tech to confirm the supported setup if different buyers must be assigned to different accounts.

Why did an order show a missing warehouse error?

When warehouse cross-referencing is enabled, the Biz-Tech Services DSCO Acumatica Integrator requires the relevant DSCO warehouse value to be mapped to an Acumatica warehouse. The manual identifies "Warehouse does not have value." as the error for an unmapped warehouse.

Does the connector automatically prevent duplicates?

The guide does not describe a duplicate-customer or duplicate-order prevention rule. Check existing orders and documents before repeating an import and confirm the behavior for your configuration.

Where can I see why an order failed?

Look for the error on the order line in the import grid and hover over the red cross. The guide also lists Tools > Trace as a source of additional error details.

Work With Biz-Tech Services on DSCO Customer Setup

For the broader order-import process, see "How to Import DSCO Orders into Acumatica." Review the default customer and test the resulting document before running larger batches.

To review your requirements for the Biz-Tech Services Acumatica DSCO Integrator, visit https://biz-techservices.com to contact Biz-Tech Services.


How to Map ShipStation Customers and Ship-To Addresses in Acumatica

ShipStation customers and ship-to addresses reach Acumatica through the ShipStation-to-Acumatica order import settings. You can choose whether to import customer information and whether ShipStation shipping and billing addresses override the addresses in Acumatica.

The Biz-Tech Services ShipStation Acumatica Connector also lets you select the ShipStation store whose orders will be retrieved. Customer selection, address overrides, and the warehouse cross-reference serve different purposes, so review each before importing orders.

Before You Configure ShipStation Customer Imports

In ShipStation Store, select the correct Store Code and configure the connection settings. Use Test Credentials to check the connection. Set Integration Option to ShipStation to Acumatica for the inbound order import screens. On General Info, Get Stores retrieves connected stores; select the store intended for the import.

The Biz-Tech Services Acumatica ShipStation Connector exposes Import Info for this direction. Review Status Key and Status, the document and Order Type settings, and Begin Order Date alongside the Customer Information options. The manual states that if no status is selected, orders with Shipped status are retrieved by default.

ShipStation Customer and Address Setup at a Glance

Choose the intended Store Code and the ShipStation to Acumatica Integration Option.

Retrieve connected stores with Get Stores and select the store to import.

Review Import Customer and the applicable default customer setup.

Choose Override Ship Address Information and Override Bill Address Information independently.

Check any needed warehouse and shipping-method cross-references.

Retrieve a representative order, import it, and compare its customer and addresses with the source.

Choose How Customer Information Is Imported

The manual states that selecting Import Customer imports customer information from ShipStation and creates a new customer record in Acumatica. It describes name, address, and contact information as examples of the customer details involved. If Import Customer is not selected, it says orders use default customer settings from ShipStation, but it does not explain the exact default account selection or how it is configured.

Before processing a batch, confirm the intended customer with your implementation team and test a representative order. The manual does not describe how an existing customer is matched, whether a record is reused, or how ambiguous matches are handled. Do not assume that a matching name, email, or address automatically links to an existing record.

Set the Ship-To and Billing Address Overrides

The Biz-Tech Services ShipStation Acumatica Integration provides separate Override Ship Address Information and Override Bill Address Information checkboxes. The first allows the shipping address from ShipStation to override the Acumatica address; the second imports the ShipStation billing address. These selections let you review the two address decisions separately.

For a test order, compare the shipping destination and billing address on the resulting Acumatica sales order with the source order, including a case where the two differ. The documentation does not describe every missing-address fallback or whether an override creates a customer location. Confirm those details in your configured environment.

Keep Store, Warehouse, and Ship Via Mapping Separate

Store Code identifies the configured integration store, while the Selected checkbox chooses a connected ShipStation store for order and shipment imports. Use Cross Ref for Warehouse enables cross-referencing between ShipStation and Acumatica warehouses. Use Cross Ref for Ship Via enables shipping-method cross-referencing; selecting these options reveals the corresponding setup tabs.

A warehouse or shipping-method cross-reference is not documented as a customer or ship-to address match. Review each mapping for its own purpose and compare the resulting order with the source. The manual does not give detailed cross-reference columns or a customer cross-reference procedure.

Review a Test Order and Duplicate Risk

On Import ShipStation Orders, choose the appropriate store code and select Get Orders. Use Import for selected orders; Import All processes all orders shown on the screen. Inspect the resulting Sales Orders record for the intended customer and addresses before broadening the process.

Import ShipStation orders

Check existing customer and order records before repeating an import when duplication is a concern. This is a review practice, not a documented automatic control: the manual does not specify customer deduplication, merge behavior, or duplicate order prevention. Confirm the behavior for your setup with Biz-Tech before scheduling or repeating bulk processing.

Where to Check Your Work

Use the Biz-Tech Services Acumatica ShipStation Integration settings and records to trace a test order:

ShipStation Store: Store Code, connection settings, Test Credentials, and Integration Option.

General Info: Get Stores and the Selected checkbox for the intended connected store.

Import Info: Status Key, Status, and Begin Order Date for the order selection.

Import Info: Import ShipStation Orders To and Order Type for the resulting document.

Customer Information: Import Customer and the default behavior chosen for your workflow.

Customer Information: Override Ship Address Information and Override Bill Address Information.

Warehouse Cross Reference and Ship Via Cross Reference: mappings where enabled.

Import ShipStation Orders: the order retrieved with Get Orders before choosing Import.

Sales Orders: the customer and shipping and billing details on the imported order.

ShipStation Customer Mapping: Frequently Asked Questions

How does ShipStation create a customer in Acumatica?

The manual says that selecting Import Customer imports customer information from ShipStation and creates a new Acumatica customer record. It does not specify the full rules for matching an existing customer.

Can the ship-to address differ from the billing address?

Yes. The Biz-Tech Services ShipStation Acumatica Integrator provides separate shipping and billing address override options. Test both choices and compare the imported order with its source.

Why is the shipping address not what I expected?

Review Override Ship Address Information and compare the source order with the imported sales order. The manual does not describe every fallback when information is missing, so verify the configuration and test the specific case.

Does a warehouse cross-reference map customers?

The documented warehouse cross-reference matches warehouses, not customers. Customer import and address override selections are separate settings.

Does the connector prevent duplicate customers or orders?

The manual does not establish automatic duplicate prevention or customer merge rules. Review existing records and confirm your implementation behavior before repeating imports.

Why can I not select the store code for an order import?

Check the ShipStation Store Integration Option. The manual says the inbound import screen requires ShipStation to Acumatica and reports an error if the store is configured for another direction; it does not quote the exact error text.

ShipStation integration direction

Where can I learn about the outbound order workflow?

The companion article How to Send Acumatica Orders to ShipStation covers sending orders in the opposite direction. This article focuses on inbound customer and address settings.

Work With Biz-Tech Services on ShipStation Customer Mapping

A useful test checks the selected store, intended customer, shipping address, and billing address together. Confirm undocumented matching and fallback behavior before relying on a high-volume import.

To discuss your requirements for the Biz-Tech Services Acumatica ShipStation Integrator, visit https://biz-techservices.com.

Check the video for more details https://www.youtube.com/watch?v=ZS94T90M20o


How to Map ShipHero Customers and Warehouses to Acumatica

ShipHero customer and warehouse mapping in Acumatica starts with the ShipHero Store setup: choose the customer handling for imported orders and map ShipHero warehouse values to the corresponding Acumatica warehouses. Then check the customer, addresses, and warehouse on a representative imported order.

The Biz-Tech Services ShipHero Acumatica Connector supports both ShipHero-to-Acumatica and Acumatica-to-ShipHero workflows. This guide focuses on the documented inbound customer and warehouse settings; the two workflow directions do not necessarily expose identical settings.

ShipHero store credential configuration

Before You Map ShipHero Customers and Warehouses

In the Biz-Tech Services Acumatica ShipHero Connector, choose the intended ShipHero Store Code and Integration Option, then enter the connection information on the Connection Settings tab and use Test Credentials. The ShipHero-to-Acumatica option exposes the inbound settings discussed below.

Under Stores to get, select the stores whose orders and shipments should be imported. The store-level Customer field can specify an individual or default customer for a store; when it is blank, the manual says order import takes customer information from the Customer Information setup. Verify that the store and customer choices match your business process.

ShipHero Customer and Warehouse Mapping at a Glance

Select the intended ShipHero Store Code and the ShipHero-to-Acumatica integration direction.

Select the source stores in Stores to get and review each store-level Customer value.

In Customer Information, choose Import Customer or the default Customer and, when applicable, Customer Class.

Review the separate shipping and billing address override options.

Select Use Cross Ref for Warehouse and map the ShipHero and Acumatica warehouse values.

Retrieve a representative order, import it, and compare its customer, addresses, and warehouse with the intended setup.

Choose the Customer for Imported ShipHero Orders

In Customer Information, selecting Import Customer imports customer information from ShipHero into a new customer record in Acumatica. The Customer Class field appears when Import Customer is selected and supplies the default class for newly created customers.

When Import Customer is not selected, the manual says orders use the default customer in the Customer field. Stores to get also has its own Customer field, with a fallback to Customer Information when the store-level field is empty. Check both places when an order uses an unexpected customer, and test the intended combination before processing a batch.

The manual does not describe a complete existing-customer matching algorithm or guarantee prevention of duplicate customers or orders. Review existing records and the source order identifiers before importing; confirm ambiguous cases with your implementation team.

Map ShipHero Warehouses to Acumatica

The Biz-Tech Services ShipHero Acumatica Integration uses the Warehouse Cross-Reference for order import and item synchronization. Select Use Cross Ref for Warehouse in Cross-Reference Options to display the corresponding tab, then map the ShipHero values to their intended Acumatica values.

The manual says an imported order receives the mapped warehouse on the sales order. It also describes the same setup being used to establish an item warehouse during ShipHero item synchronization. Review both results when a warehouse serves multiple order or inventory workflows.

The documentation does not specify a complete fallback or error message for a missing or conflicting warehouse mapping. If the warehouse is unexpected, inspect the selected store and cross-reference, then confirm the correct values before repeating the process.

Review Shipping and Billing Addresses

Customer Information contains separate Override Ship Address Information from Ship Hero Order and Override Bill Address Information from Ship Hero Order options. The manual describes the first as importing the destination address. Its billing description names a different platform, so confirm the billing behavior for your installed version before relying on it.

Compare the source order with the customer and both addresses on the resulting Acumatica document. A shipping address and a customer account answer different questions: review both when an order is assigned to a default customer.

Understand Warehouse Locations and Item Defaults

Warehouse mapping and location mapping are related but separate settings. The Locations tab offers Use Location Mapping, which shows a grid for mapping locations. The manual says locations are loaded for warehouses configured in Warehouse Cross-Reference. Check the warehouse mapping first when a required location is missing from the loaded list.

The Sync Info tab also provides a Warehouse ID default for newly created items when Import Item is selected. When Import Item is not selected, the manual describes using the configured replacement item and Warehouse ID instead of creating a new item. These item defaults should be reviewed alongside the warehouse cross-reference, without assuming the manual defines every precedence case.

Where to Check Your Work

Use these screens and fields to review the Biz-Tech Services Acumatica ShipHero Integration before and after a test import:

ShipHero Store: Ship Hero Store Code and Integration Option.

Connection Settings: connection information and Test Credentials result.

Stores to get: Selected and the store-level Customer field.

Customer Information: Import Customer, Customer Class, and Customer.

Customer Information: shipping and billing address override settings.

Cross-Reference Options: Use Cross Ref for Warehouse.

Warehouse Cross-Reference: the ShipHero and Acumatica warehouse values.

Locations: Use Location Mapping and locations loaded for mapped warehouses.

Import Ship Hero Orders: selected Ship Hero Store Code, Get Orders, and Import.

Import ShipHero orders

Ship Hero Order and the resulting sales order: source order, customer addresses, and assigned warehouse.

ShipHero Customer and Warehouse Mapping: Frequently Asked Questions

Why did an imported order use the default customer?

Check Import Customer and the Customer field in Customer Information, as well as the Customer field for the selected source store. The manual says a blank store-level Customer falls back to Customer Information.

How do I show the Warehouse Cross-Reference tab?

Select Use Cross Ref for Warehouse in Cross-Reference Options. The Biz-Tech Services ShipHero Acumatica Integrator then exposes the corresponding tab for mapping values.

Why is the wrong warehouse on an imported order?

Check the selected store and the ShipHero-to-Acumatica warehouse mapping, then compare the result on the sales order. The manual does not give a specific error message or complete fallback rule for an absent mapping.

Does the connector prevent duplicate customers?

The supplied manual does not establish a general duplicate-prevention or merge rule. Review existing records and validate a representative import before relying on automated customer creation.

Why is a warehouse location missing from the loaded list?

The manual says locations load for warehouses configured on Warehouse Cross-Reference. Check that the intended warehouse is mapped and review Use Location Mapping before loading locations.

Where can I check the source order and addresses?

The Ship Hero Order screen displays the store code and order identifiers, with an Addresses tab for customer addresses. Compare those values with the imported sales order.

Work With Biz-Tech Services on ShipHero Mapping

For the broader order process, see "How to Sync Orders Between ShipHero and Acumatica"; for inventory synchronization, see "How to Sync ShipHero Inventory with Acumatica."

To review your customer, warehouse, and location requirements with Biz-Tech Services, visit https://biz-techservices.com and ask about the Biz-Tech Services Acumatica ShipHero Integrator.

Watch video for more details https://www.youtube.com/watch?v=nmPg3d1oAPI


How to Map Magento Customers to Acumatica Customers

Magento customer information can be imported into a new Acumatica customer record using the Import Customer setting on the Magento Store screen. The connector can also export eligible Acumatica customers to Magento and record the resulting Magento Customer ID on the customer record.

The Biz-Tech Services Magento Acumatica Connector has separate controls for customer creation, shipping and billing addresses, customer groups, and outbound synchronization. Review those controls together, then check a representative order and customer record before processing a larger batch.

Before You Configure Magento Customer Information

The Biz-Tech Services Acumatica Magento Connector uses the Magento Credentials and Magento Store screens to connect to and configure a store. Magento Credentials includes a Store Code, connection settings and Test Credentials; Magento Store controls order import and Customer Information options.

Decide which existing Acumatica customer records and classes should be used in your implementation. The supplied connector documentation describes how to create new customer records, but does not explain the matching rules for an existing customer, how duplicates are detected, or how the connector resolves competing matches. Confirm those rules with your implementation team before relying on automatic matching.

Magento Customer Mapping at a Glance

Select the intended store in Magento Credentials and test its connection.

Review Import Customer and the default Customer Class in Magento Store.

Choose whether to import shipping and billing addresses using their separate override options.

Review Customer Groups and customer price classes before exporting customers.

Retrieve a representative order and check its address and imported sales order.

For an eligible outbound customer, run Sync Magento Customer and inspect the Magento Customer ID.

Import Customer Information into Acumatica

In the Customer Information section of Magento Store, Import Customer imports customer information from Magento into a new customer record in Acumatica. Customer Class supplies the default class for new customers that do not already exist in Acumatica and are created by the integration.

The documentation does not say which Magento field is used to locate an existing customer, what happens when Import Customer is off, or whether an existing record is updated. Treat the setting as a documented new-customer option, not proof that every Magento account is matched or merged automatically.

As an operational check, compare the customer on a representative imported sales order with the intended account. Investigate unexpected records before repeating the import. A manual review helps identify possible duplicates; it is not a documented connector duplicate-prevention feature.

Keep Shipping and Billing Address Choices Separate

The Biz-Tech Services Magento Acumatica Integration includes Override Ship Address Information and Override Bill Address Information under Customer Information. The first imports the address where the order is to be shipped; the second imports address information for the party paying the order bill.

Review both settings against your order-entry process. A customer may need different shipping and billing addresses, so inspect the resulting order rather than assuming the two addresses should be identical. The Magento Orders screen also has an Addresses tab that displays customer address details.

The manual does not specify a field-by-field mapping, address-matching algorithm, or a rule for choosing an existing ship-to location. Confirm those details for your version before documenting them as automatic behavior.

Align Customer Groups and Price Classes

The Customer Groups tab can synchronize Magento Customer Groups to Acumatica Customer Price Class. The customer export instructions also require the relevant Customer Price Class and customer group to exist in both systems. Check this prerequisite before an outbound sync.

The manual does not describe a group conflict-resolution rule or say that syncing a group merges customer records. If group values or the resulting price class do not look right, review the configured records in each system with the implementation team.

Export an Acumatica Customer to Magento

Customer export can be initiated from the Customers screen through Actions > Sync Magento Customer, or from the Export Magento Customer processing screen. The manual lists these conditions for a customer to sync:

The relevant Customer Price Class and Magento Customer Group must exist in both systems.

The customer must have a contact.

The contact must have First Name, Last Name, Email, and a Magento Customer Password combining letters, numbers, and special characters.

After customer export, the Magento Customer checkbox is checked on the Customers screen and the Magento Customer ID appears under its Magento Customers tab. Review those indicators on the intended customer. They document the export result; the manual does not establish how a pre-existing Magento account is matched or whether duplicate accounts are prevented.

Check the Customer on an Imported Order

The Import Magento Orders screen retrieves orders with Get Orders. The documented grid includes Magento orders in Partially Shipped, on hold, Pending, and Processing statuses. Import processes selected orders and Import All processes the displayed grid.

Open the Magento order through its order-number link to review the Addresses tab. The Magento Orders screen shows Order Number and, if imported, Sales Order Number. Follow the sales order and check its customer and addresses against the source order and the intended account.

For the broader retrieval and import sequence, see How to Import Magento Orders into Acumatica. Customer validation is the focus here; the order article covers the wider transaction workflow.

Magento order refresh screen

Where to Check Your Work

Use these screens and fields to review the Biz-Tech Services Acumatica Magento Integration after a controlled test:

Magento Credentials: Store Code identifies the intended store; Test Credentials checks the connection.

Magento Store > Customer Information: review Import Customer and Customer Class.

Magento Store > Customer Information: review the shipping and billing address override options separately.

Customer Groups: review the Magento groups and corresponding Acumatica customer price classes.

Customers: check the intended customer and contact before outbound synchronization.

Customers > Magento Customers: check Magento Customer ID after export.

Customers: check the Magento Customer checkbox after export.

Import Magento Orders: compare the retrieved order list with the documented eligible statuses.

Magento Orders > Addresses: review the imported address information.

Magento Orders > Sales Order Number: follow the resulting order and check the customer and addresses.

Magento Customer Mapping: Frequently Asked Questions

Does Import Customer update an existing Acumatica customer?

The manual describes importing information into a new customer record, but does not explain how existing records are matched or updated. Confirm that behavior for your installation before relying on it.

Why did a customer not export to Magento?

Check the prerequisites for the Biz-Tech Services Magento Acumatica Integrator: the customer price class and Magento group, a contact, and the contact fields and password described above. The manual does not provide a specific customer-export error message.

How do I confirm an outbound customer sync?

On the Acumatica Customers screen, check the Magento Customer checkbox and look for the Magento Customer ID under the Magento Customers tab. The manual describes these indicators after customer export.

Can shipping and billing addresses differ?

The connector provides separate override options for shipping and billing information. Review the imported addresses on the order and confirm that each matches the intended destination or billing party.

Does the connector automatically prevent duplicate customers?

The supplied manual does not document duplicate detection, matching keys, or merge behavior. Review representative results and agree on a duplicate-handling process with your implementation team.

Why is a Magento order missing from the import list?

Check the store connection and whether the order has one of the statuses documented for the import screen: Partially Shipped, on hold, Pending, or Processing. Review the configured retrieval settings as well.

Work With Biz-Tech Services

A reliable customer workflow depends on correct settings and a review of the records created or linked in each system. Confirm any undocumented matching and duplicate-handling rules before expanding a test to production volumes.

For help reviewing your customer workflow, visit https://biz-techservices.com and contact Biz-Tech Services about the Biz-Tech Services Acumatica Magento Integrator.

Watch video for more details here: https://www.youtube.com/watch?v=o8rZAgH0ASk


How to Map Amazon Customers and Marketplace Orders in Acumatica

Amazon customer handling in Acumatica depends on the fulfillment path and the customer settings in the Amazon Store: fulfillment by merchant (FBM) orders can create a customer or use a default customer, while fulfillment by Amazon (FBA) settings specify a default customer for order imports.

The Biz-Tech Services Amazon Acumatica Connector also offers separate FBM options for the shipping and billing addresses from an Amazon order. Review the customer and address on the resulting document together; an order address and the customer account are different pieces of information.

How Amazon Customer Settings Work in Acumatica

The Biz-Tech Services Acumatica Amazon Connector uses settings on the Amazon Store screen to control how Amazon orders enter Acumatica. For FBM, selecting Import Customer directs the integration to import Amazon customer information into a new customer record. If it is not selected, the order uses the default customer. The manual also describes customer creation when a customer does not already exist.

7 FBM Settings

For FBA, the Customer field sets a default customer used during the order import process. The guide describes FBA orders being imported as invoices; it does not establish that the FBM customer-creation option applies to FBA orders.

Amazon Customer Mapping Step by Step

Use this sequence to check the customer outcome for each fulfillment path before processing a larger set of orders:

Identify the correct Amazon Store and determine whether the order uses FBM or FBA.

For FBM, review Import Customer and the configured default customer, as well as the separate shipping and billing address override options.

For FBA, review the Customer field and the configured order dates and statuses.

On Import Amazon Orders, choose the store and retrieval dates, select GET ORDERS, and inspect a retrieved FBM order by selecting its Order Number.

Import the selected order or use IMPORT ALL when the full displayed batch is ready. Inspect the created document and compare its customer and addresses with the source order.

For FBA, use Import FBA Orders for orders matching the configured dates and statuses, then check the resulting invoice.

Choose Between a New Customer and a Default Customer for FBM

The Biz-Tech Services Acumatica Amazon Integration provides the Import Customer checkbox under FBM customer information. When selected, customer information is imported into a new customer record. When the checkbox is clear, Amazon orders use the default customer. Review the setting for each store before an import, because it determines whether the order is associated with a default account or customer information is brought into a new record.

The guide does not explain which attributes identify an existing customer, the matching precedence, or how duplicates are prevented. Before processing a batch, review a representative order and the resulting customer record. If the expected account is not used, confirm the store settings and ask Biz-Tech Services to verify the matching behavior for your configuration.

Review Shipping and Billing Addresses Separately

For FBM, Override Ship Address Information from Amazon Order imports the destination address from Amazon. Override Bill Address Information from Amazon Order imports the billing address. These are separate settings, so check the customer, ship-to address, and bill-to address individually on a representative imported order.

Do not assume that selecting the address options creates separate Acumatica customer accounts or establishes a permanent ship-to mapping. The guide identifies the address override options but does not document such behavior. It also does not describe the full address result when each option is cleared.

Keep FBA Customer Defaults Distinct from FBM Settings

In the Biz-Tech Services Acumatica Amazon Integration, FBA settings include a Customer field for the default customer used during order import. They also include the beginning order date and a table for mapping Amazon order statuses to Acumatica statuses. Select the corresponding order status for retrieval and import, and review the resulting invoice under the documented FBA workflow.

The manual describes an FBA shipment billing-address override inconsistently: its two branches both say the option is selected, while describing different address results. Confirm the behavior in your own configuration before relying on that setting. The source does not establish a customer matching algorithm for FBA.

Check Marketplace Orders and Investigate Exceptions

The Import Amazon Orders screen retrieves orders for a Store Code and the selected Start Date and End Date. GET ORDERS retrieves the orders; importing is a separate action. Select an Order Number to inspect the source details before import, and use the resulting Acumatica document to confirm the customer and addresses.

10 Import Order

If an order fails, the guide says the grid displays an error on the corresponding line. Hover over the red cross for more information, or open Tools > Trace for additional detail. The manual does not provide a duplicate-customer error message or guarantee that an existing record will be matched in a particular way.

For the broader import process, see How to Import Amazon Orders into Acumatica. For item mapping, see How to Map Amazon SKUs to Acumatica Inventory IDs.

Where to Check Your Amazon Customer Mapping

Use the Biz-Tech Services Amazon Acumatica Integrator to review these settings and results:

Amazon Store: verify the Store Code for the marketplace being processed.

FBM Customer Information: inspect the Import Customer setting and default customer.

FBM address options: inspect shipping and billing overrides independently.

FBA Customer: review the default customer selected for FBA orders.

FBA dates and status mapping: check whether an order qualifies for retrieval.

Import Amazon Orders: verify Start Date and End Date and review retrieved orders.

Amazon Orders: open an Order Number and inspect any reported error.

Imported sales order or invoice: compare the customer and addresses with the Amazon order.

Import grid and Tools > Trace: examine processing errors before retrying.

Amazon Customer Mapping Frequently Asked Questions

Can an FBM order use a default Acumatica customer?

Yes. The documented FBM behavior uses the default customer when Import Customer is not selected.

Can an Amazon order create a customer in Acumatica?

The Biz-Tech Services Acumatica Amazon Integrator supports importing Amazon customer information into a new customer record when the FBM Import Customer option is selected. The manual does not explain the complete matching and duplicate-prevention rules.

Does the FBA order use the same setting as FBM?

The manual describes a separate Customer field in FBA settings for the default customer. It does not say that the FBM Import Customer option controls FBA customer creation.

Why is the shipping address different from the customer default?

For FBM, the shipping address override option imports the destination address from the Amazon order. Review that option and compare the imported order with the source information.

How can I avoid creating duplicate customers?

The guide does not document a duplicate-detection rule. Review the Import Customer setting and representative imported records, and confirm the matching rules with Biz-Tech Services before a larger import.

Where do I find an order import error?

Check the affected line in the import grid and hover over the red cross for detail. Tools > Trace can provide additional information.

Work With Biz-Tech Services on Amazon Customer Mapping

Correct customer defaults, address settings, and a review of representative orders help your team confirm the intended account and address before scaling the workflow.

For help reviewing your Biz-Tech Services Acumatica Amazon Integrator configuration, visit https://biz-techservices.com to contact Biz-Tech Services.

Watch video for more details https://www.youtube.com/watch?v=TM6M2iuTFsQ


How to Map Shopify Customers and B2B Companies to Acumatica Customers

Shopify customers can be connected to Acumatica customers through order import settings, tag cross-references, and, for business-to-business (B2B) companies, company synchronization. The appropriate path depends on whether you are importing an order or synchronizing a company and its contacts and locations.

The Biz-Tech Services Shopify Acumatica Connector gives teams several ways to handle customer data, but the settings do different jobs. This guide separates the default customer and tag choices for incoming orders from Shopify Plus B2B company synchronization so you can verify the customer and address on the resulting records.

Before You Map Shopify Customers

The Biz-Tech Services Acumatica Shopify Connector uses the Shopify Stores record to hold connection and import settings. Confirm that the intended Store Code identifies the correct store and that its credentials have been configured and tested. For Shopify Plus B2B synchronization, select Use B2B on the store record.

The customer path also depends on your workflow. Import Customer and customer tag cross-references are described under order import. Import Shopify Companies, Shopify companies, and Export Shopify Companies handle company data. The documentation does not specify a universal matching or duplicate-detection rule across these paths.

Shopify customer information settings

Shopify Customer Mapping at a Glance

  1. Choose the correct Shopify Stores record and verify the connection.
  2. For incoming orders, decide whether Import Customer is selected or a default customer is used.
  3. If you use order tags to select a known customer, configure the tag and Acumatica customer code in Cross-Reference.
  4. Choose the ship-to and billing address override settings for incoming orders.
  5. For Shopify Plus B2B company data, enable Use B2B and choose the appropriate company import or export process.
  6. Check the resulting customer, contacts, locations, and order addresses before relying on the configuration.

Choose the Customer for Incoming Shopify Orders

On the store record, the documentation says selecting Import Customer imports Shopify customer information into a new Acumatica customer record. If Import Customer is not selected, Shopify orders are imported with the default customer. Confirm the intended default before importing orders, especially when a single account is used for multiple buyers.

The manual does not explain how an existing customer is matched or whether a new customer is prevented when an order is imported repeatedly. Review existing customer records and test a representative order before processing a large batch. Do not assume that a default customer identifies an individual buyer.

Map a Shopify Tag to an Acumatica Customer

The Biz-Tech Services Shopify Acumatica Integration can use a configured Shopify tag to select an Acumatica customer during order import. In the Import Settings tab, select Use Tags to Import Customer and choose type Code. On Cross-Reference, enter the Shopify tag in Shopify Value and the corresponding Acumatica customer account code, AcctCD, in Acumatica Value.

The manual says an order with a mapped tag should select the customer according to that setup. Check the exact tag and account code with a test order. It does not specify which customer wins if multiple tags match, or how tag mapping interacts with every Import Customer setting. Resolve those cases with Biz-Tech before depending on the behavior.

Import and Export Shopify B2B Companies

For Shopify Plus B2B, the manual describes bidirectional synchronization of customers, contacts, and location information after Use B2B is enabled. Import Shopify Companies retrieves company data from Shopify into Acumatica; its filter uses the Shopify updated date. The manual says a company disappears from that processing screen after successful import.

For a specific company, the Shopify companies screen provides Get Company by ID and Create Customer. The first fetches a company using its Shopify ID; the second imports the selected company as an Acumatica customer. Review its customer details, associated contacts, and locations before creating the customer. The documentation does not state that Create Customer automatically merges a pre-existing Acumatica customer.

Export Shopify Companies sends customers, contacts, and locations from Acumatica to Shopify in a batch. The manual says a successfully synchronized customer disappears from the export screen and returns when changes occur. For the separate Sync Customer action, it describes Acumatica as the source of customer and contact details sent to Shopify. Confirm ownership of each field before synchronizing in both directions.

Check Contacts, Locations, and Order Addresses

The manual describes a B2B customer ID on the Shopify Customers tab for customers linked to a Shopify B2B company. Associated contact IDs are shown on the Contacts tab of the Acumatica Customers screen and on the Contacts screen. A location ID is stored on the Shopify Info tab of the Locations screen. Compare these identifiers with the intended company and location; the manual does not provide a complete field-by-field matching algorithm.

Export Shopify companies in Acumatica

For incoming orders, Override Ship Address Information from Shopify Order and Override Bill Address Information from Shopify Order control whether address information is brought from the order. For outbound orders, the separate Order Export Settings include Export Customer, Update Shipping Address, and Update Billing Address. If Export Customer is unchecked, the manual says the selected default customer is used for exports.

Before enabling automation, compare a representative order with its customer, billing address, and ship-to address in both systems. Review shared company names and contacts manually; neither a company name nor an address is documented as a guaranteed unique match.

Where to Check Your Work

Use the Biz-Tech Services Acumatica Shopify Integration settings and records below to trace a customer from the store setup to the resulting transaction.

  • Shopify Stores: confirm Store Code and test the connection credentials.
  • Import Settings: review Import Customer and the configured default customer.
  • Import Settings: check Use Tags to Import Customer and its selected type.
  • Cross-Reference: compare Shopify Value with the tag and Acumatica Value with the customer AcctCD.
  • Import Settings: check the ship and bill address override selections.
  • Shopify Stores: verify Use B2B when using the documented Shopify Plus B2B flow.
  • Shopify companies: inspect company details, contacts, and locations fetched by company ID.
  • Customers and Contacts: inspect the linked B2B customer and contact IDs.
  • Locations: inspect the location ID on Shopify Info.
  • Shopify Orders and the resulting Acumatica document: compare customer and address information with the source order.

Shopify Customer Mapping: Frequently Asked Questions

Why do imported orders use the same Acumatica customer?

Check whether Import Customer is unselected and a default customer is configured. The manual says orders use the default in that case. Also inspect any tag cross-reference setup used for customer selection.

How do I assign an order to an existing customer using a tag?

Select Use Tags to Import Customer, choose type Code, and map the Shopify tag to the Acumatica customer AcctCD in Cross-Reference. Test the resulting selection using an order carrying that tag.

Does B2B company synchronization need a setting?

Yes. The Biz-Tech Services Shopify Acumatica Integrator documentation says to enable Use B2B for bidirectional synchronization with Shopify Plus B2B.

Can I import one specific Shopify company?

The Shopify companies screen offers Get Company by ID to retrieve a specific company and Create Customer to import the selected company as an Acumatica customer.

Does the connector automatically prevent duplicate customers?

The supplied manual does not establish a general duplicate-prevention or merge rule. Review existing records and test your own workflow before importing companies or orders in bulk.

Why is the shipping address different from the one I expected?

Compare the Shopify order address with the Acumatica document and check Override Ship Address Information from Shopify Order. The manual does not document every fallback or conflict case, so verify the result with a representative order.

Where can I find more on Shopify order imports?

The companion article How to Import Shopify Orders into Acumatica covers the broader order-import process. Use this guide when the question is which customer, company, contact, or location is associated with the transaction.

Work With the Biz-Tech Services Shopify Connector

A reliable customer setup starts with an explicit choice of order defaults, tag mappings, company synchronization, and address settings. Validate those choices with real records and review undocumented matching scenarios before enabling batch processes.

For help reviewing your configuration, visit https://biz-techservices.com to discuss the Biz-Tech Services Acumatica Shopify Integrator.

Watch video for more details: https://www.youtube.com/watch?v=1YZGvGQRiCs


How to Map WooCommerce Customers to Acumatica Customers

WooCommerce customers are connected to Acumatica customers through customer information brought in with orders and through customer synchronization or a manually entered Woo Customer Info record. Configure the store and customer options first, then verify the customer, contact, store code, and WooCommerce customer ID before relying on the connection for orders.

The Biz-Tech Services WooCommerce Acumatica Connector supports both standard customer synchronization and business-to-business (B2B) contact synchronization. The two directions serve different purposes: order import brings customer information into Acumatica, while customer export sends Acumatica customer or contact information to WooCommerce.

Before You Map WooCommerce Customers in Acumatica

The Biz-Tech Services Acumatica WooCommerce Connector uses a WooCommerce Store configuration and customer records with suitable contact information. In WooCommerce Store Preferences, enter the store credentials and use Test Credentials. A successful test displays "Credentials are valid." Then review the store settings for the intended Store Code.

On the WooCommerce Store screen, decide whether Use B2B store should be selected for the intended workflow. Review Import Customer, Customer Class, and the ship and bill address override options under Order Settings. These choices affect the information used when importing orders; they do not substitute for checking the customer link.

WooCommerce Customer Mapping Step by Step

  1. Confirm the Store Code and test the connection in WooCommerce Store Preferences.
  2. Review Import Customer, Customer Class, and the shipping and billing address options in WooCommerce Store Order Settings.
  3. Check that the Acumatica customer has a contact with first name, last name, and email for automatic customer synchronization.
  4. For a manual link, open the customer, add a record on Woo Customer Info, and set Contact ID, Store code, WooCommerce Customer ID, and B2B.
  5. For synchronization, use Sync WooCommerce Customer from Actions on the Customers screen, or use the Export WooCommerce Customers processing screen.
  6. Inspect the resulting Woo Customer Info record and compare its customer ID and store with the intended WooCommerce account.
  7. Test an appropriate order and review its customer and address information before using the configuration more broadly.

How Order Import Uses Customer and Address Settings

The manual says individual customers are not imported directly from WooCommerce into Acumatica; customer information arrives through WooCommerce orders. When Import Customer is selected, the integration imports customer information into a new Acumatica customer record. Customer Class supplies the default class for new customers that do not already exist and are created by the integration.

Override Ship Address Information from WooCommerce Order brings in the address to which the order will be shipped. Override Bill Address Information from WooCommerce Order brings in the billing address. When Import Customer and both address override options are unselected, the manual says the order uses default customer information in Acumatica instead.

Review an imported order against the source order, especially when the billing and shipping addresses differ. The manual does not specify every matching rule used to choose an existing Acumatica customer on order import, so confirm that behavior for your configuration instead of assuming email alone determines the match.

Link Existing Customers and Reduce Duplicate Risk

The Biz-Tech Services WooCommerce Acumatica Integration can connect a customer manually through Woo Customer Info. On the Customers screen, add a record on that tab and enter the Contact ID, Store code, WooCommerce Customer ID, and B2B fields. Verify each value against the intended contact and store before saving.

For standard customer synchronization, the documentation says the program checks WooCommerce using the customer email, WooCommerce Customer ID, and first name plus last name. If it finds the customer, it creates a Woo Customer Info record with the WooCommerce Customer ID. If it does not find the customer, it creates a new customer on the WooCommerce website and sets the ID on that tab.

That makes accurate contact information and an existing ID useful checks before synchronization. Similar names or shared email addresses deserve human review. The documentation does not define all tie-breaking rules or guarantee that duplicates can never occur; review the record selected by the process.

Choose Standard or B2B Contact Synchronization

With Use B2B store selected, the documented B2B process synchronizes customer contacts and creates users in WooCommerce. Before export, the system searches for an existing user by contact ID, then email, and finally a username made from the contact first and last names. The manual requires a password to be set on the contact in Acumatica before export.

The Customers screen includes Woo Customer Info, where one or more contacts can be selected for synchronization. If the tab is empty and B2B Store is enabled, the manual says all contacts are exported as separate users. With B2B Store disabled, it says only the primary contact is exported, or the first available contact if no primary contact exists. Check which contacts should represent the customer before processing.

Check the Customer Used for an Outbound Order

When exporting an Acumatica sales order to WooCommerce, the manual says the connector uses the corresponding customer ID in Woo Customer Info if the customer has already been exported. Otherwise, the order is created with the Guest customer. A completed customer sync and a reviewed ID therefore matter when the order must use the intended WooCommerce account.

Customer mapping and order-field mapping are related but separate checks. Order Mappings defines which order fields synchronize; a change to that configuration does not affect orders already retrieved. The manual says an already retrieved order can be changed manually in its Import Fields tab before import.

WooCommerce default import options in Acumatica

Where to Check Your Work

Use these checks when reviewing the Biz-Tech Services Acumatica WooCommerce Integration and its customer records:

  • WooCommerce Store Preferences: Store Code and the result of Test Credentials.
  • WooCommerce Store: Use B2B store and the Order Settings customer options.
  • Order Settings: Import Customer and the default Customer Class for newly created customers.
  • Order Settings: the separate ship and bill address override selections.
  • Customers, Contacts tab: the intended contact and its first name, last name, and email.
  • Customers, Woo Customer Info tab: Contact ID, Store code, WooCommerce Customer ID, and B2B.
  • WooCommerce Orders, Addresses tab: the address details retrieved for the order.
  • WooCommerce Orders, Import Fields tab: order-field values retrieved under the mapping.
  • WooCommerce Orders, Sales Order Number: the Acumatica sales order associated with an imported order.
  • Get Order Process Error Messages: errors generated during order retrieval.

WooCommerce Customer Mapping: Frequently Asked Questions

Can I link an existing WooCommerce customer manually?

Yes. On the Acumatica Customers screen, add a Woo Customer Info record and set the Contact ID, Store code, WooCommerce Customer ID, and B2B fields. Confirm that the ID belongs to the intended account before saving.

Why did synchronization create a new WooCommerce customer?

In the documented standard customer sync, a new WooCommerce customer is created when the program does not find a matching customer. Check the existing ID and contact details, and investigate the result before repeating the process. The manual does not provide every matching or tie-breaking condition.

Why does an exported order show a Guest customer?

The manual says an outbound order uses the customer ID in Woo Customer Info when the customer was exported beforehand. Without that corresponding ID, the order is created with the Guest customer. Check the customer export and linked ID for the relevant store.

Why can a customer sync fail?

The Biz-Tech Services WooCommerce Acumatica Integrator requires a corresponding contact for the documented standard sync. The manual says missing first name, last name, or email prevents retrieval of the customer from WooCommerce, and a missing contact produces an error; it does not give the exact error text.

Does a different shipping address require a different customer?

The documented address options let an order bring in shipping and billing address information separately from WooCommerce. The documentation does not establish a rule that a different shipping address requires a new customer. Compare the order and its configured override options.

Can I synchronize customers in a batch?

Yes. Export WooCommerce Customers supports processing customers individually or all at once and can be scheduled. Review contact and mapping data before enabling a recurring schedule.

What happens to existing customer links after a package update?

The manual says customer synchronization uses Woo Customer Info and instructs users to run Update Synchronized Customers after publishing a new package to transfer existing data from WooCommerce Info to Woo Customer Info. Verify the transferred information for the applicable store.

Work With Biz-Tech Services on WooCommerce Customer Mapping

A reliable customer mapping review starts with the store, contact, customer ID, and intended order addresses. For the broader import workflow, see "How to Import WooCommerce Orders into Acumatica"; for product mapping, see "How to Map WooCommerce Products to Acumatica Inventory Items."

To discuss the Biz-Tech Services Acumatica WooCommerce Integrator and your customer workflows, visit https://biz-techservices.com to contact Biz-Tech Services.

Watch video for details https://www.youtube.com/watch?v=N8bnQS5EKTw


How DocVision Recognizes Customers and Ship-To Addresses in Acumatica

DocVision recognizes customer and ship-to information in PDF documents through configured templates, with a Customer Cross-Reference that maps PDF customer values and locations to Acumatica customers and locations. The mapping should be reviewed before a sales order is generated.

This guide focuses on the customer and location mapping decisions behind that process. It also explains what the documented review screens show and where the DocVision guide leaves the recognition and duplicate-prevention rules unspecified.

What DocVision Customer Recognition Does

DocVision is an Acumatica enhancement for creating sales orders from PDFs. Its documentation describes per-customer PDF mapping and customer and ship-to recognition using pre-configured templates. A template connects fields in an imported document to Acumatica values; the Customer Cross-Reference maps PDF customer values and locations to Acumatica customers and locations.

The manual does not explain how DocVision selects a template for an incoming PDF or how it resolves ambiguous customer and location matches. Confirm those rules for your implementation rather than assuming that a name, address, or other field is sufficient on its own.

Customer and Ship-To Mapping at a Glance

Import a representative PDF in PDF Import Settings and create its template.

Review the automatically populated PDF FieldName, PDF Value, Target Object, and Source Field mappings.

Manually map the relevant PDF fields to the corresponding Acumatica values and activate the fields needed on the sales order.

When Cross Reference is selected, use the Customer Cross-Reference tab to map PDF customer values and locations to Acumatica customers and locations.

Review the imported document, its Template ID, customer, and mapped data before generating a sales order.

After generation, inspect the resulting order and trace it to the source document.

Configure a Template for Customer and Ship-To Data

On PDF Import Settings, press the Plus button to open a workspace where a PDF can be imported and a template created. The imported document is displayed on the right, with controls for changing pages and zooming. Use that view to compare source values with the mapping fields.

The system automatically sets PDF FieldName and PDF Value and automatically sets mappings between Target Object and Source Field in the Import Mappings tab. The guide says the PDF fields can then be mapped manually to corresponding Acumatica values. For sales order header fields, it specifies Sales Order > Advanced as the Target Object path.

The Active checkbox matters: the guide states that only fields marked Active are uploaded during sales order generation. Check the relevant customer and ship-to fields and their intended targets before relying on the generated order.

DocVision generate sales orders screen

Map Customer Values and Locations

When Cross Reference is selected, the Customer Cross-Reference tab appears. There, map the customer values and locations from the PDF to the intended Acumatica customers and locations. The guide does not name the cross-reference columns or explain the exact matching algorithm, so confirm the displayed fields in your installed version.

Review mappings against the source document and the intended customer account and location before processing orders. This is a practical review step: the documentation does not establish that DocVision automatically detects duplicate customers, prevents duplicate orders, or chooses among similar addresses.

Review the Imported Document Before Generating an Order

The Import Documents screen can display a previously imported PDF and its mappings when a document number is selected. The screen retains the Template ID. Its Documents tab displays the Template ID, document number, Order Type, and Customer. Compare those values and the mapped data with the PDF before proceeding.

The guide describes green as ready for sales order generation, red as an item-line issue with details in the Error Message field, and yellow as a warning such as an item that is not mapped correctly. It does not define those colors as a complete customer or ship-to validation test. A green indication alone should not replace review of the intended customer and location.

Validate Items is described for resolving item mappings already present in Inventory Cross Reference. The guide does not say that this button validates or repairs customer or location mappings.

Duplicate Prevention and Order Accuracy

Check the document number and existing records before generating another order if duplicate processing is a concern. The guide says the Generated checkbox is selected after a sales order is generated and the document number is visible on the Sales Order screen. These fields help with review and traceability, but the guide does not describe an automatic duplicate check or guarantee that it will block a second order.

After selecting Generate Sales Order from the three dots menu, compare the resulting order with the PDF, including the customer and ship-to information your workflow requires. The guide describes creation from mapped data but does not specify the complete set of fields written in every configuration. Investigate discrepancies before downstream processing.

Where to Check Your DocVision Customer Mapping

PDF Import Settings: the template created from the representative PDF.

PDF FieldName and PDF Value: the fields and values detected from the document.

Import Mappings: Target Object, Source Field, and Active status for required fields.

Customer Cross-Reference: the PDF customer and location values and their Acumatica mappings.

Import Documents: the selected document, displayed PDF, retained Template ID, and mappings.

Documents tab: Template ID, document number, Order Type, and Customer.

Error Message field: the documented location for details of a red item-line issue.

Generated checkbox and Sales Order screen: generation status and document number for traceability.

Import PDF Documents inquiry: document numbers, Template IDs, customer information, and generation dates.

DocVision Customer Mapping: Frequently Asked Questions

How does DocVision identify the customer and ship-to information?

The guide says DocVision identifies customer and ship-to information using pre-configured templates. It does not specify the recognition algorithm or the fields used to select a customer.

Where are PDF customers mapped to Acumatica customers?

When Cross Reference is selected in PDF Import Settings, the Customer Cross-Reference tab appears. It maps PDF customer values and locations to Acumatica customers and locations.

Why might a mapped field be missing from a generated order?

Check whether the mapping is Active. The guide states that only fields whose Active checkbox is selected are uploaded during sales order generation. Also review the mapping target and the source PDF.

Does Validate Items fix a customer mapping?

The guide describes Validate Items for PDF items that are already mapped in Inventory Cross Reference. It does not document customer or location validation through that button.

Does DocVision automatically prevent duplicate customers or orders?

The guide does not document an automatic duplicate-customer or duplicate-order control. Review existing records, the document number, and Generated status according to your company process.

Where can I trace a generated order back to its PDF?

The guide says the document number is visible on the Sales Order screen after generation. Import Documents displays the PDF and its mappings by document number, while the Import PDF Documents inquiry lists document and customer information.

Work With Biz-Tech Services on DocVision

Biz-Tech Services can help you review how DocVision templates and customer cross-references fit your PDF order workflow. Visit https://biz-techservices.com to discuss your requirements.


Privacy Preference Center