Versions Compared

Old Version 9

changes.mady.by.user jonathan.day

Saved on

compared with

New Version 10

changes.mady.by.user jonathan.day

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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. 

  2. This sync must take into account the mappings that have been configured by the administrator. 

  3. Order sync must be able to recover in the case of order sync failing

    1. For example, if a shipment sync (or any request to SH API) failed:

      • save detailed information to logs that can be accessed by an administrator

      • ensure there is a system that will try sending the record again after some time

      • if fails constantly (10 attempts over 5 hours with exponential delay) - mark the order/fulfillment as failed to sync.

  4. Allow the user to manually sync an order to ShipHawk by clicking a button

Expand
titleTechnical details

Order sync uses the ___ endpoint. Please refer to the order sync documentation for information on various JSON objects . The following fields are required:

  • The order_number of the object being shipped.

  • Origin address block, with the warehouse code field populated.

    • The warehouse code is an ID that is set in ShipHawk to differentiate warehouses. The order creation request should include a warehouse ID that corresponds to a warehouse inputted in ShipHawk:

  • The destination address block

  • The items being shipped, in the order_line_items block:

    • Required:

      • sku

      • name

      • description

      • qty

      • item weight

      • ShipHawk specific Smartpacking information:

        • item_type (parcel, handling_unit, unpacked)

        • type_of_item (loose, box, pallet)

        • do_not_pack_with_other_items (boolean)

        • do_not_palletize (boolean)

        • do_not_pack_before_palletize (boolean)

    • If available:

  • order status

  • order level reference_numbers, as mapped by the administrator

  • billing_details, if mapped by the administrator

    • Note: If the bill_to field is not populated by the mapping, then the field should default to ‘sender’

  • requested_rate_id, for cases where the user rates the shipment. See #2 below.

...