Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Add Shipment Box Fields to the ShipHero Connector

Answered
vishal khode User

Connector name: ShipHero

Table name:shipment_shipping_label 

Column to add: 

  • box_id
  • box_name
  • box_code

API documentation link: ShippingLabel - GraphQL API

 

Additional details:

We would like to request support for the box_id, box_name, and box_code fields in the ShipHero connector.

These fields are important for shipment reporting and fulfillment analytics, as they identify the packaging used for each shipment.

Fivetran Support (Case #402382) confirmed that these fields are already available in the ShipHero Orders GraphQL API within the nested shipping_labels object but are not currently mapped to the destination schema.

We kindly request that these fields be added to the shipment_shipping_label table (or another appropriate table) so customers can access complete shipment data without building custom integrations. This would significantly improve the reporting capabilities of the ShipHero connector.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Syead Mujtaba Imam Rizwi Fivetranner
    Hi Vishal,
     
    Thank you for the request. We have added the box_id, box_name, and box_code fields to our active backlog for the ShipHero connector. We have confirmed these fields are available in the source API, so this is primarily a schema mapping change. We will keep you updated on this thread as we make progress.
     
    Best,
    Syead Mujtaba Imam Rizwi
  • vishal khode User

    Hi Team,

    Thank you for adding box_id, box_name, and box_code to the backlog.

    Could you also consider including the dimensions field from the ShipHero ShippingLabel object, specifically:

    • length
    • width
    • height
    • weight

    The field is available in the ShipHero API documentation here: Dimensions - GraphQL API

    Including these fields would provide more complete shipment-level packaging information and would help us with:

    • Packaging and box utilization analysis
    • Shipping cost and carrier charge validation
    • Fulfillment and operational reporting
    • Identifying the packaging used for each shipment
    • Auditing shipment dimensions against expected package sizes
    • Downstream logistics and packaging analytics

    Since these fields are already available in the source API, exposing them through the connector along with the box details would make the shipment data significantly more useful for downstream reporting.

    Thank you for considering this addition.

    Regards,
    Vishal Khode