CUSTOMER CASE · WEIGHING, LABELLING & SYSTEM INTEGRATION

Dingdong Grocery — Weighing & Labelling System Integration Case Study

At food production facilities associated with Dingdong Grocery, NCN implemented more than an integrated weighing and labelling machine. The installed system connects production tasks, product records, label templates, measured weights, label printing and application, and execution data returned to the business system. The project has operated for several years, with software and labelling rules revised as business requirements changed.

Dingdong GroceryWeighing & LabellingProduction Task RetrievalAPI IntegrationLabel Template ManagementResult Data ReportingLong-Term Operation & Updates
Dingdong Grocery Food Production Site with NCN Weighing and Labelling System
On-site image: NCN weighing and labelling equipment at a Dingdong Grocery-related food production site. This case focuses on how production tasks, label generation and data interfaces work behind the machinery.
The aim was not simply to print a measured weight on a label. The equipment needed to use tasks defined in the customer’s business system and return weighing and labelling results to that data flow. When the equipment, products, labels and business system share reliable data relationships, weighing and labelling can operate as part of the production process.
PROJECT BACKGROUND

Why Connect the Weighing & Labelling Equipment to Dingdong Grocery’s Business System?

A multi-SKU food factory manages not only packs of differing weight but also product codes, production tasks, work groups, label templates, QR-code rules and master data. Re-entering this information at the machine can create a second, inconsistent set of records.

In this project, the weigh-price labeller acts as the execution station, while label management software, the database and API services provide the data layer. The operator enters a group identifier to retrieve the labelling tasks assigned to that station, selects the product, then runs weighing and labelling. Execution data is returned according to the defined interface.

Business System

Production tasks are defined in the host system

Products, materials, jobs and group information do not need to be recreated as separate business logic on the machine.

Production Equipment

The weigh-price labeller performs the physical operations

After retrieving the job, the machine captures the weight, generates label data, prints and applies the label, then sends results back to the system.

SYSTEM WORKFLOW

How Do Production Tasks Become Returned Labelling Records?

Operators confirm the current job; product records, measured weights, labelling rules and result reporting form one connected process.

01Enter Group IdentifierConfirm the current production group
02Retrieve Labelling JobRead product details assigned to the equipment
03Select ProductOpen the current product’s labelling screen
04Dynamic WeighingRead weight data from the weighing system
05Generate & Print LabelProduct data + actual weight
06Apply LabelMachine applies the printed label
07Return Labelling DataSend results back to the business system
SYSTEM ARCHITECTURE

More Than a Stand-Alone Machine: Business System, Label Software, Database and Weighing Equipment

The customer’s third-party business system exchanges data with NCN’s local label management software through interface services. The label system handles label design and templates, master data, database records, printing services and weighing equipment monitoring, then communicates with the on-site weighing and printing devices.

This architecture separates business data from machine actions. The host system defines what to produce, the local software converts the job into weighing and labelling operations, and the equipment reports its execution results.

Why Is This Arrangement Suitable for Ongoing Operations?

Product records, label rules and interface logic can be maintained as business requirements change, without mechanically modifying the equipment for every change.

Dingdong Grocery System Architecture: Business API, Label Software, Database and Weighing Equipment
System architecture: third-party business systems exchange data through an interface service with the label management system, which coordinates label design, templates, database, printing services and weighing equipment monitoring.
PRODUCT & LABEL DATA

Labels Are Generated from Product Records and the Measured Weight — Not Stored as Fixed Images

Product master data can include product name and code, sales and packaging specifications, storage conditions, instructions for use, applicable product standards, shelf life, manufacturer, label template, nominal weight, upper and lower weight limits and weight units.

Print-command templates are maintained within the system, with NiceLabel used for label design. At printing time, the machine combines the current product, its master data and the actual measured weight to generate the final label.

  • Link each product to the correct label template
  • Maintain multiple label command templates
  • Use the measured weight as a variable in label generation
  • Configure nominal weight and upper/lower limits by product
  • Capture weight data in grams and convert the displayed or printed units based on product settings
  • Query and export printing history
