United States / Amazon Compliance / CPSIA Tracking Labels

Amazon CPSIA Tracking Label Rejected? What Your Images Must Prove

Amazon’s message “The tracking label format is not accepted” sounds as if the seller used the wrong federal label template. That is often the wrong starting assumption.

CPSC does not prescribe one tracking-label layout. Amazon performs a separate evidence review: the physical marks must be visible, readable or reliably decoded, connected to the product and packaging, and consistent with the ASIN under review.

By Natallia Vasilyeva Reviewed July 27, 2026 U.S. market only

01 / Product mark Show the physical mark in context, then close enough to read it.

Answer in 30 seconds

Amazon’s “tracking label format is not accepted” message does not necessarily mean that the label uses an illegal format. CPSC has not created a mandatory tracking-label template. The rejection may instead mean that Amazon could not verify the required information, the permanence or placement of the mark, the packaging evidence, the code-to-record connection, or a match between the photographed unit and the ASIN. Do not upload the same files again until you identify which link in that evidence chain is missing.

That difference explains why a seller may possess a Children’s Product Certificate (CPC), a laboratory report, a production code, and photographs—and still receive a tracking-label rejection.

This guide is a rejection decoder. It does not attempt to replace Amazon’s case-specific instructions, CPSC guidance, or legal advice. Its purpose is to help a seller determine what a rejection message does—and does not—establish, then build a coherent evidence response.

No federal templateCPSC does not prescribe one mandatory tracking-label size, layout, font, or numbering system.
Two evidence surfacesThe product and its packaging must be analyzed separately, to the extent practicable.
One identity chainThe ASIN, unit, package, visible code, and retained production record must describe the same product.

Umbrella rejection: audit the entire chain before changing the label

What it may meanAmazon could not verify content, placement, permanence, packaging evidence, code interpretation, or ASIN identity.

Check firstCompare the exact rejection, the submitted image set, the physical unit, the retail package, and the visible production code.

Correct routeAdd the missing proof. Do not redesign a potentially lawful tracking system merely because the word “format” appears.

This diagnostic narrows the likely proof problem. It is not a legal determination or a guarantee of Amazon approval.

The federal requirement is found in CPSIA Section 103, codified at 15 U.S.C. § 2063(a)(5). It requires permanent distinguishing marks on children's products and their packaging, to the extent practicable. The marks must allow required production and source information to be ascertained.

CPSC's published guidance makes three points that matter immediately after an Amazon rejection:

Permanent marks—not one template A tracking label is shorthand for the statute's "distinguishing permanent marks." It does not have to be one rectangular label containing every field in one location.
No prescribed layout CPSC has not prescribed a standard size, location, layout, sample label, or numbering system.
The marks may work together Existing permanent marks may form part of the tracking system if, taken together, they make the required information ascertainable.

Amazon, however, is not deciding only whether a theoretical label design could comply with federal law. It is reviewing evidence attached to a product listing or compliance request. The reviewer may be asking a different set of questions.

Two decision systems

Federal compliance questions and Amazon evidence questions

Federal compliance questions and Amazon evidence questions
Federal compliance question	Amazon evidence question
Can the required information be ascertained from permanent marks?	Can the reviewer read or reliably decode that information from the submitted evidence?
Are the product and packaging marked to the extent practicable?	Do the images actually show the mark on the physical product and the relevant packaging?
Does the system identify the production source and cohort?	Does the photographed item match the ASIN, model, variation, quantity, and packaging under review?
Is a departure from product marking reasonably justified?	Has the seller provided enough evidence for Amazon to recognize the asserted exception or classification?
Does another federal rule add labeling duties?	Has Amazon classified the ASIN into a category with additional documentation or image requirements?

Read the rejection as an evidence problem

The phrase "format is not accepted" therefore should be treated as an umbrella rejection message, not a precise legal conclusion. Public Seller Central cases show the same wording being associated with missing packaging images, a missing manufacturer or private-labeler name, marks that were not physically present on the product, and images that did not match the listed ASIN.

The tracking-label requirement applies to a children's product: a consumer product designed or intended primarily for children 12 years of age or younger.

That scope question comes before the photograph question.

A seller should confirm:

the intended age represented on the listing, packaging, instructions, advertising, and product itself;
the product's design, sizing, themes, features, and expected use;
whether Amazon has classified the ASIN as a children's product;
whether a specific product category adds another labeling rule;
whether the photographed variation is the variation Amazon is reviewing.

An exemption from one material-testing requirement does not automatically remove the tracking-label requirement. For example, a children's paper product may have a different testing analysis from a plastic toy, but if it remains a children's product, it is not excluded from CPSIA Section 103 merely because of its material.

Responsibility and label content also must not be confused. CPSC states that the domestic manufacturer is responsible for a domestically manufactured product and the importer of record is responsible for an imported product. The permanent marks must allow the manufacturer/importer or private labeler and the required production information to be ascertained. The party legally responsible for compliance and the entity named as part of the tracking system are related questions, but they are not always phrased identically in marketplace requests.

The Part 1130 gateway

Additional-rule gatewaySeparate the general tracking-label rule from Part 1130

