# 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 (emails, carousels, captions, landing pages, ads) must explicitly name a real Linx product by its full product name, not a generic category like "coding systems" or "inspection equipment."

This mirrors how Linx's own corporate social posts close: they spend the body of the post on a pain point or capability, then name the exact product/series at or near the end (e.g. "The Linx 9000 series printers come with an optional Linx Iris vision system...").

## What Counts as a Valid Product Name

Always use the full, correctly capitalized product name. Acceptable names to draw from:

- **Linx 9800 Series** (CIJ printer: 9810, 9820, 9830, 9840, 9840 Spectrum)
- **Linx 9000 Series** (printer platform the 9800 Series sits within)
- **Linx Iris** (vision system, integrates with 9800/9000 Series, verifies code presence/position/accuracy)
- **Linx PrinterNet** (remote monitoring: fluid levels, print status, production insights)
- **Linx QuickSwitch** (real-time message changes from barcode scanner/external device)
- **Linx Message Studio** (PC application for creating/editing/sending messages)
- **Linx SureClean** (automatic printhead wash station)
- **Linx PureFlow** (5x ink filtration system, reduces nozzle blockages)
- **Linx Vortex** (mixing tank for high-opacity pigmented inks)

Do not invent product names or specs not found in the project's Linx brochures/FAQs/spec sheets. If unsure a feature exists on a given series, check the source PDFs in the knowledge base before naming it.

## Where the Product Name Goes

Place the product name in the **second half of the content**, after the pain point and value proposition have already been established, never in the opening hook. The pattern is:

1. Pain point / risk (no product name)
2. Why it happens / what's really going on (no product name)
3. What the right equipment does about it, **naming the specific Linx product(s)** that solve it
4. CTA button or link

## Selecting the Right Product for the Context

Match the product to the persona and pain point, don't default to the same one every time:

| Persona / Angle | Default Product(s) |
|---|---|
| QA Manager / Compliance, audit trail, documentation | Linx 9800 Series + Linx Iris |
| VP of Operations, line reliability, uptime | Linx 9800 Series + Linx PrinterNet |
| FSMA 204 / traceability (CTE/KDE) | Linx 9800 Series (GS1 Data Matrix builder) + Linx Iris |
| Pharma / nutraceutical serialization | Linx 9800 Series (GS1 Data Matrix builder, sNDC-ready) |
| Multi-SKU changeover speed | Linx 9800 Series + Linx QuickSwitch |
| Maintenance / uptime reduction | Linx SureClean + Linx PureFlow |

## Positioning Constraint (does not change)

Naming the product does not change Factronics' positioning. Factronics sells and deploys equipment; it is not a compliance consultancy. Never write lines like "we help you pass FDA audits" or "we ensure compliance" as a standalone claim. Instead, describe what the named Linx product physically does on the line (prints, verifies, monitors, switches) and let the compliance/audit/traceability outcome follow naturally from that description. The product name is what makes the outcome credible, not a substitute for it.

## Formatting Constraint (does not change)

No em dashes or en dashes anywhere in copy, per standing style rule. Use periods, commas, or "and" instead.

## Quick Self-Check Before Finalizing Any CTA

- [ ] Does the closing section name a real Linx product?
- [ ] Is the product chosen appropriate to the persona/pain point (see table above)?
- [ ] Does the product appear after the problem is established, not before?
- [ ] Does the copy describe what the product *does*, not just assert compliance as a claim?
- [ ] No em dashes or en dashes?
- [ ] Spec/feature claims about the named product are verifiable against the Linx brochures in the knowledge base?