Month: September 2026

How to Import EZCom Purchase Orders into Acumatica

How to Import EZCom Purchase Orders into Acumatica

Importing EZCom purchase orders into Acumatica starts on the Import Purchase Orders screen: retrieve orders for the required partner and period, review the returned grid, and import selected records or the full displayed set. The result is an Acumatica sales order created according to the trading partner settings, customer rules, warehouse defaults, and cross-references configured for the integration.

This guide explains the task from prerequisites through retrieval, validation, import, and follow-up. The Biz-Tech Services EZCom Acumatica Connector supports this controlled process through an intermediate server managed by Biz-Tech Services, so users can bring selected EZCom orders into Acumatica and then monitor the related inbound and outbound documents.

Before You Start: What Must Be Configured

Before retrieving an order, confirm the connection, defaults, and partner-level rules. The Biz-Tech Services Acumatica EZCom Connector uses the General Settings and Trading Partners screens to determine which data can be retrieved and how an imported order is created.

1. Install and publish the customization package through Customization Projects (SM204505).

2. On General Settings, supply the Account, API Key, and EZCom admin Login and Password when Modify API Connectivity is selected.

3. Use Test Credentials under Actions to verify the connection to the Acumatica-Biz-Tech server.

4. Retrieve partner records with Get Trading Partners, then select the relevant Partner Code.

5. Set the partner Order Type, eligible EZCom Status, Begin Order Date, Customer ID, and Warehouse ID as required.

6. Select the applicable order-status checkbox. The documentation states that the corresponding status must be selected for an order to be retrieved and imported.

7. Configure enabled cross-reference options and map each required EZCom item under Inventory Items.

If Get Order From All Partners is used on General Settings, its date-based default does not take effect until the checkbox is selected and Apply Order Date Update for Partners is run from Actions. For broader setup context, see the sibling articles EZCom EDI Acumatica Connector Configuration Checklist and How EZCom EDI Data Flows Through Acumatica ERP.

How to Import EZCom Purchase Orders into Acumatica, Step by Step

The Biz-Tech Services EZCom Acumatica Integration separates retrieval from import. This gives the user a chance to see the orders returned for the selected period before creating records in Acumatica.

Step 1: Open Import Purchase Orders

Open the Import Purchase Orders screen. The screen is designed to retrieve and import orders for the corresponding EZCom trading partner.

Step 2: Retrieve the available orders

Click Get Orders. A timer shows elapsed time while the connector retrieves orders from the EZCom partner. All orders for the selected period are returned and displayed together in the grid. If retrieval must be stopped, click the loading icon next to the timer to cancel the process.

Step 3: Review the returned order set

Confirm that the intended partner and period produced the expected records. An order must have a status enabled in the partner settings, and item mapping must be complete before import. The Inbound Purchase Orders screen is also available to display information related to an EZCom order for the corresponding partner.

Step 4: Import selected orders or the entire grid

Select the required rows and click Import, or click Import All to process every order currently displayed. The integration creates the sales order using the configured order type, customer selection logic, shipping address option, warehouse rule, and enabled cross-references.

Step 5: Check the created order and related records

Verify the customer, location, inventory items, warehouse, shipping method, and quantities against the source order and partner configuration. Later workflow actions can generate acknowledgements, routing requests, warehouse orders, shipment updates, and invoices; those actions are separate from the initial import.

Document Triggers: What Each Action Creates

The source describes a sequence of screens and process triggers rather than a single automatic chain. Use each action only when the related order is at the required stage.

1. Get Orders retrieves orders for the selected partner and period and places them in the Import Purchase Orders grid.

2. Import or Import All creates Acumatica sales orders from selected or all displayed EZCom orders.

3. Import Changed Purchase Orders retrieves and imports changed orders for the corresponding partner.

4. Send or Send All on Send Outbound PO Acks sends acknowledgement requests; the EZCom order becomes acknowledged and the Acumatica sales order status changes to Closed.

5. Send Routing Request submits the EZCom Order ID when the order is at shipment level and indicates that the product is ready for shipment.

6. Import Routing Response uses Carrier Code and Carrier Service to find a Ship Via cross-reference and update the shipment.

7. Import Warehouse Shipment brings item quantity and tracking number from EZCom into the shipment and updates shipped quantity and tracking number.

8. Prepare Invoice can export a shipment when Export Shipment During Prepare Invoice is enabled; otherwise the order appears on Send Outbound Shipments.

9. Release Invoice can export an invoice when the partner export option is enabled; otherwise the order appears on Send Outbound Invoices.

Mapping Rules That Decide What Appears on the Order

Partner settings control the resulting sales order. Order Type determines the default order type. Customer ID supplies the fallback Acumatica customer, while Override Ship Address Info from EZCom Order brings in the destination address from EZCom.

Country, ShipVia, and warehouse values can come from the Cross-Reference tab when their corresponding Use Cross Ref options are enabled and mappings exist. For warehouse mapping, the documentation says the Default Warehouse field must be empty for the cross-reference value to be used.

Every corresponding EZCom item must be mapped on the Inventory Items tab. The available search field choices depend on the cross-reference options selected. The manual illustrates UPC Code: the system searches by that code and associates the result with an Acumatica Inventory ID.

Customer Ship To setup changes customer selection. The integration searches for Trading Partner Ship To ID using the order Location Number, then looks for matching parent and child customer values and a Customer ID and Location CD mapping. If no Customer Ship To setup exists, it uses the customer configured in Partner Settings.

Validation and Common Exceptions

The strongest pre-import validation is configuration-based. Test credentials, confirm the partner and date settings, enable the intended order status, and verify item, customer, warehouse, country, and shipping mappings before clicking Import.

1. No expected orders in the grid: check the Partner Code, Begin Order Date or applied all-partner date, and the eligible EZCom Status checkbox.

2. Item mapping error during import: map the EZCom item on the Inventory Items tab to an Acumatica Inventory ID.

3. Unexpected warehouse: determine whether Warehouse ID is populated. The source says it must be blank when the cross-reference warehouse should win.

4. Unexpected customer or location: review Customer Ship To mappings, including Location Number, parent and child customer values, Customer ID, and Location CD.

5. Unexpected Ship Via on a shipment: review the Carrier Code and Carrier Service mappings used during Import Routing Response.

6. Long-running retrieval: monitor the timer; use the loading icon next to it if the retrieval should be cancelled.

The manual warns that an unmapped item produces an error, but it does not provide the exact error message, a complete validation catalog, or recovery instructions for every exception. Avoid relying on undocumented message text when training users or writing operating procedures.

Where to Check Your Work

The Biz-Tech Services Acumatica EZCom Integration provides several screens and fields for confirming the result after retrieval and import:

1. Import Purchase Orders grid - orders retrieved for the selected period.

2. Inbound Purchase Orders - information for EZCom orders by partner.

3. Trading Partners: Partner Code, Order Type, EZCom Status, and Begin Order Date.

4. Trading Partners: Customer ID and Override Ship Address Info from EZCom Order.

5. Trading Partners: Warehouse ID and enabled Cross-Reference Options.

6. Inventory Items tab - EZCom item lookup values and Acumatica Inventory ID mappings.

7. Customer Ship To tab - Location Number, parent and child customer, Customer ID, and Location CD mappings.

8. Import Changed Purchase Orders - changed orders retrieved for the partner.

9. Import Routing Response - shipment routing updates based on carrier mappings.

10. Import Warehouse Shipment - imported item quantities and tracking numbers.

11. Send Outbound PO Acks, Send Outbound Shipments, and Send Outbound Invoices - documents awaiting manual transmission when automatic triggers are not used.

How to Import EZCom Purchase Orders into Acumatica: Frequently Asked Questions

Why does an EZCom order not appear on Import Purchase Orders?

Check the selected partner, retrieval period, Begin Order Date, and EZCom Status. The corresponding order-status checkbox must be selected before the order can be retrieved and imported.

Should I use Import or Import All?

Use Import for selected rows. Use Import All when every order displayed in the current grid should be imported into Acumatica.

Why does an item fail during EZCom order import?

The source explicitly warns that unmapped items cause an error. Map the corresponding EZCom item under the Inventory Items tab and associate it with the correct Acumatica Inventory ID.

Which customer is used for the imported sales order?

The Biz-Tech Services EZCom Acumatica Integrator follows Customer Ship To setup when it exists. Without that setup, the integration uses the Customer ID configured in Partner Settings.

Why did the imported order use the default warehouse instead of a cross-reference?

The source says the Default Warehouse field must have no value for the system to take the cross-reference warehouse value. Also confirm that Use Cross Ref for warehouse is enabled and mapped.

Can I stop Get Orders after retrieval starts?

Yes. The documentation says to click the loading icon next to the elapsed-time timer to cancel the process.

Does importing an order automatically send every later EZCom document?

No. The documentation identifies separate screens and triggers for acknowledgements, routing, warehouse orders, shipments, invoices, and inventory availability. Some shipment and invoice exports can run during Acumatica processing when their partner options are enabled.

Work With the Biz-Tech Services EZCom Connector

A reliable EZCom purchase order import depends on three things: a tested connection, partner rules that match the intended workflow, and complete item, customer, shipping, and warehouse mappings. Retrieve first, review the grid, import deliberately, and then verify the created sales order and downstream document queues.

If your team needs help configuring, validating, or operating the Biz-Tech Services Acumatica EZCom Integrator, visit https://biz-techservices.com to work with Biz-Tech Services on an Acumatica integration grounded in your documented trading partner workflow.