General CPSIA scopeIs this a children’s product?Some products require an additional analysis under 16 CFR Part 1130. Part 1130 does not apply to every children's product or every item marketed for a baby. It applies to defined durable infant or toddler products intended for use, or reasonably expected to be used, by children under five.

then

Additional-rule scopeIs this a covered durable infant or toddler product?For covered products, additional permanent information is required on the product, including manufacturer contact information, model name or number, and date of manufacture. Product-registration requirements also apply. CPSC's comparison table distinguishes these additional duties from the general CPSIA tracking-label elements.

This distinction is essential when Amazon requests a U.S. address, telephone number, model number, or registration-card evidence. Those items should not be presented as universal CPSIA tracking-label fields for every children's product. First determine whether the ASIN falls within Part 1130 or another product-specific rule.

For the general tracking-label requirement, the permanent distinguishing marks must make the following information ascertainable:

Responsible entity the manufacturer/importer or private labeler;
Production location the location of production;
Production date the date of production;
Production cohort cohort information, such as a batch, run number, or another identifying characteristic;
Specific source information needed to facilitate identification of the specific source of the product.

"Ascertainable" is more demanding than "some code is printed somewhere." It means the marks and the supporting traceability system work together so that the relevant party can determine the required information.

Field-by-field inspectorWhat each permanent mark and supporting record must establish

Manufacturer, importer, or private labeler

The name relied upon in the tracking system must identify a real entity. A logo or brand may contribute if it unambiguously identifies the responsible company, but a marketplace seller should not assume that an unfamiliar brand symbol will be understood by a reviewer.

Amazon's current public marking-and-labeling guidance notes that the manufacturer or private labeler listed on a tracking label may be a domestic or foreign entity. A U.S. address should therefore not be described as a universal general-tracking-label requirement. If Amazon requests one, the seller should identify whether the request comes from Part 1130, another category-specific rule, or a case-specific marketplace instruction.

Production location

CPSC explains that the city and state or province, together with the country, are sufficient to describe the production location. Some or all of that information may be represented in code form.

Made in China by itself usually identifies only a country. It does not necessarily establish the city or province, the date, or the cohort.

Production date

CPSC states that month and year are sufficient. A date range may be used when production occurs over a period. For disparate components assembled or gathered into one package, CPSC interprets the production date as the date of assembly or placement into the package.

A seller should not create a new date merely to satisfy an image request. The mark must correspond to the actual manufacturing or assembly record for the unit or cohort shown.

Cohort and specific source

A batch, run, lot, serial sequence, or other identifying characteristic should narrow the product to a meaningful production cohort. A number that identifies only the model across every production run does not perform the same function as a batch identifier.

The underlying record should permit the company to move from the mark to the relevant production source. Depending on the system, that may include the facility, production period, line, supplier, assembly run, or other information used to isolate affected units.

Sellers often use several identifiers on the same product. The correct question is not simply "Is this a tracking label?" The better question is: Which required fact can this identifier prove, and what remains unproved?

Identifier matrix

What common identifiers can—and cannot—prove

What common identifiers can—and cannot—prove
Identifier	What it can help establish	What it normally does not establish by itself
UPC or GTIN	The commercial identity of a product type	Production date, production location, and manufacturing cohort
FNSKU	An Amazon offer or fulfillment identity	The federal production source, batch, or run
Model number	The model or design family	A specific production date and cohort
Serial number	A specific unit, if a real serial-traceability system exists	The responsible entity or decoded production facts without supporting records
Batch, lot, or run code	A production cohort	The responsible company or consumer contact path if neither appears elsewhere
Country-of-origin mark	The country of origin	City/province, production date, and cohort
Textile RN	A responsible textile business	The remaining tracking-label elements
Website or QR code	A route to more information	A complete system if the company is not identified or the code cannot be interpreted
Amazon barcode	Amazon inventory handling	CPSIA source and production traceability

Any of these marks may contribute to the totality of the system. None should be treated as a substitute merely because it contains numbers or the word "tracking."

The practical audit is field by field:

0 of 7 traceability questions answered Field audit—not approval

Which mark identifies the responsible entity?
Which mark identifies or decodes the production location?
Which mark identifies or decodes the production date?
Which mark identifies the cohort?
Which record connects the code to the specific source?
Can a consumer determine whom to contact?
Can the company retrieve the underlying record for the unit shown?

Confirm every field before treating an existing identifier as a complete tracking system.

Operational weakness

If one answer is "the supplier knows," but the importer or private labeler cannot retrieve the information, the system is operationally weak.

The default federal expectation is that both the children's product and its packaging bear permanent distinguishing marks, to the extent practicable.

This does not always require two identical rectangular labels. Different permanent marks may appear in different locations, and the totality may provide the information. But a seller must be able to explain and prove how the product-side and packaging-side requirements are satisfied.

Recognized circumstances affecting separate packaging marks

CPSC identifies important circumstances:

