Skip to content

MK Booking To Packing Preview Baseline

  • Evidence date: 2026-07-16
  • Environment: Local Client 2
  • Evidence class: no-write browser trace and legacy/current source comparison

No-write Trace

An authorized Client-2 session entered Operations → Orders → Booking List, opened an existing Booking detail, and reached #packing_list. A post-login route guard aborted every non-GET/HEAD request; no input, print, download, email, file, rate or save control was used. The ignored local screenshot is not repository evidence. This proves menu/preview reachability only, not a user-approved document, output correctness, full row parity or field UAT.

Legacy And Current Comparison

Concern Current disposition
Entry Current detail opens mkPackingList.php?BOOKING_ID=… only when the MK document-workflow flag is enabled; equivalent entry intent is partial.
Relation Current T_BOOKING plus outbound load/equipment rows is not the legacy sales/commodity record model.
Shipper, consignee, lines, rate and UOM Business/rate parity is not established; current UOM-aware rows and linked sales-order values remain authoritative.
Container prerequisite Current preview rejects a booking without a linked container; it is stricter than legacy behavior.
Template literals Static text alone is not a source-backed parity criterion.

MOD-DEC-018 preserves the safe current-output policy. This evidence does not approve email, download, rate persistence, Booking/Packing mutation, DB/schema work, provider use or deployment.

Current Owners

Wiki mk-packing-document is the Local/Production user procedure. The current Booking and Packing process contracts own technical/recovery behavior.

---

Source: docs/research/mk/2026-07-16/MK_BOOKING_PACKING_PREVIEW_BASELINE.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.