---

by Gary

How to Import DSCO Orders into Acumatica

Importing DSCO orders into Acumatica is a two-stage task: retrieve orders for the configured period on the Import DSCO Orders screen, then process selected records to create either Sales Orders or SO Invoices. This guide focuses on that operating procedure, the settings that control document creation, and the checks to make when an order does not import.

The Biz-Tech Services DSCO Acumatica Connector lets an operator review retrieved records before choosing IMPORT or IMPORT ALL. You will learn how to configure the import target, select orders, understand the documented triggers, verify mappings, and trace common exceptions without repeating the broader order-to-cash overview covered in How DSCO Data Flows Through Acumatica Order-to-Cash Automation.

Before You Start: What Must Be Configured

The Biz-Tech Services Acumatica DSCO Connector depends on a published customization and a working DSCO Store connection. The source identifies the Customization Projects screen by form ID SM204505. On the DSCO Store General Settings tab, enter the Partner Code, Access Token, and Base URL, then use Test Credentials to test the application programming interface, or API, connection before retrieving orders.

1. Keep the order prerequisites tight and complete before the first production import:

2. Import DSCO Orders to: choose the Acumatica document type. The documented choices are Sales Order and SO Invoice.

3. Order Type: select the default order type that the integration will use for created orders.

4. DSCO Status: identify the DSCO order status eligible for import, and select the corresponding order-status checkbox. The manual says the checkbox must be selected for orders in that status to be retrieved and imported.

5. Begin Order Date: set the date used to filter retrieval. Review Last Imported Order Date, which records when the last order was imported.

6. Customer: choose the default customer that will be assigned to imported DSCO orders.

7. Cross-Reference options: select the entities that must be matched between DSCO and Acumatica. Only checked entities become available in the Cross-Reference tab drop-down.

8. Use Cross Ref for Warehouse: when selected, map each DSCO item warehouse to an Acumatica warehouse value on the Cross-Reference tab.

9. Inventory Items: choose the lookup basis used to associate DSCO items with Acumatica Inventory IDs. The manual illustrates SKU as one selection.

The documentation describes acknowledgments and outbound shipment and invoice settings, but those options do not replace the core order-import configuration. Set Order as Acknowledged decides whether a separate acknowledgment is necessary. Export Shipment During Prepare Invoice and Export Invoice During Release Invoice control later outbound actions.

How to Import DSCO Orders into Acumatica, Step by Step

The Biz-Tech Services DSCO Acumatica Integration separates retrieval from document creation. GET ORDERS fills the review grid for the selected period; IMPORT and IMPORT ALL process records from that grid into the configured Acumatica document type.

How do you retrieve DSCO orders for review?

Open the Import DSCO Orders screen and press GET ORDERS. A timer displays elapsed time while the request runs. The source states that the action retrieves and displays all orders for the selected period at once, subject to the DSCO Status and corresponding status-checkbox configuration.

How do you inspect an order before importing it?

Click the Order Number in the grid to open the corresponding order in a pop-up window. The manual says the most important information is shown on the DSCO Orders screen. Use this review point to confirm that the order belongs in the current batch and that its visible values are consistent with the configured customer, warehouse, and item rules.

How do you import selected DSCO orders?

Select the order or orders that should be processed and click IMPORT. To process every record currently in the grid, click IMPORT ALL. After IMPORT is pressed, successfully processed selected orders are filtered from the Import DSCO Orders screen. If the batch must be stopped while processing, click Cancel Processing.

How do you confirm which Acumatica document was created?

Open the DSCO Orders screen after import. The record shows its DSCO Order Status and, when applicable, the associated sales order number and invoice number. The result depends on Import DSCO Orders to: Sales Order creates a sales order path, while SO Invoice creates the invoice-oriented path described by the manual. The source does not document a separate purchase-order document being created in Acumatica.

How do you handle the acknowledgment after import?

If Set Order as Acknowledged is enabled, the manual says sending a separate acknowledgment is unnecessary and the Acknowledged Status in DSCO field on the Sales Orders screen should be Closed. If the checkbox is not selected, the imported order appears on Export DSCO PO Acknowledgement. Process it there; it should leave that screen, and Acknowledged Status in DSCO should become Closed.

Document Triggers: What Each Action Creates

These controls distinguish retrieval, Acumatica document creation, and later DSCO status updates:

1. GET ORDERS retrieves and displays DSCO orders for the selected period. It does not, by itself, document the creation of the configured Acumatica order or invoice.

2. IMPORT processes selected grid records and creates the document type selected in Import DSCO Orders to.

3. IMPORT ALL applies the same import processing to all records currently displayed in the grid.

4. Import DSCO Orders to = Sales Order directs imported DSCO orders into Acumatica sales orders, using the configured Order Type.

5. Import DSCO Orders to SO Invoice directs the imported records into Acumatica SO Invoices. The manual does not describe additional invoice field rules for this choice.

6. Prepare Invoice, with Export Shipment During Prepare Invoice selected, sends shipment information to DSCO and marks the order as shipment pending.

7. Release Invoice, with Export Invoice During Release Invoice selected, sends invoice information to DSCO and changes the DSCO order to Shipped.

The last two triggers occur after import and document processing. They explain how later shipment and invoice actions can update DSCO, but they should not be confused with GET ORDERS or IMPORT.

Mapping Rules That Decide What Appears on the Order

The default Customer setting is assigned to DSCO orders during import. Cross-Reference options determine which entities can be matched, and checked options become available for configuration on the Cross-Reference tab. When Use Cross Ref for Warehouse is enabled, the incoming DSCO warehouse value must map to an Acumatica warehouse value.

On Inventory Items, choose how the connector searches for an item and associates it with an Acumatica Inventory ID. The source gives SKU as its example lookup value. These item and warehouse relationships affect whether an order can be built with valid Acumatica values. The manual also warns that inaccurate or incomplete cross-references can prevent later API requests from updating order status and tracking numbers correctly.

The source does not provide a field-by-field transformation table for prices, taxes, freight, addresses, purchase-order numbers, or invoice lines. It also does not state precedence when a default value and an incoming value are both present. Those details should be confirmed in the implemented configuration rather than inferred from the manual.

Validation and Common Exceptions

Validate the connection first with Test Credentials, then validate the actual batch in the Import DSCO Orders grid. If processing fails, the affected row displays an error indicator. Hover over the red cross for additional information, and use TOOLS > Trace when more detail is needed.

1. No expected orders after GET ORDERS: review Begin Order Date, Last Imported Order Date, DSCO Status, and the corresponding status checkbox. The manual does not provide a specific message for an empty result.

2. Warehouse does not have value: this is the one exact import error documented. It occurs when warehouse cross-referencing is enabled but the DSCO warehouse value is not mapped to an Acumatica warehouse.

3. Item mapping failure: the manual warns that an error appears when item values are not mapped, but it does not supply the error text. Review the Inventory Items lookup choice and Inventory ID association.

4. Order remains on the processing grid with a red cross: hover over the indicator, then inspect TOOLS > Trace. Correct only the configuration or data supported by the displayed detail, and retry the appropriate order.

5. Unexpected document type: verify Import DSCO Orders to and Order Type before reprocessing. The source does not explain duplicate handling, reversal, or recovery after an unintended document is created.

6. Acknowledgment remains pending: verify Set Order as Acknowledged. If it is cleared, process the order on Export DSCO PO Acknowledgement and check that the record disappears and the Sales Orders field becomes Closed.

The manual does not provide a comprehensive error catalog, required-field matrix, duplicate-order rule, retry policy, or rollback procedure. Its validation guidance is limited to connection testing, the warehouse error, a general item-mapping warning, the row-level red cross, and TOOLS > Trace.

Where to Check Your Work

The Biz-Tech Services Acumatica DSCO Integration exposes the import result across the configuration, processing, and result screens. Check these documented locations:

1. DSCO Store - General Settings: Partner Code, Access Token, Base URL, and Test Credentials.

2. DSCO Store - Order Settings: Import DSCO Orders to, Order Type, DSCO Status, status checkbox, Begin Order Date, and Last Imported Order Date.

3. DSCO Store - Customer Information: default Customer, Cross-Reference options, and Use Cross Ref for Warehouse.

4. DSCO Store - Cross-Reference: selected entity mappings, especially DSCO-to-Acumatica warehouse values.

5. DSCO Store - Inventory Items: lookup selection and the association to Acumatica Inventory ID.

6. Import DSCO Orders: retrieved period, Order Number pop-up, selected rows, elapsed-time indicator, and records remaining after processing.

7. Import DSCO Orders error row: red cross details and TOOLS > Trace.

8. DSCO Orders: DSCO Order Status, sales order number, and invoice number.

9. Sales Orders: Acknowledged Status in DSCO when acknowledgment behavior applies.

10. Export DSCO PO Acknowledgement: orders waiting for manual acknowledgment when Set Order as Acknowledged is cleared.

How to Import DSCO Orders into Acumatica: Frequently Asked Questions

Why did GET ORDERS return no DSCO orders?

Check the selected period through Begin Order Date and the recorded Last Imported Order Date. Also confirm DSCO Status and its corresponding checkbox. The manual says the status checkbox must be selected for orders with that status to be retrieved and imported, but it does not document a no-results error message.

Why does an order show Warehouse does not have value?

Use Cross Ref for Warehouse is enabled, but the incoming DSCO warehouse does not have an Acumatica warehouse mapping. Add or correct that relationship on the Cross-Reference tab before retrying the order.