ProductProduct Codes, Names & Master Data
TaskJob Numbers, Group Identifiers & Production Tasks
TemplateProduct Label Templates & Print Rules
WeightActual Weight, Nominal Weight & Limits
QR / BarcodeProduct QR-Code & Barcode Rules
HistoryPrint, Exception & Labelling History
WEIGHT CONTROL

A Measured Weight Is Not Automatically a Printable Weight

The system evaluates each reading against the limits configured for the current product. A reading outside those limits does not proceed through normal label printing; it is recorded in the exception or rejection history. Accepted readings are formatted using the product’s unit and display settings.

01 · RANGE CHECK

Upper & Lower Weight Limits

Readings outside product-specific limits are not printed as ordinary accepted-product labels.

02 · UNIT CONVERSION

Gram / Kilogram Conversion

The source data is in grams; label units and decimal places follow the product settings.

03 · HISTORY

Exception & Print History

Printing and exception records support on-site lookup, reprinting and troubleshooting.

LONG-TERM OPERATION & ITERATION

Business Requirements Continue Changing After Years of Operation

A long-running system must accommodate new product data, label formats and shop-floor practices, not merely function on its first day of commissioning.

Continuous Operation

Equipment and software used in daily production

Weighing, label generation, printing, application and production-task data exchange have become part of normal operations rather than a one-off trial.

2025 · LABEL RULE UPDATE

Two-Line Product Name Fields

For long product names, the master record was extended with Name 1 and Name 2 fields, each referenced separately by the label template.

2025 · TARE LOGIC

Tare Field & Net Weight Calculation

A tare field was added to product records; business-use weight is calculated as scale reading minus tare weight to meet updated site requirements.

PROJECT VALUE

What Does This Case Demonstrate?

01

Equipment-to-Business-System Integration

Production equipment follows jobs defined by the business system instead of maintaining a separate product database indefinitely.

02

Product, Weight & Label Matching

Actual measurements and product records are used together when generating labels.

03

Returning Execution Results

Applying the label is not the end of the process; results are sent back according to the interface specification.

04

Ongoing Software Maintenance

Product name layout, tare handling and label rules can be revised after the system enters production.

ENGINEERING VIEW

The Key Question for Integrating Weighing Equipment Is Not Simply Whether It Has an API

Define the Relationship Between Data and Physical Operations

Equipment IDs, work groups, product tasks, label templates, weight limits, barcode rules, printing status and returned results each need a clear data owner, trigger point and exception-handling rule. Without those definitions, an interface may work in a test but fail as part of continuous production.

Can the Weighing & Labelling Equipment Retrieve Tasks from MES, ERP or WMS?

Integration is possible where the customer’s system provides suitable interfaces. The interface specification, task fields, equipment identification, triggers and exception handling must be confirmed for the project.

Must a Product’s Label Template Be Redesigned for Every Job?

No. Products can be associated with label templates and the correct template selected for the current task. New rules may require software changes depending on the content and printing logic.

Can the Software Still Be Changed After Years of Production?

Yes, subject to the project architecture and operational requirements. Here, two-line product names and tare-weight handling were added after the system had been in use.

EXPLORE MORE

Related Equipment & System Capabilities

Need to Connect Weighing & Labelling to an Existing Business System?

Share production task fields, label samples, product master data and interface specifications. We can then assess how the machine and data systems should interact.

Discuss System Integration
纽才纳微信二维码 微信扫码咨询 可发送产品照片、视频及标签样张
电话咨询
电话咨询

微信扫码咨询

可直接发送产品照片、现场视频、标签样张及其他项目资料。

纽才纳微信二维码

发这些资料,方案判断会更快

资料不齐也没关系,可以先加微信沟通。

1 产品照片或现场视频
2 产品尺寸、重量范围
3 生产速度或每分钟节拍
4 标签尺寸、内容及贴标位置
5 现场布局、MES / ERP接口需求
纽才纳微信二维码