Ridge × BOMET — Vendor Intelligence Report

Production Performance Analysis

Source: Latest WIP file — Jun 2026
Shipped Complete: 762 orders
Open Production: 213 orders
Generated: June 24, 2026
ℹ️
Back-stock correctly excluded throughout this report. 207 shipped orders (27%) and 130 open orders (61% of WIP) are flagged as back-stock / replenishment / backup — produced on time and held at Bomet per Ridge's instruction. Excluded from all on-time and delay statistics. Detection: Launch Date contains REPLEN, BACKUP, or BACK STOCK.
On-Time Rate (Shipped)
94%
283 of 301 shipments on time
Late Shipments
18
6% · avg 28 days late
Avg Lead Time
82d
Issue → Confirmed Ex-Factory
Prod. Finishes Early
77d
Avg days ahead of conf date
Active WIP (Open)
83
10 late · 4 critical (>30d)
Back-Stock Held
338K
Balance units at Bomet

On-Time by Product Group

Actual first ship date vs Confirmed Ex-Factory · backstock excluded

Monthly On-Time Trend

By Confirmed Ex-Factory month — Oct 2025 outlier highlighted

Summary by Product Group

Shipped Complete · active production only · all from uploaded WIP file
GroupOrdersOn-TimeLateOn-Time %Avg Lead TimeAvg Days LateGrade
Wallet 2.01501428
95%
82 days21 days (when late)✓ Good
MagSafe 3.022220
100%
101 days—✓ Excellent
KeyCase35350
100%
94 days—✓ Excellent
Wallet 1.020200
100%
46 days—✓ Excellent
Accessories (all)746410
86%
90 days avg36 days avg⚠ Watch
📋
On-Time definition: Actual first shipment date (extracted from Vendor Comments — e.g. "Full finished 7/28, shipped 8/8") is within 7 days of the Confirmed Ex-Factory date. Measured on 301 orders that have both the Confirmed Ex-Factory date AND a parseable actual ship date in vendor comments. Requested Ex-Factory is blank in ~40% of Shipped Complete rows — so Confirmed is used as the committed baseline.
⚠️
October 2025 Anomaly: Only 41% on-time in Oct 2025 (13 late orders). All other months are 85–100%. This is a specific cluster — likely a shared root cause (capacity squeeze, material shortage, or holiday factory slowdown). Worth investigating what happened in Q3/Q4 2025 production cycle.
Overall On-Time
94%
283/301 measurable orders
Late Orders
18
Actual ship > conf+7 days
Avg Overrun (late only)
28d
When late, avg ~1 month
Problem Month
Oct 25
41% — only bad month in data
Production Finishes Early
77d
Before conf date on average

On-Time vs Late by Group

Count of orders

Monthly On-Time Trend

All groups combined · % on-time per conf-date month

Production Finish vs Confirmed Ex-Factory (from Vendor Comments)

227 orders have a "Full finished DATE" in comments AND a Confirmed Ex-Factory date. This shows how much buffer Bomet builds in.
116
Finished >7 days BEFORE confirmed date
(51% — Bomet overestimates production time)
111
Finished within 7 days of confirmed date
(49% — on schedule)
0
Finished >7 days AFTER confirmed date
(0% — production itself never runs late!)
💡
Key insight: Bomet's production itself is never late — they finish 77 days early on average. Delays happen in the shipping step, not production. The gap between "Full finished" and actual ship date is where issues occur. This strongly suggests Bomet holds finished goods and releases them on their own schedule, not necessarily Ridge's. A "Production Finished Date" structured column would expose this gap clearly.
📅
Lead Time = Confirmed Ex-Factory minus Issue Date. Excludes backstock. Only rows with both dates and lead time between 10–400 days. N shown is count of orders used for average.
Fastest: Wallet 1.0
46d
Simplest product, shortest LT
Wallet 2.0
82d
Most common product
KeyCase
94d
More complex construction
Slowest: MagSafe 3.0
101d
Most technically complex
Acc - AirTag
135d
Longest of any category

