Shimadzu vs. Agilent HPLC

Shimadzu and Agilent both offer current HPLC and UHPLC systems, detectors, software, consumables, and services. Neither manufacturer is the better choice in every laboratory. A defensible comparison starts with the controlled method, required system configuration, installed data environment, and work needed to keep the system supportable over its life.

Portfolio and software context was checked against official manufacturer sources on July 21, 2026. Exact modules, drivers, software versions, service terms, and regional availability must be confirmed for the proposed configuration.

Start with the laboratory decision

Situation	Compare first
Replacing one established HPLC	Method history, column, detector, gradient delay, dispersion, injection behavior, data files, and qualification or transfer work.
Adding to a single-brand fleet	Method portability, staff familiarity, shared spares and consumables, CDS control, reporting, and local service coverage.
Standardizing a mixed fleet	Analytical fit first, then control drivers, data review, method migration, training, support ownership, and retirement costs.
Moving from HPLC to UHPLC	Column and particle size, pressure, system volume, gradient behavior, detector cell and rate, sample handling, and revalidation risk.
Building a new laboratory	Method and evidence requirements, throughput, detectors, software architecture, utilities, training, and lifecycle budget.

If the method, detector, or system class is not yet defined, begin with the HPLC overview, detector selection guide, and HPLC product-family map.

Map the current portfolios to a system class

Agilent’s current Infinity III LC portfolio includes the 1260 family for analytical HPLC and HPLC/UHPLC bridge configurations and the 1290 family for higher-pressure, lower-dispersion, high-throughput, or specialized work. The modular platform can be assembled from pump, sampler, column, detector, and application-specific options. Agilent HPLC and UHPLC systems 🔗 Agilent 1260 Infinity III LC 🔗

Shimadzu’s current portfolio includes integrated i-Series HPLC and UHPLC systems and modular Nexera systems spanning routine through higher-pressure and application-specific workflows. This creates a choice between an integrated configuration and a modular system as well as a choice between performance tiers. Shimadzu HPLC and UHPLC 🔗 Shimadzu i-Series 🔗 Shimadzu Nexera series 🔗

These portfolio descriptions are not equivalence claims. Compare the quoted modules and flow path, not an i-Series, Nexera, 1260, or 1290 family name in isolation.

Compare the configured method

Decision factor	Questions for either manufacturer
Pump and gradient formation	Is the method isocratic, binary-gradient, or quaternary-gradient? Which mixer, dwell volume, flow range, solvent selection, and pressure behavior must be reproduced?
Injection and sample handling	What volume range, vial or plate format, cooling, wash sequence, carryover control, and unattended capacity are required?
Column environment	Which column chemistry, dimensions, particles, preheating, temperature range, and switching or regeneration functions are method-critical?
Detector	Does the method require VWD, DAD/PDA, fluorescence, refractive index, aerosol-based detection, mass detection, or another response? Which cell and acquisition settings support the peaks?
Wetted materials	Are pH, salts, buffers, biomolecules, adsorption, corrosion, or metal-sensitive analytes relevant to the complete flow path?
Throughput	Is the bottleneck run time, injection cycle, sample preparation, equilibration, review, maintenance, or instrument availability?

A headline pressure, precision, carryover, or sensitivity figure applies under its published conditions. It cannot rank two different configurations for a method using different samples, columns, gradients, detectors, or acceptance criteria.

Treat method transfer as experimental work

A method can change when gradient delay, extra-column dispersion, mixer volume, injection solvent, needle wash, temperature control, detector cell, data rate, or integration rules change. Continuity within one manufacturer does not eliminate these effects, and a cross-manufacturer transfer does not fail merely because the labels differ.

Create a transfer inventory before selecting the replacement: controlled method, column and guard column, mobile phases, injection program, wash solvents, temperature settings, detector parameters, system-suitability criteria, processing method, calculations, report, standards, blanks, and representative samples. Then evaluate the proposed systems using a predefined transfer or verification plan. Chromatograms from a supplier demonstration are useful only when the configuration and acceptance criteria reflect the laboratory’s method.

Compare OpenLab and LabSolutions at the workflow level

Agilent positions OpenLab CDS 🔗 for chromatography acquisition, processing, reporting, and data management across supported Agilent and third-party instruments. Shimadzu presents LabSolutions within its software and informatics portfolio 🔗 for analytical-instrument data workflows. A brand-level statement does not establish compatibility.

For either data system, verify:

exact instrument modules, control drivers, CDS release, operating system, database or workstation architecture, and license;
acquisition functions, processing algorithms, calibration models, custom calculations, report templates, and supported file exchange;
user roles, audit records, electronic review or signatures, backup, retention, disaster recovery, cybersecurity, and upgrade ownership;
how existing methods and historical data will remain readable, reviewable, and supportable after migration;
whether mixed-vendor control covers every required function or only basic acquisition.

The cost of rebuilding methods, reports, interfaces, permissions, and validation evidence can outweigh a hardware price difference. Test the actual workflow with representative users rather than comparing screenshots or feature lists.

Include detectors, consumables, and expansion plans

The base LC rarely represents the final operating system. Compare the configured detector and its lamps, cells, acquisition limits, and maintenance. Inventory columns, guard columns, fittings, capillaries, seals, needles, filters, vials, plates, and solvent-handling parts that are standardized in the laboratory. Separate genuinely method-specific consumables from items that can be qualified across suppliers.

If LC-MS, automation, online sample preparation, multidimensional LC, purification, or centralized data management is likely, evaluate that future interface now. Both manufacturers span LC and LC-MS workflows, but compatible modules, software, sources, and responsibilities must be confirmed for the exact system. The LC-MS product-family map explains why analyzer role and front-end requirements should be resolved before model selection.

Compare lifecycle support locally

Service quality cannot be inferred from the brand name. Ask both suppliers the same location-specific questions:

Which quoted modules and software versions can local personnel support?
What installation, qualification, training, preventive maintenance, response, remote-support, and parts arrangements are offered?
Which tasks can laboratory staff perform, and which require supplier service or controlled documentation?
How long are modules, consumables, operating systems, drivers, and data systems expected to remain supported?
What are the costs and operational consequences of software upgrades, instrument moves, requalification, loan equipment, and eventual data migration?

Record contractual answers separately from general portfolio claims. A strong local installed base may reduce training or spare-parts burden, but it is evidence about the laboratory context, not universal manufacturer superiority.

A defensible comparison record

Build the final decision record around the proposed configurations:

Define mandatory methods, samples, detectors, throughput, and acceptance criteria.
List every quoted module, accessory, software component, license, consumable, service item, and exclusion.
Run representative standards, blanks, and samples under an agreed evaluation protocol.
Document transfer differences, required method changes, data migration, training, qualification, and downtime.
Calculate lifecycle cost over the laboratory’s planning horizon, including internal labor and transition work.
State why the selected configuration fits this laboratory without generalizing the conclusion to other laboratories.