Why is a DSCO item not importing into Acumatica?

Review the Inventory Items cross-reference selection and confirm that the incoming item can be associated with an Acumatica Inventory ID. The source warns that an unmapped item produces an error but does not provide the exact message.

Can I import only selected DSCO orders?

Yes. Select the required rows and click IMPORT. Use IMPORT ALL only when every order currently displayed in the grid should be processed. The Biz-Tech Services DSCO Acumatica Integrator also provides Cancel Processing when an active import must be stopped.

Can DSCO orders create invoices instead of sales orders?

Yes. Import DSCO Orders to supports Sales Order and SO Invoice. Choose the required destination before processing. The documentation does not provide a separate mapping table or validation sequence for SO Invoice creation.

Does importing a DSCO order create an Acumatica purchase order?

The manual describes incoming DSCO orders becoming Sales Orders or SO Invoices. It calls the acknowledgment screen Export DSCO PO Acknowledgement, but it does not document the creation of a separate Acumatica purchase order. Do not treat the acknowledgment label as proof that an Acumatica purchase-order document is created.

Why is the acknowledgment still waiting after import?

When Set Order as Acknowledged is cleared, the imported order must be processed on Export DSCO PO Acknowledgement. After processing, it should disappear from that screen and Acknowledged Status in DSCO on Sales Orders should be Closed.

Where can I find more detail for a failed import?

Hover over the red cross on the failed order row to view additional information. Then open TOOLS > Trace for further detail. The source does not list all possible messages or prescribe a universal correction.

Work With the Biz-Tech Services DSCO Connector

A reliable DSCO order import starts with the correct target document, eligible status, date filter, customer default, and complete warehouse and item mappings. Retrieve first, inspect the grid, import deliberately, and verify the linked sales order or invoice on DSCO Orders.

If your team needs help configuring, validating, or troubleshooting the Biz-Tech Services Acumatica DSCO Integrator, visit https://biz-techservices.com to work with Biz-Tech Services on an Acumatica integration grounded in your documented DSCO workflow.

Check the video for mre details - https://www.youtube.com/watch?v=Hk296jscNtA

How to Import DSCO Orders into Acumatica

Importing DSCO orders into Acumatica is a two-stage task: retrieve orders for the configured period on the Import DSCO Orders screen, then process selected records to create either Sales Orders or SO Invoices. This guide focuses on that operating procedure, the settings that control document creation, and the checks to make when an order does not import.

The Biz-Tech Services DSCO Acumatica Connector lets an operator review retrieved records before choosing IMPORT or IMPORT ALL. You will learn how to configure the import target, select orders, understand the documented triggers, verify mappings, and trace common exceptions without repeating the broader order-to-cash overview covered in How DSCO Data Flows Through Acumatica Order-to-Cash Automation.

Before You Start: What Must Be Configured

The Biz-Tech Services Acumatica DSCO Connector depends on a published customization and a working DSCO Store connection. The source identifies the Customization Projects screen by form ID SM204505. On the DSCO Store General Settings tab, enter the Partner Code, Access Token, and Base URL, then use Test Credentials to test the application programming interface, or API, connection before retrieving orders.

1. Keep the order prerequisites tight and complete before the first production import:

2. Import DSCO Orders to: choose the Acumatica document type. The documented choices are Sales Order and SO Invoice.

3. Order Type: select the default order type that the integration will use for created orders.

4. DSCO Status: identify the DSCO order status eligible for import, and select the corresponding order-status checkbox. The manual says the checkbox must be selected for orders in that status to be retrieved and imported.

5. Begin Order Date: set the date used to filter retrieval. Review Last Imported Order Date, which records when the last order was imported.

6. Customer: choose the default customer that will be assigned to imported DSCO orders.

7. Cross-Reference options: select the entities that must be matched between DSCO and Acumatica. Only checked entities become available in the Cross-Reference tab drop-down.

8. Use Cross Ref for Warehouse: when selected, map each DSCO item warehouse to an Acumatica warehouse value on the Cross-Reference tab.

9. Inventory Items: choose the lookup basis used to associate DSCO items with Acumatica Inventory IDs. The manual illustrates SKU as one selection.

The documentation describes acknowledgments and outbound shipment and invoice settings, but those options do not replace the core order-import configuration. Set Order as Acknowledged decides whether a separate acknowledgment is necessary. Export Shipment During Prepare Invoice and Export Invoice During Release Invoice control later outbound actions.

How to Import DSCO Orders into Acumatica, Step by Step

The Biz-Tech Services DSCO Acumatica Integration separates retrieval from document creation. GET ORDERS fills the review grid for the selected period; IMPORT and IMPORT ALL process records from that grid into the configured Acumatica document type.

How do you retrieve DSCO orders for review?

Open the Import DSCO Orders screen and press GET ORDERS. A timer displays elapsed time while the request runs. The source states that the action retrieves and displays all orders for the selected period at once, subject to the DSCO Status and corresponding status-checkbox configuration.

How do you inspect an order before importing it?

Click the Order Number in the grid to open the corresponding order in a pop-up window. The manual says the most important information is shown on the DSCO Orders screen. Use this review point to confirm that the order belongs in the current batch and that its visible values are consistent with the configured customer, warehouse, and item rules.

How do you import selected DSCO orders?

Select the order or orders that should be processed and click IMPORT. To process every record currently in the grid, click IMPORT ALL. After IMPORT is pressed, successfully processed selected orders are filtered from the Import DSCO Orders screen. If the batch must be stopped while processing, click Cancel Processing.

How do you confirm which Acumatica document was created?

Open the DSCO Orders screen after import. The record shows its DSCO Order Status and, when applicable, the associated sales order number and invoice number. The result depends on Import DSCO Orders to: Sales Order creates a sales order path, while SO Invoice creates the invoice-oriented path described by the manual. The source does not document a separate purchase-order document being created in Acumatica.

How do you handle the acknowledgment after import?

If Set Order as Acknowledged is enabled, the manual says sending a separate acknowledgment is unnecessary and the Acknowledged Status in DSCO field on the Sales Orders screen should be Closed. If the checkbox is not selected, the imported order appears on Export DSCO PO Acknowledgement. Process it there; it should leave that screen, and Acknowledged Status in DSCO should become Closed.

Document Triggers: What Each Action Creates

These controls distinguish retrieval, Acumatica document creation, and later DSCO status updates:

1. GET ORDERS retrieves and displays DSCO orders for the selected period. It does not, by itself, document the creation of the configured Acumatica order or invoice.

2. IMPORT processes selected grid records and creates the document type selected in Import DSCO Orders to.

3. IMPORT ALL applies the same import processing to all records currently displayed in the grid.

4. Import DSCO Orders to = Sales Order directs imported DSCO orders into Acumatica sales orders, using the configured Order Type.

5. Import DSCO Orders to SO Invoice directs the imported records into Acumatica SO Invoices. The manual does not describe additional invoice field rules for this choice.

6. Prepare Invoice, with Export Shipment During Prepare Invoice selected, sends shipment information to DSCO and marks the order as shipment pending.

7. Release Invoice, with Export Invoice During Release Invoice selected, sends invoice information to DSCO and changes the DSCO order to Shipped.

The last two triggers occur after import and document processing. They explain how later shipment and invoice actions can update DSCO, but they should not be confused with GET ORDERS or IMPORT.

Mapping Rules That Decide What Appears on the Order

The default Customer setting is assigned to DSCO orders during import. Cross-Reference options determine which entities can be matched, and checked options become available for configuration on the Cross-Reference tab. When Use Cross Ref for Warehouse is enabled, the incoming DSCO warehouse value must map to an Acumatica warehouse value.

On Inventory Items, choose how the connector searches for an item and associates it with an Acumatica Inventory ID. The source gives SKU as its example lookup value. These item and warehouse relationships affect whether an order can be built with valid Acumatica values. The manual also warns that inaccurate or incomplete cross-references can prevent later API requests from updating order status and tracking numbers correctly.

The source does not provide a field-by-field transformation table for prices, taxes, freight, addresses, purchase-order numbers, or invoice lines. It also does not state precedence when a default value and an incoming value are both present. Those details should be confirmed in the implemented configuration rather than inferred from the manual.

Validation and Common Exceptions

Validate the connection first with Test Credentials, then validate the actual batch in the Import DSCO Orders grid. If processing fails, the affected row displays an error indicator. Hover over the red cross for additional information, and use TOOLS > Trace when more detail is needed.

1. No expected orders after GET ORDERS: review Begin Order Date, Last Imported Order Date, DSCO Status, and the corresponding status checkbox. The manual does not provide a specific message for an empty result.

2. Warehouse does not have value: this is the one exact import error documented. It occurs when warehouse cross-referencing is enabled but the DSCO warehouse value is not mapped to an Acumatica warehouse.

3. Item mapping failure: the manual warns that an error appears when item values are not mapped, but it does not supply the error text. Review the Inventory Items lookup choice and Inventory ID association.

4. Order remains on the processing grid with a red cross: hover over the indicator, then inspect TOOLS > Trace. Correct only the configuration or data supported by the displayed detail, and retry the appropriate order.

5. Unexpected document type: verify Import DSCO Orders to and Order Type before reprocessing. The source does not explain duplicate handling, reversal, or recovery after an unintended document is created.

6. Acknowledgment remains pending: verify Set Order as Acknowledged. If it is cleared, process the order on Export DSCO PO Acknowledgement and check that the record disappears and the Sales Orders field becomes Closed.

The manual does not provide a comprehensive error catalog, required-field matrix, duplicate-order rule, retry policy, or rollback procedure. Its validation guidance is limited to connection testing, the warehouse error, a general item-mapping warning, the row-level red cross, and TOOLS > Trace.

Where to Check Your Work

The Biz-Tech Services Acumatica DSCO Integration exposes the import result across the configuration, processing, and result screens. Check these documented locations:

1. DSCO Store - General Settings: Partner Code, Access Token, Base URL, and Test Credentials.

2. DSCO Store - Order Settings: Import DSCO Orders to, Order Type, DSCO Status, status checkbox, Begin Order Date, and Last Imported Order Date.

3. DSCO Store - Customer Information: default Customer, Cross-Reference options, and Use Cross Ref for Warehouse.

4. DSCO Store - Cross-Reference: selected entity mappings, especially DSCO-to-Acumatica warehouse values.

5. DSCO Store - Inventory Items: lookup selection and the association to Acumatica Inventory ID.

6. Import DSCO Orders: retrieved period, Order Number pop-up, selected rows, elapsed-time indicator, and records remaining after processing.

7. Import DSCO Orders error row: red cross details and TOOLS > Trace.

8. DSCO Orders: DSCO Order Status, sales order number, and invoice number.

9. Sales Orders: Acknowledged Status in DSCO when acknowledgment behavior applies.

10. Export DSCO PO Acknowledgement: orders waiting for manual acknowledgment when Set Order as Acknowledged is cleared.

How to Import DSCO Orders into Acumatica: Frequently Asked Questions

Why did GET ORDERS return no DSCO orders?

Check the selected period through Begin Order Date and the recorded Last Imported Order Date. Also confirm DSCO Status and its corresponding checkbox. The manual says the status checkbox must be selected for orders with that status to be retrieved and imported, but it does not document a no-results error message.

Why does an order show Warehouse does not have value?

Use Cross Ref for Warehouse is enabled, but the incoming DSCO warehouse does not have an Acumatica warehouse mapping. Add or correct that relationship on the Cross-Reference tab before retrying the order.

Why is a DSCO item not importing into Acumatica?

Review the Inventory Items cross-reference selection and confirm that the incoming item can be associated with an Acumatica Inventory ID. The source warns that an unmapped item produces an error but does not provide the exact message.

Can I import only selected DSCO orders?

Yes. Select the required rows and click IMPORT. Use IMPORT ALL only when every order currently displayed in the grid should be processed. The Biz-Tech Services DSCO Acumatica Integrator also provides Cancel Processing when an active import must be stopped.

Can DSCO orders create invoices instead of sales orders?

Yes. Import DSCO Orders to supports Sales Order and SO Invoice. Choose the required destination before processing. The documentation does not provide a separate mapping table or validation sequence for SO Invoice creation.

Does importing a DSCO order create an Acumatica purchase order?

The manual describes incoming DSCO orders becoming Sales Orders or SO Invoices. It calls the acknowledgment screen Export DSCO PO Acknowledgement, but it does not document the creation of a separate Acumatica purchase order. Do not treat the acknowledgment label as proof that an Acumatica purchase-order document is created.

Why is the acknowledgment still waiting after import?

When Set Order as Acknowledged is cleared, the imported order must be processed on Export DSCO PO Acknowledgement. After processing, it should disappear from that screen and Acknowledged Status in DSCO on Sales Orders should be Closed.

Where can I find more detail for a failed import?

Hover over the red cross on the failed order row to view additional information. Then open TOOLS > Trace for further detail. The source does not list all possible messages or prescribe a universal correction.

Work With the Biz-Tech Services DSCO Connector

A reliable DSCO order import starts with the correct target document, eligible status, date filter, customer default, and complete warehouse and item mappings. Retrieve first, inspect the grid, import deliberately, and verify the linked sales order or invoice on DSCO Orders.

If your team needs help configuring, validating, or troubleshooting the Biz-Tech Services Acumatica DSCO Integrator, visit https://biz-techservices.com to work with Biz-Tech Services on an Acumatica integration grounded in your documented DSCO workflow.

Check the video for mre details - https://www.youtube.com/watch?v=Hk296jscNtA

---

by Gary

How to Send Acumatica Orders to ShipStation

Sending ERP orders to ShipStation starts with an ERP sales order, a connected store configured for outbound processing, and either the Create Orders in ShipStation process or an action on the Sales Orders screen. This guide explains the documented setup, order-creation actions, mapping controls, validation points, and exceptions so you can move sales orders into ShipStation and confirm the result.

The Biz-Tech Services ShipStation Acumatica Connector supports two documented outbound workflows: creating an order in ShipStation before bringing its shipment back to Acumatica, or creating both the ShipStation order and shipment when an Acumatica shipment is confirmed. The focus here is the order-creation task; the broader two-way record movement is covered in the sibling article, How ShipStation Data Flows Between Shipping and Acumatica ERP.

Before You Start: What Must Be Configured

Before an order can be sent, the Biz-Tech Services Acumatica ShipStation Connector needs a published customization package, working ShipStation credentials, the correct data direction, and store-specific outbound choices. Keep these prerequisites tight so a failed export can be traced to a setting instead of to an undefined process.

1. Install and publish the connector customization package through Customization Projects (SM204505).

2. On the ShipStation Store screen, enter the Consumer Key, Consumer Secret, and Base URL in Connection Settings, then use Test Credentials to verify API connectivity.

3. Use Get Stores on the General Info tab, identify the applicable connected store, and select the store used by the integration.

4. Set Integration Option to Acumatica to ShipStation. The Create Orders in ShipStation screen is not documented for the reverse direction.

5. Choose the Process Flow that matches the intended workflow: Shipment in ShipStation or Shipment in Acumatica.

6. Load the available carrier codes, packages, and platform warehouses on their respective tabs. Select the package that should be used for the order.

The documentation says the General Info tab remains consistent between integration directions, while the other tabs change with the selected direction. It does not provide screen IDs for ShipStation Store, Create Orders in ShipStation, Sales Orders, or Shipments, so this article does not assign any.

Send Acumatica Orders to ShipStation, Step by Step

The Biz-Tech Services ShipStation Acumatica Integration provides a batch path and a single-order path for the Shipment in ShipStation flow, plus a shipment-confirmation path when both records should be created together.

Step 1: Confirm the outbound direction and process flow

Open the applicable connector configuration and confirm that Integration Option is Acumatica to ShipStation. For the dedicated Create Orders in ShipStation screen, Process Flow must be Shipment in ShipStation. This combination determines whether eligible ERP orders appear for export and whether the later shipment is expected to originate in ShipStation.

Step 2: Load and select outbound reference values

Open the Carriers and Services, Packages, and ShipStation Warehouses tabs. Use the relevant retrieval button on each tab; for example, Get Carriers retrieves carrier codes and Get Packages retrieves available packages from the platform. Select the package that applies to the order. The manual says the warehouse tab follows the same logic, but it does not describe a line-by-line mapping rule for these outbound values.

Step 3: Create orders in a batch

Open Create Orders in ShipStation. The screen displays ERP orders that can be exported and created on the platform. Choose the configured Store Code and corresponding ShipStation Store ID, select the orders to process, and run the export. The documentation states that the selected store identifiers determine where the ERP orders are created.

Step 4: Create one ShipStation order from Sales Orders

For a single record, open the ERP sales order. In the Actions menu, open the connector option and click Create ShipStation Order. This is the documented alternative to the batch processing screen.

Step 5: Confirm that ShipStation returned its order identifier

After a successful export, review the ShipStation Order ID field on the Sales Orders screen. The workflow documentation states that exporting the order generates the order on the platform and places that identifier on the ERP sales order.

Step 6: Complete the selected shipment workflow

If Process Flow is Shipment in ShipStation, create the shipment there and bring it back through Import Shipment from ShipStation or the Get ShipStation Shipments action on Sales Orders. The imported shipment number and tracking number are added to the corresponding ERP order, and its status is updated to Prepare Invoice.

If Process Flow is Shipment in Acumatica, first create the sales order and shipment in Acumatica. On the Shipping tab of the Shipments screen, manually complete the ShipStation Information option, then confirm the shipment. The confirmation creates both the destination order and its shipment. The returned Store Code, ShipStation Store ID, ShipStation Order ID, and ShipStation Order Number appear in ShipStation Information, while tracking information appears on the Packages tab.

Document Triggers: What Each Action Creates

1. Create Orders in ShipStation: exports displayed ERP orders to the configured connected store and creates destination orders.

2. Create ShipStation Order on Sales Orders: creates the destination order for the current ERP sales order.

3. Import ShipStation Shipment: retrieves shipment information for ERP orders already exported to ShipStation; it adds shipment and tracking details to the corresponding order and moves the ERP order to Prepare Invoice.

4. Get ShipStation Shipments on Sales Orders: performs the documented shipment-import process for the current order.

5. Confirm Shipment with Process Flow set to Shipment in Acumatica: creates both the order and shipment on the platform after the required ShipStation Information is completed on the ERP shipment.

The source documents triggers for sales orders and shipments only. It does not describe an action that exports an Acumatica purchase order, creates a purchase order on the platform, creates an Acumatica invoice during order export, or sends an invoice to ShipStation. Prepare Invoice is an ERP order status reached after shipment information returns; the manual does not claim that the import creates the invoice.

Mapping Rules That Decide What Appears on the Order

