Clients

Customers who never fall through the cracks.

A customer directory that grows with the relationship. Complaints, customer audits, and corrective actions land on the right profile — so account reviews write themselves.

app.qformance.io / clients / Northwind Aerospace
ActiveOEMCreated 4 Mar 2024 · Updated 30 Apr 2026

Northwind Aerospace · structural assemblies

Facilities · 3 External code visible to commercial only
FacilityNumberExt codeStatus
BirminghamCLI-024NW-44218Active
ToledoCLI-003NW-44218Active
AugsburgCLI-009Prospect
One customer, one profile — and a clean record per site you ship to them from.
One profile, every site

One client. One profile. A clean record per site.

A client is one record in your system — name, category, contact info — with a separate working history at every facility you ship to them from. The history reflects the relationship as it really is: when did Birmingham start shipping, when did Toledo come on board, what's happened at each site since.

Northwind Aerospace · facility memberships
Birmingham
CLI-024
Counter local to this site
Toledo
CLI-003
Counter local to this site
Augsburg
CLI-009
Counter local to this site
The customer's basic details are shared everywhere. The history at each site stays local to the site.
Your categories, your naming

The categories your team thinks in.

A starter set of categories ships with every new org — OEM, Aftermarket, Distribution, End-customer — but they're a list, not a fixed taxonomy. Rename them, reorder them, add the ones your industry uses, drop the ones you don't. The naming convention for the directory is yours to set, too.

Admin → Clients
Categories · drag to reorder
1OEM38 clients
2Aftermarket33 clients
3Distribution28 clients
4End-customer23 clients
5Government18 clients
6Reseller13 clients
Naming
CLI
Pick the convention your team uses
Total active
126
Across 4 facilities

Customer vendor codes stay with commercial.

What the customer calls you in their procurement system is a commercial-team detail. Capturing a complaint is everyone's job. Both work — without two systems and without anyone seeing what they shouldn't.

Right people only

One directory. Two cleanly different views.

For the commercial team, the customer's vendor code sits alongside every client — searchable, editable, theirs to manage. For everyone else, it's not even there. Same directory, the same customers, but a view that matches what each person actually needs to do.

Same client · two roles
Commercial liaison
NumberCLI-024
Ext codeNW-44218
StatusActive
Customer-care lead
NumberCLI-024
Ext code(Hidden)
StatusActive
Set who owns it once — works across every customer in the directory.
Statuses that match real life

Active, Prospect, Inactive, Former.

Prospect captures pre-contract relationships so the system can hold a customer record before the contract is signed. Active is the in-flight relationship. Inactive sits between contract pauses. Former preserves the audit trail when a relationship has fully ended. The directory grows with the relationship — never deleted, just retired.

Client status lifecycle
ProspectPre-contract; held for early linkage.
ActiveCurrently shipping or contracted.
InactiveNo current contract; kept searchable.
FormerRelationship ended; preserved as record.
What you build for them

The parts, and everything that happened to them.

A client links to the products you build for them — many-to-many, so a part sold to three customers says so, and a customer with forty parts has all forty on one profile.

That link is what makes the account view worth opening. A non-conformance raised against a part is a non-conformance that reached this customer, and it lands on their profile without anyone tagging it twice. When they call about a shipment, the history is already assembled.

Their paperwork sits alongside it. A customer’s quality specification or purchasing clauses can be registered as a controlled document tied to that client — approved, versioned, searchable, and on a Documents tab on their profile, so the terms you are held to are as controlled as the procedures that meet them.

Apex Aero · products
PRD-118Hydraulic manifold assemblyRev C · current
PRD-121Manifold assembly, high-flowRev A · current
PRD-204Service kit, field replacementRev B · current
Every NCR raised against these parts is already on this profile.
Cross-module rollup

Every customer NCR, every customer audit, every action — already attached.

Nine modules can name a client: NCR, Audit, MOC, Exemption, FMEA, Risk, Meeting, JHA, and controlled Documents. The link is bidirectional — the client profile shows the record, the record shows the client. When an account manager asks “how have we performed for them this year?” the answer is one click, not a spreadsheet.

Actions roll up differently, on purpose. An action never attaches to a customer directly — it belongs to the record that raised it. So the actions on this profile are the ones hanging off their NCRs and audits, which is what stops “what are we still doing for this customer” becoming a second list somebody has to keep current.

Northwind Aerospace · linked records
NCR-2026-0411Customer complaintSurface finish out of spec on lot LH-220819 Apr · Toledo
AUD-2026-009Customer auditAnnual on-site quality audit · 2 minor findings02 Apr · Birmingham
NCR-2026-0388Customer complaintWrong revision on shipped drawing · single unit11 Apr · Toledo
ACT-2026-0205Action · via NCR-0391Update customer-furnished material handling SOPIn progress · Toledo
MOC-0102MOCTooling change to address recurring complaintApproved · Toledo
Filter by facility, status, or module — same set of records, queried from the client's side.

The customer record your account managers actually use.

Linkable, filterable, scoped, permission-aware. Built so the next account review writes itself.

Customer audit type, picker required

Picking the Customer audit type makes the client picker required, so when the customer comes to audit you the right client is captured at creation rather than tagged on later.

NCRs attached to customers

An NCR can be attached to a client from the create form's optional Client picker. Once attached, the NCR shows up on the client's profile rollup — one click from an account manager's question to the answer.

The right people, every time

Decide once who owns customer records, who maintains the vendor codes, and who handles facility relationships. The directory keeps the lines clean throughout.

Make every customer one record, not three drawers.

What you build for them, what went wrong, and how you answered — one profile, ready before they ask.