Packaging codes in China: follow the information to the line
Research Chinese packaging marking systems through batch data, template changes and supplier responsibilities. Prepare questions for manufacturers and integrators.
Article language: English

In this article
The printer applied the number without hesitation. The problem was that it was the previous one. The machine did what it was told, the package looks tidy, and someone watching the demonstration video has no reason to spot the error. Before discussing a marking system offered in China, it is a good moment to ask about something less spectacular than speed: where does the printed content come from?
Imagine a plant packing craft-material kits. This is a fictional example. Halfway through the day it finishes one batch and starts another, with similar packaging but a different marking. The team is researching equipment and software suppliers. We are not setting marking parameters or assessing legal label requirements. We are preparing a description of the task to take to the appropriate providers.
A batch number does not appear through the printer's courtesy
The inquiry “batch-number printer” lacks at least two pieces of information: who determines the number and how it reaches the machine. In one organisation a person selects a prepared message. In another an external system sends specified fields. Both can describe marking, but they call for very different discussions with a supplier.
On its HAE-4000 product page, HAE discusses date and number coding in general and lists PC communication and remote control as options. What a particular configuration supports and how data is transferred to the line require separate confirmation with the supplier.
This example permits a more precise question. Is our number an externally transmitted field, the result of a counter, or part of a previously prepared template? The answer describes the source of information. Only then can we discuss whether the specified model supports the necessary route and who will prepare it.
In the fictional plant, the date on the packaging stays the same while the batch marking changes. Setting the current date therefore does not solve the issue. Show two actual field meanings in the discussion material rather than one screenshot of a string of digits. The supplier should understand what stays constant, what changes and which company decision triggers the change.
Also describe an empty value. If the number has not yet been determined, the field should be identified as missing in the agreed workflow. A person preparing a demonstration who inserts zero on their own can turn missing data into apparently complete information. The design question then becomes: who notices the absence and makes the next decision? Do not guess the behaviour of a machine that has not been checked.
The Polish-language guide to product catalogue content models (in Polish) explains why a field's name, meaning and source need separate definitions. Here we are describing information to be applied, rather than building a commercial catalogue. The same discipline helps when two systems exchange a field called ‘code’ but understand it differently.
Keep product, batch and individual-item identifiers separate when they appear in the task. A worker may know that the item is “that blue kit”, while software needs an unambiguous value. Agree on the meaning using your own example. Do not create a new product identification merely to fill every box in a form you received.
In our example, a batch marking might begin with zeros. “0038” and “38” may look similar to someone reading a message, but the company needs to decide whether they mean the same thing. Show the value exactly as it is to be understood, including permitted characters and spaces. This describes your requirement without attributing support for an unconfirmed format to the machine. Also provide an incorrect example and explain the difference. Then “compatible” refers to particular content, not just the presence of a print.
A job change has a location worth finding
Our plant finishes packing one batch, but packaging prepared for the previous job is still at the station. Discuss this situation with the line's operator. Which event signals a task change to the marking system, and how is it linked to the correct items?
“Change the number at noon” is too broad if the operation occurs in several places. The planned time of the change, the transmission of new content and its use on a particular package are separate events. The team needs to describe them to establish the offer's boundary. Choosing technical safeguards and acceptance methods belongs to the appropriate specialists.
Show a normal flow and one exception in the inquiry. A change has been approved, but the material at the station does not match the new job. Ask which part of the proposed solution recognises that relationship, if any. “Our printer can print both numbers” does not yet cover the whole problem.
Prepare two sample templates and explain their difference. They need not contain real plant data. Use them to show different jobs: a different batch number, product variant or intended recipient of a package. The material should show the meaning of the change, not merely that the program can save another file.
The Polish-language article about warehouse robotics in China (in Polish) starts by identifying the unit moved by the equipment. Marking likewise requires naming the object: an individual product, an outer package or another carrier. Their markings can serve different purposes. The same content placed in two locations does not necessarily carry the same information.