If all required tracking information on the product is plainly visible through clear outer packaging, a duplicate mark on that outer package is not required.
If no retail packaging encloses the product, an additional hangtag is not required merely to create packaging evidence.
If a reusable container is intended to remain with the product, such as a board-game box or storage bag, it may be treated as part of the product for on-product marking purposes.
Some products may be too small, impossible to mark permanently, damaged by marking, or functionally impaired by a mark.

A limitation is not an automatic exemption

These are not automatic exemptions. CPSC expects a considered and definable reason for departing from the general requirement. A firm that determines marking is not practicable should create a written record of its reasoning, relevant product characteristics, research, and peer-market practices.

Permanent does not mean the same thing on every surface

Two evidence surfacesPermanence follows the physical surface

Physical productExpected to remain for the useful life

For a product, CPSC describes a permanent mark as one reasonably expected to remain during the product's useful life.

Disposable packagingExpected to reach the consumer intact

For disposable packaging, the mark must be durable enough to reach the consumer. An adhesive label on disposable packaging may therefore be sufficient under the federal guidance.

CPSC also states that adhesive labels may be used on a product if they meet the permanency standard. But the analysis is product-specific. A hangtag or removable adhesive label on a textile item generally will not remain for the product's anticipated life and therefore will not satisfy the product-side requirement.

Amazon review boundary

Amazon's general product-compliance documentation includes a stricter operational warning not to submit a tracking label printed on paper and stuck on the product. Sellers should treat that as an Amazon evidence instruction for the review, not as a complete restatement of every circumstance recognized in CPSC's permanency guidance.

The safest response is not to debate adhesives in the abstract. Identify:

the material and surface;
how the mark is attached or formed;
whether normal use, washing, handling, or wear will remove it;
whether the submitted photograph shows the actual production method;
whether the packaging mark will reach the consumer intact;
whether Amazon has issued a more specific instruction for the category.

CPSC permits required information to appear in code form. But the code must not become a dead end.

A defensible coded system has four layers:

Visible identity. The product identifies the manufacturer, importer, or private labeler so a consumer knows whom to contact.
Permanent code. The code remains with the product for its expected useful life.
Reliable decoder. The company can map the code to location, date, cohort, and source information.
Consumer access. A consumer can obtain the required information, including through a stated contact path. A website may assist, but CPSC says the responsible firm still must be identified so a consumer without internet access knows whom to contact.

Interactive code keyConnect each visible segment to the retained production record

Consider an illustrative code:

----

TL-2606-SZ-04-B12

The manufacturer might internally map that code as follows:

Selected segmentTL — internal tracking-system prefix

26-06 = June 2026;
SZ = a defined production location;
04 = production line or run;
B12 = batch 12.

There is no federal requirement to use that structure. The example is useful only because each segment has a stable meaning and the company retains the mapping record.

Weak coded system

A weak system looks like this:

the item displays B12;
no company name or clear contact path appears;
the supplier says B12 is a batch;
the importer has no code key;
the code cannot be connected to a city, date, or production record;
the Amazon submission contains no explanation.

Stronger coded system

A stronger system looks like this:

the physical product and packaging identify the company;
the code is permanent and legible;
the code key is controlled and documented;
the decoded record identifies the production location, month/year, and cohort;
the model and physical characteristics match the ASIN;
the submitted evidence explains what the reviewer cannot infer from the photograph alone.

Evidence must connect the mark and the record

A digital artwork showing what a future label will say is not evidence that the code is present on the current physical product. A factory spreadsheet without a photograph of the corresponding mark proves only that a record exists, not that the product carries the mark. The evidence must connect both.

A strong submission allows a reviewer to follow one uninterrupted chain:

Identity chainEight links Amazon must be able to follow

ASIN
Catalog variation
Physical product
Product mark
Packaging
Packaging mark
Production code
Supporting record

Each arrow is a potential failure point.

Evidence-link inspectorLocate the identity break before rebuilding the packet

ASIN and catalog identity

Verify the exact ASIN under review, not only the parent listing. For variations and sets, compare:

An image of a three-piece unit does not establish the identity of a 12-count ASIN. A photograph of the blue variation does not necessarily prove the label for the red variation. A close-up that removes every identifying feature may show readable text while failing to show which product carries it.

Physical product identity

The seller should be able to point to a visible feature that connects the full product image to the close-up label image. That may be the label location, seam, molded area, color, shape, model marking, or another stable feature.

Packaging identity

The packaging should show enough context to establish:

that it belongs to the same product;
that the pack count and model match;
where the tracking information appears;
whether the package is the actual retail package reaching the consumer;
whether a transparent-package exception is being relied upon.

Document identity

A CPC or test report may identify a model, product description, manufacturer, importer, age grading, or photographed test sample. Those facts should not contradict the physical product or catalog. But a report photograph is not automatically proof of the current production unit, current packaging revision, or current cohort.

Amazon's wording varies by product category, compliance request, and case. The table below does not claim that each message has only one cause. It identifies the proof that may be missing and the first audit to perform.

Rejection decoder

Translate Amazon’s wording into the missing proof

