Ridgeline Outfitters · case file · eleven days, one root cause, three helpers

Why 212 orders shipped to the wrong address

Evidence tagsSix tags on the rail · the clues (scene A) show what was known on day one; the verdict (scene B) fills them in

Orders affected
0 → 212
Days before anyone noticed
0 → 11
Root causes
? → 1
Contributing causes
? → 3
Cost (reships, refunds, labels)
$0 → $6,340
Days to fix once found
— → 2

The boardEight cards · string thickness is the weight of the clue · every string ends at the verdict · hover a card to light its chain

  1. Apartment numbers missing on labels — STRONG (the symptom)
  2. Address form autofill swaps line 1 and line 2 in one browser — CONTRIBUTING
  3. Sync truncates address line 2 at 20 characters — ROOT CAUSE
  4. Label template hides line 2 when it is empty — CONTRIBUTING (hid the bug)
  5. No alert on return-to-sender spikes — CONTRIBUTING (11 days)
  6. Support macro blamed the carrier — RED HERRING
  7. Carrier scan data shows correct building, wrong unit — CONFIRMS 3
  8. Verdict: line 2 truncated in sync; two other bugs hid it — CLOSED

The reportTyped, on the clipboard

Case 0311

Ridgeline Outfitters · ops · incident report · 12 March 2026

The label was right and wrong at the same time: right street, no unit. The sync cut address line 2 at 20 characters, and "Apartment 14, Building C" is 24. The label template then hid the empty line, so the label looked clean. Support had a macro that blamed the carrier, so 212 customers were told to check with the depot.

The fix took two days. The finding took eleven, and that is the real defect: a return-to-sender spike is now an alert, and "check with the carrier" is no longer a macro.

What changedFive lines, each ticked as it scrolls in

  1. Sync keeps address lines whole (limit raised to 120 characters, test added).
  2. Label template prints "—" for an empty line 2, never hides it.
  3. Return-to-sender count over 5 per day pages the ops lead.
  4. The carrier macro is deleted; replies must quote the label.
  5. All 212 customers got a reship and a note; 31 asked for a refund instead.

The ledgerEvidence · source · what it proved

EvidenceSourceProved
212 labels, no unitlabel archivethe symptom
20-char fieldsync code, line 88the root cause
"—" never printedtemplatehow it hid
RTS spike 9 Marcarrier reportthe 11 days

The tapeOff the teleprinter

basecamp orders find --rts --since 2026-03-01     # 212
basecamp sync fields address2                     # max 20 → 120
basecamp alerts add rts --threshold 5/day --page ops-lead
The label was right and wrong at the same time.
exit