Lead Time by Group — Avg / Min / Max

Real lead times from this WIP file only

Lead Time Distribution — Wallet 2.0

Spread shows how variable production scheduling is

Lead Time Reference Table — Use for Setting PO Dates

Based on actual historical data. Add 10–15% buffer when setting Requested Ex-Factory.
Product GroupAvg Actual LTMinMaxSpreadOrders (n)Recommended PO Buffer
Wallet 1.046d10d94dNarrow20Plan 55d · safest 70d
Wallet 2.082d29d197dVery Wide153Plan 95d · confirm early
MagSafe 3.0101d56d204dVery Wide27Plan 115d · weekly check-in
KeyCase94d52d114dModerate35Plan 105d
Acc - Screws99d82d116dTight5Plan 110d
Acc - Other79d30d199dVery Wide57Plan 90d · SKU-dependent
Acc - AirTag135d135d135d—3Plan 150d minimum
Acc - Strap182d135d229dVery Wide8Likely mixed materials — verify per order
🏭
Capacity data from Bomet questionnaire: 2.0 Wallets 200K/month, 3.0 MagSafe 150K/month, Keycases 150K/month. Open units = balance qty on current active open orders. Back-stock units are shown separately — they exist physically at Bomet but are not consuming production capacity.
Wallet 2.0 Production
44%
87K open / 200K cap
MagSafe 3.0 Production
34%
52K open / 150K cap
KeyCase Production
~0%
No active production orders
Weekly Output
47.5K
All products combined
Back-Stock Stored
338K
balance units at factory

Active Production Capacity Utilization

Open production units vs monthly capacity limit (from questionnaire)

Back-Stock Held at Factory

130 open WIP lines that are produced and waiting — by group

Back-Stock Detail — What is Held at Bomet

These orders are COMPLETE production-wise. Shipment is withheld per Ridge instruction. Units = Balance Qty (remaining unshipped units), not original order qty.
GroupOrders (lines)Balance Units at BometStorage RiskAction
Wallet 2.091234,870High — largest volumeDefine clear release schedule with Bomet
Wallet 1.01962,625MediumConfirm return-to-active timeline
MagSafe 3.02041,000MediumSome may be released with upcoming shipments
⚠️
338K balance units sitting at Bomet warehouse is a significant inventory risk (previously shown as 404K ordered qty — corrected to actual balance units remaining). If Bomet has a fire, flood, or financial issue, these goods are at risk. Recommend: (1) add inventory insurance clause, (2) set maximum hold duration policy, (3) track back-stock separately from production WIP.
Total Open Lines
213
All open production orders
Active Production
83
Excludes back-stock/hold
Back-Stock / Hold
130
61% of open WIP
Late (>7 days)
10
Unique SKUs · conf > req+7
Critical (>30 days)
4
Titanium Terrain/Summit
CF is text string
36
Not parseable as date

Late Active Orders — Needs Attention

Active orders where Confirmed Ex-Factory > Requested + 7 days · unique SKUs only · sorted by severity
SKUDescriptionGroupReq Ex-FtyConf Ex-FtyDays LateVendor Comment
A1284Ridge Wallet 2.0 - Titanium Terrain - Matte OliveWallet 2.02026-06-052026-08-14+70dNew titanium finish — extended processing time
A1285Ridge Wallet 2.0 - Titanium Terrain - Matte BlackWallet 2.02026-06-052026-08-14+70dSame batch as A1284
A1287Ridge Wallet 2.0 - Titanium Summit - Matte OliveWallet 2.02026-06-052026-08-14+70dTitanium Summit surface treatment issue
A1288Ridge Wallet 2.0 - Titanium Summit - Matte BlackWallet 2.02026-06-052026-08-14+70dSame batch
A1255Ridge Wallet for MagSafe 3.0 - BatmanMagSafe 3.02026-07-032026-07-24+21dLicensed collab, additional sign-off required
A1199Ridge Wallet 2.0 - Burnt DamascusWallet 2.02026-06-052026-06-19+14dDamascus etching requires external supplier
A1200Ridge KeyCase - Burnt DamascusKeyCase2026-06-052026-06-19+14dSame etching supplier dependency
A1325Ridge Wallet for MagSafe 3.0 - Dark CherryMagSafe 3.02026-07-312026-08-14+14d2026/5/22 extent to 6/5...
A1326Ridge Wallet for MagSafe 3.0 - Light BlueMagSafe 3.02026-07-312026-08-14+14d2026/5/29 need extent one week...
A1274Ridge Wallet for MagSafe 3.0 - Forged EmberMagSafe 3.02026-07-312026-08-14+14dForged material processing delay

Confirmed Ex-Factory Data Quality

36 of 213 open orders have CF date as text string — not parseable. These cannot be tracked automatically.
StatusCount% of OpenImplication
Structured date ✓17381%Trackable automatically
Text string (e.g. "2026/5/22 extent to 6/5")3617%Partially parseable — best effort
Blank / TBC / Pending21%Cannot track — no commitment
"BOMET REQUEST TO TAKE BALANCE"21%Bomet keeping finished goods — needs decision
🚨
These are orders Bomet flagged in their own Production Delays Report (June 17, 2026). These represent Bomet's self-reported current problems. All are MagSafe 3.0 or related — confirming the 3.0 line has structural issues (QC, etching dependency, material complexity) beyond normal schedule variance. Updated 2026-06-25: A1077 has since shipped and been removed. A1161 not found in current WIP or Shipped data — verify SKU.
Total Flagged
7
Active (A1077 shipped, removed)
Max Days Overdue
267d
Kintsugi — etching supplier
Root Causes Found
4
QC, Etching, Material, Process
All in Group
3.0
100% MagSafe 3.0 variants

Bomet Self-Reported Delay Orders — Full Detail

Source: Bomet_Production_Delays_6_17_26.xlsx · Days overdue updated to 2026-06-25 · A1077 removed (shipped 6/12–6/19) · A1161 flagged ⚠
SKUDescriptionReq Ex-FtyDays OverdueRoot CauseVendor Explanation
A1078MagSafe 3.0 - Kintsugi2025-10-01+267dEtching Supplier BacklogSame etching factory, shared dependency
A1067MagSafe 3.0 - Atomic Purple2025-06-05+143dQC Defect — Screw HolesScrew holes on colored variant prone to self-explosion during QC
A1167MagSafe 3.0 - Silicone Print2026-02-01+113dMaterial — 50% Scrap RateSilicone printing layer has 50% scrap rate, need full redo
A1160MagSafe 3.0 - Carbon Transparent2026-03-15+99dQC — Surface DefectsSurface scratch and sand hole issue during CNC/polishing
A1161MagSafe 3.0 - Transparent2026-03-15+85dQC — Surface Scratches⚠ SKU not found in current WIP or Shipped Complete file — verify SKU is correct
A1236MagSafe 3.0 - Matt Black (New)2026-04-01+80dTBCNo explanation provided
A1255MagSafe 3.0 - Batman2026-07-03+21d vs confCollab ComplexityLicensed collab requires additional approvals. Note: req date 7/3/2026 is still future — this is a confirmed delay (conf 7/24), not yet overdue from Ridge's req perspective. Also in Active Delays tab.

Root Cause Pattern Analysis

From the delays report — 3 structural issues are recurring
🔩 Etching Supplier Dependency
Damascus (A1077) has since shipped (6/12–6/19/2026). Kintsugi (A1078) is +267d overdue — same etching factory, still blocked. Risk: single point of failure.
⚙️ CNC / Surface QC Issues
Atomic Purple screw-hole defects, Carbon Transparent surface scratches — all 3.0 MagSafe variants. The new MagSafe body design introduces QC failure modes not present in 2.0 wallets. Root cause: new product complexity.
🎨 Material Scrap Rate
Silicone printing layer at 50% scrap rate. This is a process quality problem — the technique isn't stable yet. Until it is, these SKUs will continue to run late. Root cause: immature manufacturing process.
🚢
This data is extracted entirely from Vendor Comments. Bomet writes ship dates and quantities in freetext like: "Full finished 7/28, shipped 8/8 and 8/12" or "2026/5/9 received 500pcs". We parsed 658 of 762 shipped rows and extracted first/last ship dates. This is exactly the problem the WIP Improvements tab addresses — this data should be in structured columns, not comments.
Comments Parsed
658
86% of shipped rows
Finish Dates Found
556
73% have "Full finished DATE"
Not Parseable
104
Comments too vague or missing
Avg Finish→Conf Gap
-77d
Production completes 77d early

Common Vendor Comment Patterns Found

These are the actual formats Bomet uses — and why structured columns are needed
PatternExample from DataWhat We Can ExtractProblem
"Full finished DATE"Full finished 7/28, shipped 8/8✓ Finish date, ✓ Ship dateBest format
DATE received Xpcs2025/4/5 received 4400pcs, 2025/7/30 received 3000pcs✓ Multiple ship dates + qtyParseable
Shipped on DATEShipped 8/8 and 8/12✓ Ship dates, ✗ No quantitiesPartial
Mix of status + dates"Doing CNC, expected 8/15, need to check with etching factory"✗ No structured dataCannot parse
"As above"As above✗ Completely unparseableUseless data
Blank(empty)✗ No dataMissing entirely

Sample Shipped Orders with Full Event Chain (from Comments)

These show the complete picture when vendor comments are complete
SKUDescriptionConf DateFinish Date (VC)Ship Date(s) (VC)Comment
A0456Wallet 2.0 - Polished Carbon Fiber—3/314/24, 6/14, 7/23Full finished 3/31, shipped 6500 on 4/24 to 4/25. shipped 6500 on 6/14, shipped 5250 on 7/23
A0277Wallet 2.0 (standard)—7/157/29–7/31Full finished 7/15, shipped 6980pcs from 7/29 to 7/31
AUWAI249301Wallet 2.0 custom6/30/20256/247/1, 7/23Full finished on 6/24. shipped 7/1. shipped 7/23
A0457Wallet 2.0 variant—7/248/8, 8/12Full finished 7/24. Shipped 8/8 and 8/12
A1051MagSafe 3.0—8/128/15–8/25Full finished 8/12, shipped from 8/15 to 8/25
💰
Unit price = Total Unit Price (FOB) from the WIP. Averaged by Confirmed Ex-Factory month per product group. Wallet 1.0 price variance is high because different SKU complexities are mixed — treat as indicative only. Prices exclude shipping, duty, and any Ridge-side costs.
Wallet 2.0 Avg Change
+20%
$7.28 (Jun '25) → $9.79 (Jun '26)
MagSafe 3.0 Stable
~$11
$11.34 → $10.58 (-7%)
KeyCase +14%
$9→$11
Jun 2025 → Oct 2025
Wallet 1.0 Volatile
Mixed
New SKU types entering

Wallet 2.0 — Unit Price Trend

Monthly average FOB · all 2.0 SKUs

MagSafe 3.0 — Unit Price Trend

Monthly average FOB · all 3.0 SKUs

KeyCase — Unit Price Trend

Monthly average FOB

Wallet 1.0 — Unit Price Trend

High variance — new SKU types entering line

Price Summary

GroupFirst Data PointLatest Data PointChangeNote
Wallet 2.0Jun 2025 · $7.28Jun 2026 · $9.79▲ +35%Significant increase — confirm with Bomet pricing schedule
MagSafe 3.0Jun 2025 · $11.34Aug 2026 · $10.58▼ -7%Stable / slightly improved — likely volume efficiency
KeyCaseJun 2025 · $9.04Nov 2025 · $10.43▲ +15%No data after Nov 2025 — KeyCase not in current open orders
Wallet 1.0Jun 2025 · $5.70May 2026 · $10.62▲ +86%High variance — new complex SKUs mixed with simpler ones
AccessoriesVaries by typeVaries by type—Too mixed to aggregate meaningfully — analyse per SKU

Why These Changes Matter

Every recommendation below is based on a specific data problem found in this analysis. When vendor comments are the only source of production completion dates, shipment dates, and delay reasons — you are dependent on human parsing to understand your own supply chain. These changes turn freetext into structured data that runs automatically.

🔴 Critical — Most Impact

Add "Production Finished Date" column — structured date, not in comments

Currently 73% of shipped orders have "Full finished DATE" buried in Vendor Comments. This is the most important production milestone and it's unstructured. A dedicated date field enables: automatic on-time tracking vs Confirmed Ex-Factory, production-to-ship gap analysis, and root cause correlation. This one column would transform the analytical value of the WIP file.

🔴 Critical — Data Integrity

Enforce structured dates in Confirmed Ex-Factory — no text

38 of 213 open orders (18%) have CF as text like "2026/5/22 extent to 6/5" or "Pending for sample approval". These cannot be parsed. The current practice of embedding revision notes in the date cell means the cell value is unreliable. Rule: CF = date only. All explanations go in Vendor Comments. This is the #1 issue per the Reset Call document.

🔴 Critical — Storage Risk

Separate Back-Stock tab from Active Production

130 of 213 open WIP lines (61%) are back-stock — finished goods held at Bomet. These are mixed into the same tab as active production, inflating apparent open orders. This makes it impossible to distinguish "how much is being made" from "how much is stored". Back-stock needs its own tab with: transfer date, expected release date, storage location, and insurance coverage status.

🟡 High Priority

Add "Actual First Ship Date" and "Actual Ship Qty" structured columns

Right now, shipment events are in comments: "shipped 6500 on 4/24 to 4/25, shipped 6500 on 6/14". These need two columns per shipment event, or at minimum one row per partial shipment. This allows: fulfillment rate calculation, split shipment tracking, and comparison of actual ship dates vs confirmed dates — all currently impossible without comment parsing.

🟡 High Priority

Add "Delay Reason" dropdown when CF date changes

October 2025 had 13 late orders — all confirmed late, but no structured reason exists in the data. A dropdown (QC Issue / Material Shortage / Machine Breakdown / External Supplier / Design Change / Capacity / Other) completed whenever CF date moves would enable root cause analysis. Without it, you can see that something went wrong but not why or whether it's a pattern.

🟡 High Priority

Add "Order Status" dropdown to Open Production

Currently, the state of an order is detected from Ridge Comments freetext ("REPLEN", "BACKUP", "Cancelled on..."). This is fragile. A required dropdown column with values: Active / Back-Stock / On Hold / Cancelled / Complete would make status explicit, searchable, and reliable for all downstream analysis including this report.

🔵 Medium

Require Wallet/Keycase Type for every row

Found blank in ~40% of rows in the 2025 WIP files. Without this field, capacity utilisation by category is inaccurate. The column name changed between "Wallet Type" and "Wallet/Keycase Type" across different file versions — causing mapping failures. Standardise the column name and make it required with validation (2.0 / 3.0 / 1.0 / KeyCase / Accessory).

🔵 Medium

Fill WIP Update Date (Cell B3) every time

Designated for the WIP update date but blank in every file analyzed. The system falls back to filename parsing which is unreliable. Enforce this as a required field — tie it to the weekly submission process. This single date field enables: WIP freshness tracking, compliance scoring, and chronological ordering of historical files.

🔵 Medium

Set Requested Ex-Factory for EVERY order

~40% of Shipped Complete rows have a blank Requested Ex-Factory date. Without this, you cannot measure whether Bomet met the original target — only whether they met their own Confirmed date. The Req column is the baseline for any honest on-time calculation. Without it, analysis defaults to Confirmed vs Actual, which is a weaker metric.