After the discussion, retain the answer in a form that can be handed to the next person. “Supports a batch change” is weaker than a description stating that specified fields come from a named source and their use concerns an agreed task. If part remains undecided, name the person who needs to be consulted. “Supports” alone will not identify who is responsible for the missing part.
With two stations, also describe the reach of the change. One may already be doing the new job while the other finishes the previous one. We do not assume how their work is organised. We want to know whether the supplier's answer concerns one device, a group of stations or a shared template. Keep that scope beside the function name in comparison material. Central management will then not accidentally be read as the ability to switch everything in the hall simultaneously at will. Your own example also helps check whether everyone understands “line” in the same way.
Software and equipment may have different owners
On its Chinese page for Automation and Designer, Domino describes central template management, version control and approval procedures. It also mentions information transfer through connections with systems and databases. These are functions stated for its own solution. They do not confirm a ready connection to a particular installation or the availability of every element in every configuration.
In discussion, distinguish preparing the template from preparing its values. A graphic designer may be responsible for the layout, someone in production for the batch number, and another provider for transferring the data. Assign each task to the person who actually performs it and can explain the result.
A division of roles can help with a smaller task too. The article on Korea's smart-factory ecosystem (in Polish) distinguishes equipment manufacturers, integrators and users. They may meet at one station without making the same promise. China's market requires its own research; the Korean example helps name the differences between roles.
Ask for the software scope in the proposed offer. Is the supplier showing a template editor, a tool for transmitting templates, or a wider approval workflow? If a partner answers, check which elements are its work. This makes it possible to compare meaningfully an equipment-only proposal and one that also includes preparing a particular connection.
Keep template versions linked to their task. The label “new” is insufficient if someone returns to the material a month later. They should be able to tell what changed and which version was agreed. This is a requirement for clear project documentation. It does not decide the technical implementation or whether the platform handles it without additional work.
Also establish what confirmation the person sending the content expects. A template may be ready without having been sent; a sent template need not have been used. A message saying it was sent should not turn into a report that a particular package received the correct marking. Ask the supplier what evidence its scope provides and what requires another part of the solution. If there is no answer, retain the unknown. The team can then avoid judging three suppliers against three different meanings of “confirmed”.
A neat print answers only some questions
A sample can show a particular result for a specified material and content. If a different substrate or simplified template was used, record the difference. Link the demonstration to a specific question before someone treats it as confirmation of the entire intended application.
The article on board-game production in China (in Polish) distinguishes individual components from the finished set. A box marking can similarly lack a link between the print and what goes inside. A correctly read code does not itself confirm that the package contains the correct product version. Mark in the project description whether that check is part of the expected task.
When packaging returns to circulation, the relationship between an existing marking and its next use needs attention. The Polish-language guide to reusable B2B packaging (in Polish) explores a separate return cycle. Do not automatically assign the method used for a single-use box: discuss the material, package history and intended use with an appropriate provider.
When researching the market, distinguish a manufacturer's offer from a solution available with local support. A company found may supply equipment or work with partners, but a public catalogue does not explain the entire support chain. In the map of parties, record who offers which scope and what still needs to be learned before the next stage.
Do not compare technology names alone when the tasks differ. First establish the carrier, content, source of the change and boundary of expected support. Only such a description lets appropriate specialists relate solution parameters to the particular situation. Market research provides material for that assessment without pretending to have performed it.
In a comparison, mark equipment, software, connection preparation and agreed support separately. Companies need not charge for them identically. If one offer covers only a selected element, retain it within that boundary. A difference in the visible price may result from a difference in scope rather than an assessment of quality. At the research stage the main need is a common subject of comparison and information about who can provide missing confirmation. Detailed terms of a particular order remain a conversation for the next stage.
With Aeneia Oriens, we can discuss research into Chinese suppliers of packaging marking solutions, taking your data flow into account. We would agree the research scope before work begins. The marking itself still needs to show the right information. The previous batch number may still look very neat. It is better left in the job history.







