Contact

Bring the method, inspection risk, or balance requirement into the first conversation.

Shimadzu support is most useful when the inquiry includes how the instrument will be used and how the result will be defended. A short note about sample matrix, acceptance criteria, environmental limits, software needs, service interval, or qualification timeline allows the response to move beyond a generic catalog reference.

Specification DeskProduct and category fit

Use this path when the team is choosing between analytical, inspection, or weighing systems and needs evidence-oriented comparison.

Service DeskCalibration and repair planning

Use this path when the instrument history, certificate scope, uptime window, or post-service release check is the main concern.

Resources DeskDatasheets and application files

Use this path when procurement, quality, or laboratory leadership needs documentation before internal approval.

Request a structured reply

Include the product family, validation status, sample type, operating environment, and deadline. If the request concerns HPLC troubleshooting, UV-Vis comparison, portable X-ray review, or analytical balance qualification, mention the current model and the record type you need to produce. This context lets the response address the practical evidence problem instead of sending a broad product note. For new projects, the same form can be used to ask whether the category should be handled as laboratory instrumentation, inspection equipment, or weighing and force measurement.

For replacement projects, describe the current limitation rather than only listing the instrument name. Useful details include failed acceptance checks, unstable response, software access concerns, missing certificates, sample throughput changes, or inspection sensitivity disputes. For new laboratories, share the planned audit framework and the people who will rely on the file: quality, validation, maintenance, production, procurement, or research leadership. That information helps the answer separate optional convenience features from records that will be needed when the instrument is placed into routine use.

  • Attach method or acceptance criteria in the message field when possible.
  • State whether the request is for procurement, validation, service, or training.
  • Note the country or audit framework if documentation wording matters.