configurability within uncountable

Configurable lab software your super users own

Fields, tests, workflows, calculations and document templates are configuration in Uncountable, set up by your own super users in the interface. A new method with its own units and limits. A test condition that changes from one grade to the next. A certificate template for one market. The real build work is integrations.

A new test method, live across six sites
Units that differ by material family
Integrations scoped before you sign

Deployed by 200+ enterprise product development teams

Lohmann logo with green abstract cross and tagline The Bonding Engineers in black text.
Dow company logo with white text on a red diamond-shaped background
Syngenta company logo with a green leaf above the letter g.
Beiersdorf
Clariant
Braskem company logo with stylized yellow and blue arrow design.
Total Energies Logo
St Jude Logo
Lubrizol company wordmark logo with blue curved line underneath the text.
Lohmann logo with green abstract cross and tagline The Bonding Engineers in black text.
Dow company logo with white text on a red diamond-shaped background
Syngenta company logo with a green leaf above the letter g.
Beiersdorf
Clariant
Braskem company logo with stylized yellow and blue arrow design.
Total Energies Logo
St Jude Logo
Lubrizol company wordmark logo with blue curved line underneath the text.

Deployed by Enterprise R&D and Innovation Teams

By the time the change request comes back, the project has moved on

On most platforms, a new test method or an extra field on a form is a ticket. It gets scoped, queued behind other customers, and lands in a release; and in the meantime the lab keeps a spreadsheet so the work can carry on. Configuration that only the vendor can touch isn't flexibility; it's a queue with your name on it.

In Uncountable, the change is made by the people who know why it matters: the formulators, lab managers and quality engineers who already know why one grade is tested at a different temperature than the next, and which of your labs needs to see it. What's left for us is the work that genuinely needs engineering: integrations into ERP, LIMS, instruments and the systems you built yourself. That work is scoped and agreed before you sign.

User interface for Rheometer Flow Test uploader with uploader details including name, allowed file extensions, detection keyword, and enabled material families. Example file demo-instrument-sample.xlsx shows parsed data table with channels: test, replicate, temperature (c), viscosity (pa.s), and shear rate (1/s). Extracted data panel displays output configuration extracting viscosity from viscosity (pa.s) with no transformation and output labeled Viscosity (Pa.s).

What it looks like when your own team owns it

A field takes about a minute. A handful of named admins covers a site. One lab's workflows become the template for the rest.

“Adding a field is a one-minute task.”
R&D lead, global specialty materials manufacturer
3-4
super users maintain the configuration for 60-80 people at a construction chemicals manufacturer.
1 Site
builds the workflows; three more reuse them through gap analysis at a multinational materials science company.

What you can configure without us

Each one is a setting in the interface. The four stages below show how each is set up, and who it reaches.

Custom fields on any data entry form
Test methods, units and spec limits
Workflow stages and transition rules
Calculated columns and formulas
Request and sample entry forms
Document, label and certificate templates
Display units per material family, with personal overrides
Separate configurations per business unit
Role-based configuration permissions
Versioned configuration with a full change log

Configuration, from the first field to the audit trail

Four stages: adding what you measure, adapting how work moves, generating the documents you send, and governing who is allowed to change any of it.

Add the field, the test or the calculation and have it on every form the same afternoon.

‍

Fields on any form: add what your scientists actually record, to the forms they already use.

Tests, methods and limits: a new method with its own unit and spec limit, shown only on the forms that need it.

Test conditions per product: the same method run at 210 for one grade and 100 for another.

Calculated columns: the equation that currently lives in a spreadsheet, written onto the record and run on every row.

Request and sample entry forms: the form someone fills in to ask for work, shaped around what your lab needs to know up front.

Display units per material family: with personal overrides, so each site reads what it's used to while the stored value never changes.

User interface displaying a Parameters table with columns for Name, Resolved Units, Quantity Type, Is Global, Always Use Dropdown, and Notes, showing various parameters like analyte, isotope, volume in mL, pressure in psi, and flow rate in mL/min with checkboxes for global and dropdown usage, along with notes for Method, Shear Rate, and Test Temperature.