Translate Amazon’s wording into the missing proof
Amazon response	What it may actually mean	File or evidence surface to inspect	Evidence to add	What not to resubmit or do
The tracking label format is not accepted	Required content, physical placement, permanence, packaging evidence, code interpretation, or ASIN identity may remain unresolved	The complete rejection, the previously submitted packet, the physical unit, the retail package, and any code key	The missing link: product or package context images, readable close-ups, an ASIN identity bridge, or a code explanation tied to the photographed mark	Do not redesign the label solely because the word "format" appears, and do not resend the unchanged packet
Tracking label is missing from product	Only packaging, artwork, a detached label, or an unidentifiable close-up may have been shown	The actual production unit and every submitted product-side image	A full-product image, a mark-location image, and a readable close-up of the same physical unit	Do not substitute package artwork, a detached sample, or a digitally added label
Tracking label is missing from packaging	Only the product may have been shown, or the package could not be connected to the ASIN	The actual retail package, package revision, and submitted package images	The full retail package, mark location, and close-up, or evidence of the relevant clear-package or no-packaging circumstance	Do not submit only the product mark or an unrelated shipping carton
Tracking label missing information	Entity, location, date, cohort, or source information may be absent or not ascertainable	The physical mark, code key, and retained production record	A field-by-field explanation connecting the visible mark to the entity, location, date, cohort, and specific source	Do not digitally add decoded fields to the photograph or invent missing production data
Manufacturer information is missing	The company name may be absent, ambiguous, or not connected to the code	The product and package company identifier, the code owner, and any additional category-specific rule	A legible physical company name or unambiguous identifier, a consumer contact path, and a code explanation where needed	Do not assume that an unknown logo, factory name, FNSKU, or seller statement identifies the required entity
Images do not match ASIN	Model, variation, color, size, quantity, components, or packaging revision may differ	The exact child ASIN, catalog attributes, photographed unit, package, CPC, and report	An ASIN identity bridge and one coherent image set for the exact model, variation, quantity, and package revision	Do not mix variations, multipack quantities, old packaging, or documents for another construction
Live images are missing	Artwork, PDF, render, edited image, or an unattached label may have been used instead of a real unit	The submitted file types and the physical product and packaging actually held in inventory	Unedited photographs of the actual production unit, product-side mark, retail package, and package-side mark	Do not resubmit artwork, a render, a report-only image, or a retouched photograph as a live image
Images do not meet labeling requirements	A generic content, placement, permanence, readability, or category-specific defect may remain	The complete case note, linked policy, category request, and every file in the packet	Evidence that answers the specifically named deficiency in the requested channel	Do not infer a universal federal field from a generic heading or upload another generic bundle

Public forum cases support a cautious interpretation. In one case, an Amazon moderator reported that "format is not accepted" was associated with missing packaging-label images and a missing manufacturer/private-labeler name. In another, the case feedback stated that the submitted live images did not match the ASIN, were not physically on the product, and showed a different quantity from the listing. These are case-specific reports, not universal policy, but they demonstrate why the rejection message cannot be decoded from its headline alone.

"Provide clear photos" is not a useful operational instruction. A good evidence set must establish both identity and readability.

Use context-and-detail pairs.

Interactive image protocolBuild the evidence set in context-and-detail pairs

01 / Product / context

Image 1: full physical product

Show the complete product in one frame. The product should be recognizable as the model, variation, color, and configuration under review.

02 / Product / location

Image 2: product-side label location

Show the side, surface, seam, molded area, tag, or component where the permanent mark appears. Keep enough surrounding product visible to connect this image to Image 1.

03 / Product / detail

Image 3: product-side close-up

Show the mark at a resolution that permits the reviewer to read the visible text or code. Do not crop away every product feature. If one frame cannot provide both context and readability, use the preceding location image as the bridge.

04 / Package / context

Image 4: full retail packaging

Show the actual packaging associated with the unit. The product name, model, quantity, variation, or another identifier should be visible where possible.

05 / Package / location

Image 5: packaging-label location

Show the side of the package where the tracking information appears. If the information is visible through clear packaging, photograph the relationship between the product mark and the clear package.

06 / Package / detail

Image 6: packaging close-up

Show the packaging mark without glare, blur, folded edges, or cropped characters.

07 / Identity / match

Image 7: ASIN identity bridge

Show the model, item number, variation, pack count, or other physical detail connecting the submitted unit to the ASIN. This is especially important for bundles, multipacks, color variations, and revised packaging.

08 / Code / decode

Image 8: coded-information support

If the mark uses a code, provide the permitted supporting explanation or record that maps the visible code to the required information. Keep the original image unaltered. Use a separate explanation rather than digitally adding decoded fields to the photograph.

Technical controls for the full image set

Use the same physical unit and packaging revision throughout.
Do not combine images from different variations or production lots without an explicit reason.
Do not digitally insert, reconstruct, replace, or retouch the label.
Avoid graphic overlays that cover the product or mark.
Do not cut off package edges, label borders, date characters, or code segments.
Control glare on glossy packaging and molded surfaces.
Use sufficient resolution for ordinary review without artificial sharpening.
Keep the camera square to the label when perspective distortion affects readability.
Include all sides when Amazon's category instruction or case request asks for them.
Use descriptive filenames that identify the ASIN, surface, and purpose of the image.

Examples:

B0XXXX_product_full.jpg
B0XXXX_product_label_location.jpg
B0XXXX_product_label_closeup.jpg
B0XXXX_packaging_full.jpg
B0XXXX_packaging_label_closeup.jpg
B0XXXX_model_packcount.jpg

Three different image channels

A seller also must distinguish where the evidence appears:

Compliance request

Compliance submission images uploaded for the request.

Upload in the channel Amazon requested.

Product detail page

Product detail page images associated with the ASIN.

Do not assume listing imagery replaces case evidence.

Test report

Images embedded in a test report showing the tested sample.

Treat it as evidence of the tested sample only.

Channel matters

A reviewer may not treat an image in one channel as a substitute for a required image in another. If a case response refers to the detail page, uploading the image only inside a report may not answer the deficiency. If the compliance request asks for live images, a polished catalog render may not answer it even though it appears on the listing.

Evidence matrix

Stronger evidence, weak evidence, and contradictions

Stronger evidence, weak evidence, and contradictions
What must be proved	Strong evidence	Weak evidence	Contradiction
Physical product identity	Full-unit image plus visible model and variation features matching the ASIN	Label close-up with no recognizable product context	The photographed model, variation, or quantity differs from the ASIN
Product-side mark	Location image plus readable close-up on the actual item	Artwork, a supplier statement, or a close-up that does not show where the mark sits	The current unit has no permanent mark, or the submitted label is detached or digitally inserted
Packaging-side mark	Full package, label location, and readable close-up	Cropped text with no proof that it is on the retail package	The package is a different revision, belongs to another product, or carries no package-side mark
Responsible entity	Legible company name or unambiguous permanent identifier with a contact path	Unknown logo, seller statement, or code with no identified company	The physical mark identifies an entity that conflicts with the CPC, report, or submitted code record
Production location and date	Visible fields or documented code mapping tied to the photographed code	Country-of-origin text alone or a supplier spreadsheet with no physical-code link	The decoded location or date conflicts with the retained record or the photographed production code
Cohort information	Permanent batch, run, or lot code connected to retained records	A model number reused across every production run	The same photographed code is mapped to a different cohort in another submitted document
Permanence	Molded, engraved, sewn, printed, or securely affixed mark appropriate to the useful life	The image shows text but not the attachment or marking method	The evidence shows a removable hangtag, loose insert, temporary paper, or a mark absent from current production
ASIN match	Same model, color, size, quantity, components, and packaging revision	One matching feature without a full product-and-package identity view	A different variation, old package, incomplete set, or conflicting model number appears in the packet
Clear-packaging exception	Full image showing all required product information visible through the package	A close-up that hides the package material and visibility relationship	The actual package is opaque, the required mark is obscured, or the sale configuration differs from the image
Supporting documents	CPC, report, and records consistent with the physical item and catalog	A general pass statement without photographs or current-revision evidence	A document names a different model, age, company, product construction, or packaging revision

Evidence quality rule

The best evidence set does not maximize the number of files. It minimizes ambiguity.

CPSC expressly states that the tracking-label requirement is not a children's product safety rule requiring assessment by a CPSC-accepted third-party laboratory. CPSC also states that a CPC does not need to cite the tracking-label requirement.

That produces two important consequences.

Consequence 01

First, a tracking-label rejection alone is not a reason to purchase new safety testing.

Consequence 02

Second, a CPC or test report cannot cure a physical marking that is absent, temporary, unreadable, or placed on a different product.

Amazon may, depending on the category, accept product images or a test report as evidence of the mandatory tracking-label requirement. That is an Amazon documentation route, not a federal requirement that laboratories "certify" CPSIA Section 103.

A report may still be useful when it:

contains images of the actual tested product;
clearly identifies the model and responsible company;
shows the tracking mark on the test sample;
matches the ASIN and current product construction;
contains no conflict with the live product or packaging images.

A report is weaker for the present rejection when:

the photographed sample is a different variation;
the report predates a label or packaging revision;
only artwork appears;
the report says "pass" without showing the mark;
the report identifies a different manufacturer, importer, model, or age grading;
the current selling unit lacks the mark shown in the report.

If Amazon also identifies a failure involving ASTM F963, lead, phthalates, a product-specific standard, or another safety rule, that is a separate testing or certification issue. Do not merge it into the tracking-label diagnosis.

Critical boundary

A tracking-label deficiency is primarily a marking, traceability, identity, and evidence problem. New laboratory testing is relevant only if a separate applicable safety rule, test scope, product change, or Amazon category requirement creates an independent testing deficiency.

Repeatedly uploading the same packet is not a diagnostic method. Use a controlled review.

Rejection recoveryTen controlled steps—one coherent replacement packet

Step 1: preserve the exact rejection

Save:

the complete message, not only its subject line;
the ASIN and variation;
the case or request ID;
the date and time;
the named deficiency;
the policy page or product-category page linked by Amazon;
the files included in the submission.

Amazon policy pages and case instructions can change. The saved record establishes what the seller was asked to prove at that time.

Step 2: freeze the submitted version

Keep an unchanged copy of every submitted image and document. Assign a version, for example Submission 01.

