Product · Supplier Quality Management

Supplier quality management (SQM) software

Track corrective actions through all eight steps, part approval through its phases and elements, and supplier audits — with your suppliers answering in the same place.

One record per issue and per programme, with every decision attributed to the person who made it. Part approval is checked where it counts: a receipt for a part awaiting approval does not pass.

Issue QA-20714 · raised and issued Illustrative
Against
A supplier and a part
Priority
High · critical carries shorter clocks
Containment due
From your own settings
Full response due
From your own settings
Issued to the supplierTheir contacts notified, and the clocks start hereNotified
Human decisionA quality engineer raises it — nothing opens a case on its own
Containment · submitted, then judged Illustrative
Supplier submits containmentIn the portal, against the step it belongs toSubmitted
Your quality team is notifiedIt arrives on their queue rather than in an inboxQueued
Specialist acceptsOr returns it with what is missing — the supplier is told either wayReturned
Who decidedThe person, their role and the time, on the issue’s own logRecorded
Human decisionContainment adequacy is a judgement, and no model makes it
The eight steps · on one record Illustrative
System updatedTeam, problem, containment, cause, action, implementation, prevention, closure
Part approval · checked at the dock Illustrative
Order raised for a part needing approvalThe submission record is created for youCreated
Eighteen elementsTracked as what has arrived and what has notTracked
Goods receipt, approval not yet givenRefused on the receipt itselfRefused
Approval givenReceipts proceed from that pointClear
Rule appliedThe one place part approval stops something, by design

With a priority, and deadlines computed from your own settings when it is issued.

The same corrective action. An email chain, or a record.

Most supplier quality still runs as a spreadsheet of open issues and a folder of attachments nobody else can find.

A spreadsheet of open issues
One record per issue
A spreadsheet of open issuesThe eight steps live in a document template
One record per issueAll eight are fields on the record, with the supplier filling their own
A spreadsheet of open issuesEvidence arrives as attachments to a reply
One record per issueThe supplier uploads against the step it belongs to
A spreadsheet of open issuesDeadlines are whatever the email said
One record per issueResponse deadlines are set from your own settings when the issue is issued
A spreadsheet of open issuesWho approved what is a memory
One record per issueEach decision carries the person, their role and the time
A spreadsheet of open issuesPart approval status lives with one engineer
One record per issueIt is checked at goods receipt — an unapproved part does not pass
A spreadsheet of open issuesProgramme milestones sit in a project plan
One record per issuePhases, deliverables and sign-offs are tracked on the programme record

The response

Eight steps. All eight on the record.

Not a template attached to an email. Each step is a field on the issue, filled in by whoever owns it, with the supplier working their own in the portal. Quality teams will know this format as 8D.

Who is on it The team

Who is working the issue on both sides, recorded on the issue rather than implied by the email thread.

What is wrong The problem

The problem described against the 5W2H structure — who, what, where, when, why, how and how much — so what is wrong is stated the same way on every issue.

Stop it spreading Containment

What the supplier has done to stop the problem reaching you, submitted in the portal and reviewed by your team before the investigation continues.

Why it happened Root cause

The cause the supplier identified, with an optional five-why chain and cause categories drafted for them to work from.

What to change Corrective action

The action chosen to remove that cause, submitted against the issue rather than described in a reply.

What was done Implementation

What was actually put in place, and what validated it.

Stop it returning Prevention

The system changes and training meant to stop it recurring — the step that usually gets lost in an email chain.

Sign it off Closure

The closing notes, recorded with the person who closed it, their role and the time they did it.

How an issue runs

Six steps. Every judgement is a person.

The product carries the record, the deadlines and the notifications. It does not decide whether containment was adequate, and it does not pretend to.

  1. 01 Human

    A quality engineer raises it

    An issue is raised against a supplier and a part, with a priority and an optional response date. An approved intake request can also open one — a goods-receipt issue, a corrective action, or an environmental and social concern someone escalated.

  2. 02 System

    Issuing it sets the clock

    When your team issues the issue to the supplier, containment and full-response deadlines are computed from your own organisation’s settings and the supplier’s contacts are notified. Critical and safety issues carry the shorter pair.

  3. 03 Human

    The supplier answers containment

    They fill in the containment step in the portal and submit it, and your quality team is notified that it has arrived.

  4. 04 Human

    Your team accepts it, or returns it

    A quality specialist reviews containment and either accepts it or returns it to the supplier with what is missing. The supplier is notified either way. That judgement is a person’s, and the product records who made it.

  5. 05 Human

    The supplier completes the investigation

    Root cause, corrective action, implementation and prevention, submitted together. Your team reviews those the same way — accept, or return with a reason.

  6. 06 Human

    A named role closes it

    Closure sits with your internal quality and procurement roles, and the closing notes, the person and the time are written to the issue’s own log.

