Best Practice for 3PL Sync
This topic covers best practices for the following in 3PL sync
Because some parts of 3PL sync are essentially Order and Fulfillment sync, for best practices related to 3PL order and fulfillment sync, refer to Best Practice for Order and Fulfillment Sync.
Mapping Logic
Handle complex logic for determining field values in NetSuite using a formula field, script, or automation. NetSuite Connector works best with simple mappings, either syncing data directly or using a simple translation. Keeping complex logic in NetSuite allows you to have full control over the logic. If unexpected data appears in a 3PL field, it's easier to figure out where it came from if the logic is in NetSuite.
Actual Shipping Cost
NetSuite Connector automatically syncs the actual cost paid to ship the order from the 3PL to the native shipping cost field on the Item Fulfillment. This syncing enables you to track the amount the customer paid for shipping on the Sales Order (incoming revenue) and the amount you paid to ship the order on the Item Fulfillment (outgoing revenue), as they are often not the same.
Inventory Detail
Select the inventory detail on the source record (like Sales Order or Transfer Order) so NetSuite can automatically carry it over to subsequent records. If you can't select the inventory detail on the source record, configure NetSuite to automatically populate it on the final record using a script or other method. Most 3PLs don't send inventory details to NetSuite Connector, except for certain data sets like fulfillments. NetSuite should automatically provide the expected inventory details. This ensures that the syncs related to inventory detail will work without error when NetSuite requests them, even if NetSuite Connector does not have the data to provide such detail. This also ensures you get the inventory details you need on the final record.
When you select the inventory detail, NetSuite automatically carries it over to subsequent records. Don't assign the inventory detail in NetSuite Connector.