Without a frozen version, it becomes difficult to determine which image Amazon reviewed, especially when filenames are reused or catalog images are updated separately.

Step 3: separate the rejection into proof elements

Rewrite the message as individual questions:

Was the mark shown on the product?
Was it shown on the packaging?
Was the company name visible?
Were date, location, and cohort ascertainable?
Did the unit match the ASIN?
Did Amazon request live images?
Did another category-specific rule appear?

Do not treat "format" as the only proof element.

Step 4: verify classification

Confirm whether the product is:

a children's product;
a toy or another specific regulated category;
a durable infant or toddler product under Part 1130;
an ASIN Amazon may have misclassified.

If classification is wrong, correcting label images may not resolve the root problem. The appeal should address classification with product design, intended-use, packaging, age, catalog, and marketing evidence.

Step 5: audit content without looking at the Amazon message

Independently test whether the marks make each federal element ascertainable. This prevents a vague Amazon response from narrowing the review too early.

Step 6: audit physical placement and permanence

Inspect an actual production unit, not artwork. Confirm how the mark is formed or attached and how it behaves during expected use.

Step 7: audit the identity chain

Compare the ASIN, variation, model, quantity, product, packaging, code, CPC, and report. Record every mismatch, including packaging revisions and multipack differences.

Step 8: choose the correct route

The next action may be:

reshoot existing compliant evidence;
correct catalog data;
explain a coded system;
document a recognized packaging circumstance;
correct physical product or packaging marking;
meet an additional product-specific requirement;
appeal a classification;
request case-specific clarification.

Step 9: create one coherent replacement packet

Do not simply append a new photograph to a contradictory packet. Build a clean version in which every image and document refers to the same product identity and label revision.

Create a short manifest:

filename;
surface shown;
fact proved;
ASIN/model/variation;
code or date visible;
related deficiency.

Step 10: resubmit against the exact deficiency

The response should state what changed in the evidence, not claim broadly that the product is "fully compliant."

For example:

The new submission includes a full image of the physical product, a context image showing the permanent mark on the lower interior seam, a readable close-up of that mark, the full retail package, and a close-up of the package mark. The visible model and 12-count quantity match ASIN [ASIN]. The code explanation maps the photographed batch code to the production month, location, and run.

Avoid promising approval. The seller can prove what was submitted; only Amazon controls the marketplace decision.

Where the public procedure ends

Amazon does not publish a complete decision logic for every compliance workflow or every rejection phrase. A fully documented packet may still require case-specific review or escalation.

An honest guide must therefore stop short of claims such as:

"Use this format and Amazon must approve it."
"This is the only tracking label Amazon accepts."
"A laboratory report guarantees reinstatement."
"The rejection proves the product violates federal law."

The defensible objective is narrower: identify the unresolved proof issue, submit consistent evidence, and preserve a record of the review.

Question 1

Find the first unresolved proof layer

Question 01 / Product scope

Is the ASIN correctly classified as a children’s product?

Question 02 / Physical mark

Is a permanent tracking mark physically present on the product?

Question 03 / Evidence set

Does the packet show product and packaging evidence in context and close-up?

Question 04 / ASIN identity

Do the product, package, variation, quantity, and documents match the ASIN?

Question 05 / Coded information

If a code is used, can it be reliably decoded to the required production facts?

Question 06 / Additional rule

Does Part 1130 or another category-specific rule add requirements?

Question 07 / Case outcome

After those layers are resolved, is the coherent packet still rejected?

Route A: the ASIN is not a children's product

Do not create a children's-product tracking label merely to make an incorrect classification disappear. Audit the intended-use and catalog evidence, correct inaccurate attributes where permitted, and use the available appeal or review route.

Route B: the physical product lacks a permanent mark

Stop treating the problem as photography. A digital label, detached paper sample, CPC, or supplier letter does not put a mark on the product. Correct the production marking and determine how existing inventory is affected before submitting new live images.

Route C: the mark exists, but the evidence set is incomplete

Use the context-and-detail image protocol. Show the product, packaging, mark locations, close-ups, and ASIN identity bridge.

Route D: the evidence conflicts with the ASIN

Determine whether the catalog is wrong, the wrong unit was photographed, or the documents cover a different variation. Correct the appropriate layer before resubmitting.

Route E: coded information is not self-explanatory

Do not replace a lawful coded system merely because the code is not human-readable at first glance. Confirm that the company is identified, the consumer has a contact path, and the code reliably maps to the required information. Then provide a permitted explanation tied to the visible code.

Route F: Part 1130 or another category rule applies

Complete the additional rule analysis. Do not describe the additional address, model, contact, or registration requirements as universal CPSIA tracking-label fields.

Route G: the complete packet is still rejected

Preserve the versions, identify the exact unresolved statement, and request targeted case review. Ask which specific element is not accepted: product-side placement, packaging-side placement, entity, date, location, cohort, permanence, ASIN identity, or category scope.

Evidence route: submit the coherent packet

The physical marks, code record, product and packaging images, ASIN identity, and applicable rule set are aligned. Submit against the exact deficiency and preserve the version sent.