Store and outbound setup values are the documented controls that determine where the order goes and which shipping references are available. Store Code and ShipStation Store ID associate an export with the intended connected store. The Carriers and Services, Packages, and ShipStation Warehouses tabs retrieve available values from ShipStation, and the package selection identifies the package used for the order.

The integration direction and Process Flow are also mapping decisions in practice because they decide which screens and actions are valid. Acumatica to ShipStation with Shipment in ShipStation exposes the order-export and shipment-return sequence. Acumatica to ShipStation with Shipment in Acumatica uses the ERP shipment confirmation as the creation event.

For the confirm-shipment path, the user manually fills the ShipStation Information option on the Shipping tab before confirmation. Afterward, Store Code, ShipStation Store ID, ShipStation Order ID, and ShipStation Order Number are populated there, and tracking information is populated on Packages. The source does not specify field-by-field transformations for customer, address, line, price, discount, tax, carrier, service, package, or warehouse data on outbound orders. Those mappings should therefore be validated in the configured environment rather than inferred from the inbound options documented elsewhere.

Validation and Common Exceptions

1. Credential validation: use Test Credentials after entering the Consumer Key, Consumer Secret, and Base URL. If the test does not connect, review those values before testing order export.

2. Direction mismatch: Create Orders in ShipStation requires Integration Option to be Acumatica to ShipStation. A store set to ShipStation to Acumatica is intended for the import screens.

3. Process-flow mismatch: the dedicated order-export and shipment-import screens require Shipment in ShipStation. Use the shipment-confirmation workflow for Shipment in Acumatica.

4. Missing reference data: retrieve carriers, packages, and warehouses from the platform and confirm the required package is selected before processing.

5. No returned order ID: if ShipStation Order ID is blank after processing, the documented success marker is absent. Recheck credentials, store selection, direction, and process flow before retrying.

6. No shipment or tracking data: in the Shipment in ShipStation flow, a shipment must first exist on the platform and then be imported. The source does not say that order export alone produces tracking information.

7. Incomplete confirm-shipment setup: in the Shipment in Acumatica flow, ShipStation Information on the Shipping tab must be filled before Confirm Shipment.

The manual mentions an error when an inbound import screen is used with an incorrectly configured store, but it does not quote the exact message. It provides no named outbound error messages, validation codes, retry behavior, duplicate-order rules, or exception log. Troubleshooting should rely on the documented settings and returned identifiers without inventing message text.

Where to Check Your Work

The Biz-Tech Services Acumatica ShipStation Integration leaves several concrete checkpoints across configuration, sales order, shipment, and inquiry screens.

1. Customization Projects (SM204505): confirm that the integration package is present and published.

2. ShipStation Store - Connection Settings: review Consumer Key, Consumer Secret, Base URL, and the result of Test Credentials.

3. ShipStation Store - General Info: confirm the intended store was retrieved and selected.

4. ShipStation Store - Integration Option: verify Acumatica to ShipStation.

5. ShipStation Store - Process Flow: verify Shipment in ShipStation or Shipment in Acumatica matches the workflow being used.

6. Carriers and Services, Packages, and ShipStation Warehouses: confirm the reference lists were retrieved and the package was selected.

7. Create Orders in ShipStation: confirm the intended ERP orders appear under the correct Store Code and ShipStation Store ID.

8. Sales Orders: check ShipStation Order ID after export and use the ShipStation actions for single-order processing.

9. Import Shipment from ShipStation: confirm that the already-exported order is available after a shipment is created on the platform.

10. Shipments - Shipping tab: review Store Code, ShipStation Store ID, ShipStation Order ID, and ShipStation Order Number in ShipStation Information.

11. Shipments - Packages tab: verify that tracking information was populated.

12. ShipStation Orders and ShipStation Shipments: use these Generic Inquiries to review initial order and shipment information recorded in Acumatica.

Send Acumatica Orders to ShipStation: Frequently Asked Questions

Which Acumatica document can I send to ShipStation?

The source specifically documents ERP sales orders. It does not document exporting purchase orders or invoices to ShipStation, so those document types should not be assumed to be supported by this workflow.

Can I send one order without running a batch?

Yes. From the Sales Orders screen, use the Actions menu, open the connector option, and click Create ShipStation Order. The Create Orders in ShipStation screen is the documented batch-oriented alternative.

Why does my order not appear on Create Orders in ShipStation?

Verify that the store uses Acumatica to ShipStation and that Process Flow is Shipment in ShipStation. Also confirm credentials, the selected store, and the Store Code and ShipStation Store ID. The manual does not provide additional eligibility rules or an exact error message for a missing order.

How do I know that the ShipStation order was created?

Check the ShipStation Order ID field on the Acumatica Sales Orders screen. The documented workflow says this value is displayed when the order is exported and generated in ShipStation.

Why is tracking information missing after I export the order?

Order export and shipment import are separate steps in the Shipment in ShipStation flow. Create the shipment on the platform, then use Import Shipment from ShipStation or Get ShipStation Shipments. The shipment number and tracking number are added only after that import.

Can Acumatica create the ShipStation shipment at the same time as the order?

Yes, through the documented Shipment in Acumatica workflow. Create the Acumatica sales order and shipment, complete ShipStation Information on the Shipping tab, and confirm the shipment. The Biz-Tech Services Acumatica ShipStation Integrator then creates both records in ShipStation during confirmation.

Does importing a ShipStation shipment create an invoice?

The documentation says the ERP order status changes to Prepare Invoice after the shipment is imported. It does not state that the import action creates an invoice.

Where can I review the resulting records?

Review the Sales Orders and Shipments screens for returned identifiers and tracking information. The order and shipment Generic Inquiries display initial information about the integrated order and shipment records.

Work With the Biz-Tech Services ShipStation Connector

A reliable outbound workflow depends on the correct store direction, Process Flow, retrieved shipping references, and clear confirmation checks. The documentation supports both batch and single-order creation, followed either by shipment import or by creation of the destination order and shipment during ERP shipment confirmation.

If your team needs help configuring, validating, or troubleshooting this workflow, the Biz-Tech Services ShipStation Acumatica Integrator can help align the documented settings with your Acumatica process. Visit https://biz-techservices.com to learn more and contact Biz-Tech Services.

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

---

by Gary

How to Sync Orders Between ShipHero and Acumatica

How to Sync Orders Between ShipHero and Acumatica

ShipHero and Acumatica synchronize orders through processing screens that retrieve or export eligible records, then create the configured document in the destination system. This guide shows how to import ShipHero orders as sales orders or invoices, export open ERP sales orders and purchase orders, bring purchase receipts back, and verify the resulting records.

The Biz-Tech Services ShipHero Acumatica Connector supports two store-level integration directions, and that choice determines which tabs and workflows are available. The steps below concentrate on document triggers, mapping rules, validation, and exceptions. Broader movement of items, vendors, locations, shipments, transfers, and returns is covered in the sibling article, How ShipHero Data Flows Between WMS and Acumatica ERP.

Before You Start: What Must Be Configured

Before processing orders, publish the ShipHero customization package through the Customization Projects screen (SM204505), create the ShipHero Store record, enter the ShipHero username, password, and Base URL, and use Test Credentials. The Biz-Tech Services Acumatica ShipHero Connector depends on a valid store connection and an Integration Option that matches the intended direction.

1. Choose ShipHero to Acumatica when orders originate in ShipHero and must be imported.

2. Choose Acumatica to ShipHero when orders originate in the ERP system, are exported for fulfillment, and later return as shipments.

3. For inbound orders, set Import Ship Hero Orders To to Sales Order or Invoice and select the Order Type used in Acumatica.

4. Set Last Imported Order Date to control the date from which the first order should be imported.

5. Select the relevant store in Stores to get. If its Customer field is blank, customer handling follows the Customer Information setup.

6. Enable and complete Ship Via Cross Reference and Warehouse Cross Reference when those mappings are required.

7. Decide whether freight and tax should be imported, and complete the related tax fields before processing live orders.

8. For outbound sales orders, activate every eligible order type in the Order Types To Export grid.

How to Sync Orders Between ShipHero and Acumatica, Step by Step

The Biz-Tech Services ShipHero Acumatica Integration uses separate processing actions for inbound and outbound documents. Follow the path that matches the ShipHero Store Integration Option.

Step 1: Retrieve an order from ShipHero

Open Import Ship Hero Orders, select the Ship Hero Store Code, and choose Get Orders. This action retrieves available orders from ShipHero and adds them to the Ship Hero Order screen. Retrieval does not yet create the Acumatica destination document.

Step 2: Import the retrieved order into Acumatica

Select the retrieved record and choose Import. The integration creates the destination document according to the ShipHero Store setup: either a Sales Order or an Invoice, using the configured Order Type. Customer, address, freight, tax, Ship Via, warehouse, and item behavior are governed by the mappings and options described below.

Step 3: Export an Acumatica sales order to ShipHero

Open Export Ship Hero Order and select an eligible order. Only ERP orders with Open status appear, and the order type must be active for the selected store. Choose Export to create the order in ShipHero.

Step 4: Export an open purchase order to ShipHero

Open Export Purchase Orders to Ship Hero. The screen displays purchase orders with Open status. Select the purchase orders to send and use Export to Ship Hero. The documentation states that this screen requires no special setup beyond the connected environment.

Step 5: Retrieve and import the related purchase receipt

After an exported purchase order has a receipt in ShipHero, open Import Receipts from Ship Hero and choose Get Receipts. The screen displays receipts that need import. Choose Import to create the receipt for the purchase order in Acumatica. It is released automatically only when the store option Release PO Receipt During Import Process is selected; otherwise it remains unreleased.