Change the route without rewriting what the old records say.

‍

Stages and transitions: add, rename and reorder stages, and restrict which workflow is allowed to follow which.

Who can advance what: set the role that moves each stage on, and who can send one back.

Review gates: require a sign-off where the risk warrants it, and drop it where it only slows a team down.

What a stage needs to close: the fields, attachments and approvals that have to be in place before work moves on.

Versioning rules: major and minor versions, numbered to match the quality system you already run.

Hide what nobody uses: a team sees the handful of workflows it runs, not the hundreds the business has.

Phase Workflows interface showing a workflow with phases: Draft, In Review, Ready for Processing, In Progress, Reporting, and Complete, each in colored boxes connected vertically. To the right, additional phases 'Request for new testing' and 'Closed' are horizontally connected to 'In Progress' and not in the main vertical flow. Tabs for Phase Diagram, Phases Listing, Transitions Listing are above the diagram, and buttons for Add phase and Transitions are below. The right panel shows details for 'Formulation & Testing Request' workflow with options to copy workflow and reorder phases.

Your label, your certificate, your report, built against your own fields.

‍

Labels, CoAs and data sheets: built by your quality team against your own fields, not hand-created each time.

Your own layout: headers, logos, column order and page furniture set to match the document you send today.

Conditional blocks: a declaration that appears only on EU shipments, a result row that appears only for adhesives.

Customer and region variants: one template, as many versions as your markets and your largest customers need.

Printable quality forms: non-conformance reports carrying disposition, quantity affected and the rationale behind it.

Pull in the supporting record: notebook pages, SOPs and safety data sheets attach to the document that references them.

User interface screen for configuring a Certificate of Analysis template labeled 'CoA — EU retail', version 2.3, template 14 of 98. It lists template blocks with their data sources and visibility: Header & site logo (Site record, Always), Batch identity (Batch, lot, date, Always), Result table (Released test results, Always), Peel 180° row (marked NEW, Test methods, Adhesives only), Declaration (Regulatory library EU, EU shipments), and Signature block (Approver e-signature, On release). A blue Publish button is at the top right. Footer notes 'Built by your quality team · 98 templates across 4 regions'.

Self-service, with the controls a regulated site needs.

‍

Super-user permissions: you decide who can change what, and nobody else can.

Versioned and attributed: every configuration change carries a version, an author and a timestamp.

Separate configurations per business unit: one instance, without one unit's forms landing on another's screens.

Scoped by site: publish a change to one lab or to all of them.

Audit-ready: the change log exports alongside the records it affected, for 21 CFR Part 11 and Annex 11 work.

A configured starting point: implementation hands your team a working setup, not an empty platform.

User interface screen showing an Edit TriggerAction popup for a static standard lab request, with fields for selecting type as Invite Portal User, user email set to lab-contact@example.com, portal form ID, action description for a 7-day link for partner lab, action name to invite external lab, access duration of 7 days, write permission, user groups selection, disabled checkbox, and buttons for Return Variables, Action Constraints, Change Target Entity, and a Save button.

Your team takes the keys at go-live

Discovery & scoping

Map how your labs actually work, which systems hold what, and which of your "custom" requirements are configuration.

Configuration & migration

We set up the starting configuration with you (methods, spec limits, workflows, templates) and bring your legacy data across.

Super-user enablement

Your named super users are trained on the configuration they'll own, on your own setup rather than a demo instance.

User acceptance testing

Structured scenarios drawn from real workflows, run by the people who will use them.

Go-live & hypercare

Cut over with embedded support, and the first few configuration changes made alongside your team.

You take it from here

New methods, fields and templates are yours to add. We're there for the integrations and the structural work.

Support doesn't end at go-live
Dedicated account manager
Priority support, manufacturing SLAs
Quarterly business reviews
Continuous updates, guided rollouts

The real build work is integrations, so we scope it first

