{"id":2318,"date":"2026-08-27T17:16:18","date_gmt":"2026-08-27T17:16:18","guid":{"rendered":"https:\/\/supplierally.com\/uncategorized\/china-supplier-udi-gudid-evidence\/"},"modified":"2026-08-27T17:16:18","modified_gmt":"2026-08-27T17:16:18","slug":"china-supplier-udi-gudid-evidence","status":"publish","type":"post","link":"https:\/\/supplierally.com\/es\/uncategorized\/china-supplier-udi-gudid-evidence\/","title":{"rendered":"China Supplier UDI and GUDID Evidence: A Buyer Source Map"},"content":{"rendered":"

A buyer can receive a product label PDF, a carton photo, an identifier spreadsheet, a factory quotation, and a database screenshot from a China supplier, then find that none of the files clearly ties back to the same version or model. That is a record-control problem. It is not solved by adding more files to a shared folder.<\/p>\n

This guide organizes China supplier UDI and GUDID evidence<\/strong> as factual source material. It helps a buyer preserve what a supplier document says, where an identifier appears, what product or package the source names, and which links are still missing. It does not decide whether an item is a medical device, whether UDI rules apply, who is a labeler, whether an identifier is valid, whether data was submitted or is accurate, or whether a product may be imported, sold, or released.<\/p>\n

The boundary matters because similar-looking documents can support very different questions. A label image may show a code. A GUDID search result may display a Device Identifier, or DI. A purchase order may name a product. These sources can be placed side by side without treating any one of them as a conclusion. The useful output is a traceable source sheet that lets the responsible compliance, regulatory, quality, or legal owner review the actual record.<\/p>\n

Start with the source, not the conclusion<\/h2>\n

The U.S. Food and Drug Administration describes its unique device identification system as a way to identify medical devices sold in the United States through distribution and use. FDA says that a UDI generally includes a fixed Device Identifier and, when present, a variable Production Identifier. FDA describes the DI as identifying the labeler and a specific version or model; it describes possible PI elements as a lot or batch number, serial number, expiration date, manufacture date, or a distinct identification code in a stated HCT\/P context. 2<\/a><\/p>\n

Those descriptions give a buyer useful labels for a source index. They do not let the buyer decide what a code means on a particular product. A practical record should therefore capture the supplier’s own wording before anyone applies an interpretation.<\/p>\n\n\n\n\n\n\n\n\n
Source question<\/th>\nRecord the factual answer<\/th>\nKeep separate<\/th>\n<\/tr>\n<\/thead>\n
What item does the source name?<\/td>\nCopy the product name, model, catalog number, size, and revision as shown.<\/td>\nWhether the item is a device.<\/td>\n<\/tr>\n
What code appears?<\/td>\nTranscribe the visible code and retain the original image or file.<\/td>\nWhether the code is a UDI, DI, or PI.<\/td>\n<\/tr>\n
Who appears on the source?<\/td>\nCapture the entity name, address, and stated role.<\/td>\nWhether that party is a labeler.<\/td>\n<\/tr>\n
What database result is shown?<\/td>\nSave the search term, URL, access date, and result fields.<\/td>\nWhether a submission was required, complete, or accurate.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Use one record for one stated product version or model<\/h2>\n

A file list becomes hard to audit when it groups several product versions under one generic item name. FDA defines a version or model as devices with specifications, performance, size, and composition within limits set by the labeler. The same rule text says a DI identifies a specific version or model and a labeler. 3<\/a><\/p>\n

For a buyer’s purposes, this supports a modest but useful discipline: create a separate source record whenever the supplier documents use different model, version, catalog, size, package, or revision wording. The record is not a regulatory determination. It is an attempt to stop one label photograph from being silently attached to a different item in a quotation.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Buyer record field<\/th>\nCopy from the source<\/th>\nUseful source location<\/th>\n<\/tr>\n<\/thead>\n
Internal source-record ID<\/td>\nA neutral internal identifier, such as SR-213-01.<\/td>\nBuyer control sheet.<\/td>\n<\/tr>\n
Supplier product name<\/td>\nExact text, including capitalization where practical.<\/td>\nQuotation, label, invoice, specification.<\/td>\n<\/tr>\n
Model or version<\/td>\nExact stated model, version, or revision.<\/td>\nLabel, product sheet, artwork approval.<\/td>\n<\/tr>\n
Catalog number<\/td>\nExact stated catalog or reference number.<\/td>\nLabel, listing, purchase order.<\/td>\n<\/tr>\n
Package description<\/td>\nUnit, pack count, carton wording, and package level if stated.<\/td>\nPackage artwork, carton photo, packing list.<\/td>\n<\/tr>\n
Source date<\/td>\nDate shown on the document or image metadata when available.<\/td>\nSource file.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Do not normalize the record too early. If one source says “Model X3” and another says “X-3,” preserve both values and mark the difference. A reviewer can later decide whether the two refer to the same item. The buyer’s source map should make the difference easy to see rather than erase it with an assumed match.<\/p>\n

Capture labels and packages as evidence objects<\/h2>\n

FDA states that a device labeler must provide a UDI in easily readable plain text and in a machine-readable form that uses automatic identification and data capture technology, subject to stated exceptions and alternatives. 2<\/a> A buyer collecting source material can preserve label images at two levels: the whole label and a close, readable image of the code area. The goal is not to judge compliance. It is to retain what the supplier showed.<\/p>\n

Each image should be linked to the product-version record and given a stable file name. A clear naming pattern avoids later confusion. For example, SR-213-01_label_front_2026-08-27.jpg<\/code> reveals which record the photo belongs to, which side it depicts, and when it was received. The original file should remain available even if a cropped view is added for readability.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Label or package item<\/th>\nWhat to preserve<\/th>\nWhy it belongs in the source map<\/th>\n<\/tr>\n<\/thead>\n
Full front label<\/td>\nUncropped image or supplied artwork.<\/td>\nShows the surrounding product and company wording.<\/td>\n<\/tr>\n
Code-area close-up<\/td>\nReadable image without altering the original.<\/td>\nLets a reviewer inspect characters and placement.<\/td>\n<\/tr>\n
Human-readable text<\/td>\nExact transcription, with uncertainty marked.<\/td>\nMakes later comparison possible.<\/td>\n<\/tr>\n
Machine-readable symbol<\/td>\nImage showing the symbol type as supplied.<\/td>\nPreserves the source appearance without naming the code type.<\/td>\n<\/tr>\n
Carton or package face<\/td>\nPhoto or artwork with package wording.<\/td>\nKeeps product and package claims in context.<\/td>\n<\/tr>\n
File origin<\/td>\nSupplier email date, portal path, or attachment name.<\/td>\nSupports a traceable chain back to the received source.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

When a character cannot be read, use a clear marker such as [unclear]<\/code> rather than guessing. If a scan has a low-resolution barcode, keep it as received and request a replacement image. A recreated code typed into a spreadsheet is useful as a working note, but it is not a substitute for the actual label source.<\/p>\n

Separate UDI, DI, and PI wording in the notes<\/h2>\n

FDA explains that GUDID contains only the DI portion of a UDI and not the PI. FDA also says GUDID includes PI flags indicating which PI attributes are in the UDI. 1<\/a> This is a source-handling point, not a reason to infer that a number on a label has been submitted to any database.<\/p>\n

A source sheet can reserve distinct columns for terms that appear in materials. Put the full text or code as shown in the UDI field. Put the fixed identifier that a source calls a DI in the DI field. Put any lot, serial, expiration, or manufacture-date string in a PI-related field only when the source itself states that relationship. If the source does not label the relationship, use a neutral field such as “code or date as shown.”<\/p>\n

\n

FDA describes the DI as the mandatory fixed portion of a UDI and describes the PI as a conditional variable portion that may identify specified production information. 2<\/a><\/p>\n<\/blockquote>\n

This small distinction keeps a working sheet readable. It prevents an internal note from becoming more definite than the source it summarizes.<\/p>\n

Record the entity names without assigning a role<\/h2>\n

FDA defines a labeler for its UDI system as a person who causes a label to be applied or modified with the intent that the device will be commercially distributed without a later replacement or modification of that label, subject to the definition’s stated distributor-contact exception. FDA notes that the labeler is often the manufacturer but may also be a specification developer, single-use device reprocessor, convenience-kit assembler, repackager, or relabeler. 2<\/a> The regulation contains a corresponding definition. 3<\/a><\/p>\n

For buyer records, the reliable action is more limited: write down every entity name exactly as it appears and identify the source where it appears. Do not relabel a factory, trading company, brand owner, or overseas address as the labeler based on a quick reading of an image.<\/p>\n\n\n\n\n\n\n\n\n
Entity source<\/th>\nCapture<\/th>\nDo not add<\/th>\n<\/tr>\n<\/thead>\n
Product label<\/td>\nName, address, contact line, logo text, and stated wording.<\/td>\nAn assumed legal or regulatory role.<\/td>\n<\/tr>\n
Supplier quotation<\/td>\nSeller name, address, contact, and quotation number.<\/td>\nA claim that the quoted seller made the label.<\/td>\n<\/tr>\n
GUDID or AccessGUDID result<\/td>\nCompany field and result URL, exactly as displayed.<\/td>\nA statement that the record proves ownership or authority.<\/td>\n<\/tr>\n
Purchase order<\/td>\nBuyer and supplier entities, product wording, and order date.<\/td>\nA conclusion that it links to a label code unless the source does so.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Names that look similar should still be kept separate until the responsible reviewer resolves the relationship. A factory may use an English trading name in one document and a Chinese legal entity name in another. A source map can display both without claiming that they are the same legal person.<\/p>\n

Treat GUDID and AccessGUDID as search sources<\/h2>\n

FDA calls GUDID a database it administers and a reference catalog for every device with a UDI. The agency says AccessGUDID is a searchable database of device identification information, including the DI on the label, device name, company name, MR safety status, GMDN term, code and status, and premarket submission numbers. FDA says AccessGUDID is available to the public. 1<\/a><\/p>\n

A database search result is best handled like any other received source. Save the exact search term, the page URL, the access date, and an unedited capture of the displayed result. If a product name search returns several results, retain the result list and do not select one merely because its wording is close to a supplier’s wording.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Search record field<\/th>\nExample of a neutral entry<\/th>\n<\/tr>\n<\/thead>\n
Search location<\/td>\nAccessGUDID public search page.<\/td>\n<\/tr>\n
Search term entered<\/td>\nExact product name or stated DI used in the search.<\/td>\n<\/tr>\n
Access date<\/td>\nDate and time the buyer opened the result.<\/td>\n<\/tr>\n
Result count<\/td>\nNumber displayed by the search page, if shown.<\/td>\n<\/tr>\n
Selected result<\/td>\nURL and capture only after the record owner identifies why it was saved.<\/td>\n<\/tr>\n
Comparison note<\/td>\n“Supplier label says X; result displays Y.”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Search results can change as a website updates. A saved capture does not freeze the underlying database, but it preserves what the buyer viewed at a particular time. Keep a PDF print or image capture alongside the URL, and give both the same source-record ID.<\/p>\n

Link lot, serial, and date sources to the shipment<\/h2>\n

FDA lists lot or batch number, serial number, expiration date, and date of manufacture among PI elements that may be included on a label. 2<\/a> A packing list, carton label, inspection photograph, and commercial invoice may contain overlapping strings. The buyer’s task is to organize the overlap without deciding what the string signifies.<\/p>\n

Use a shipment link table that begins with the commercial document and then links any matching source by a stated product, carton, quantity, lot, serial, or date field. Retain the exact format. A date shown as 2026-08-15<\/code> should not be silently rewritten into a different convention. When a source has no shipment number, note that absence rather than creating a link from timing alone.<\/p>\n\n\n\n\n\n\n\n\n\n
Shipment source<\/th>\nStated fields to capture<\/th>\nSource-map treatment<\/th>\n<\/tr>\n<\/thead>\n
Commercial invoice<\/td>\nInvoice number, seller, buyer, product text, quantity, date.<\/td>\nStore as a transaction source.<\/td>\n<\/tr>\n
Packing list<\/td>\nCarton count, package text, quantity, marks, and lot strings if shown.<\/td>\nLink only to stated product or shipment references.<\/td>\n<\/tr>\n
Carton photograph<\/td>\nVisible marks, labels, and code areas.<\/td>\nPreserve full image plus close-up.<\/td>\n<\/tr>\n
Inspection record<\/td>\nRecord date, inspector-supplied image ID, observed wording.<\/td>\nKeep it separate from supplier-created claims.<\/td>\n<\/tr>\n
Freight document<\/td>\nShipment reference, package count, and date fields as shown.<\/td>\nUse as a transport source, not a product conclusion.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Make factual requests to the supplier<\/h2>\n

A vague request for “all UDI documents” can produce a mixed batch of screenshots, label drafts, and spreadsheets with no source dates. A structured request can be more useful without asking the supplier to make a legal statement. Ask for source objects and exact associations.<\/p>\n

A practical request can ask for the current product label artwork or readable photographs; all stated model, catalog, and package variations being quoted; any supplier-controlled identifier list with its issue date; the product and package relationship used in the supplier’s own records; and original files for any database screenshot supplied. Ask the supplier to identify which product version each file concerns. If the supplier cannot identify the version, record that answer as a gap.<\/p>\n

Avoid asking a supplier to certify outcomes that sit outside the source map. The goal is to obtain complete records, not to convert a sourcing conversation into a regulatory conclusion.<\/p>\n

Build a contradiction queue rather than overwriting sources<\/h2>\n

Differences are common. One supplier document may show one company name, while a database result displays another. A carton may use one model number, while a spreadsheet uses a shortened form. The source sheet should preserve both and create a contradiction entry.<\/p>\n\n\n\n\n\n\n\n\n\n
Difference found<\/th>\nPreserve<\/th>\nFollow-up record<\/th>\n<\/tr>\n<\/thead>\n
Product name differs<\/td>\nBoth exact names and their source files.<\/td>\nAsk which version each name identifies.<\/td>\n<\/tr>\n
Model differs<\/td>\nBoth model strings, including punctuation.<\/td>\nRequest the supplier’s stated cross-reference, if any.<\/td>\n<\/tr>\n
Code differs<\/td>\nBoth codes and original images.<\/td>\nAsk for readable original label sources.<\/td>\n<\/tr>\n
Company differs<\/td>\nBoth company names and addresses.<\/td>\nRequest the source-based relationship statement.<\/td>\n<\/tr>\n
Database field differs<\/td>\nResult capture and supplier source.<\/td>\nEscalate the comparison to the designated owner.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Do not “fix” a mismatch by editing an old file name or changing a spreadsheet cell. The unresolved difference itself is useful information. It tells the reviewer which records need attention and protects the source trail from accidental cleanup.<\/p>\n

Keep the evidence map separate from decisions<\/h2>\n

The value of China supplier UDI and GUDID evidence<\/strong> comes from separation. A sourcing team can prepare a clear packet without stepping into decisions assigned to another function. The packet should show the sources, their dates, the product-version links, and the open questions. A responsible owner can then review the packet under the process that applies to that organization.<\/p>\n

This division also improves supplier communication. Instead of telling a factory that an identifier is wrong, a buyer can state the observed difference: “The label image received on August 27 shows Model X3, while the spreadsheet received the same day shows X-3. Please identify the product version for each source.” That request is specific, factual, and easier to track.<\/p>\n

Use a compact handoff sheet<\/h2>\n

A handoff should be short enough for a reviewer to scan, with links to the full source set. It should not substitute a buyer’s conclusion for the source materials.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Handoff heading<\/th>\nInclude<\/th>\nLeave for the assigned reviewer<\/th>\n<\/tr>\n<\/thead>\n
Product record<\/td>\nExact product, model, catalog, package, and revision wording.<\/td>\nDevice or regulatory classification.<\/td>\n<\/tr>\n
Identifiers<\/td>\nFull strings and images as supplied.<\/td>\nIdentifier validity or required use.<\/td>\n<\/tr>\n
Entities<\/td>\nNames and addresses from each source.<\/td>\nLabeler or legal-role conclusion.<\/td>\n<\/tr>\n
Database captures<\/td>\nSearch terms, URLs, access dates, and saved results.<\/td>\nSubmission, completeness, or accuracy conclusion.<\/td>\n<\/tr>\n
Shipment links<\/td>\nInvoice, packing, photo, and freight source links.<\/td>\nImport, sale, or release decision.<\/td>\n<\/tr>\n
Open items<\/td>\nMissing records and unresolved differences.<\/td>\nRisk acceptance or disposition.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

A good handoff names the owner of the next review and the date the packet was assembled. It does not need a dramatic summary. The source links and open-item list are the useful parts.<\/p>\n

Common source-map mistakes<\/h2>\n

The first mistake is treating a code typed into a spreadsheet as stronger evidence than the original image or document. Keep the spreadsheet as an index, but link it back to the source file.<\/p>\n

The second mistake is calling every number on a package a DI or PI. FDA’s explanations distinguish those terms, but a buyer should only record the relationship that a source states. 1<\/a><\/p>\n

The third mistake is saving a database search result without the search term and access date. A reviewer then cannot reproduce what the buyer searched or tell whether the result was selected from a list.<\/p>\n

The fourth mistake is merging similar company names. Similarity is not a source relationship. Preserve the names as written, then ask for documents that state the relationship if the designated owner needs it.<\/p>\n

The fifth mistake is turning a source packet into an approval note. A factual source map can be complete while the responsible reviewer still needs to make several decisions.<\/p>\n

Frequently asked questions<\/h2>\n

Does a label photograph prove that a code is a UDI?<\/h3>\n

No. A label photograph proves that the photograph displays a code. FDA describes UDI, DI, and PI in its own regulatory context, but a buyer-side source map should not assign a code to one of those categories unless the source itself makes that statement. 2<\/a><\/p>\n

Does an AccessGUDID result prove that a supplier is the labeler?<\/h3>\n

No. Record the company field, source URL, search term, and access date as displayed. FDA explains that AccessGUDID contains device identification information available to the public, while the UDI materials describe a labeler in a specific context. The responsible reviewer should make any role determination. 1<\/a><\/p>\n

Why retain the PI-related fields if GUDID does not include PI?<\/h3>\n

FDA says GUDID contains DI and not PI, while PI may include stated production information such as lot, serial, expiration, or manufacture date. A buyer may preserve those strings from labels and shipment records so that the source packet remains complete, without inferring any submission or identifier outcome. 1<\/a><\/p>\n

What should a buyer do when supplier and database wording differs?<\/h3>\n

Keep both source records, describe the difference in neutral words, request the supplier’s source-based clarification, and send the unresolved comparison to the designated reviewer. Do not overwrite either source or select the result that looks closest.<\/p>\n

A factual packet makes later review faster<\/h2>\n

A disciplined source map gives each document a home. It connects label images, package wording, supplier spreadsheets, database captures, and shipping records to a stated product version or model. It also makes missing links and contradictions visible.<\/p>\n

For China supplier UDI and GUDID evidence<\/strong>, the practical first step is simple: make one record per stated product version, preserve original sources, and list unresolved differences without interpreting them away. Supplier Ally can help buyers organize supplier communications, product records, and sourcing documentation so the appropriate internal or external reviewer receives a clearer evidence packet.<\/p>\n

References<\/h2>\n","protected":false},"excerpt":{"rendered":"

Organize China supplier UDI and GUDID evidence while keeping source records separate from device, identifier, submission, import, sale, and release decisions.<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2318","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"trp-custom-language-flag":false},"uagb_author_info":{"display_name":"Azar Pamir","author_link":"https:\/\/supplierally.com\/es\/author\/admin\/"},"uagb_comment_info":0,"uagb_excerpt":"Organize China supplier UDI and GUDID evidence while keeping source records separate from device, identifier, submission, import, sale, and release decisions.","_links":{"self":[{"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/posts\/2318","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/comments?post=2318"}],"version-history":[{"count":0,"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/posts\/2318\/revisions"}],"wp:attachment":[{"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/media?parent=2318"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/categories?post=2318"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/supplierally.com\/es\/wp-json\/wp\/v2\/tags?post=2318"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}