A coding or labelling project rarely fails because the machine is wrong. It fails because nobody planned the line survey, the operators were never trained, the spare parts were not stocked, or the consumables were chosen for the wrong substrate. This page explains how MAISUI runs implementation and after-sales service – what we do, what you get, what we need from your team, and what to check before something stops the line.
Service at a glance
- Scope
- Management software (ERP / MES / WMS / SRM / MS7) and identification equipment (printers, TTO, CIJ, TIJ, laser, labeling, scanners, PDAs, displays)
- Service stages
- Process review, solution planning, implementation, commissioning, training, go-live support, maintenance
- Channels
- Email, phone, WhatsApp and remote video; on-site attendance is scheduled per project or service agreement
- Working languages
- English and Chinese engineering support
- Spare parts
- Quoted from the manufacturer’s parts list; recommended stock list agreed at commissioning
- Consumables
- Ribbons, labels, inks and cartridges matched to the substrate and the print head
- Training
- Operator, line engineer and supervisor tracks – on site or remote
- Contracts
- One-off implementation, start-up package, preventive maintenance, or a combined support agreement
Why service decides whether the project works
Most buyers compare hardware first: print resolution, speed, print area, price. In production, the difference between a line that runs and a line that stops is usually elsewhere – how the print head is mounted, whether the code was tested on your real substrate, whether an operator knows what to do at 2 am, and whether a spare print head is on the shelf or on a ship.
MAISUI supplies software, equipment and consumables, and then supports what we deliver. That means one team can answer a question that crosses all three: for example, why a code that reads perfectly on paper fails on a coated film, or why a warehouse system reports stock that the handheld terminal disagrees with. Our service work is organised around that reality rather than around a product catalogue.
What usually goes wrong – and the first thing to check
These are the situations we are called about most often. Before an engineer is dispatched, the first check is usually something the line team can do in minutes.
| Symptom | Likely cause | First action |
|---|---|---|
| Code is faint, patchy or missing dots | Print head contamination, low ink or solvent, wrong ribbon grade for the substrate | Clean the head per the manual, check consumable levels and the grade against the material actually running |
| Code position drifts when line speed changes | Encoder or trigger settings not refreshed after a speed change | Re-teach the print trigger and confirm speed matching; check that the encoder wheel is clean and in contact |
| Scanner cannot read a code that looks fine to the eye | Contrast, quiet zone, code height or print direction vs. scanner angle | Test with a verifier or a second scanner, check quiet zone and magnification, then adjust the code layout before changing hardware |
| Ribbon wrinkles, breaks or leaves gaps | Ribbon width or tension mismatch, worn rollers, wrong ribbon grade | Confirm ribbon width against the print head, check the tension path and roller condition |
| Printer will not start after a weekend or holiday | Dried ink, blocked nozzle, start-up routine not completed | Run the automatic cleaning/start-up cycle, check solvent level and ambient temperature |
| System quantity does not match the physical warehouse | Transactions posted without scanning, or units of measure mismatched | Freeze the item, run a cycle count, check UoM mapping between ERP and handheld |
| New SKU produces unreadable or rejected codes | Label template or code layout copied from another product | Re-test the code on the new packaging and confirm the template’s data source before release to production |
Four ways to work with us
Not every customer needs the same level of service. These are the four arrangements we quote most often; the boundary of each is written into the proposal so there are no surprises later.
| Engagement | What it covers | Best for | Typical outputs |
|---|---|---|---|
| Project implementation | Requirement review, line survey, equipment and software specification, configuration, data setup, commissioning, operator training and go-live support | New line, new factory, or a system replacing manual records | Configured system, trained team, commissioning report, recommended spare parts list |
| Start-up package | Unpacking and installation check, print test on your substrate, parameter baseline, first-shift operator coaching | Equipment bought for an existing line, where your team installs it | Working baseline settings, quick-reference SOP, first-line checklist |
| Preventive maintenance | Scheduled inspection and cleaning, wear-part replacement, consumable consumption review, firmware and settings check | Multi-shift production where an unplanned stop is expensive | Service record per visit, wear-part forecast, action list |
| Remote support and consumables programme | Remote diagnosis by video and photos, settings advice, spare and consumable replenishment, re-order planning | Single-site factories and customers in other countries | Resolved issues without a site visit where possible, predictable consumable supply |
How a project runs, step by step
| Step | What we do | What you get | What we need from you |
|---|---|---|---|
| 1. Process review | Walk the line, review current records, identify the data that must be captured and where | Written scope with priorities, risks and open questions | Access to the line, samples of every package type, and the people who run it |
| 2. Solution planning | Specify software modules, equipment, mounting, interfaces and consumables against the real substrate and line speed | Equipment and software list, interface diagram, quotation with lead times | Line speed, conveyor layout, available space, air and power, IT contacts |
| 3. Configuration | Set up master data, templates, user roles, print parameters and integrations | Configured environment ready for a trial run | Sample data, label artwork, ERP or WMS access for integration |
| 4. Commissioning | Install and align hardware, run code tests across the product range, tune parameters | Commissioning report with the tested settings per product | Production time window and product samples |
| 5. Training | Train operators, line engineers and supervisors on daily tasks, first-line checks and escalation | Trained staff, SOP and quick-reference cards | Named trainees and a quiet training slot |
| 6. Go-live and support | Stay available through the first production runs, then move into the agreed support mode | Stable running line, service record, spare parts baseline | A named contact and a channel for escalation |
What an implementation actually includes
When we quote an implementation, these are the deliverables we plan for. Items that are not needed are removed in the proposal, not silently assumed.
- Line survey covering speed, conveyor, space, air, power and ambient conditions
- Code test on real packaging, including curved, chilled, wet or dark surfaces
- Equipment mounting plan and print head alignment
- Software configuration, master data and user roles
- Interface mapping to ERP, WMS or line PLC where required
- User acceptance test with the production team before go-live
- Operator SOP, quick-reference card and escalation path
- Recommended spare parts list and consumable re-order points
- Backup and recovery routine for software and device settings
- Commissioning and training record for audits and handover
Support and maintenance, without the guesswork
Support works best when the first conversation includes the facts: what the line is running, what changed, and what the machine or system reports. We ask for a photo or short video where it helps, because most coding issues are visible in the print itself.
| Channel | Use it for | How it works |
|---|---|---|
| Quotations, documentation, orders, non-urgent questions | Send the model, application and photos; we reply with a recommendation or a formal quotation | |
| Phone | Line stopped or a decision needed quickly | Call the number in the header; we triage on the call and agree the next step |
| Photos, short videos, quick confirmation | Use the floating button; useful when a code or a label needs to be seen rather than described | |
| Remote session | Software configuration, settings review, operator refresher | Screen share or guided walkthrough at an agreed time |
| On-site visit | Installation, commissioning, mechanical work, training | Scheduled per project or service agreement, with a written scope before attendance |
Two habits prevent most emergency calls. First, keep a consumable and wear-part baseline: what is used per shift, and what the minimum stock is. Second, keep a simple log of changes – ink batch, ribbon grade, template edits, line speed changes. When something goes wrong, that log usually shortens the diagnosis from hours to minutes.
Training that sticks
Training is not a product demo. It is the difference between an operator who can recover the line and one who waits for help. We train three groups separately, because they need different things.
| Track | Audience | Content |
|---|---|---|
| Operator essentials | Line operators and shift leaders | Start-up and shutdown, message selection, code checks, consumable change, first-line cleaning, when to escalate |
| Line engineer | Maintenance and engineering | Print head care, parameter tuning, mounting and alignment, fault codes, wear-part replacement, test print interpretation |
| Supervisor and IT | Production supervisors, IT and warehouse system owners | Master data, user roles, template control, integration checks, backup and recovery, reporting |
Service notes by industry
Beverage, dairy and liquid filling
Wash-down, condensation and returnable glass are the three factors that decide ink choice and maintenance interval. Lines running several bottle types need the code tested on each one, not just the fastest product. Where filler OEM protocols are involved, plan the integration before the equipment arrives.
Cable, wire and extrusion
Codes must survive stretching, UV, fluids and vulcanisation, and the print head bracket has to be repositionable in seconds because product size changes during the shift. Agree the metering method and tolerance with the line team during commissioning rather than after the first rejection.
Frozen and dry food
Condensation on the pack is the usual reason a code smears or fails to adhere. Ink or ribbon grade, air knife, and the distance between the coder and the pack all matter. Test on packs taken straight from the freezer, not on samples at room temperature.
Pharmaceutical and healthcare
Code legibility, batch traceability and change control matter more than speed. Templates should be locked, changes recorded, and the verification step documented so an audit can follow the trail.
Warehouse and traceability
Most stock errors are data errors, not hardware errors: units of measure, duplicate item codes, or transactions posted without a scan. A short cycle count after go-live catches most of them before they reach the finance report.
Who does what
| Area | MAISUI | Customer |
|---|---|---|
| Scope and specification | Survey, recommend, document the scope and quotation | Confirm production targets and approve the scope |
| Equipment supply | Source, configure, deliver and document the equipment | Prepare the installation point: power, air, space, conveyor access |
| Installation | Install, align, commission and test with real products | Provide a production window and product samples |
| Training | Deliver the three training tracks and materials | Release named trainees for the agreed time |
| Production use | Support, advise and supply consumables and spares | Follow the SOP, keep the log, maintain first-line checks |
| Maintenance | Schedule preventive visits per the agreement | Provide access and report symptoms early |
Before you sign: questions worth asking
- Has the supplier tested the code on our real packaging and line speed?
- Who installs and aligns the equipment, and who pays for a re-visit if it is wrong?
- What exactly is included in the service agreement, and what is charged separately?
- Which spare parts should we hold, and what is their lead time?
- Who trains our operators, and do we get written SOPs?
- How are software changes controlled and recorded?
- What happens if the line stops at night or during a holiday?
- Can the supplier support both the equipment and the system around it?
Frequently asked questions
Do you support equipment you did not sell?
In many cases yes. Send the model, photos and the problem description; we confirm whether parts and documentation are available before quoting. For machines from brands we do not carry, support is limited to what the manufacturer’s parts and manuals allow.
Can you maintain printers and coders from other brands?
We service the brands we supply and can advise on common CIJ, TIJ, TTO and laser systems. Where a part is proprietary, we tell you the lead time before you commit.
Is support available in English?
Yes. Engineering and after-sales support are provided in English and Chinese, including remote sessions and documentation.
How quickly can a project start?
It depends on equipment lead time and site readiness. After the scope is agreed we confirm a schedule with the quotation, and we plan the commissioning window with your production team.
Do you train our operators?
Yes – operator, line engineer and supervisor tracks, on site or remote. Training is part of implementation and can also be booked as a refresher or for new staff.
Can maintenance be handled remotely?
Many settings and software questions can be resolved by video call and photos. Mechanical work, alignment and print head replacement normally need attendance, which is scheduled under the service agreement.
Do you supply consumables and spare parts?
Yes. Ribbons, labels, inks and cartridges are matched to the substrate and print head; spare parts are quoted from the manufacturer’s list, and we recommend a minimum stock level at commissioning.
What does a service agreement cover?
It defines response channels, preventive visits, wear parts, training refreshers and what is chargeable. The exact scope is written into the agreement so both sides know what to expect.
Can you support a line that runs several brands of equipment?
Yes. A mixed line is common; the practical limit is parts availability for each brand. We document what is covered and where a third-party service would be needed.
How do we start?
Send your application, line speed, packaging material and the problem you want to solve. We reply with a recommendation and a quotation within 24 hours on business days, and propose a survey if the line needs one.
Talk to an engineer
Describe the line: what it produces, the material, the code content and where it hurts today. We will tell you what can be solved remotely, what needs a visit, and what it will cost – before anything is ordered.