When this is the right route.

For incidents that stop or seriously disrupt production, despatch, compliance output or another business-critical operation.

Report an incident when

  • Production is stopped.
  • Despatch is stopped.
  • Labels needed for compliance or despatch can’t be produced.
  • Several lines or sites can’t label.
  • A critical labelling workflow is seriously disrupted.

A standard enquiry is better for

  • Planned template changes.
  • Feature questions.
  • Cosmetic label adjustments.
  • Standard printer configuration.
  • Planned upgrades.
  • Projects that can be scheduled.

Send a standard enquiry

Where the fault can sit.

The symptom shows at the printer or the scanner; the cause can sit anywhere in the chain behind it, often at a join between two systems.

  1. Business systems

    1. 01 Business systems and data

      An ERP, WMS or MES change, a failed interface or a missing record

    2. 02 Product and master data

      A field the label needs that is missing, incomplete or in the wrong format

  2. Labelling

    1. 03 Templates and labelling rules

      A changed template, or a rule that no longer selects or fills the right label

    2. 04 Label management and integrations

      A stopped service, an expired licence or certificate, a broken connection

  3. At the point of print

    1. 05 Print services and queues

      A stalled queue, a stopped print service or a changed driver

    2. 06 Printers and devices

      Media, ribbon, calibration, firmware or the network connection

    3. 07 Operational workflow

      A changed process, user permissions, or the step that triggers the print

Fig. 1The chain behind a printed label, with the kind of fault that can stop it at each stage.

How an incident runs.

Each stage ends with something defined, starting with your incident reference.

  1. 01

    Report

    You submit the form below. It asks only for what triage needs.

    ProducesAn incident reference

  2. 02

    Triage

    We review the operational impact and the technical information supplied. If we can’t take the incident, we say so.

    ProducesA decision to accept, decline or refer

  3. 03

    Accept and confirm

    If we accept, we confirm the commercial terms and the access required. No chargeable work begins until they are agreed.

    ProducesAgreed terms and first steps

  4. 04

    Investigate and stabilise

    Diagnosis across the chain, then work to restore operation and verify output. A system can be running again while the underlying cause remains.

    ProducesA record of what changed and what was verified

  5. 05

    Summary

    The probable or root cause, the changes made, the risk that remains and the recommended next action.

    ProducesAn incident summary

Commercial terms are confirmed before work begins.

After triage we confirm availability, the proposed response, commercial terms and the access required.

Availability

Emergency requests can be submitted at any time. Production-critical incidents are reviewed ahead of standard enquiries. Availability and response timing are confirmed when Sysnaro accepts the incident. Submission does not itself create a guaranteed response time or support SLA. Out-of-hours assistance may be available, but Sysnaro does not currently provide a guaranteed 24/7 service.

After the incident

The recommended next action may be nothing further. Where the incident points to a wider problem, it may be remediation, a labelling health check, or label management, modernisation or integration work, scoped separately.

Report an incident.

Six questions are required. Everything else is optional, so send what you know now.

01 Who you are and what it’s affecting

Their name and phone number.

Is production or despatch stopped right now?
02 What happened

What people are seeing: for example labels not printing, wrong data on the label, or scans failing.

For example: 06:40 today, or since the start of the night shift.

Software updates, template or data changes, new printers, network or server work. “Nothing we know of” is a useful answer.

For example orders held, despatch cut-offs at risk, or a manual workaround in place.

03 Technical environment

All optional.

Copied exactly, if you can, including any codes.

Can remote access be made available? (optional)

This form takes no attachments. If we accept the incident we’ll agree a secure way to share screenshots, logs and access.

Do not send credentials

Do not submit passwords, API keys, access tokens or other credentials through this form or by email.

Leave out personal information from labels and records

Do not include patient, customer or other personal information copied from labels or records. Describe the issue without identifying individuals.