Document Triggers: What Each Action Creates

1. Get Orders retrieves available ShipHero orders and places them on the Ship Hero Order screen; it does not create an Acumatica sales document by itself.

2. Import on Import Ship Hero Orders creates the configured Sales Order or Invoice in the ERP system.

3. Export on Export Ship Hero Order creates an order in ShipHero from an eligible open source order.

4. Export to Ship Hero on the purchase-order processing screen creates a ShipHero purchase order from an open Acumatica purchase order.

5. Get Receipts retrieves ShipHero receipts and displays those awaiting import.

6. Import on Import Receipts from Ship Hero creates an Acumatica receipt for the related purchase order and may release it according to store setup.

7. Shipment processing is separate. Get Shipments retrieves ShipHero shipments, while Import brings the shipment into Acumatica and confirms it. The source also documents shipment webhooks that can retrieve and automatically import shipment data, match it to the corresponding sales order, and process it under the selected webhook branch.

Mapping Rules That Decide What Appears on the Order

The order result is controlled by the ShipHero Store rather than by a single processing-screen action. Review these rules before diagnosing a document that imported with unexpected values.

1. Document type: Import Ship Hero Orders To selects Sales Order or Invoice; Order Type supplies the destination document type.

2. Customer: with Import Customer selected, ShipHero customer information creates a new customer using the selected Customer Class. Without it, the order uses the default Customer.

3. Addresses: Override Ship Address Information and Override Bill Address Information control whether order address data replaces the default address information.

4. Freight: Import Freight determines whether the ShipHero order freight is included.

5. Tax: Import Tax enables ShipHero order tax import. Customer Tax Zone, Tax ID, and Taxable Category provide the documented tax setup values.

6. Ship Via: when Use Cross Ref for Ship Via is selected, the Ship Via Cross Reference tab maps ShipHero and Acumatica values.

7. Warehouse: Warehouse Cross Reference assigns the mapped warehouse to the imported sales order and is also used during item synchronization.

8. Missing items: with Import Item selected, a missing item can be created using the configured imported item type, item class, unit of measure, and warehouse ID. Without it, the integration uses Replace Missing Products and the configured Warehouse ID rather than creating a new item.

9. Packaging: when Automatic Packaging is not selected, Default Box ID becomes available. The documentation instructs users to select the default box and then select Automatic Packaging to use that package with the order.

Validation and Common Exceptions

Validate eligibility and setup before treating an empty grid as a connection failure.

1. An outbound sales order does not appear unless its status is Open and its order type is active in Order Types To Export for the selected store.

2. An outbound purchase order does not appear unless its status is Open.

3. An inbound order can use the wrong warehouse when Warehouse Cross Reference is incomplete or does not match the incoming value.

4. A missing product becomes a newly created item only when Import Item is selected; otherwise the documented replacement-item behavior applies.

5. A receipt remains unreleased when Release PO Receipt During Import Process is not selected.

6. A webhook will not work if Webhook Name and Webhook Type do not match, if Branch for Webhooks is blank, or if the same URL has already been registered.

7. The document does not provide an error-message catalog for failed order import, export, invoice creation, or purchase-order processing. Use the eligibility rules, store options, cross-references, and displayed source records as the documented diagnostic path.

For webhook-based shipment validation, first enable Use Webhook in the ShipHero Store header so the Webhook Settings tab becomes available. On the Webhooks screen, select a Webhook Name that exactly matches Webhook Type in the store. Generate the URL, place it in Webhook Settings, and choose Create Webhook to register it for POST requests. The same URL can be created for only one webhook and set only once. Select Branch for Webhooks because incoming shipments, purchase order receipts, transfers, and returns are processed under that branch. The webhook grid then shows Webhook Type, Webhook URL, Registered, and Enabled. Registered indicates that ShipHero accepted the registration; Enabled indicates that the event is active. Create Webhook registers the URL, Enable Webhook starts real-time synchronization, and Disable Webhook stops incoming events while preserving the configuration. These fields help distinguish a registration problem from a disabled event or a document-mapping issue.

Where to Check Your Work

The Biz-Tech Services Acumatica ShipHero Integration keeps source and processing details visible across its dedicated screens. Check the following places after each action:

1. Ship Hero Order header: Order ID, Store Code, Acumatica order status, ShipHero order number, and ShipHero order status.

2. Ship Hero Order financial area: the financial portion of the imported source order.

3. Ship Hero Order Details tab: ordered products.

4. Ship Hero Order Addresses tab: customer address information.

5. Ship Hero Order Shipments tab: shipment records and the linked shipment ID.

6. Ship Hero Store: Last Import Date and Last Imported Order Date.

7. Export Ship Hero Order: confirm the Acumatica order is Open and visible for the selected store.

8. Ship Hero Purchase Order inquiry: synchronized purchase-order data and the Update Order action for changes made in ShipHero.

9. Import Receipts from Ship Hero: receipts retrieved by Get Receipts and awaiting Import.

10. Ship Hero Shipment: package, label, and shipment information, plus the Processed checkbox after processing.

How to Sync Orders Between ShipHero and Acumatica: Frequently Asked Questions

Can a ShipHero order create an Acumatica invoice instead of a sales order?

Yes. The Biz-Tech Services ShipHero Acumatica Integrator provides Sales Order and Invoice choices in Import Ship Hero Orders To. Order Type supplies the Acumatica document type.

Why is my open Acumatica sales order missing from the export screen?

The order must be Open, and its order type must be active in the selected store's Order Types To Export grid.

Why did Get Orders not create a sales order in Acumatica?

Get Orders only adds the record to Ship Hero Order. Run Import to create the configured Acumatica Sales Order or Invoice.

Why did the imported order use a replacement product?

Without Import Item, a missing item uses Replace Missing Products and the configured Warehouse ID. Configure Import Item when new item creation is intended.

Why was the purchase receipt not released?

Check Release PO Receipt During Import Process. When it is unselected, receipts import as unreleased. For a partial receipt, the source states that the last imported receipt is released.

Can order and shipment updates run through webhooks?

Shipment webhooks can import shipment data and match it to the corresponding sales order. The source does not document a general order-created webhook configuration, so not every order action should be assumed to be webhook-driven.

How can I verify a purchase order changed in ShipHero?

In Ship Hero Purchase Order, Update Order brings ShipHero changes to the synchronized purchase order back to Acumatica.

Work With the Biz-Tech Services ShipHero

Use the correct direction, eligible statuses, active order types, and complete mapping rules. Treat retrieval and creation as separate steps, then verify the ShipHero records.

If your team needs help configuring, testing, or troubleshooting the Biz-Tech Services Acumatica ShipHero Integrator, visit https://biz-techservices.com to work with Biz-Tech Services.

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

---

by Gary

How to Import Magento Orders into Acumatica

How to Import Magento Orders into Acumatica

To import Magento orders into Acumatica, retrieve eligible orders on the Import Magento Orders screen, review the staged order records, and use Import, Import All, or the individual order action to create the corresponding Acumatica sales order. This guide explains the settings that control that task, the documented actions, the mappings that shape the result, and the checks to make when an order does not import as expected.

The Biz-Tech Services Magento Acumatica Connector supports a controlled order-import process rather than a blind transfer. If you need the broader inbound and outbound sequence, see the sibling article How Magento Data Flows into Acumatica ERP. Here, the focus stays on the operator workflow for Magento orders and on what the product documentation actually confirms about sales orders, payments, customers, taxes, discounts, shipping, and item handling.

Before You Start: What Must Be Configured

The Biz-Tech Services Acumatica Magento Connector depends on the Magento Credentials and Magento Store configuration before an operator retrieves an order. The customization project must be installed and published through Customization Projects (SM204505), and the connector must run under one of the documented licenses: PCSR, PERP, or SAAS.

1. On Magento Credentials, identify the store with Store Code, add a Description if needed, and use Default Store when the record should be the default.

2. Enter Username, Password, and Base URL on the Connection Settings tab, then use Test Credentials to test the application programming interface (API) connection.

3. On Magento Store, choose the entities in Get Magento and set Import Magento Orders to. The manual names this destination setting but does not list its available values.

4. Set Order Type, Begin Order Date, and the default Warehouse ID used on imported orders. Last Imported Order Date is maintained as the date of the last import.

5. Decide whether Import Customer and Import Item are enabled. If the connector may create customers or items, set Customer Class, Import Item Type, Item Class, Unit of Measure (UOM), and the other documented defaults.

6. Configure payment, tax, freight, discount, address, shipping, and cross-reference options before testing a production order.

7. Add an email address on the Order Settings tab if Send Email Notifications for Errors will be used. The manual says failed-order notices go to that address.

How to Import Magento Orders into Acumatica, Step by Step

The Biz-Tech Services Magento Acumatica Integration separates retrieval from import, giving the operator a staged list to review before Acumatica creates a sales order.

Step 1: Retrieve eligible Magento orders

Open the Import Magento Orders screen and click Get Orders. A timer shows elapsed time while the retrieval runs. The manual says the processing page shows Magento orders with Partially Shipped, on hold, Pending, and Processing statuses. If necessary, click the loading icon next to the timer to cancel the retrieval process.

Step 2: Review the retrieved order list

Use the grid as a staging point. Each retrieved order number is a hyperlink to its Magento Orders record. Open that record before import when you need to inspect Document Details, Addresses, credit card payment information, or the order-level values used for validation.

Step 3: Inspect the individual Magento Orders record

