This article describes the setup requirements for the techSHIP Acumatica (v23) plugin. 

 

NOTE: This article is for the v23 plugin. For the deprecated version, please refer to: Acumatica - Onboarding Requirements [Information].

 

This article is divided into the following sections:

  1. Configuring Plugin Parameters
    1. Required
    2. Optional
  2. Final Considerations


I. CONFIGURING PLUGIN PARAMETERS



i. Required


When onboarding or adding a new Acumatica portal, you must provide and verify the following information (highlighted in red in the previous screenshot):

  • Acumatica Username
  • Acumatica Password
  • Acumatica Update Username
  • Acumatica Update Password
  • Acumatica Service URL
  • Acumatica Endpoint (Typically, Techship/[AcumaticaVersion])


ii. Optional


The following parameters are optional (highlighted in blue in the previous screenshot):

  • Acumatica Company 

  • Acumatica Tenant 

  • Acumatica Branch 

  • Acumatica default box type (e.g., SINGLE) 

  • Acumatica Rate Limit

     

    NOTE: The Acumatica Rate Limit field is based on the order volume. Consult with the development or implementation team if this needs to be completed or modified.

     

  • Load Stock Items: If checked, this will load lines UPC from Acumatica StockItem entities.

  • Load item dimensions: If checked, this will load height, length, width, and weight of StockItems defined on Acumatica to the lines.

  • Acumatica Order Type: If detailed, allows techSHIP to set what order types to support. 

  • Acumatica Warehouse ID: Used to filter shipments when importing by sales orders.

  • Flex Field Mapping: Allows binding custom fields in addition to the standard plugin bindings.

     

II. FINAL CONSIDERATIONS

 

WARNING: Please be aware of the following critical setup requirements and behaviors.

 

Packing logic is conditional:

  • If packing is done in techSHIP, imported shipments must not have packages (boxes) created in Acumatica.
  • If packing is done in Acumatica, the corresponding shipments can have packages and content, which will be transferred to techSHIP.


Any missing or non-validated, incorrect setup or information will delay the setup process.