Skip to content

Ship orders from different origins on one shipment (#329) - #340

Merged
Connor-Finn merged 1 commit into
mainfrom
tms/329-multi-pickup
Oct 4, 2026
Merged

Connor-Finn merged 1 commit into
mainfrom
tms/329-multi-pickup

Conversation

@Connor-Finn

Copy link
Copy Markdown
Collaborator

Slice 1 of #329 (consolidations): multi-pickup shipments.

  • Each order origin becomes a pickup stop before the drops; orders link to their pickup via new Order.pickupStopId (migration, no new index).
  • pickupWaypoints on shipment create/update; syncShipmentStops keeps pickups and refuses to drop stops orders still use.
  • Tracking: leaving a pickup puts only the orders collected there in transit; arriving later with an earlier pickup open infers its departure.
  • Create page lists Pickups and Drops separately; Ship together and Add order no longer require a shared origin.

Tested live: a two-origin milk run (Green Bay + Chicago → Atlanta + Memphis) via pings — each order went in transit at its own pickup, was delivered at its own drop, and the shipment completed. Full backend suite, frontend tests, tsc and lints pass.

🤖 Generated with Claude Code

Each origin becomes a pickup stop before the drops, and orders link to
their pickup through Order.pickupStopId. Leaving a pickup puts only the
orders collected there in transit; arriving later with an earlier pickup
still open infers its departure. The create page lists pickups and drops
separately, and Ship together no longer needs a shared origin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Connor-Finn
Connor-Finn merged commit d748255 into main Oct 4, 2026
1 check passed
@Connor-Finn
Connor-Finn deleted the tms/329-multi-pickup branch October 5, 2026 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant