From 25dfb1b22ad5436fa85c59492523ad18ebdb04c9 Mon Sep 17 00:00:00 2001
From: Mike Swanson <mike@azcomputerguru.com>
Date: Fri, 22 May 2026 12:08:31 -0700
Subject: [PATCH] sync: auto-sync from DESKTOP-0O8A1RL at 2026-05-22 12:08:26

Author: Mike Swanson
Machine: DESKTOP-0O8A1RL
Timestamp: 2026-05-22 12:08:26
---
 .claude/commands/syncro.md                     | 18 ++++++++++++++++++
 .claude/memory/MEMORY.md                       |  1 +
 .../feedback_syncro_estimate_hardware.md       | 12 ++++++++++++
 3 files changed, 31 insertions(+)
 create mode 100644 .claude/memory/feedback_syncro_estimate_hardware.md

diff --git a/.claude/commands/syncro.md b/.claude/commands/syncro.md
index 1dcba7f..1d68235 100644
--- a/.claude/commands/syncro.md
+++ b/.claude/commands/syncro.md
@@ -636,6 +636,24 @@ curl -s -X DELETE "${BASE}/estimates/${ESTIMATE_ID}?api_key=${API_KEY}"
 
 **GET /estimates line_items vs POST response:** GET returns `line_items` as an array on `.estimate.line_items[]`. POST `/line_items` returns the line item under `.line_item` (singular, not nested under estimate).
 
+**Hardware on estimates:** All hardware line items use a single generic product — `product_id: 32252` ("Hardware", `price_retail: 0.0`). The specific item name and price are set per-line-item via the `name` and `price_retail` fields on each line. Never look up a separate product ID for hardware items on estimates — always use `32252` and vary the description and price per item.
+
+```bash
+# Example hardware line item on an estimate
+curl -s -X POST "${BASE}/estimates/${ESTIMATE_ID}/line_items?api_key=${API_KEY}" \
+  -H "Content-Type: application/json" \
+  --data-binary @- <<JSON
+{
+  "product_id": 32252,
+  "name": "Dell OptiPlex 7010 SFF",
+  "description": "Refurbished desktop, 16GB RAM, 512GB SSD",
+  "quantity": 1.0,
+  "price_retail": 649.00,
+  "taxable": true
+}
+JSON
+```
+
 ### Display formatting
 
 When showing ticket lists, format as:
diff --git a/.claude/memory/MEMORY.md b/.claude/memory/MEMORY.md
index 9f07d25..8f62639 100644
--- a/.claude/memory/MEMORY.md
+++ b/.claude/memory/MEMORY.md
@@ -44,6 +44,7 @@
 - [SQL instance role — verify by connections, not name](feedback_sql_instance_role_by_connection.md) — Standard installed under default `SQLEXPRESS` instance name is real. Prove role with `sys.dm_exec_sessions` + `Get-NetTCPConnection -OwningProcess` before recommending stop/uninstall. IMC1 2026-05-05/06 near-miss.
 - [Syncro — confirm appointment owner explicitly](feedback_syncro_appointment_owner.md) — When creating tickets with appointments, always ask "who is the appointment owner?" in the preview. Don't auto-default to ticket's assigned tech. Don't add additional attendees without explicit confirmation. Howard caught on Kittle ticket #32263 2026-05-08.
 - [Syncro — verify appointment date day-of-week](feedback_syncro_appointment_date_check.md) — Always compute and display the day name (e.g. "Saturday 2026-05-23") in the ticket preview — never just the numeric date. Verify with `py -c "import datetime; ..."` before posting. Wrong-day incident on #32312 2026-05-21 (Sunday booked instead of Saturday). Reported by Winter.
+- [Syncro estimate hardware product](feedback_syncro_estimate_hardware.md) — All hardware on estimates uses product_id 32252 ("Hardware", $0 base); set name/price_retail per item. Never look up individual hardware product IDs.
 - [Clear-RecycleBin fails silently as SYSTEM](feedback_clear_recyclebin_system_context.md) — RMM-dispatched cleanup scripts cannot use `Clear-RecycleBin -Force`; the cmdlet uses Shell COM and silently no-ops without an interactive desktop. Enumerate `C:\$Recycle.Bin\<SID>\*` directly. Hit on ASSISTMAN-PC 2026-05-08.
 - [Cascades — ask security group on user creation](feedback_cascades_user_security_group.md) — When creating any Cascades user, always ask which security group(s) they go in. Deliberate per-user decision; an OU→group auto-mirror was explicitly declined 2026-05-14. OU = sync scope; group = access/CA decision.
 
diff --git a/.claude/memory/feedback_syncro_estimate_hardware.md b/.claude/memory/feedback_syncro_estimate_hardware.md
new file mode 100644
index 0000000..3d3eb5b
--- /dev/null
+++ b/.claude/memory/feedback_syncro_estimate_hardware.md
@@ -0,0 +1,12 @@
+---
+name: feedback_syncro_estimate_hardware
+description: Hardware line items on Syncro estimates always use product_id 32252 with varying name/price per item
+metadata:
+  type: feedback
+---
+
+All hardware on estimates uses a single generic product: `product_id: 32252` ("Hardware", `price_retail: 0.0`). The specific item name and cost are set per-line-item via the `name` and `price_retail` fields. Never search for individual hardware product IDs on estimates.
+
+**Why:** There is only one hardware product in Syncro. All hardware items are differentiated by description and price, not by product ID.
+
+**How to apply:** When building an estimate with hardware, always use `32252` as the product_id and set `name` to the specific item (e.g. "Dell OptiPlex 7010") and `price_retail` to the actual cost. Hardware is typically `taxable: true`.