ShipHero to Apache Iceberg integration
Connect ShipHero to Apache Iceberg and automatically sync your ecommerce platform data. Weld extracts data from ShipHero, loads it into Apache Iceberg, and lets you transform the data using SQL or dbt, no custom scripts required.
Source
WarehouseSourceShipHeroConnected- order59 cols
- location24 cols
- vendor20 cols
- product35 cols
- purchase_order_line_item25 cols
- shipment24 cols
- Extract
- Load
- Keep in sync
DestinationApache IcebergReady- shiphero.orderSynced
- shiphero.locationSyncing
- shiphero.vendorSynced
- shiphero.productSynced
- shiphero.purchase_order_line_itemSynced
- shiphero.shipmentSynced
- ShipHero tables
- 50
- fields, typed
- 763
- relationships kept
- 21
- agent context included
- MCP
Trusted by data and AI teams
How to set up ShipHero to Apache Iceberg in Weld.
In the app, with the API or an agent.
New connectionShipHeroAuthorisedWhy sync ShipHero to Apache Iceberg?
Ready for analysis.
Centralizing your ShipHero data in Apache Iceberg lets you join it with other data sources for cross-platform analytics and deeper insights.
Build reliable dashboards and reports by querying ShipHero data directly in Apache Iceberg using SQL or your preferred BI tool.
Revenue and order analytics
Track orders, products, and customer behavior from ShipHero in Apache Iceberg. Build cohort analyses, LTV models, and inventory forecasting.
Centralized data warehouse
Bring ShipHero data into Apache Iceberg alongside other sources to create a single source of truth for your organization.
Automated reporting
Replace manual exports and spreadsheet-based reporting with automated pipelines from ShipHero to Apache Iceberg. Connect BI tools like Looker, Metabase, or Power BI.
What data can you sync?
Every ShipHero table, keys intact.
Weld syncs the objects the ShipHero connector exposes into Apache Iceberg, and you choose which tables and fields to include. The connector's docs list what is available.
- order
- location
- vendor
- product
- purchase_order_line_item
- shipment
- wholesale_order
- pick_per_day
- inventory_change
- pack_per_day
- shipment_shipping_label
- order_rma_label
- purchase_order
- return
- return_line_item
- warehouse_product_inbound
- order_line_item_tote_pick
- product_vendor
- warehouse_location
- expiration_lot_location
- warehouse_product
- order_line_item
- return_label
- order_shipping_address
- order_billing_address
- wholesale_order_shipping_details
- purchase_order_attachment
- expiration_lot
- order_allocation_line_item
- order_attachment
- and 20 more
Ask your agent.
It queries Apache Iceberg for you.
Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the ShipHero context, finds the tables it needs and runs the query in Apache Iceberg.
How many order rows do we have per wholesale_order? Use our ShipHero data in Apache Iceberg.
Reading the ShipHero context first, so the query uses the right tables and keys.
Technical considerations.
What to expect.
- Incremental syncing
- Weld uses incremental syncing where supported by the ShipHero API, loading only new and updated records to minimize data transfer and warehouse costs.
- Schema handling
- Weld automatically manages schema changes. If ShipHero adds new fields, they're detected and added to the corresponding Apache Iceberg tables.
- Data freshness
- Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
- Security
- All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
Keep reading.
Guides, docs and schema.
Common questions.
About ShipHero to Apache Iceberg.
Start syncing ShipHero to Apache Iceberg.
Set up your ShipHero data pipeline in minutes. No credit card required. Free for 14 days.
SourceWarehouse
