EUCDM 7.0.11: Which customs data is changing for China imports

On 27 August 2026, the European Commission released EUCDM 7.0.11. The model harmonises customs data elements and includes updates relevant to low-value consignments. For China importers, it is a timely reason to test master data and interfaces before a missing field appears in a live declaration.

Why procurement should care

Many errors occur because the invoice, ERP and broker describe the same goods differently. A shared record for SKU, maker, origin, value, weight and code reduces queries.

Low-value is not a separate universe

Data requirements for small consignments continue to evolve. Check that marketplace, carrier and customs software pass the same product identifiers and values.

Keep a versioned mapping

Record each EUCDM field, its ERP source, format and owner. That makes it clear whether a missing value comes from technology or the supplier.

Practical checklist

1. Review EUCDM 7.0.11 with the customs broker and flag changed fields.
2. Run the top 20 China SKUs through invoice, packing list and ERP exports as test cases.
3. Source descriptions and origin from approved master data instead of free text.
4. Add interface tests for returns, partial shipments and low-value parcels.

<!-- Longform expansion: research review 2026-09 -->

Decision frame for your import

EUCDM 7.0.11 is a data-model update, not a blanket change to tariff codes. The Commission describes harmonised data across NCTS, AES, ICS, CDS, EOS and national systems. For importers, the practical task is to bring master data, roles and message fields to the same version as the customs broker.

Data and document pack per item

Build a field matrix with your ERP label, EUCDM data element, format, mandatory status, source and transmission system. Check goods description, origin, consignee, authorisations, security data and attachment references. Structured XML and multilingual sections help technically, but they do not replace the legal check against the applicable Union rule.

• Document old and new field names side by side.
• Test mandatory fields with real import cases, not only dummy values.
• Version the mapping between ERP, broker portal and customs message.
• Record error codes, rejections and manual corrections by system.

A verification workflow from supplier to import

1. Select a representative China import declaration.
2. Trace every data field back to the EUCDM structure.
3. Test with the broker which fields are automatic, manual or not transferred.
4. Test low-value, transit and export cases separately because message paths differ.
5. Review one month of post-launch errors and refine the mapping.

A worked decision example

A retailer carries its old import template forward. The goods description is acceptable, but the structured message expects a different mapping and a mandatory special-case field. The test entry is rejected. A field matrix with owner, format and fallback would have exposed the problem before a live shipment.

Common failure modes and countermeasures

• Treating EUCDM as a substantive legal change — read data model and law separately.
• Testing only a standard import — add low-value and special procedures.
• Changing the broker portal without ERP and archive updates — keep one end-to-end version.
• Using vague free-text descriptions — keep technical characteristics and commercial description consistent.

Message to send to the Chinese supplier

The Chinese supplier does not implement EUCDM, but it supplies the source data:

Please use the same SKU, model and goods description on invoice and packing list as in our approval. Please provide origin, manufacturer, material and technical characteristics consistently. Please notify us before documents are issued of any change to item number, composition or packaging.

Release criteria for the file

A release is defensible only when four questions can be answered from the same record: What exactly was checked? Which SKU, batch, route or period does the statement cover? Which primary source or supplier document supports it? Who assessed the deviation and when is it reviewed again? Put those answers in the inspection report instead of marking a line only “passed”. Link the file to the order, sample and receipt. If evidence is missing, give the line an “open” status with an owner and due date. This keeps later corrections traceable and lets procurement distinguish evidence from assumptions.

Follow-up and recheck

Approval is not the end of the check. Set a trigger for the next review: a new batch, material or process change, an authority notice, a price or lead-time deviation, or the scheduled review date. A short monthly reconciliation of orders, supplier data and received goods catches drift earlier than an annual catch-up. When a deviation appears, hold the affected batch, obtain a written supplier response and reopen approval only after a documented corrective record.

<!-- Release template: research review 2026-09 -->

Internal release template

A check mark saying “reviewed” is not enough for this topic. In one short line, state that document old and new field names side by side.. Add the exact scope (SKU, batch, plant, shipment or period), the primary source and document version. The second line records the open assumption or deviation, its owner and due date. The third line records the release decision and which shipment or version remains on hold. Another colleague should be able to reproduce the decision without searching an entire email thread.

Conclusion

A data-mapping exercise costs less than repeated delays caused by inconsistent entries. Start with the China SKUs you import most and expand iteratively.

Frequently asked questions

Must a small importer reprogram immediately?

Not every company needs to change its own system. Ask the broker, ERP provider and carrier how relevant fields will be transferred.

Is EUCDM only a customs issue?

It is a customs data model, but it affects the master data and interfaces that feed your declaration.

Do I need to code EUCDM myself?

Not necessarily. You do need to verify that ERP, customs software and the service provider transfer required data correctly and with version control.

Are XML data automatically legally correct?

No. A valid format does not prove origin, classification or authorisation. Those contents still require a professional check.

Sources

• Europäische Kommission: EUCDM 7.0.11