Wiki · NS freight routing check R594

Freight is the moment GFS hands physical goods to a carrier. When a SO is fulfilled by inventory or assembly, when a PO arrives at a dock, when a dropship vendor ships direct to the customer — freight has to be planned, carrier picked, BOL generated, tracking captured. This check is the dispatcher: it decides whether freight needs human routing (parcel-with-handling, LTL, FTL, dropship vendor freight, freight collect) or can be auto-handled (standard parcel, customer pickup, freight already arranged). When human routing is needed, the record lands on the logistics review queue.

A v2 workflow contract that fires on:

• SO entry — after credit check, before fulfillment. Sets freight_status on the SO body.
• PO creation — for dropship POs (where vendor ships direct to GFS customer or warehouse) where GFS pays freight.

It does NOT fire on: SOs marked customer pickup, POs where vendor pays freight, parcel orders < threshold, or records already past Item Fulfillment / Item Receipt.

1. classify_freight_type — LTL / FTL / parcel / dropship_vendor_freight / customer_pickup / freight_collect. Based on weight, volume, dollar value, ship method on the record.
2. assess_special_handling — refrigerated / frozen / hazmat / oversize / fragile. Based on item attributes.
3. estimate_freight_cost — pull from carrier rate cards if integrated, else flag for manual quote. Lane history is consulted.
4. flag_for_logistics_review — stages a proposed_actions row, HITL-gated per ADR-031.
5. notify_logistics — email draft to logistics team with classification summary + estimated cost.
6. update_so_or_po — D1 write: freight_status = 'pending_logistics_review'. NS push when approved.

• Record lands on logistics queue with full classification + cost estimate
• Logistics team has all the data they need to pick a carrier without re-reading the source record
• Customer PO# (SO.otherrefnum or PO.memo) carries forward to the logistics workflow
• If freight is auto-handleable (standard parcel), it skips the queue and goes straight to shipping

workflow_type: freight_routing_check
risk_level: 2
trigger: SuiteFlow on SO/PO save (conditional)
inputs_required:
  source_record_type: ['so', 'po']
  source_record_id: number
  ship_method: string | null
  ship_carrier: string | null
  shipping_cost: number | null
  total_weight: number | null
  total_volume: number | null
  ship_address: object
context_to_load:
  - customer_or_vendor_address
  - line_items (with shipping_cost)
  - special_handling_flags
preconditions:
  - source_record_exists
  - ship_address_valid
  - freight_relevance_check (block if no shipping_cost AND no ship_method)
fan_out_targets:
  - classify_freight_type (chat_tool)
  - assess_special_handling (chat_tool)
  - estimate_freight_cost (chat_tool)
  - flag_for_logistics_review (stage_proposed_action)
  - notify_logistics (hitl_email_draft)
  - update_so_or_po (d1_write)
post_actions:
  - log_run
  - reflexion
  - event(workflow.completed, 'freight_routing_check')
verify_checks:
  - logistics_review_completed (+24h)
  - freight_cost_finalized (+48h)

Apply migration:

npx wrangler d1 execute gfs-netsuite --remote --file migrations/schema/134_freight_logistics_workflows.sql

Verify contracts:

npx wrangler d1 execute gfs-netsuite --remote --command "SELECT workflow_type, description, risk_level FROM workflow_definitions WHERE workflow_type LIKE 'freight%' OR workflow_type LIKE 'logistics%';"

Manual trigger (test):

POST /api/workflow/run
{ "workflow_type": "freight_routing_check", "inputs": { "source_record_type": "so", "source_record_id": 12345 } }

• TBD Mike confirms NS custom freight field names
• Carrier rate card integration (currently manual quote fallback)
• Lane history scoring — reflexion writes back carrier reliability per lane
• Hazmat compliance workflow split-out
• Customer-facing tracking page (PO# → tracking link)
• Logistics dashboard at https://gfs-netsuite.pages.dev/logistics-review.html — build