Missing Shipment Data Pull 2.0 (Backup)

This is the production "2.0" pull. It backfills missing ShipHero shipment data into Supabase for all active brands and reconciles the whole graph: orders, packages, line items, Product SKUs, customers, stores, warehouses, and shipping zones.

At a glance

• Status: Active, the live version of the 2.0 pull.
• Trigger: Daily schedule (~03:00), a self-restarting webhook, and a manual Test trigger.
• Runs on: Every active brand, one brand/date at a time.
• Talks to: ShipHero GraphQL, Supabase, the National Commerce app API (shipment zones), and internal n8n webhooks (SKU lookup, self-restart, voided-label cleanup).

How it works

1. The schedule or self-restarting webhook fires, and a merge node normalizes the cursor, date, and brand inputs.
2. It pages ShipHero shipments day-by-day for one brand, self-restarting through its webhook to advance dates and dodge execution timeouts, with ShipHero rate-limit wait handling.
3. It upserts Shipments, Orders, Shipment Line Items, Product SKUs, and Warehouses, plus the m2m links between them, and creates or links customers and brand stores.
4. It computes shipping zones by calling the app API /api/shipment-zones/get-zone, looking up the origin warehouse and saving the zone (or an error) back to Supabase.
5. It fixes changed line-item quantities, links stores to both orders and shipments, and calls the voided-labels webhook to remove voided shipments for the brand.

Notes

• The flow re-POSTs to its own webhook to paginate and advance dates. This is intentional: it keeps each execution short so long runs never hit the timeout.
• This is a superset of the reconciliation copy (~160 nodes): it adds shipment-zone calculation, order/shipment store linking, and quantity-fix logic.

Related

• Missing Shipment Data Pull 2.0 (Reconciliation): the disabled reconciliation copy.
• Missing Shipment Data Pull (v1): the original, superseded flow.
• Delete Voided Shipment Labels (Daily): the voided-label cleanup webhook this flow calls.
• Backfill Missing Product SKUs: repairs line items this flow may leave with a null SKU.
• SKU Information Handler: the shared SKU-resolution service.
• Error Handler: the shared error workflow.
• Features: Shipments, Inventory. See also Data flows.