Dropshipping Waterproof Claims: 670-Product Audit
Dropshipping waterproof claims need more than a Yes field. Our 670-product audit shows what to ask suppliers before promising water resistance.
Dropshipping product identifiers need a source check before they enter your product feed. A supplier's model label might be a useful lead, a long description, or the word “None.” Copying it into an MPN field changes an ambiguous research note into a specific claim about who assigned the code.
We queried ProductLair's stored specifications to see what a seller could establish from those fields alone. The examples exposed several different meanings hiding behind similar labels. This guide explains how to separate them before listing a product on Shopify or submitting it to Google.
It is for sellers preparing a feed or checking imported product data. If your immediate task is connecting colors and sizes to fulfillment, use our product variant mapping guide. Here, the narrower question is whether a code identifies the manufacturer's item, your store's record, or something else.
What dropshipping product identifiers actually identify
Start by naming the job each code performs. A seller can legitimately use several codes for the same item without making them interchangeable.
| Field | What it identifies | Evidence to retain |
|---|---|---|
| Store SKU | Your internal product or variant record | Your naming convention and exact variant mapping |
| Supplier item ID | An item within that supplier's system | Supplier listing, option selection, and confirmation |
| Model number | A model as described by its source | Manufacturer documentation explaining the model |
| MPN | A manufacturer-assigned part number | Manufacturer record for the specific item |
| GTIN | A standardized trade-item identity | Assigned number and matching product evidence |
| Barcode value | Data encoded in a scannable symbol | Code type, decoded value, and its purpose |
Shopify's product details documentation describes SKUs as internal business codes and distinguishes them from barcodes, which can contain custom or standardized identifiers. Creating a sensible SKU does not create a manufacturer-assigned number.
A model name can help locate documentation, but its label alone does not establish an MPN. Likewise, a barcode can serve an internal workflow. Shopify's barcode terminology distinguishes GTIN formats from non-GTIN barcode types. Seeing a scannable label does not settle which kind it is.
Consider a hypothetical black phone stand. You might call it STAND-BLK internally while the supplier has its own item ID. Neither code should become its GTIN merely because the feed has an empty box. Keep each source value in its own field and leave unresolved claims unresolved.
This identity check comes before product compatibility checks. A correct identifier still does not establish that a stand fits a particular device or supports every function you intend to advertise.
What our dropshipping product identifiers audit found
On October 28, 2026, we read 670 unique parent records from ProductLair's curated product table and 2,633 unique rows from its linked product_attribute table. Every specification row matched a parent in the snapshot. We used read-only requests and did not change the database.
For the table below, we trimmed surrounding spaces from field names and ignored capitalization. We then matched the complete names shown, rather than searching for fragments inside unrelated labels.
| Exact normalized field name | Saved rows | Distinct products | What the count establishes |
|---|---|---|---|
| Model Number | 84 | 83 | Stored model-number labels exist for these parents |
| Brand Name | 96 | 96 | A brand-name value is recorded |
| SKU | 1 | 1 | One specification uses this field name |
| Barcode | 3 | 3 | Each stored value is “No” |
| GTIN, UPC, EAN, or MPN | 0 | 0 | No specification has one of these exact field names |
The 83 products with Model Number fields represent 12.4% of the 670-product snapshot. This is field coverage in one table, not the share of products with manufacturer-issued identifiers. The 587 other parents might have relevant information in packaging, supplier records, descriptions, or systems we did not inspect.
The groups overlap. Do not add the distinct-product column and call the result a count of identified products. Nor should 84 model rows become 84 products: one parent contributes more than one matching row.
Our initial broad keyword search also caught “Compatible Brand,” “Compatible iPhone Model,” and even “Cleaner Type” because the text contained the letters “ean.” Those are reasons to narrow a query, not extra identifier evidence. The final counts above exclude those names.
Parent addition dates run from October 6, 2024, through October 25, 2026. They date catalog additions, not manufacturer checks. The specification table contains id, product_id, attribute_key, and attribute_value; it has no dedicated verification date, issuer, or variant identifier column. That statement is limited to this table.
We did not inspect physical packaging, contact these manufacturers, submit a merchant feed, or measure approval, sales, returns, or profits. AI-generated business analysis elsewhere in ProductLair was not used as evidence. The same distinction matters when evaluating a dropshipping product: a research field is a starting point for verification.
Five saved examples that need different follow-up
The following values are reproduced from the snapshot. They describe historical catalog entries, not verified current supplier offers or recommended feed values.
| Catalog product | Saved field and value | Appropriate next check |
|---|---|---|
| Wireless HDMI Transmitter | Model Number: G57L | Ask whether the manufacturer assigns this code to the exact version |
| Magsafe iPhone Stand | Model Number: Magnetic Folding Wallet Card Holder Leather Phone Stand | Request an explicit manufacturer code rather than promoting description text |
| No Pull Dog Harness | SKU: DD191 | Establish whose SKU this is and which option it identifies |
| Toy Pistol Soft Bullet Blaster | Barcode: No | Ask whether a manufacturer-assigned identifier exists for the exact item |
| Push Down Beer Bottle Opener | Model Number: None | Treat the saved word as unresolved information |
The transmitter's compact G57L value looks like a code. Appearance does not establish who assigned it, whether it identifies a family, or whether a particular accessory pack shares it. A useful supplier response would name the issuer and attach documentation for the version you will buy.
The stand shows the opposite problem: its Model Number field contains a long product description. We cannot infer why the text landed there. Copying it into a feed's MPN field would not resolve that uncertainty. Preserve the original wording in your research notes while requesting a proper source.
The harness illustrates a scope question. DD191 is a stored SKU value, but the specification does not identify the issuing system or exact size and color. Your store could have a completely different internal SKU. Keeping both can be useful once each is mapped, as our inventory sync audit explains for supplier records and store options.
The blaster is one of three Barcode entries, each reading “No.” A saved negative does not explain whether the original question concerned printed packaging, a marketplace field, or a global identifier. We did not establish the original meaning. It cannot independently justify a no-identifiers declaration.
Finally, “None” is still a value in a Model Number field. Counting nonempty text would count that row as populated. Counting verified manufacturer codes would require a different dataset and method. This is why completion percentages should state what was counted.
Collect evidence before filling GTIN and MPN fields
For each item you plan to sell, create a short identity record outside the marketing copy. Retain the supplier URL, selected option, manufacturer or brand, proposed code, code type, evidence link or attachment, and date checked. Keep your internal SKU alongside them so you can trace the record back to the store.
Ask for readable photos of the item label and retail packaging. Ask which number is manufacturer-assigned, what product and option it covers, and whether a different pack quantity has a different identity. A photograph of an outer shipping label alone may not answer those questions.
GS1 explains GTIN allocation as normally the responsibility of the brand owner. Verified by GS1 can help check the company associated with a GS1 number and available product data. Compare that information with the actual item rather than stopping when a lookup returns a company name.
Our proposed evidence check has three separate outcomes: the number has a plausible structure, its assignment can be traced, and the product details match. Passing the first does not establish the other two. If the registry has only company information, retain that limitation and seek the item evidence separately.
Do not change a number's digits to make an import succeed. Preserve leading zeros as text when preparing a working spreadsheet, compare the saved export with the source, and check the destination's formatting requirements. A convenient numeric column can be a poor place to preserve an identifier exactly.
When ordering a sample, compare the delivered item and packaging with the evidence record. Our packaging checklist covers what arrives in the parcel, while the product photo audit explains why several attractive images do not prove the delivered version. A confirmed code should be tied to the same version you photograph and describe.
These are proposed seller checks. We did not carry them out on the five catalog examples, so this article does not label those products verified or unverified in every other context.
Handle missing identifiers in a Google product feed
Google's current identifier guidance says to provide correct assigned identifiers and avoid guessed values or codes from similar products. If an assigned identifier is unavailable to you, leave that attribute blank rather than substituting an internal SKU. Missing data and nonexistent identifiers are different situations.
For MPNs, use the manufacturer-assigned value. Google's MPN specification says not to guess and describes requirements and exceptions for products without a manufacturer-assigned GTIN. A supplier's generic Model Number field is not sufficient evidence by itself.
Treat a proposed value as a claim you must be able to trace. If the source only says G57L, ask what it identifies before assigning a feed attribute. If the source returns a descriptive sentence, do not shorten it into a code that the manufacturer never supplied.
The identifier_exists setting requires its own decision. Google's documentation for that attribute says to use no or false only when you are certain that the product has no assigned unique product identifiers. It is not a switch for “supplier has not answered.” Our three Barcode: No observations do not establish that condition.
An ordinary reseller should not invent a manufacturer identity to clear an error. If you move into manufacturing or private label, your responsibilities and evidence change; that is a separate workflow, not permission to relabel another manufacturer's product.
After editing, inspect the actual channel submission. Shopify's Google product sync guidance describes handling missing GTIN or MPN information through barcode data or brand and MPN details as applicable. Verify the exported values for your selected variant and read the resulting diagnostics. Saving a field in Shopify does not establish Google acceptance.
If you are still deciding how paid search fits your store, our Google Ads versus Facebook Ads comparison covers that broader choice. Identifier cleanup answers a data question; it does not forecast profitable traffic.
Keep dropshipping product identifiers stable through changes
Use your internal SKU as the join between your store record and the evidence you retain. Keep supplier codes and manufacturer identifiers in separate columns, with a status such as awaiting source, source received, or checked against item. Those are suggested working labels, not industry certification levels.
For a hypothetical phone accessory with two finishes, begin with a row for each sellable option. If a manufacturer confirms that a code covers both finishes, retain that response. If different codes apply, preserve the distinction. Do not manufacture differences, and do not erase documented differences to simplify the feed.
When replacing a supplier, compare the proposed item with the existing identity record before routing orders. Similar photos, names, or model strings do not independently establish the same trade item. Our supplier replacement guide covers the broader operational decision, including what needs rechecking when the source changes.
Product descriptions should follow the evidence, too. A compatible brand name does not necessarily identify the accessory's own brand. Keep that distinction visible while writing product descriptions, and use the materials audit for composition claims that need separate support.
For every revision, retain the old and new values, the reason, and the effective date in your working record. This gives you a way to investigate a later mismatch without assuming that today's supplier page reflects yesterday's shipment. It also stops an importer refresh from quietly replacing a checked value with an ambiguous one.
You can browse candidates in ProductLair's catalog, then do this identity work on the shortlist. Our audit shows why saved research specifications should not be treated as a ready-to-submit manufacturer registry.
A practical review before submission
Review one complete item from source evidence to store export before repeating the process across your catalog. This is a proposed review sequence, not a claim that we tested a merchant's feed.
- Select the exact version you will sell, including the pack quantity and option.
- Record your store SKU and the supplier's own reference separately.
- Obtain evidence explaining any proposed manufacturer code or GTIN.
- Compare the item, packaging, brand, and available registry information.
- Preserve the source text, including leading zeros, and map it to the right field.
- Inspect what your channel actually receives and resolve the specific diagnostic.
Stop the identity review when the evidence conflicts. An unresolved brand mismatch should not become a guessed replacement number. Keep the affected feed record under review and ask the source to reconcile the discrepancy.
An identifier record also does not replace physical quality control. You still need to establish whether the sample works, whether the advertised claims are supported, and whether the delivered version matches the offer. Each check answers a different customer question.
Questions sellers ask about product codes
Do dropshipping products need a GTIN?
Check the product and the channel's requirements. Some products have assigned GTINs and some do not. Obtain the actual manufacturer's information rather than assuming dropshipping creates an exemption. Our audit counted saved fields, not which products must have a GTIN.
Can I use my Shopify SKU as the MPN?
Your internal SKU does not establish a manufacturer-assigned part number. Keep it for your store's own identification and obtain evidence for the MPN separately. Do not copy an internal code into that field just to make it nonempty.
Does Barcode: No mean identifier_exists should be false?
No. It is a saved specification value without enough context to establish whether assigned identifiers exist. Google requires certainty about that condition. Ask for product-specific evidence before making the declaration.
Is a supplier model number always an MPN?
No. It may be a useful manufacturer reference, a broader model label, or ambiguous listing text. Our snapshot includes both G57L and a long stand description under Model Number. Establish who assigned the value and what item it identifies.
Can a valid barcode prove the supplier sent the right product?
A number's structure alone cannot establish what was shipped. Compare its assignment and product details with the exact item and packaging. Keep the supplier and variant evidence so a later substitution can be investigated.
Did ProductLair test Google approval for these 670 products?
No. We read 670 curated product records and 2,633 linked specifications on October 28, 2026. We did not submit feeds, inspect physical packaging, or measure approval or sales outcomes. The findings describe recorded field names and values only.
Put the source beside the code
The useful finding in this audit is the distance between a populated field and a confirmed identity. Model Number appears on 83 products, but that count cannot tell you which values are manufacturer-assigned MPNs. Three negative Barcode values cannot tell you which products lack identifiers.
For your next listing, keep the store SKU, supplier reference, and manufacturer identifier separate. Put the evidence beside each claim and check what reaches the channel. That gives you a defensible answer when an imported code turns out to mean something different from the field you put it in.
