The booking window closes in six hours. The forwarder needs carton counts. The warehouse needs a packing sequence. Procurement needs to know whether the 40HC still beats two 20GPs. Someone forwards LoadPlan_Sept_FINAL.xlsx — and three people open three different copies because someone else already edited the attachment on their laptop.
That is not collaboration. That is version drift with a freight deadline.
As of September 5, 2026, shareable load-plan links are the cleaner pattern: one URL encodes the plan inputs (cargo, equipment choices, settings, lane metadata). Recipients open the same starting point, re-run optimize, and argue about results — not about which spreadsheet is current.
This is an ops guide for shippers and 3PLs. It is not a carrier booking tool and not legal advice.
Why spreadsheets fail at cutoffs
Excel is excellent for analysis. It is a poor handoff format under time pressure:
| Failure mode | What happens | Cost |
|---|---|---|
| Attachment forks | Each reply creates a new “truth” | Wrong box count booked |
| Silent edits | Dims change without changelog | Phantom leftover cartons |
| Missing context | Rate, lane, shipment date live in email body | Quote and plan disagree |
| No optimize replay | Recipient cannot re-run packing | Debates stay qualitative |
| Mobile dead ends | Warehouse opens a 12-tab workbook on a phone | They ignore it and stuff by memory |
When Transpacific West Coast spot prints sit near $7,185 / 40ft (Drewry early-September lane level — reconfirm before booking), a wrong plan is not an academic error. It is an extra sailing or a residual pile.
What a shareable plan link should carry
A useful share is inputs, not a screenshot of utilization:
- Cargo list — SKUs, dims, weights, quantities, stack flags
- Equipment intent — single type, auto-select, or multi-type fleet settings
- Optimization settings — the knobs that change the packing outcome
- Lane metadata — origin / destination, shipment date, typed freight rate and currency when you use them for cost estimates
- Plan identity — name / customer order so replies stay attached to the same job
What it should not pretend to carry: a frozen 3D result that never needs re-running. Packing engines and server policies change; the honest handoff is “here are the inputs — run it again.”
When a URL beats email
Use a shareable link when:
- Two or more functions must agree (procurement, warehouse, forwarder)
- You are comparing equipment scenarios before a booking email
- Someone remote needs to reproduce your leftover-carton claim
- You want a clean “start from here” without attaching master-data files
Keep email for:
- Commercial negotiation with carriers
- Formal booking confirmations
- Documents that must be archived as PDFs for compliance
Pattern that works: link for the plan, PDF/CSV export for the floor, email for the commercial yes.
Operator workflow (15 minutes)
- Freeze the SKU library for the job (see SKU library habit).
- Build or open the load plan in the calculator; set equipment and settings.
- Run optimize once so you know the plan is solvable.
- Share the link from Results — recipient gets a new in-progress plan with the same inputs.
- Ask them to re-run optimize and reply with container count + leftover cartons + (if used) typed freight estimate.
- Export packing order / PDF only after both sides match on inputs.
If their leftover count differs from yours, debug data and settings before arguing about the engine.
Pair with compare — decide, then book
Sharing gets everyone on the same inputs. Comparing two saved plans decides which inputs win:
| Question | Share link | Compare two plans |
|---|---|---|
| Can remote ops reproduce my run? | Yes | Indirectly |
| Does 40HC beat 40GP on this PO? | After both run | Direct side-by-side |
| Did currency / typed rate change the picture? | If metadata included | Freight delta when currencies match |
For scenario math before the product compare UI, see compare two packing scenarios.
Security and hygiene (keep it boring)
- Share only with people who should see customer order details.
- Do not paste links into public tickets with PII in the plan name.
- After the booking, export a dated PDF for the file — links are for speed, archives are for audit.
- If the link is long or fails to load, fall back to JSON export / import of the portable plan — same idea, different pipe.
Bottom line
Emailing spreadsheets at cutoff is how teams book the wrong box count. A shareable load-plan link passes the same cargo, equipment, and lane fields to everyone who needs to re-run packing — then export the floor instructions once the numbers agree.
Open the Palletizr calculator, build the plan, and use Share link on Results when the next person in the chain needs the inputs — not another attachment named FINAL.