Core capabilities

What supplier quality management (SQM) software has to get right.

The eight-step corrective action

The whole response on one record, with the supplier filling in their own steps

  • Team, problem, containment, root cause, action, implementation, prevention and closure
  • The supplier works their own steps in the portal — no account chasing, no attachments by email
  • Containment is reviewed and accepted or returned before the investigation goes on

Deadlines from your own settings

Containment and full-response clocks your organisation sets, not ones we impose

  • Defaults of forty-eight hours for containment and thirty days for the full response
  • Critical and safety issues carry a shorter pair — twenty-four hours and twenty-one days
  • Both are configurable per organisation by your administrators

APQP programmes, phase by phase

The five standard phases with their deliverables tracked against each one

  • Around five deliverables per phase, each marked mandatory or optional
  • A risk register scored on severity, occurrence and detection, and control-plan lines as real records
  • Supplier sign-off and your own sign-off captured separately on each phase

Phase gates with a readiness view

A recorded gate decision, with the evidence for it in front of you

  • Approve, approve with conditions, or reject — each recorded against the phase
  • A readiness view shows deliverable coverage and outstanding risks before you decide
  • An approved gate starts the next phase, so the programme moves without a second step

Part approval, element by element

All eighteen submission elements, tracked as what has arrived and what has not

  • Part submission warrant, dimensional results, material tests, control plan, failure-mode analyses and the rest
  • Submission levels one to five recorded on the record, with a readiness view per level
  • A programme reaching its part-approval phase can start the submission with its files carried over

Approval checked at goods receipt

The one place part approval actually stops something

  • A receipt for a direct-material line is refused while that part’s approval is not approved
  • Raising an order for a part flagged as requiring approval creates the submission record for you
  • Checked on the receipt itself, so it cannot be missed by whoever is on the dock

Audits and questionnaires on the record

The audit history and the self-declarations, against the supplier rather than in a folder

  • Audit number, type, scope, dates, auditor, findings, nonconformance count, score and next audit date
  • Your worklist surfaces audits coming due in the next fortnight
  • Questionnaires you compose or take from a template, answered by the supplier in the portal

Drafting help that never decides

Model assistance on the slow parts, with every decision still a person’s

  • A five-why chain, cause categories and failure-mode estimates drafted for the supplier to work from
  • Uploaded documents checked and marked for a reviewer’s attention, never approved or rejected on their own
  • A written brief before a gate or a part-approval decision — advice, recorded as advice

Features

Supplier quality management software that holds its own rules.

Five groups of features, and not one of them depends on someone remembering the policy.

The checks that refuse, and the clocks that run

One hard check, two deadline settings, and decisions restricted to named roles.

  • A goods receipt for a direct-material line is refused while the part’s approval is not approved
  • Raising an order for a part flagged as requiring approval creates the submission record
  • Containment and full-response clocks are computed when the issue is issued to the supplier
  • Critical and safety issues carry the shorter pair of deadlines
  • Closure is restricted to your internal quality and procurement roles

What is on the record

Who did what. And when they did it.

  • Every corrective action records its creation, each update, the moment it was issued, each supplier submission, each acceptance or return, and its closure.
  • Every programme records its creation, each gate outcome, each signature, each upload, each review and each waiver.
  • Each of those entries carries the person, the role they held and the time. Not a system user, and not a mailbox.
  • Containment adequacy, root-cause acceptance, gate outcomes and part-approval decisions are all human judgements. No model makes any of them.
  • Where a model drafts a five-why chain or checks an uploaded document, what it produces is advice for a reviewer. Nothing it says approves, rejects or closes anything.
  • The closing notes on an issue are written to its log with the person who closed it, so a closure can be explained months later.
  • Response deadlines come from your organisation’s own settings, and the shorter pair for critical and safety issues is part of those settings rather than ours.

Two issues. Two different shapes.

1

Porosity found on a cast component

A quality engineer raises the issue against the supplier and the part, sets it to high priority and issues it. Containment and full-response deadlines are computed from your settings and the supplier is notified. They submit containment in the portal; your team is notified, reviews it, and returns it once for more detail. The supplier then completes root cause, corrective action, implementation and prevention together. Your team accepts it, and a named role closes it with notes recorded against the issue.

