ShipHero Connector

ShipHero is a comprehensive e-commerce warehouse management system (WMS) and fulfillment solution designed to help brands and 3PLs streamline their shipping, inventory, and returns processes.

4.8 on G2

Weld · Data Sources

ShipHero

ShipHeroYour warehouseLive

order59 columnsSynced

location24 columnsSynced

vendor20 columnsSynced

product35 columnsSyncing

purchase_order_line_item25 columnsQueued

Lands in

snowflake

bigquery

databricks

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

ShipHero

ShipHero

Data source

Authenticating...

Ready to connect

Overview

ShipHero in your warehouse.
Ready for your agents.

ShipHero is a comprehensive e-commerce warehouse management system (WMS) and fulfillment solution designed to help brands and 3PLs streamline their shipping, inventory, and returns processes. Weld's ShipHero connector is fully managed: it extracts data from ShipHero, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

Agent context

ShipHero data schema.
The map your agents read.

Every table, field and relationship Weld syncs from ShipHero is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables: 50
fields: 763
relationships: 21

Loading diagram…

warehouse_product

wholesale_order

expiration_lot_location

inventory_change

previous_on_hand

change_in_on_hand

wholesale_order_id

partner_order_id

fulfillment_status

total_discounts

order_shipping_line

order_shipping_address

order_billing_address

order_authorization

authorized_amount

postauthed_amount

refunded_amount

order_rma_label

tracking_number

shipping_method

order_allocation

allocation_reference

order_allocation_line_item

allocation_reference

parent_allocation_reference

quantity_allocated

is_kit_component

order_line_item

partner_line_item_id

fulfillment_status

quantity_pending_fulfillment

order_line_item_shipped_line_item_lot

lot_expiration_date

order_line_item_serial_number

order_line_item_tote_pick

picked_quantity

order_merged_order

parent_order_id

order_attachment

user_first_name

barcodes_scanned

pending_shipment_line_item_id

user_first_name

country_of_manufacture

product_fba_inventory

product_kit_component

parent_product_id

parent_product_sku

purchase_order_line_item

purchase_order_line_item_expiration_lot

purchase_order_attachment

purchase_order_tracking_number

tracking_number

cost_to_customer

shipping_carrier

tracking_number

shipping_method

return_line_item

quantity_received

return_exchange

exchange_order_id

original_return_id

return_exchange_item

return_exchange_id

pending_shipment_id

shipment_line_item

shipping_label_id

shipment_shipping_label

tracking_number

alternate_tracking_id

order_account_id

default_po_note

warehouse_product

warehouse_identifier

warehouse_product_inbound

purchase_order_line_item_id

quantity_received

quantity_rejected

warehouse_location

wholesale_order

fulfillment_flow

shipping_option

staging_location_id

outbound_progress

wholesale_order_shipping_details

wholesale_order_id

shipping_method

gs1_company_prefix

wholesale_order_line_item

wholesale_order_id

unit_of_measure

Open the schema explorer Open the full schema explorer

Weld MCP server

Ask your agent.
It already knows ShipHero.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the ShipHero context, finds the tables it needs and queries your warehouse.

Agent contextShipHero tables, fields and joins
QuerySQL against your warehouse
OperateCheck, rerun and refresh syncs

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextShipHerotables50fields763joins21

>

How many order rows do we have per wholesale_order? Use our ShipHero data.

Reading the ShipHero context first, so the query uses the right tables and keys.

●weld·search_available_references

⎿raw.shiphero.order

raw.shiphero.wholesale_order

+ 48 more ShipHero tables

●weld·get_reference_schema

⎿order · 59 columns

joins wholesale_order on wholesale_order_id

●weld·run_query

⎿select w.id, count(*) from {{raw.shiphero.order}} o

join {{raw.shiphero.wholesale_order}} w on o.wholesale_order_id = w.id

group by 1

submitted

●weld·get_query_status

⎿DONE

●weld·get_query_result

⎿rows returned

✓Answered from ShipHero data in your warehouse

>Ask about your ShipHero dataMCP

Destinations

Load ShipHero into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create ShipHero connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a ShipHero ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "shiphero",
    "destination_schema_name": "shiphero_data",
    "sync_interval": "0 * * * *"
  }'
▌

FAQ

Common questions.
About connectors.

Something not covered here? A data engineer can walk through your setup with you.

Put your ShipHero data to work.

Connect ShipHero, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.

ShipHero

Source

Weld

MCPAgents

Start for free Talk to us

Connectors

Explore more connectors.
300+ and counting.

View all connectors