ShipHero Fulfillment and WMS API

Known Gotchas

• ⚠ GRAPHQL QUERY COMPLEXITY LIMITS: ShipHero enforces GraphQL query complexity scoring; automated deep-nested queries fetching orders with all line items, shipments, and inventory data in a single query may exceed complexity limit and return 429; decompose complex queries into multiple focused queries with cursor-based pagination
• ⚠ GRAPHQL MUTATIONS IDEMPOTENCY: ShipHero GraphQL mutations (order create, inventory adjustment) may not be idempotent; automated retry on timeout without idempotency key can create duplicate orders or double inventory adjustments; implement order ID deduplication before retry
• ⚠ Shopify webhook-to-ShipHero timing — automated order routing from Shopify webhook to ShipHero fulfillment must account for Shopify webhook delivery delay; automated fulfillment trigger immediately on Shopify webhook without fraud and payment verification creates fulfillment of fraudulent orders
• ⚠ Inventory count discrepancy during cycle count — automated inventory adjustment during active picking creates inventory count discrepancy for in-flight picks; implement inventory freeze during automated cycle count reconciliation
• ⚠ Returns fraud detection gap — automated RMA creation and return authorization without fraud scoring creates return abuse exposure for high-value e-commerce items; implement return policy validation before automated RMA generation
• ⚠ Multi-tenant 3PL client context — automated 3PL ShipHero workflows must include client account context in GraphQL context headers; cross-client data access without client context creates inventory data exposure between 3PL clients