Most of what sounds like a build is configuration your own team owns. What genuinely needs engineering is the connection to the systems around you, and that lands in one place.

Chat conversation with four white text bubbles from user LT asking about adding fields to data entry forms, needing a different label template, setting test conditions per product with specific viscosity, and separate configurations per business unit; followed by a blue response bubble confirming the team can configure all these without a ticket.
Chat conversation with messages from LT asking about building integration with SAP, homegrown system, device count, cost, and auto-creation of test samples in LIMS, followed by a reply stating, 'We build these — scoped before you sign.'
Already connects to
SAP · bi-directional
Dynamics 365
Business Central
Oracle Fusion
JD Edwards
LabWare LIMS
MES
400+ instrument types
AnIML · Allotrope
Document stores
Homegrown systems
OPC-UA · MQTT
REST API · Python SDK
Your team configures it
No ticket, no code: real customer asks.
“If we need to add a field to one of the data entry forms, can we do that ourselves?”
“We need a different label template. It would be so nice just to be able to make your own.”
“Can users set test conditions per product: viscosity at 210 rather than 100?”
“We want separate configurations per business unit.”
We scope and build it
Scoped before you sign. Never on your license or renewable ARR.
“SAP, in both directions.”
“Would you be willing to build something to go alongside our homegrown system?”

What changes when your team holds the controls

Cost
Stop paying for change requests
A new field or method is an afternoon's work for someone you already employ. So is a unit conversion, a certificate variant for one market, or a workflow that lost a stage.
A build doesn't become a subscription
You pay for that work once, as part of implementation. It doesn't change what you pay each year after.
speed
A change takes one afternoon
The lab stops keeping a parallel spreadsheet while it waits for the system to catch up.

‍
New sites inherit a configuration that already works
Roll out what one site proved rather than starting the argument again.
Risk
No private version to maintain
Your configuration sits on the product everyone else runs, so upgrades arrive on time and arrive intact.
‍
An answer when an auditor asks
You can show an auditor the exact configuration a batch was released under, and everything that's changed since.

Configuration you change yourself. Integrations we build with you.

A platform that can be configured only by its vendor isn't configurable: it's a queue. The line between what your super users own and what genuinely needs building is the most useful thing a vendor can tell you, and you should know where it sits before you commit.

FAQs

Can our own team add fields and tests, or does it go through Uncountable?

Your team. Fields on data entry forms, test methods, spec limits, calculated columns, workflow stages, and report, label and certificate templates are configured by your named super users in the interface. There is no ticket to us and no release cycle between deciding and doing.

What still needs Uncountable to build it?

Integrations, mostly: ERP and LIMS connections, parsers for proprietary instrument formats, and connectors to homegrown systems. A smaller number of feature requests also become builds, and those go onto the core roadmap rather than into a private version of the product. We scope this work before you sign.

If everything is configurable, won't it overwhelm our users?

Nobody starts from an empty platform. Implementation delivers a working configuration built around how your labs already run, and scientists see the forms for their own work rather than the options behind them. Configuration controls are limited to the super users you name.

Who maintains the configuration after go-live?

Your named admins. Implementation hands over a working configuration and the training to change it, and from then on new methods, fields, workflows and templates are added by your team. We stay involved for integrations, structural changes, and anything that genuinely needs engineering.

What is the difference between configuration and customisation?

Configuration is a setting in the product: your team changes it, and it carries forward through every upgrade. Customisation is code written for one customer, which somebody then has to maintain, and which can strand you on a version only you are running. Almost everything on this page is configuration. The work that genuinely needs building goes into the core product rather than a private version of it.

Does a feature built for us put us on a separate version?

No. Work we do with you goes into the core product and is maintained there. You stay on the same release as every other customer, and your configuration carries forward through upgrades.

Get a platform that fits your process, not the other way round

Book a 30-minute intro call and see how Uncountable would be configured to your materials, tests and workflows.

Book an intro call
200+ customers · We reply within 30 minutes during business hours
Not ready for a call?