For sending information to ShipHawk, the ERP must meet the following requirements:
When a shipment is ready to be packed and/or shipped in ShipHawk, the shipment must be synced over to ShipHawk. Only the object related to the actual shipment needs to be synced.
For example, in NetSuite there are Sales Order objects, and each Sales Order may have multiple Item Fulfillment records which represent the pick task and shipment.
This sync must take into account the mappings that have been configured by the administrator.
Prior to fulfillment, users must be able to rate the order in the ERP with ShipHawk by clicking a button. Upon clicking this button, the connector must send a rating request to shiphawk, receive rates from ShipHawk, and display them in a dropdown menu. If a rate is selected, it is to be applied to the ‘ship method’ field.
In our other integrations, this rating exists at the Sales Order level, and not at the shipment level object.
Not all customers will use this, but it is important for some B2B use cases.
The serial/lot numbers available for packing/ shipping must be synced with ShipHawk so that they can be verified in ShipHawk.
The user must be able to scan a serial/lot number into ShipHawk
ShipHawk must have a list of serial/lot numbers in stock for that SKU, and be able to verify the serial number scanned.
After a shipment is booked, the serial/lot numbers must be recorded in the ERP using webhooks.