This guided diagnostic organizes the article’s evidence routes. It is not a legal determination or a guarantee of Amazon approval.

Scenario 1: the label is readable, but the pack count does not match

A seller offers a 12-count children's craft set. The compliance submission includes:

a close-up of a readable batch code;
a CPC for the model family;
a product photograph showing three pieces;
no full image of the 12-count retail package.

Amazon returns a tracking-label or ASIN-match rejection.

Diagnosis: The close-up may prove that a code exists, but the evidence does not connect that code to the 12-count ASIN. The reviewer cannot verify that the photographed three-piece unit is the listed configuration or that the retail packaging carries the required information.

Correct route: Photograph the actual 12-count unit and retail package. Include the full product, quantity, packaging identity, product-side mark, and packaging-side mark. Do not reuse a label close-up from another configuration merely because the text is identical.

Scenario 2: a small silicone bowl has information only on the package

A children's silicone bowl has a brand molded into the base. The packaging lists a production location, month/year, and batch. The seller argues that product marking is impracticable because the bowl is small and the label would affect appearance.

Amazon requests live images showing tracking information on the product and packaging.

Diagnosis: This is not resolved by saying "there is no space." The seller must first determine whether the existing molded brand plus another permanent product code could make the information ascertainable. Size, material, available inconspicuous locations, peer practices, and product function all matter. Packaging may be fully marked even when a product-side limitation exists.

Correct route: Create a documented practicability analysis, inspect whether permanent product marking is feasible, and verify how the company maps any product code to the packaging cohort. For Amazon, provide the physical product, molded mark, package, package code, and the explanation appropriate to the case. If the product should have been marked and was not, photography cannot cure the production defect.

Scenario 3: the report says "CPSIA Section 103 - Pass," but the current unit is unmarked

A laboratory report contains a line stating that the sample passed a tracking-label review. The CPC and test report match the model name. Current inventory, however, has only a removable hangtag and no permanent product-side mark.

The seller submits the report repeatedly after Amazon asks for live images.

Diagnosis: The seller is relying on the wrong type of evidence. Federal law does not require third-party laboratory assessment of the tracking label, and a report statement does not create a permanent mark on current inventory. A removable hangtag on a textile item generally does not remain for the useful life of the product.

Correct route: Determine why current production differs from the reported sample, correct the physical marking, assess affected inventory, and then provide live images of the corrected unit and packaging. Ordering the same safety tests again would not, by itself, solve the marking defect.

Do not assume FNSKU, UPC, or an Amazon barcode is a CPSIA tracking system.
Do not invent a production date or batch to satisfy a review.
Do not digitally add the label to a product photograph.
Do not photograph different variations and present them as one unit.
Do not rely on a CPC as proof that the current physical product is marked.
Do not order new safety testing solely because a tracking-label image was rejected.
Do not claim marking is impracticable without a considered, documented reason.
Do not state that a U.S. address is universally required for every children's tracking label.
Do not treat Amazon's rejection headline as a complete statement of federal law.
Do not repeatedly upload the same packet without identifying a new proof element.

Why does Amazon say "The tracking label format is not accepted" when all fields are present?

Because the message can cover more than field content. Amazon may be unable to verify that the mark is physically on the product or packaging, that it is permanent, that a code can be interpreted, or that the photographed unit matches the ASIN. CPSC does not prescribe one mandatory tracking-label layout, so the word "format" should not be read as proof of a federal template violation.

Must the tracking information appear on both the product and packaging?

In most instances, both must be marked to the extent practicable. CPSC recognizes circumstances involving clear packaging, no retail packaging, reusable storage containers, small or difficult-to-mark products, and other physical limitations. Those circumstances are fact-specific and do not create a general packaging-only option.

Can a sticker be used as a CPSIA tracking label?

Potentially, under CPSC guidance, if it satisfies the permanency standard for the surface. A product mark should remain for the product's useful life; a disposable-package mark must reach the consumer. A removable hangtag or temporary label may fail, especially on textiles. Amazon may also apply a stricter evidence instruction to paper labels stuck on products.

Can the production information be coded?

Yes. CPSC permits codes if the required information remains ascertainable. The responsible company should be identified, a consumer should know whom to contact, and the company should retain a reliable code-to-production record.

Is a U.S. address always required?

Not as a universal field under the general CPSIA Section 103 tracking-label requirement. Amazon's public guidance states that the manufacturer or private labeler listed on the tracking label may be domestic or foreign. A U.S. address and telephone number are additional requirements for defined durable infant or toddler products under Part 1130 and may also appear in category-specific requests.

Does a CPC prove compliance with the tracking-label requirement?

No. CPSC states that tracking labels do not require third-party laboratory assessment and do not need to be cited in the CPC. The CPC may help establish product identity or responsible-party consistency, but it does not prove that the current item and package carry permanent marks.

Can a test report replace live images?

Amazon's category pages may allow product images or a test report as evidence in some workflows. Whether a report answers the request depends on the category and case. A report showing the actual tested product may help, but it does not prove that a different current production unit or packaging revision is marked.

What if the product has no retail packaging?

