# RULE: Linx Product Naming in Calls to Action

**Source:** Directive from Jovan Gutic (CEO, Factronics USA), June 2026.

## The Rule

Every call to action (CTA), closing paragraph, or final section of marketing content must explicitly name a real Linx product by its full product name, not a generic category like "coding systems" or "inspection equipment."

## Valid Product Names

- Linx 9800 Series (9810, 9820, 9830, 9840, 9840 Spectrum)
- Linx Iris (vision system)
- Linx PrinterNet (remote monitoring)
- Linx QuickSwitch (real-time message changes)
- Linx Message Studio (PC application)
- Linx SureClean (automatic printhead wash)
- Linx PureFlow (ink filtration)
- Linx Vortex (mixing tank for pigmented inks)

## Persona-to-Product Mapping

| Persona / Angle | Product(s) |
|---|---|
| QA Manager / Compliance | Linx 9800 Series + Linx Iris |
| VP Operations / Uptime | Linx 9800 Series + Linx PrinterNet |
| FSMA 204 / Traceability | Linx 9800 Series + Linx Iris |
| Pharma Serialization | Linx 9800 Series (GS1 Data Matrix, sNDC) |
| Multi-SKU Changeover | Linx 9800 Series + Linx QuickSwitch |
| Maintenance / Uptime | Linx SureClean + Linx PureFlow |

## Copy Pattern

1. Pain point / risk (no product name)
2. Why it happens (no product name)
3. What the equipment does, naming the specific Linx product(s)
4. CTA button or link

## Constraints

- No em dashes or en dashes in copy
- Describe what the product physically does on the line; let compliance outcomes follow naturally
- Do not invent product names or specs not found in Linx brochures/FAQs

Full rule document: `[PROJECT_ROOT]/RULES-LINX-NAMING.md`