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.

Privacy Preference Center