SPOT, DOPP and labelling

Import from the EAEU by road: DOPP, QR and labelling do not match

If transport data, the contract, invoice, universal transfer document, DOPP/QR data or labelling codes do not match, first identify where the discrepancy arose: shipment, electronic document, import tax documents or product data.

Describe the shipment and identify the documents needed See what to check first

QR status does not verifyDOPP does not matchlabelling codes are disputedshipment in transit

For an initial assessment, start with the goods, EAEU country, transport data, shipment stage and the DOPP/QR and labelling documents.

DocumentWhat to reconcileRiskNext action

contract / invoice

subject matter, EAEU tariff classification, delivery terms / Incoterms; check SPOT applicability separately

differences in delivery terms, price, goods or transaction details

compare the contract, invoice and transport data with the import tax documents and correspondence

transport documents

CMR/consignment note, origin and destination points, cargo, weight, packaging and seals

transport, cargo or carrier data do not match

compare the transport file with import documents, DOPP/QR data and supplier information

DOPP or QR

DOPP: number, date and status; QR: displayed status and connection to the shipment, goods and import documents

DOPP does not match the shipment or shipment data

check DOPP status and its link to the shipment

labelling codes

GTIN and, where relevant to the product group, serial or batch data, aggregation and code status in the labelling system

codes cannot be read, are not linked to the shipment or conflict with the documents

reconcile codes, status and documents before the next action involving the goods

QR status does not verifythe QR does not show the required status or conflicts with shipment dataDOPP does not matchDOPP data conflict with the shipment or import documentslabelling codes are disputedthe code status or link to the shipment is unclear from the system and documentsshipment in transitcheck the risk before the next action involving the goods

Where exactly do the data diverge?

Choose the point of discrepancy. The page then moves through the documents, risks and first action rather than a general practice description.

01DOPP mismatchnumber, date, shipment or status does not align with the transactionNext: compare DOPP with the contract, transport and import documents 02QR status does not verifythe code does not show the required status or link to the goodsNext: record the code check and identify the source of the discrepancy 03Chestny Znak codes do not match the documentsstock balance, placement into circulation or status does not match the documentsNext: open the import-labelling review 05EAEU supplier provided inconsistent datathe invoice, universal transfer document, transport data and shipment do not form one coherent fileNext: review the transaction-document chain 06The goods should not move to the next stage yetacceptance, placement into circulation or a response to the discrepancy may be risky without reviewNext: collect the minimum file before the next action involving the goods

Initial discussion

Documents for the initial assessment

At the first stage, the task is not to prove the entire case. Build a consistent shipment chronology from the documents, statuses and actions of the parties.

01goods, EAEU country and road-transport data
02contract, invoice, universal transfer document and shipment correspondence
03DOPP: number, date and status; QR: status check and link to the shipment
04CMR or consignment note, carrier details, seals and packaging
05labelling codes, GTIN and product-group data relevant to those codes

Where applicability must be checked

SPOT, DOPP and labelling depend on transport data, product group, document status and participant role. Deadlines, potential liability and correction procedures can be assessed only after checking the goods, transport, documents and applicable rules.

When this review applies

This scenario is limited to road imports from the EAEU where the goods and transaction fall within SPOT. A preliminary legal position requires the specific shipment documents and a check of the applicable rules.

What is happening

Do not assess the error from a single screenshot or the carrier's oral explanation. Compare the transport data, documents, product group, DOPP/QR status and labelling information before inconsistent explanations appear in correspondence, acceptance records or formal replies.

Where information usually diverges

the contract, invoice and transport data describe the shipment differently
DOPP or QR does not show the required status, or conflicts with shipment data
labelling codes are not linked to the shipment or conflict with the documents
it is unclear who entered, transmitted or should explain the data: supplier, carrier, importer or technical document-processing participant

What to reconcile now

contract / invoice: subject matter, EAEU tariff classification, delivery terms, price, currency and payment terms
transport documents: CMR or consignment note, origin and destination points, cargo, weight, packaging and seals
DOPP: number, date and status; QR: displayed status and link to the shipment, goods and import documents
labelling codes: GTIN and, where relevant to the product group, serial or batch data, aggregation and code status in the labelling system

When to act: Before the next action involving the goods: acceptance, placement into circulation or a response to the discrepancy, where relevant to the specific product group.

Materials on this issue

Continue with this topic

All articles