2

A new part going through approval

The programme is created against the part and the supplier, and the five phases arrive with their deliverables already on them. The supplier uploads as they go, and each document is checked and marked for a reviewer rather than passed automatically. Supplier and customer sign-offs are captured per phase, and the gate decision is recorded with its readiness view alongside. Once the programme reaches its part-approval phase, the submission is created with the mapped files carried across — and until that submission is approved, a receipt for the part does not pass.

Where it fits

It owns the quality record. The supplier record sits next door.

The supplier record belongs to supplier management

Identity, onboarding, certificates and the hold or block that stops a buyer transacting are held there. This module holds the issues, the programmes, the submissions and the audits against that supplier.

Suppliers answer in the portal they already use

Open corrective actions, programme deliverables, part-approval submissions, declaration requests and questionnaires all appear for the supplier in the same place, with no separate quality login.

Part approval reaches the receiving dock

The check that refuses a receipt for an unapproved part runs in procure-to-pay, on the receipt itself, which is why it needs the orders and receipts to be there.

Buyers see the open issues while they compare

Quote comparison shows the count of open corrective actions and part-approval status beside each supplier, so a commercial decision is made with the quality position in view.

Bring us one corrective action you are running now.

We will set it up with your own deadlines and show you the point where your specialist has to accept or return it.

Request a demonstration

Security, compliance and recognition

Checked by auditors. Judged by the industry.

Where each compliance programme stands, and what the procurement industry has given us so far.

Security and compliance

Awards

Five, presented on stage at three industry events.

  • Autonomous Procurement Platform of the Year
  • Procurement Technology Innovation Award
  • Unified Procurement and Supplier Management Platform
  • Procurement Startup of the Year
  • AI in Procurement or Supply Chain Award — Solution Provider

See the events and the trophies

Before you book anything. Answered honestly.

What is supplier quality management (SQM) software?

Supplier quality management software holds the quality work that happens between you and a supplier after they are approved — the corrective actions when something goes wrong, the part-approval programmes when something new starts, the audits and the declarations. The part that separates a useful one from a shared folder is whether the supplier works in it directly, and whether every decision in it is attributable to the person who made it months later.

What does the eight-step response actually capture?

All eight, as fields on the issue rather than a document attached to an email: the team, the problem stated in the 5W2H structure, containment, root cause, the corrective action, what was implemented and validated, the prevention work including system changes and training, and the closure notes. The supplier fills in their own steps in the portal and submits them, and your team accepts or returns each submission.

How are response deadlines set?

From your organisation’s own settings, applied when your team issues the issue to the supplier. The shipped defaults are forty-eight hours for containment and thirty days for the full response, with a shorter pair — twenty-four hours and twenty-one days — for issues marked critical or safety. Your administrators change both, so the clocks match the quality agreements you actually have.

Who can close a corrective action?

Closure is restricted to your internal quality and procurement roles, and it is a decision a person makes rather than a status something reaches. The closing notes, the person and the time are written to the issue’s log. Containment adequacy and root-cause acceptance are the same — a specialist accepts or returns them, and the product records which, by whom.

What does APQP tracking include?

The five standard phases, each arriving with its deliverables already attached and marked mandatory or optional. A risk register scored on severity, occurrence and detection, and control-plan lines, are real records rather than attachments. Supplier sign-off and your own sign-off are captured separately per phase, and a gate decision — approved, approved with conditions, or rejected — is recorded against the phase with a readiness view beside it. An approved gate starts the next phase.

How does part approval work?

All eighteen submission elements are tracked, from the part submission warrant through dimensional results, material tests, control plan, failure-mode analyses and the rest, with the submission level recorded on the record. The supplier uploads against each element in the portal, enters capability values, and responds to findings. A programme that reaches its part-approval phase can start the submission with its mapped files carried over.

Does part approval stop anything?

Yes, in one place and deliberately: a goods receipt for a direct-material line is refused while that part’s approval record is not approved. It is checked on the receipt itself rather than relying on somebody at the dock remembering. Raising a purchase order for a part flagged as requiring approval also creates the submission record, so the requirement is there before the first delivery is.

What do suppliers see?

Their own open corrective actions with the steps they have to complete, the programme deliverables assigned to them, their part-approval submissions, any material-declaration requests, and any questionnaires you have sent. They upload, respond and sign in the same portal they use for the rest of their relationship with you, with no separate quality account to maintain.

One issue. Eight steps.

No slides. Your deadlines, your roles, and the receipt that will not pass until the part is approved.

Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.