📋 Proposed Column Changes — Priority Order
Production Finished Date
DATE
NEW
When 100% of production qty is complete. Do not put in comments.
Actual First Ship Date
DATE
NEW
Date of first physical departure from factory.
Actual Ship Qty (latest)
NUMBER
NEW
Qty shipped in most recent shipment event.
Delay Reason
DROPDOWN
NEW
QC Issue / Material / Machine / External Supplier / Capacity / Design Change / Other
Order Status
DROPDOWN
NEW
Active / Back-Stock / On Hold / Cancelled / Complete
Confirmed Ex-Factory
DATE ONLY
ENFORCE
Date field only — no text notes. All explanations go in Vendor Comments.
Wallet/Keycase Type
DROPDOWN
REQUIRED
2.0 / 3.0 / 1.0 / KeyCase / Accessory — required, no blanks allowed.
Requested Ex-Factory
DATE
REQUIRED
Must be filled for every order — enables on-time tracking vs original target.
WIP Update Date (Cell B3)
DATE
ENFORCE
Must be updated every time file is submitted. Enables freshness and compliance tracking.

Data Sources — Exactly What Was Used

📄 SHIPPED COMPLETE tab (from latest WIP file)

  • 762 total rows
  • Historical completed orders
  • Key columns: Issue Date, Confirmed Ex-Factory, Vendor Comments, RIDGE Comments, Launch Date, Total Unit Price
  • Requested Ex-Factory is blank in ~40% of rows — this limits "vs original target" on-time analysis

📄 OPEN PRODUCTION tab (from same WIP file)

  • 213 total rows
  • Current open orders — both active production and back-stock held at factory

📄 Bomet Production Delays Report (Jun 17, 2026)

  • 8 rows — Bomet's own self-reported delay list
  • Used for the Delays Report tab only

How Each Metric is Calculated

Back-Stock Exclusion

  • Launch Date contains: REPLEN, REPLENISHMENT, BACKUP, BACK STOCK, BACK-STOCK, ON HOLD, HOLD
  • RIDGE Comments contains: "back stock", "cancelled", "cancel "
  • Result: 207 shipped (27%) and 130 WIP (61%) excluded from performance metrics
excluded = launch_date.includes("REPLEN") OR "BACKUP" OR ridge_comments.includes("cancelled")

On-Time Rate (Shipped)

  • Actual first ship date extracted from Vendor Comments ("shipped DATE" or "shipped QTY on DATE")
  • Compared to Confirmed Ex-Factory date
  • On-time = within 7 days (tolerance for logistics)
  • Sample: 301 orders with both Confirmed date AND parseable ship date in comments
  • This is NOT measuring Requested vs Actual — it's Confirmed vs Actual. Bomet ships when they say they will, but the confirmed date may already have been set late vs requested.
on_time = (first_ship_date - conf_exf_date) <= 7 days

Lead Time

  • Confirmed Ex-Factory minus Issue Date (in days)
  • Excludes rows where either date is blank, or calculated value <10 or >400 days
lead_time = conf_exf - issue_date

Production Finish vs Confirmed Gap

  • "Full finished DATE" extracted from Vendor Comments using regex
  • Compared to Confirmed Ex-Factory date
  • Negative = finished early (before conf date)
  • Average of -77 days means Bomet finishes production 77 days before their own committed date
  • This suggests Confirmed Ex-Factory dates are very conservative
finish_gap = parse("Full finished DATE") - conf_exf

Capacity Utilization

  • Open units = sum of Balance Qty for active (non-backstock) WIP orders by group
  • Capacity from Bomet questionnaire: 2.0=200K/mo, 3.0=150K/mo, Keycase=150K/mo
cap_util = sum(balance_qty WHERE group=X AND NOT backstock) / monthly_cap_X

Known Limitations

  • Vendor Comments are the primary source of actual ship dates — if comment is blank, vague, or uses non-standard format, data is missing
  • Requested Ex-Factory blank in 40% of shipped orders — cannot measure "did Bomet meet the original ask"
  • Wallet Type blank in older (2025) files — group classification relies on product description text
  • Price data averages multiple SKUs per group — individual SKU prices may vary significantly
  • October 2025 anomaly — 13 late orders in a single month, cause unknown without structured delay reason tracking
  • Confirmed Ex-Factory as text string — 18% of open orders: best-effort parsing applied, some dates may be off by days