Customer ID Mapping
RepairShopr customer IDs for ESA programs and other key accounts.
The RepairShopr customer IDs that get used most often — primarily for ESA program order processing. Re-verified against the live RS data on 2026-06-01 (each ID fetched and its program name/order subjects confirmed).
ESA / EFS programs
| Program | RS Customer ID | RS account name | Order subjects |
|---|---|---|---|
| Odyssey Iowa | 30805989 | Odyssey — Portal Order | ”New Order Iowa Marketplace” |
| Tennessee Portal | 31938978 | Tennessee Portal | ”New Order TN (FSA) Marketplace” |
| Odyssey Georgia | 34276337 | Odyssey - Georgia | ”New Order Georgia Marketplace” |
| Odyssey Louisiana | 34338975 | Odyssey Louisiana | ”New Order Louisiana Marketplace” |
| Odyssey Utah | 34467295 | Odyssey Utah | ”New Order Utah Marketplace” |
All five sit under RS location Odyssey (location_id 3230).
Payment terms
All ESA programs are net-30 from ticket_created_at. The invoice generator
uses ticket_created_at (not invoice creation date) to compute the due date.
Why this matters
When the RS ticket sync runs and produces the master order list at:
/home/superht/pricing/exports/repairshopr_ticket_invoice_report_sheet_sync_latest.csv…it joins on these customer IDs to bucket orders by program. If a new ESA program comes online, it has to be added to:
- The customer record in RepairShopr (so tickets/invoices route correctly)
- The mapping table consumed by the ESA order processor
- This page (so the next person looking for it can find it)
Related references
- Hosts — where the sync runs and where the export lives
- Cron Schedule — when the sync runs
- ESA Order Processing — the workflow that consumes these IDs
Last verified against live RepairShopr data: 2026-06-01 — see doc freshness.