Every serial, one line
Serial, verdict, operator, device, location, UTC timestamp and the scope revision in force at that moment. Searchable by serial number years after the action closed.
Live sort-action console
QuantusScan — containment readiness for every part, at every site
every part accounted for
06:12 — the complaint lands: one lot, four production days, 17,000 units.
2,000 on your dock, 5,000 in transit, 10,000 inside four customer plants.
Not one of them looks any different from a good part.
By 08:00 the customer wants a containment statement: how many checked, how many bad. QuantusScan is how you already know.
Built by engineers and quality leaders with OEM and supplier experience in the USA, Germany and beyond. Meet the team
This is a generic quality incident, not a real case.
Automotive, medical, food, pharma, electronics, consumer goods — the sector does not matter.
What matters is a lot or serial ID readable as a barcode, QR code or data-matrix code.
If the defect is traceable but invisible on the part, the response is always the same.
The day the complaint lands, side by side.
Six moments decide what an incident costs. Here is how each one changes, and where on this page you can check it.
First sorted part
Usual way after 2 days of set-up
With QuantusScan: < 1 hour
The four steps · 01
Scanners on the floor
Usual way 8 handhelds, shipped in
With QuantusScan: Every phone on shift
The scanner · 04
Status for your customer
Usual way emails, compiled by hand
With QuantusScan: One live number
The live console · 03
Scope change mid-action
Usual way re-brief every site, re-sort
With QuantusScan: New rule on the next scan
Try “Expand scope” · 03
Evidence for the 8D
Usual way pieced together afterwards
With QuantusScan: Writes itself while you sort
Audit evidence · 06
Cost of one example incident
Usual way $251k
With QuantusScan: $39k
Calculator defaults · run your own numbers · 07
00 · Site map
Where does this land on your desk?
Choose your side of the incident. We mark the sections that answer your questions first, in the order that makes sense for you — every other section stays one click away.
Your route
All chapters
On your route · your choice also sets the live console in chapter 03 to the matching view.
Lost later? The chapter pill at the top always shows where you are and opens this list.
Start reading01 · Management summaryThe whole case in two minutes.→
01 · Management summary
What it does, and why it pays.
The whole product in one screen, for the person who has to approve it and does not intend to read the rest of the page.
How it works, in a nutshell
STEP 01
Define what is suspect
Serial ranges, lot IDs, production time windows, station numbers — or upload a list. Minutes, not an IT project.
STEP 02
Send one link per location
Your plant, a 3PL, a customer site, a sorting service. They open it and are in. No app store, no hardware, no rollout.
STEP 03
Teams scan the code
Any phone, tablet or existing handheld reads the barcode, QR or data-matrix code. The answer is two words: clear or suspect.
STEP 04
Everyone sees the same number
Every scan lands in one live view within a second, worldwide. The audit evidence builds itself while you sort.
QuantusScan never decides whether a part is good — your engineering does that once, when it defines the scope. We remove everything in between.
Why it pays
Elapsed since the complaintDay 0.0
Calculator defaults from chapter 07: 17,000 parts, 30 sorters, 8 handhelds, 2 days of set-up the usual way, 48 hours of stock at the customer. Run your own numbers.
Where it hurts today
Coordinated the usual way
With QuantusScan
Status of the action
Compiled by hand, hours old
Live to the second, one screen
People who can sort
Capped by handheld scanners
Set by your staffing and your plan
When the scope changes
Phone calls, shift by shift
In force on the very next scan
Time to first sorted part
Days, waiting on equipment
Under an hour, at every site
What you tell the customer
An estimate, revised hourly
A figure with a timestamp
Chasing the status
Email and phone ping-pong, all day
Nobody asks. It is on the screen
Logistics and planning
Stale figures, so planners buffer
Live coverage, so they reschedule
Expedited freight
Booked defensively, just in case
Booked only where data says so
Line-down risk
Discovered when the line stops
Seen while there is time to act
Escalation meetings
Called because nobody trusts it
Rarely needed, all see the same
Several actions at once
One spreadsheet each
One portfolio, ranked by risk
Proof six months later
Rebuilt from emails, if at all
Exported in one click
What it changes at your desk
QualityYou answer with a number and a timestamp, not an estimate that ages.
Plant managementYou learn which lines are genuinely at risk hours earlier.
Production planningYou reschedule on live coverage instead of buffering blind.
LogisticsYou expedite only what the data says must move — not everything.
FinanceThe biggest numbers in an incident turn out to be the avoidable ones.
PurchasingSupplier containment performance becomes visible, not anecdotal.
Sales & customer teamsYou arrive with proof instead of an apology and a promise.
The sorting teamsOne link, any phone, a two-word answer. No training day.
The bottom line
Next chapter02 · The problemWhy does a sort action slip, even at a good supplier?→
You are not buying scans. You are buying readiness.
When the call comes, your sites, your teams and your customers’ access already exist. The first part is sorted within the hour — not after days of equipment, lists and briefings.
The sorting itself costs roughly the same either way — the same parts get checked by the same people. What changes is elapsed time and certainty, and that is where the money in a quality incident actually sits: the customer line that did not stop, the air freight you did not book, the good inventory you did not scrap defensively because you could finally prove it was good, and the suspect part that never reached the field.
One avoided line-down shift typically pays for years of readiness.
02 · The problem
How far does one bad lot travel?
One incident, three depths. The first is the version that reaches the customer. The other two are why sort actions go wrong.
A generic incident, walked from the first email to the invoice.
No real company, part or customer is described anywhere on this page.
Read “control unit” as whatever you ship: an implant, a food batch, a harness, a board.
The only requirement is a lot or serial ID a camera can read off the part or its label.
Most people stop at the first level. The other two are where the money is.
Level 00 · The email
03 · The live console
One screen. Every location. Right now.
Same live data, two sides of the fence. The supplier runs the action and watches every customer, site and scanner. The customer sees where their own parts are and how many are sorted — as soon as the supplier grants view access.
No view access yet
Locations in action QS-4471
Event stream
Generated data, so you can break it without booking anything. Toggle a customer’s access in the supplier view, then switch to the customer view as that customer — that is exactly what they would see.
Third parties, without the phone tree
Invite a 3PL, a sorting provider or your customer's own quality team to one location. They never see the rest of your action.
Time zones stop mattering
Every event is stored in UTC and shown in local time. Night shift and morning shift work from the same number.
Several actions at once
Each keeps its own scope, teams and evidence trail, ranked by what is closest to hurting a customer line.
Any code you already print
Data-matrix, QR or 1D barcode — whatever your traceability put on the part. No relabelling before you start.
04 · The scanner
The scanner is already in their pocket.
Eight handhelds means eight sorters — the ninth waits. Any phone runs it, so scale is a staffing decision again.
QS-4471Online
Sorting for
ECU-8813 rev C
Scope rev 1 · 3 supplier lots
Ready
Point the camera at the data-matrix code on the housing.
No training day
Open a link, pick your station, scan. The verdict is two words and a color, because the person holding the phone is wearing gloves in a cold aisle at 2 a.m. A temp agency crew is productive in five minutes.
Scope changes reach the aisle in seconds
New findings widen the lot window? Change it once in the console. Every connected device picks up the new rule on the next scan — no briefing, no reprinted list, no parts cleared against yesterday's criteria.
⚡ Try it: press Expand scope in the console above, then scan again. The verdict changes on the spot.
The aisle has no signal. That is fine.
Scans queue on the device and upload the moment it reconnects, each one keeping the timestamp of when it was actually taken. The count is never wrong, only briefly behind.
Nothing gets scanned twice
Every serial is unique, so a re-scan is recognized instantly and reported as a duplicate rather than inflating the number. Your completion figure means what it says.
05 · The supply chain
One standard, all the way down the chain.
The moment your suppliers run their containments the same way, you stop being told what happened and start watching it happen.
Material flow
Live containment status, scoped per action
If you are the customer · OEM
Risk you see, not risk you are told
Ask your suppliers to run containments in QuantusScan and every one arrives in the same structure, with the same coverage figure, live.
Escalation stops being a matter of tone. You can see whether a supplier is at 12% or 94%, which location is lagging, and whether the parts heading for your line have actually been cleared — in time to reschedule instead of in time to apologise.
Put it in the supplier quality agreement once and it applies to every future incident, from every supplier, without another negotiation.
If you are Tier 1
You sit on both sides of it
Downstream you prove containment to your OEM in real time instead of defending an estimate. That beats any apology on a scorecard.
Upstream, you can require the same of your Tier 2 and Tier 3. A sub-supplier's problem then reaches you as a live action you can watch, not as an email three days after their sorting started.
You also stop absorbing their uncertainty: when a component maker can show exactly which lots were cleared, you no longer block your own stock defensively to be safe.
If you are Tier 2 or Tier 3
Meet the requirement with a link
Adopting a customer's system usually means a project. Here it means an account and a scope. No hardware, no integration, no training week.
And you get the tool itself, not just the obligation: the same live control, the same evidence pack, on your own incidents where no customer is watching.
It is also the cheapest credibility available. A supplier who can show coverage live is a supplier who keeps getting quoted.
What sharing actually means
Next chapter06 · Audit evidenceSix months later, the auditor asks you to prove it.→
Being in the loop is not the same as opening your books.
Access is granted per action and can be narrowed to the locations that concern that customer. Each customer sees their own parts, live. Everything else stays yours.
The supplier switches that access on and off per customer, at any time. If you are an OEM rolling this out across a supply base, we run that as an programme rather than as a stack of individual contracts.
06 · Audit evidence
The evidence pack writes itself.
The record is a by-product of the scanning, not a project after it. An action you cannot document is an action you did not do.
Append-only by design
Corrections are recorded as new events carrying an author and a reason. Nothing is ever silently overwritten, which is exactly the property an auditor sets out to test.
8D-ready export
One click produces the containment section of your 8D: scope, coverage, findings, escape analysis and the full scan register, as PDF for the file and CSV for your systems.
Audit-ready by default
Supports the traceability and containment records expected under IATF 16949 and customer-specific requirements, in a form your quality team can hand over unchanged.
Closing an action
What lands in your quality file
Generated at close-out, or at any point during the action if the customer asks for an interim statement. Everything is dated and versioned, so an interim pack and the final pack can never contradict each other. Export formats depend on your plan.
containment_summary.pdf
scan_register.csv
coverage_by_location.pdf
scope_history.pdf
operator_log.csv
07 · Your numbers
Run your own numbers.
The subscription is never the interesting number. The day you did not lose and the line-down hour you did not fund are.
Your incident
Defaults describe a mid-size Tier-1 containment. Everything here is your input — we do not assume a defect rate, a recovery or a saving on your behalf.
Side by side
QuantusScan plan for this action
Coordinated the usual way
—
—
With QuantusScan
—
—
| Cost driver | Usual way | QuantusScan | Delta |
|---|
How we calculate — assumptions you can argue with
08 · Readiness & pricing
You pay for readiness. The scans come with it.
Incidents don’t book appointments. Your plan keeps everything set up between them, so the first part is sorted within the hour when the call comes. Projects, scans and parallel scanners are the capacity you have on the day. Pay annually and save 10% on every plan.
Included in every paid plan
What stays ready between incidents
Your sitesPlants, 3PLs and customer sites are set up before anything happens.
Your teamsSorters and sorting providers already have their link and know the two-word verdict.
Your customers’ accessWho may watch which action is settled in advance — not on the phone at 06:12.
Your first hourOpen an action, set the scope, scan. No purchase order, no hardware, no rollout on the day.
Not ready yet? Emergency activation. If the call has already come and you are not a customer yet, we
can open a
single action on an annual plan and have your first team scanning the same business day.
— tell us the part, the
locations and the volume, and we will come back with a start time, not a quote request.
Next chapter09 · Who we areWho stands behind it when the call comes?→
09 · Who we are
We have been on both ends of the complaint.
Behind QuantusScan are engineers and quality leaders with many years in high-volume manufacturing, at OEMs and at suppliers, in plants around the world.
Between us, we have handled customer complaints and containments, led audits, managed escalations and fixed the processes behind them. We built QuantusScan for exactly those days.
One team across the USA and Germany, with one focus: solve the real problem, keep the cost calculable and make the value visible from the first day.
What the team brings
- Dr.-Ing.Doctorate in engineering
- Dipl.-Wirt.-Ing.Industrial engineering and management
- Engineering degreesUniversities in Germany and the United States
- Both ends of the supply chain
- International experience at OEMs and at suppliers.
- Quality and manufacturing
- Many years in high-volume production, complaint and process management.
- When it escalates
- Problem solving, audits and escalation management, face to face with the customer.
- One team
- USA and Germany · QuantusScan CORP, Summerville, South Carolina.
What we hold ourselves to
Solve the real problem
We start from the morning the complaint lands, not from a feature list.
Keep the cost calculable
Every number on this page comes with its arithmetic. Change the inputs and check it yourself.
Make the value visible
The first sorted part, the first live count and the first line of evidence, within the hour.
Respect both sides
We know OEMs and suppliers from the inside. Each side gets its own view, and the supplier decides what is shared.
10 · Questions
Questions you will be asked internally.
Short answers you can paste into the approval email.
What do we actually pay for when nothing is happening?
Readiness. Between incidents your sites, your teams and your customers’ access stay set up, so the next action starts within the hour instead of after days of equipment, lists and briefings. Projects, scans and parallel scanners are the capacity you use on the day — the subscription is what makes that day short. One avoided line-down shift typically pays for years of it.
Do we have to connect it to our ERP or MES first?
No. An action needs three things: the part identifier, the scope rule, and the locations. You can create it by hand in a few minutes and start scanning. Integration is an improvement, not a prerequisite — on the Enterprise plan you can push scope from your QMS and pull results back into your ERP once the urgency has passed.
How is scope defined?
By whatever your traceability actually gives you: serial ranges, production date-time windows, supplier lot numbers, station or line identifiers, or an uploaded list of serials. Rules combine, and every change creates a new numbered revision that stays in the record.
What if a plant will not let personal phones onto the floor?
Common, and fine. QuantusScan runs the same way on plant-owned tablets, on the rugged Android devices most warehouses already have, and on existing handhelds with a browser. The point is not phones specifically — it is that you are never blocked waiting for a device to arrive.
Who owns the data?
You do. Your scan records are yours, exportable at any time in open formats, and deleted on your schedule when you leave. We do not sell, share or aggregate customer quality data, and we never use it to train anything.
Can our customer see our whole quality history?
Only what you deliberately share. A customer link is scoped to one action, and can be limited further to the locations that concern them. They see coverage and findings for their own parts, live. Everything else stays yours.
What happens to parts already flagged suspect?
They are held against the serial, not against a sticker. The device tells the sorter what to do with it — quarantine bin, rework cell, scrap — and that disposition is recorded. If a suspect part is scanned again anywhere in the action, it is recognized and blocked again.
Can we require our suppliers to use it?
Yes, and several customers approach it that way. It is written into the supplier quality agreement like any other containment requirement, and because adoption costs a supplier an account rather than a hardware rollout, it is a requirement they can actually meet on the day you ask. Talk to us before you write the clause — we run supply-base rollouts as a programme, with pricing and onboarding built for it.
How fast can we actually be live?
An account and a first action, under an hour. A properly briefed multi-site action with customer access, typically the same day. The constraint is your scope definition, not our setup.
The next call is not a question of if
Get ready on a quiet Tuesday, not at 06:12 on the day it matters.