Confirm the Magento Order ID, Magento order status, payment method, Ship Via, total line amount, discount total, shipping total, total tax, and total. The Sales Order Number field is populated if the order has been imported, while Invoice Number is displayed if the order is invoiced. The Refund Info tab appears when an order has been refunded.

Step 4: Import selected orders or the whole grid

Return to Import Magento Orders. Select the orders you intend to process and click Import, or click Import All to process every order displayed in the grid. The documentation does not specify row-level validation messages, retry behavior, or whether Import All continues after one order fails, so confirm results for every processed order.

Step 5: Import one order from its order record

For a single staged order, open the Magento Orders screen and choose Import Order from the Actions workspace. A confirmation popup asks whether you want to create a Sales Order for that Magento order in Acumatica. Confirm only after the order details and mappings have been reviewed.

Step 6: Refresh and record the result

After import, verify that Sales Order Number is present on the Magento Orders record. Use Refresh Order when you need Acumatica to update the stored Magento status to match the store. This status refresh is different from creating the Acumatica sales order.

Document Triggers: What Each Action Creates

The manual documents several actions, but only one order action explicitly confirms document creation. Keeping retrieval, creation, status refresh, and later invoice activity separate prevents an operator from expecting the wrong result.

1. Get Orders retrieves qualifying Magento orders and displays them on Import Magento Orders. It does not state that an Acumatica order is created at retrieval time.

2. Import processes selected rows. Import All processes all rows displayed in the grid.

3. Import Order on an individual Magento Orders record opens a confirmation popup that explicitly asks whether to create a Sales Order in Acumatica.

4. Receive Orders retrieves an individual order when the Magento store code and order ID are supplied.

5. Refresh Order updates the Magento order status stored in Acumatica.

6. Sales Order Number identifies the imported sales order. Invoice Number is shown if the order is invoiced, but the manual does not say that initial order import creates an invoice.

Mapping Rules That Decide What Appears on the Order

Magento Store settings provide the documented rules and defaults that shape the imported record. Review them before troubleshooting the result.

1. Order Type sets the default type of order created by the integration.

2. Warehouse ID supplies the default warehouse for orders imported from Magento.

3. Cross-Reference Options chooses entities to match between Magento and Acumatica. In the Cross-reference area, Field selects the entity, while Magento Value/Ship Via records the matching Magento and Acumatica values.

4. Import Customer can create a new Acumatica customer from Magento customer information. Customer Class is the default for a new customer created by the integration.

5. Override Ship Address Information and Override Bill Address Information bring the documented shipping and billing addresses from Magento.

6. Tax ID is the default tax identifier on orders. Customer Tax Zone, Taxable Category, and Is Freight Included In Magento control the documented tax context.

7. Payment Method and Payment Type govern the imported payment. Skip Magento Payment imports the order without payment, while Release Payment during Order Import releases the payment during import.

8. Use Credit Card Payment exposes the CC Payment Mapping tab for mapping Magento credit card payment methods to Acumatica.

9. Calculate Discount On Order Lines places discounts in Discount Amount and Discount Code on sales order lines; otherwise, the documentation says the discount is calculated for the order and shown in the Discount section.

10. The Magento product stock-keeping unit (SKU) is used to find the Acumatica Inventory CD. Import Item can create a missing item; Replace Missing Products can substitute a selected item when Import Item is disabled.

Validation and Common Exceptions

Validation should begin with what the manual makes observable: connection testing, eligible Magento statuses, item lookup, configured defaults, and order-level totals. The source includes one explicit item error and two Magento quantity checks, but it does not provide a comprehensive error catalog.

A Magento order is not listed after Get Orders

Check the Begin Order Date and confirm that the Magento status is Partially Shipped, on hold, Pending, or Processing. Test the credentials and connection. The manual does not describe other filters, paging limits, or a message for an excluded order.

An order contains an item that Acumatica cannot find

The connector searches Inventory CD using the Magento Product SKU. If Import Item is disabled and no matching item exists, the source shows the message "The item {0} does not exist in the system." The manual prints this message with a missing closing quotation mark. Configure item creation or Replace Missing Products before retrying.

An imported customer or address is not what you expected

Review Import Customer, Customer Class, Override Ship Address Information, and Override Bill Address Information. These settings determine whether a customer may be created and whether Magento address information overrides the order addresses.

Payment, tax, shipping, or discount values need review

Compare Payment Method, Payment Type, Skip Magento Payment, Release Payment during Order Import, Tax ID, Customer Tax Zone, Taxable Category, freight treatment, Ship Via cross-references, and Calculate Discount On Order Lines with the displayed order values.

Invoice preparation or release finds insufficient Magento quantity

Check Magento Qty While Prepare Invoice validates quantity before invoice creation, and Check Magento Qty While Release Invoice validates it during release. The documentation does not state the exact failure message or remediation sequence.

A failed import notice is not received

Confirm Send Email Notifications for Errors and the email address on the Order Settings tab. The manual says notices can occur during batch imports and process updates because orders in the selected period are checked again, but it does not document the email template or delivery troubleshooting.

Where to Check Your Work

The Biz-Tech Services Magento Acumatica Integrator exposes the order result through the staged import grid, the individual Magento Orders record, and the created Acumatica document. Check these documented points after each import:

1. Import Magento Orders grid: confirm the expected order was retrieved and selected or included in Import All.

2. Magento Orders hyperlink: open the individual record from the order number.

3. Document Details tab: review the imported item information.

4. Addresses tab: compare customer shipping and billing details with the configured override options.

5. CC Payment tab: review credit card payment information when that tab is applicable.

6. Magento Order ID and Magento order status: confirm identity and the status captured from Magento.

7. Payment Method and Ship Via: compare these values with payment and cross-reference settings.

8. Total Lines Amount, Discount Total, Shipping Total, Total Tax, and Total: reconcile the staged values before and after import.

9. Sales Order Number: verify that the imported order has an Acumatica sales order reference.

10. Invoice Number: check this field only when the order has subsequently been invoiced.

11. Refresh Order: update the displayed Magento order status when the store status changed after import.

How to Import Magento Orders into Acumatica: Frequently Asked Questions

Which Magento order statuses appear for import?

The source says the processing page shows Partially Shipped, on hold, Pending, and Processing orders.

Does Get Orders create a sales order in Acumatica?

No creation is documented for Get Orders. It retrieves orders into the processing screen; Import, Import All, or Import Order performs the documented import step.

Can I import one Magento order without processing the entire grid?

Yes. Select a row and use Import, or open its Magento Orders record and use Import Order. Receive Orders can retrieve an individual order by store code and order ID.

Why did a Magento item stop the order import?

The Biz-Tech Services Acumatica Magento Integration looks up Inventory CD by Magento Product SKU. If the item does not exist and creation or replacement is not configured, the documented missing-item error can block the import.

Can Magento orders be imported without payment?

Yes. The Skip Magento Payment option is documented as importing the order without payment.

Does importing a Magento order create a purchase order or invoice?

The manual explicitly confirms sales order creation through the individual Import Order confirmation. It does not document purchase order creation during this workflow, and it only says Invoice Number is displayed if the order is invoiced.

How can I cancel a long Get Orders operation?

Click the loading icon next to the elapsed-time timer. The source identifies that icon as the control for canceling retrieval.

Where do failed-order email notifications go?

They go to the email address entered on the Order Settings tab when Send Email Notifications for Errors is enabled.

Work With the Biz-Tech Services Magento

A reliable Magento order import starts with tested credentials, intentional defaults, reviewed mappings, and a check of each staged and created record. The documented workflow gives operators distinct controls for retrieval, selected or bulk import, individual order processing, and status refresh.

If your business needs help configuring and validating the Biz-Tech Services Acumatica Magento Integrator for dependable order processing, visit https://biz-techservices.com to learn more and contact Biz-Tech Services.

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

---

by Gary

How to Import Amazon Orders into Acumatica

How to Import Amazon Orders into Acumatica

Importing Amazon orders into Acumatica starts by retrieving orders for a selected Amazon store and date range, reviewing the records, and importing selected orders as the document type configured for that store. The Amazon Connector can create either sales orders or invoices for Fulfillment by Merchant orders, while Fulfillment by Amazon orders are imported as invoices.

This guide follows the documented order-import workflow and focuses on the settings, document triggers, mapping rules, validation points, and exceptions that determine the result. The Biz-Tech Services Amazon Acumatica Connector keeps the work inside dedicated Amazon Store and processing screens so users can review an order before creating its Acumatica document.

Before You Start: What Must Be Configured

Before retrieving an order, the Amazon Connector package must be installed and published in Acumatica, and an Amazon Store record must identify the store. The Connection Settings tab must contain the credentials and marketplace information required for the connection through the Biz-Tech Services intermediate server. The Biz-Tech Services Acumatica Amazon Connector also relies on the import defaults and mappings described below.

1. Store Code identifies the corresponding Amazon store. A store marked Default Store appears automatically when users open processing and store screens.

2. Import Amazon Orders determines where Fulfillment by Merchant, or FBM, orders are imported in Acumatica.

3. Order Type supplies the default order type created by the integration.

4. Import Customer decides whether the connector creates a new customer from Amazon data or uses the default customer.

5. Import Item decides whether a missing Amazon product can create a new Acumatica inventory item. If this option is cleared and the item does not exist, the documentation says the integration produces an error.

6. Warehouse ID and Unit of Measure, or UOM, provide order-line defaults.

7. Taxable Category, Customer Tax Zone, and Tax ID provide the documented tax defaults.

8. Payment Method provides the default payment method for new customer records created from imported orders.

9. Cross-Reference Options determine which entities are matched between Amazon and Acumatica, including items, payments, and Ship Via values.

For a deeper explanation of the full inbound and outbound lifecycle, refer to the sibling article How Amazon FBA and FBM Data Flows into Acumatica ERP. The present guide stays centered on the operator steps and decisions that create the order document.

How to Import Amazon Orders into Acumatica, Step by Step

The Biz-Tech Services Amazon Acumatica Integration separates retrieval from import. That separation gives the user a review point before Acumatica creates a sales order or invoice.

Step 1: Retrieve orders for the correct store and dates

Open Import Amazon Orders, select the Store Code, and use Start Date and End Date to define the retrieval period. Click GET ORDERS. A timer reports elapsed time while the connector retrieves orders, and the loading icon next to the timer can cancel the retrieval. The resulting grid can contain every order found in the selected period, so confirm the dates before continuing.

Step 2: Review the retrieved Amazon orders

Inspect the grid and decide which orders should be imported. Click an Order Number to open the corresponding record in the Amazon Orders pop-up. This screen shows the important order information and is also where the documentation says an import error message can identify what must be corrected and in which system.

Step 3: Select individual orders or prepare a full batch

Select the checkbox for each required order when you want a controlled batch. Use IMPORT ALL only when every retrieved order in the grid is ready. Reviewing individual records first is especially important when item creation, customer creation, address overrides, or cross-references may produce different results across the batch.

Step 4: Run the import

Click IMPORT for the selected records, or click IMPORT ALL for the entire grid. After IMPORT is pressed, the screen filters out unselected orders. The process can be canceled by closing it, as described in the manual.

Step 5: Confirm the created Acumatica document

Open the created record and verify its type, customer, lines, warehouse, tax, payment, shipping, and address information. For FBM orders, the configured destination and Order Type decide whether the integration creates a sales order or an invoice. For Fulfillment by Amazon, or FBA, the FBA settings specify an Invoice Type, and the Import FBA Orders process creates an invoice displayed on the Sales Orders Invoice screen.

Document Triggers: What Each Action Creates

GET ORDERS retrieves Amazon records into the processing grid; it does not by itself create the final Acumatica order document. IMPORT or IMPORT ALL triggers creation for the selected retrieved records. The result depends on the store configuration and fulfillment channel.

1. FBM import can create a sales order or invoice, according to the Import Amazon Orders destination and configured Order Type.

2. FBA order import creates an invoice based on the configured FBA Invoice Type.

3. Import Customer can create a new customer when no matching customer exists; otherwise the default customer is used when that option is cleared.

4. Import Item can create a missing inventory item from the Amazon product SKU. When it is cleared, a missing item stops the import with an error.

5. An imported item uses the Amazon item price on the order rather than the mapped Acumatica item price.

6. Insert Item in Inventory Details Tab adds retrieved items to the Amazon Store Inventory Details tab during order import.

The import is only the first document event in the FBM lifecycle. After an imported sales order is acknowledged, users can create a shipment, confirm it with Ship Via, package, and tracking information, prepare an invoice, and release the invoice. Those later actions drive acknowledgement and fulfillment communication back to Amazon, but they are separate from the initial order import.

Mapping Rules That Decide What Appears on the Order

The Biz-Tech Services Acumatica Amazon Integration applies store defaults and cross-references while creating the Acumatica document. Review these rules before treating a successful import as complete.

Customer and address rules

When Import Customer is selected, customer information from Amazon can create a new Acumatica customer. When it is not selected, the connector uses the default customer. Override Ship Address Information from Amazon Order brings in the shipping destination from Amazon, and Override Bill Address Information from Amazon Order brings in the billing address. The manual does not provide a complete decision table for every combination, so test the chosen configuration with a controlled order before processing a large batch.

Item, price, warehouse, and UOM rules

The connector matches products through the configured item cross-reference and Inventory Details mappings. A missing product can be created from the SKU only when Import Item is selected. The order line uses the Amazon item title as its description even when an existing stock item description is not updated. The imported line uses the Amazon price, while Warehouse ID and UOM provide defaults.

Tax, payment, and shipping rules

The store settings provide Taxable Category, Customer Tax Zone, Tax ID, and Payment Method values for the import. Cross-reference selections control which Amazon values match Acumatica values. The manual specifically notes that the mapped Amazon Ship Via value should appear in Delivery Settings on the Shipping tab of the Sales Orders screen after import.

FBA-specific rules

FBA orders use a required default customer and the configured Invoice Type. If Import Amazon FBA Payment is selected, a payment-method field becomes available for the imported FBA order. The FBA status mapping table determines which Amazon order statuses are eligible for retrieval and import, and the Begin Order Date limits the retrieval window.

Validation and Common Exceptions

A completed process is not enough by itself; validate the generated document against the Amazon record and the store settings. The manual documents where errors appear but does not list all possible error messages.

1. If an order line shows an error in the import grid, hover over the red cross for additional information.

2. Open the Amazon Orders record to see the error message and the system in which the correction is required.

3. Use TOOLS > Trace for more detail when the grid message is not sufficient.

4. If a product does not exist and Import Item is cleared, correct the item mapping or configuration before retrying.

5. If Ship Via is wrong or blank, review Cross-Reference Options and the Amazon-to-Acumatica value mapping.

6. If the wrong customer appears, check Import Customer and the default customer setting.

7. If the wrong document type appears, review Import Amazon Orders, Order Type, and, for FBA, Invoice Type.

8. If an expected FBA order is missing, verify Begin Order Date and the selected Amazon status mappings.

The Send Email Notifications for Errors option can send notifications that identify Order IDs with errors. Because the source does not document a complete error-message catalog, use the order record, the grid indicator, and Trace rather than relying on guessed error text.

Where to Check Your Work

After the import, the Biz-Tech Services Amazon Acumatica Integrator exposes the most useful checks across the processing grid, Amazon order record, store configuration, and created Acumatica document.

1. Import Amazon Orders: confirm Store Code, Start Date, End Date, retrieved rows, and the import result.

2. Amazon Orders: open the Order Number and review the source details and any displayed error message.

3. Amazon Store - FBM Settings: verify Import Amazon Orders, Order Type, Last Imported Order Date, customer options, item options, warehouse, UOM, tax, and payment defaults.

4. Amazon Store - Cross-Reference: verify the Field, Amazon Value, and Acumatica Value pairs used by the order.

5. Amazon Store - Inventory Details: verify the Amazon SKU to Acumatica inventory mapping.

6. Sales Orders - Shipping tab: confirm the Ship Via result under Delivery Settings.

7. Created sales order or invoice: compare customer, addresses, lines, descriptions, quantities, prices, warehouse, taxes, and payment information with the Amazon order.

8. Import FBA Orders: confirm eligible statuses, retrieved FBA orders, and the resulting invoice.

9. FBM & FBA Orders: use the Fulfillment Channel field to distinguish how the order was fulfilled.

10. TOOLS > Trace: inspect technical details for a failed processing record.

How to Import Amazon Orders into Acumatica: Frequently Asked Questions

Can Amazon orders be imported as sales orders or invoices?

Yes. The documented FBM settings allow Amazon orders to be imported as a sales order or invoice document type, according to the configured destination and Order Type. FBA order import creates an invoice using the FBA Invoice Type.

What is the difference between GET ORDERS and IMPORT?

GET ORDERS retrieves records for the selected Store Code and date range into the grid. IMPORT creates Acumatica documents for selected records, while IMPORT ALL processes every retrieved record shown in the grid.

Why did an Amazon order fail because of an item?

A documented cause is a product that does not exist in Acumatica when Import Item is not selected. Review the Inventory Details mapping and the Import Item option, then use the red-cross details or TOOLS > Trace to confirm the actual cause before retrying.

Where can I see an Amazon order import error?

The error appears on the corresponding grid line, with more information available by hovering over the red cross. The Amazon Orders screen can also display the message, and TOOLS > Trace provides additional diagnostic detail.

Why did the imported order use the default customer?

When Import Customer is not selected, the connector imports the order with the default customer. The Biz-Tech Services Acumatica Amazon Integrator creates a new customer from Amazon information only when Import Customer is selected and the workflow requires a new customer record.

Why is the Ship Via value wrong after import?

Review the selected Cross-Reference Options and the Amazon-to-Acumatica carrier mapping. The mapped value should appear in Delivery Settings on the Shipping tab of the Sales Orders screen.

Why is an FBA order not available to import?

Check the FBA Begin Order Date and the status mapping table. The documentation states that the corresponding Order Status checkbox must be selected for the order to be retrieved and imported.

Does importing an Amazon order also send fulfillment?

No. Order import creates the configured Acumatica document. Fulfillment is a later FBM process involving shipment creation, shipment confirmation, invoice preparation, and either the automatic flow or the Export Amazon Fulfillments processing screen.

Work With the Biz-Tech Services Amazon Connector

A reliable Amazon order import begins with the store defaults and mappings, continues through separate retrieval and review steps, and ends with validation of the created Acumatica document. Use a controlled test order to confirm customer, item, address, tax, payment, warehouse, and document-type behavior before increasing batch size.

If your team needs help configuring or validating Amazon order imports, work with the Biz-Tech Services Acumatica Amazon Integration team. Visit https://biz-techservices.com to learn how the Biz-Tech Services Amazon Acumatica Integrator can support your Acumatica and Amazon workflow.

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

---

by Gary