ShipHero walkthrough

Prerequisites

• ShipHero connection.

ShipHero reports

Most of the reports in ShipHero depend on time. The order, product, return, and purchase order reports include an additional option to provide an ID list. In the ID list type, you can filter by a specific ID, if required, or leave the field empty to pull all the IDs by selecting the List type.

Time-dependent reports

The time-dependent reports include Widgets, sub ID stats, and more.

Selecting a time period

Time-dependent reports support two kinds of time periods:

1. Date Range
   • Pulls data in the date range between the start and end date provided, including the end date.
   • You must select a start date.
   • Leaving the end date empty pulls data according to the current time of the river's run.
   • Select a timezone offset to send dates considering the offset.
   • Use the Last Days Back For Each Run to expand the start date and pull data a given number of days back before the chosen start date.

2. Predefined date - A date range defined by Data Integration:
   • Day - Yesterday.
   • Week (From Monday to Sunday) - Week to date, Previous week, Previous week to date.
   • Month - Month to date, Previous month, Previous month to date.
   • Year - Year to date.

Special use case

In the Order History report, select the orders.

Use case-nested fields

ShipHero lets you pull specific sets of fields to increase performance. For optimal performance, pull only the fields you need for your use case instead of pulling everything.

Minor queries can provide additional data; ensure that you include those fields when pulling them.

ShipHero provides a maximum of 1000 simple fields (int, char, strings, etc.) at a given time. So, nested fields (records, lists, etc.) contain more than a straightforward field. When you input nested fields, such as order, returns, line items, and line item details, the maximum available limit for pulling the data is reduced.

In general, Line Item Picks and Orders reports have the most nested fields. To address excessive hierarchy, several convenient nested fields contain one additional level of subfields. These are represented as the last field in a given level, X, Y, and Z. Considering the field Z:

1. Z = Address contains subfields: name, address1, address2, city, state, country, zip, phone
2. Z = order info contains the subfields: id,legacy_id,order_number,partner_order_id,shop_name,fulfillment_status,order_date
3. Z = dimensions: weight, height, width, length
4. Z = original return: id,order_id,legacy_id,partner_id,reason,status,label_type,created_at
5. Z = order: id,legacy_id,order_number
6. Z = kit components: legacy_id,account_id,sku,quantity
7. Z = vendors: vendor_id,vendor_sku,price
8. Z = warehouse: id,dynamic_slotting,profile

Line Item Picks report

Retrieve details of each line item picked in a given time.

Packs per Day report

Retrieve the shipment's package within the specified timeframe.