Acumatica Field Mapping

StarShip allows you to customize the way data is translated between Acumatica Sales Orders, Shipments, and Customers and the StarShip shipment. Using the field mapping feature, you can control how the data in these documents is translated to StarShip, allowing you to define what information populates the shipment fields, and how the data is interpreted into accepted shipment values, when necessary.

My Interface

StarShip comes with one predefined interface called “My Interface” that installs default field maps for your Acumatica Shipments, which you can customize. You can also create multiple interfaces to use with different companies if you plan to map to user-defined fields or Ship Vias that vary between companies.

How to Access Customize Interface

To access field mapping, go to Setup > Source Interfaces > Acumatica (version), and click the Interfaces heading.

Select the Customize Interface button for Sales Orders, Shipments, or Customers.

Click Customize Interface

Then, click the Select Mappings heading.

Click Select Mappings


Many fields from Acumatica are mapped by default as part of the basic interface. If you want more control over how data is translated from Acumatica into shipment fields, you can add fields or customize field mapping to suit your company’s needs. For any information that you want imported with the Shipment, you can map those fields to StarShip shipment fields and when applicable, set up value translations.

If you want to import a field that doesn’t have a corresponding field in StarShip, you can use StarShip User Definable fields and map your Acumatica field to one of them. Mapping User Definable fields to Acumatica fields allows you to bring in values that may not normally be imported with the Acumatica document.

You can map any field in StarShip, but let’s go through a common example.

Ship Via

Ship Via is an example of a field that is mapped by default, but which requires you to set up value translations for the most accurate results. Although the field is mapped, you now need to define what the Acumatica Ship Via methods mean in StarShip terms. For example, the Acumatica Ship Via field value “AM” can be set up to translate to “FedEx 2Day® A.M.” when the Acumatica document is imported into StarShip. When the Ship Via is “AM”, the Carrier/Service fields on the Shipping screen will automatically populate with “FedEx 2Day® A.M.”.


If no value translations are provided, StarShip will attempt to translate the Ship Via based on default keywords.

The Acumatica values are populated from Ship Via key field values that are set up in Acumatica.

Expand Shipment > Carrier Information > Carrier – Service. For each of the Acumatica Ship Via values In the Value Translations list, select the corresponding StarShip Carrier – Service value from the drop-down list.

Field Mapping Notes

Package Contents (for Shipments)

Users who want to import package contents information in StarShip (for EDI, packing lists, etc.) should not create packages in Acumatica. Instead, you should define packages and contents in StarShip.

For users who want or need to use the auto packing functionality in Acumatica, or want to create packages in Acumatica INSTEAD of packing shipments in StarShip, there are two options:

  1. Use StarShip’s default mapping for package contents – when mapped, the package contents fields will automatically pack all lines in the first package on the Acumatica shipment (if one exists); OR
  2. Un-map the package contents fields – all line items will be loose when imported into StarShip. You can then use packing preferences in StarShip or manually pack loose items into packaging.
Shipment Defaults

If a shipment field is not mapped, or no value is sent in for the field, StarShip will use your configured Shipment Defaults to populate the field.

Value Translation Notes

StarShip retrieves a list of possible values for certain Acumatica fields (listed below) These fields can be mapped to a shipment field that also requires a set of allowed values, and then you can customize the translation between these sets of values to suit your company’s needs.

Address ID

The Sender Address ID is mapped to the Warehouse ID by default. If you have multiple Sender addresses for a company, you can add values so that StarShip will translate the Acumatica value into StarShip and populate the correct address.

Fields with Value Lists

The following Acumatica fields have value lists:

Acumatica FieldSample Values
Credit HoldTrue, False
InsuranceTrue, False
Order TypeCM, SO, TR, SA
Residential DeliveryTrue, False
Saturday DeliveryTrue, False
Shipping RuleBack Order Allowed, Cancel Remainder
Shipping TermsFLATRATE1, FOB
Shipping ZoneFLATRATE1, FOB
StatusOpen, Shipping, Cancelled
Use Customer's AccountTrue, False
Line Item BranchHQ, VA
Line Item Discount CodeP10000
Line Item Free ItemTrue, False
Line Item Is a KitTrue, False
Line Item Item ClassCHARGE, SOFTWARE
Line Item Item TypeSubassembly, Finished Good
Line Item Lot/Serial ClassLRF, SRF
Line Item Manual DiscountTrue, False
Line Item Posting ClassAOL, CON, ELE, NSS
Line Item Volume UOM*
Line Item Weight UOM*


Adding Values

For fields that have value lists, you can add the values from Acumatica. When you click the “Click here to update Value Translations” link, the Value Translations dialog appears. Click the Edit Values button. Type in the values and click Add after each one. When you’re done, click OK. You can then adjust the values to the correct translations. Click OK when you’re done.

Map a Field to a Fixed Value

You can set a fixed value for any mapped shipment field. You can either type in a value or choose one of the possible shipment values from a drop-down list. If the shipment field says (Select) next to it, then the fixed value will be either selected (checked) or not (unchecked).

Fixed Value

Map to a User Definable field

StarShip provides User Definable fields at the Item, Order, Packaging, Pallet and Shipment levels. Although it is possible to map StarShip User Definable fields to different level source fields, we recommend that you only map User Definable fields to the same level fields from Acumatica.

More Information

More information about setting up and using User Definable Fields in StarShip.

  1. Create the StarShip User Definable fields.
  2. In Select Field Mappings, locate the User Definable field. User Definable fields are noted by a (UDEF) after the field name you created.
    Locate the UDEF field
  3. Select Maps from “Acumatica Field” and then select the field to map to.
    Select the Acumatica field


Save All Maps

Whenever you change field mapping, be sure to click the Save All Maps button to save your work!