Your browser. Your workspace.
Shipping Packing Lists and Labels
Allocate ready fabrication quantities to dated shipping bundles, prevent overpacking, print packing lists and piece-mark labels, and record dispatched quantities locally.
Local browser tool. No accounts, uploads or background synchronization. Export backups for records you need to retain.
How this register works
Choose ready fabrication lines and allocate whole-piece quantities to a bundle. Draft bundles reserve quantities immediately after saving. Marking a bundle dispatched freezes its contents and keeps its quantities allocated. This is a local packing record; it does not book transport, certify loading, or send a shipping notification.
Choose an existing project workspace or use an unassigned local project. Keep different physical lots on distinct records. Up to 500 records per register and 2 MB for the combined operations backup.
Loading local records...
Reuse an existing reference
This page packs ready lines from the fabrication board. The source controls below are not needed for shipping.
Receipt sources include all typed purchasing project references. Assembly BOM sources are the saved global plan. Workspace takeoffs and drawing registers are limited to the selected project. Repeated copying can create duplicates; reconcile the source and existing ledger first.
Add or review a record
Recorded work
Examples, backups and recovery
All four operations tools share one backup. A JSON file includes traceability, fabrication, shipments and transmittals with their linked identifiers. Loading a sample or backup replaces only this open view. An explicit record save or Save loaded view writes the entire current operations view to this browser. Export the existing saved records first before replacing them.
If another tab changes operations, saving stops instead of overwriting its newer records. Export your current view, reload saved data, and reapply the intended change. If browser storage is full or disabled, preserve the form and export the open records before closing. These are independent local copies, not a multi-user audit system.
Worked example
Three B101 pieces are ready and none have been dispatched. Save a bundle with two pieces: two become packed and only one remains available. A second bundle requesting two more is rejected. After dispatch, the first bundle still accounts for those two pieces so they cannot be packed again. Each printed line label shows the mark, quantity and bundle reference for a human check.
Use the clearly labeled fictional sample to inspect the relationships between a six-piece material lot, its production stages, a two-piece bundle, and a one-drawing issue. None of these records describes a real customer or project.
Troubleshooting before the next handoff
- Confirm the workspace and mark before copying a source row. A copied snapshot will not update automatically.
- Resolve missing or conflicting references through the responsible project team. The tools do not invent approvals.
- Print or export the relevant record, check its quantity and revision, and retain an operations JSON backup alongside the controlled project files.
Questions about shipping packing lists and labels
Do packing lists reduce stock inventory?
No. Fabrication and shipment quantities form their own operations ledger. They do not consume stock, modify a takeoff, or change purchasing receipts. Reconcile those tools through your normal project process.
Can I print one label per loose piece?
The current output provides one quantity label per bundle line. Print additional copies deliberately if your identification procedure needs them; the tool does not claim that each printed copy represents a separate tracked piece.
Can I change a dispatched bundle?
The ordinary interface freezes it. Draft bundles can be deleted and recreated after confirmation. A full operations backup can replace the local history, so retain controlled exports for records that must be preserved.