Page Comparison

Here is a screenshot of part of the ShipHawk settings page on NetsuiteNetSuite:

Here is a screen of one of the ShipHawk configuration pages in Acumatica:

Customers have used these mappings for the following use cases:

• To put store number information on carton labels to meet EDI requirements, customers have mapped store numbers and additional customer information

• To tell ShipHawk to rate shop rates that will arrive within _ number of days, customers have mapped a custom service days field

• To create customer specific rules, customers have mapped fields denoting the customer processing the shipment

Additionally, the administrator should be able to map information from the customer record, order record, shipment record, and any other important sources of data that pertains to the order object.

Here are the Order Reference number mapping settings as in the Netsuite NetSuite connector:

Here is the order reference number mapping page in Acumatica:

Here are some use cases that customers have used order field mappings for:

• Some companies book shipments for their customers using their carrier account. In order to do this, the third party billing information needs to be mapped from the ERP to ShipHawk

• Some customers want to be able to map alternate return addresses, which are possible via order field mappings.

• In some situations, the default field for some data is not the field that the customer is using. It is good to have integration flexibility out of the box

Additionally, the administrator should be able to map information from the customer record, order record, shipment record, and any other important sources of data that pertains to the order object.

Here is what the order field mapping look like in NetsuiteNetSuite:

Here is what order field mappings look like in Acumatica:

Example use case:

When generating international documentation, ShipHawk needs the value of items in the shipment. In our Netsuite NetSuite environment we have product sync enabled and can sync the sku’s SKU’s value to ShipHawk.

In some cases, however, the value may change depending on other circumstances.

For many of our Netsuite NetSuite customers, line item field mappings are used to map the value of the items being shipped in that Sales Order instead of the value stored at the product/ sku SKU level.

Additionally, the administrator should be able to map information from the item record, inventory details record and any other important sources of data that pertains to the order object.

Here is what line item field mappings look like in NetsuiteNetSuite:

Here is where line item fields are mapped in Acumatica:

Line item reference numbers are frequently used to bring custom information at the line level onto documentation. For example- , one customer has 5 T shirts of the same size and design, but just with a different color. The customer wants to be able to map the color of the shirt onto their packing slips to show their customer. Using line item reference number mappings, the user is able to bring this custom information onto their documentation.

Additionally, the administrator should be able to map information from the item record, inventory details record and any other important sources of data that pertains to the order object.

Here is what line item reference number mappings look like in NetsuiteNetSuite:

Here is where line item reference number are mapped in Acumatica:

Example: If the ERP has a service called FedEx Ground, that service needs to be mapped to ShipHawk’s FedEx Ground service.

Here is where shipment method mappings are configured in NetsuiteNetSuite:

Here is where shipping method mappings are configured in Acumatica:

Here is a page with some of the logs for the Netsuite integration. As you can see, this fits into Netsuite’s script log interface:

Here is a page where admins can view logs in Acumatica:

Image Added