CPSC states that when no retail packaging encloses the product, labeling the product with the tracking information can be sufficient; an additional hangtag is not required merely to create packaging evidence. The seller should still show the actual sale configuration and follow any case-specific Amazon image instruction.

What if all information is visible through clear packaging?

CPSC states that if all required product tracking information is plainly visible through clear outer packaging, the same information does not need to be duplicated on that outer package. The photographs should prove the clear-package relationship, not merely provide a close-up of the product mark.

Should the seller submit the old packet plus one new photo?

Only if the complete set remains coherent. If the old packet contains a different variation, old packaging, an incomplete quantity, or a conflicting label, adding one correct image may make the submission more confusing. Create a clean, versioned replacement packet when necessary.

15 U.S.C. § 2063(a)(5), enacted through CPSIA Section 103Statutory basis for permanent distinguishing marks on children's products and packagingJuly 27, 2026
CPSC Tracking Label Business GuidanceOfficial CPSC summary of required information, coded information, responsibility, and CPC/testing boundaryJuly 27, 2026
CPSC Tracking Label FAQOfficial explanations of date, location, format, permanence, adhesives, product/packaging circumstances, and practicabilityJuly 27, 2026
CPSC Statement of Policy on Section 103(a)Commission interpretation and enforcement policy; explains totality of marks and ascertainabilityJuly 27, 2026
16 CFR Part 1130Current eCFR requirements for defined durable infant or toddler productsJuly 27, 2026
CPSC Durable Infant or Toddler Product Labeling TableOfficial comparison of general tracking elements and additional registration/product-identification dutiesJuly 27, 2026
Amazon: Marking and Labeling Requirements for Children's ProductsPublic Amazon marketplace guidance for tracking-label review, including the domestic-or-foreign entity noteJuly 27, 2026
Amazon: CPSC-Regulated ProductsPublic Amazon overview of CPSC product and evidence requirementsJuly 27, 2026
Amazon: Product Compliance DocumentationPublic Amazon evidence and product-image guidance, including its paper-label warningJuly 27, 2026
Amazon forum case: missing packaging evidence under "format" rejectionCase-specific seller report and Amazon moderator response; operational example, not general policyJuly 27, 2026
Amazon forum case: physical images and ASIN mismatchCase-specific moderator description of product, packaging, quantity, and ASIN inconsistenciesJuly 27, 2026
Amazon forum case: repeated "format is not accepted" messageSeller-reported experience illustrating that the message may persist despite claimed field completenessJuly 27, 2026

How the sources are used

Source methodOfficial rules, marketplace policy, reported experience, and analysis remain separate

Official legal

Official legal requirements in this article come from the statute, CPSC guidance, CPSC FAQs, and the eCFR.

Federal requirement

Amazon public

Amazon marketplace requirements come from Amazon's public help pages. Amazon may issue additional ASIN-, category-, account-, or case-specific instructions inside Seller Central.

Marketplace requirement

Seller reports

Seller-reported experience and moderator case responses are used only to demonstrate recurring operational patterns. They are not treated as federal law, statistical evidence, or universal Amazon policy.

Operational experience

Expert analysis

Expert analysis includes the evidence-chain model, context-and-detail image protocol, rejection-decoder structure, version-control workflow, and diagnostic routes. These are operational methods derived from the cited requirements; they are not represented as official Amazon or CPSC procedures.

Derived method

An Amazon tracking-label rejection should not begin with a search for a different graphic template.

Begin with five questions:

Is the ASIN correctly classified as a children's product, and does an additional product-specific rule apply?
Can each required source and production fact be ascertained from the permanent marks and supporting system?
Are the product and packaging marked as required for their actual physical circumstances?
Does one coherent identity chain connect the ASIN, variation, physical unit, packaging, code, and documents?
Can the Amazon reviewer see and understand that chain in the requested evidence channel?

If the answer to one question is no, the next step becomes specific. Reshoot the evidence, correct the catalog, explain the code, document the physical circumstance, correct the production marking, meet the additional rule, or appeal the classification.

If every answer is yes and the rejection continues, preserve the record and request a case-specific explanation of the unresolved element. That is more defensible than guessing at an unpublished format - and far more useful than submitting the same files again.

Editorial notice: This material is an independent, source-led explanation for commercial and compliance operations. Registry Intelligence is not affiliated with Amazon or the U.S. Consumer Product Safety Commission. The article does not provide legal advice and does not guarantee marketplace approval.

Author / Editorial responsibility

Natallia Vasilyeva

Author and founder of Registry Intelligence

View author profile

Official-source marketplace research

Prepared and reviewed using current CPSC, CBP, Amazon marketplace, eCFR, and other official U.S. sources. The research focuses on certification evidence, product testing, CPSC eFiling, structured regulatory data, and importer and private-label workflows.

Editorial boundary

Independent educational resource. Registry Intelligence is not affiliated with, endorsed by, or operated by Amazon, the U.S. Consumer Product Safety Commission, or U.S. Customs and Border Protection. This material is informational and does not constitute legal advice, product certification, customs classification, or an official applicability determination. Verify current product-specific requirements with the responsible platform and agencies.