--- title: "HTS revisions: record the editions before review" description: "Compare two named HTS editions, preserve download evidence, and prepare a broker review brief that separates publication labels from effective-date text." canonical: "https://scalewithsearch.com/articles/hts-revision-edition-date-retailer-change-brief" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # HTS revision dates: prepare a retailer change brief from two named editions Before asking whether a tariff change affects an order, identify the two schedule editions behind the question. A screenshot labeled “current tariff” leaves the broker guessing which text the buyer inspected. A useful change brief names both editions, preserves their sources, and separates observed wording from unresolved applicability. The retailer's job here is evidence preparation. Start with a classification already approved for the relevant product by your customs broker. Record who approved it and which product specification supported that review. Keep a supplier's suggested code and an unreviewed catalog description in separate fields. This guide proposes a worksheet for that handoff. It does not classify merchandise, choose a duty rate, or recommend entry timing. The [retail intelligence overview](/intelligence/retail-and-ecommerce) places this task beside other public-source review work. The broader [retail and ecommerce page](/for/retail-and-ecommerce) covers store office tasks. ## Name both editions before comparing text The [USITC HTS archive](https://www.usitc.gov/harmonized_tariff_information/hts/archive/list) provides named editions and downloadable formats. On October 28, 2026, the inspected page listed 2026 HTS Revision 20 with a September 28 label. It listed Revision 21 with an October 9 label. The [tariff information page](https://www.usitc.gov/harmonized_tariff_information) separately announced publication of Revision 21 on October 9. Use the complete edition names in your brief. “September file” and “latest download” are weak references because another person cannot identify them without further explanation. Preserve the displayed date label exactly, then describe what that label establishes. For a comparison using these editions, retain the [Revision 20 JSON download](https://www.usitc.gov/sites/default/files/tata/hts/hts_2026_revision_20_json.json) and [Revision 21 JSON download](https://www.usitc.gov/sites/default/files/tata/hts/hts_2026_revision_21_json.json). These links identify actual edition files inspected for this guide. They do not establish that either edition controls a particular shipment. During our October 28, 2026 check, those two downloads returned identical bytes. This establishes matching downloaded content only, without explaining why the files match. It does not establish unchanged legal notes or shipment treatment. The worked change below is synthetic, rather than an observed difference between these downloads. Save the archive page reference beside each download reference. Record the retrieval time with a time zone and the downloaded filename. If your process calculates a file hash, store it as a file-identity check. A hash supports later comparison of saved bytes; it does not establish a legal effective date. Keep the source file unchanged. Put annotations and normalized comparison text in separate working files. If you correct a display problem, preserve the original value alongside your correction so another reviewer can reconstruct the comparison. ## Separate publication, retrieval, and effective-date language Use three separate fields: schedule publication label, your retrieval time, and applicable effective-date language awaiting broker review. Do not fill the third field by copying either of the first two. The archive links modification sources under its edition entries. One source linked under Revision 21 illustrates the distinction. The [official Federal Register notice, 91 FR 64211–64212](https://www.govinfo.gov/content/pkg/FR-2026-10-07/pdf/2026-20511.pdf), was published October 7, 2026. Its Dates section states July 1, 2026, for the conforming amendment. Its Annex adds entry-related language. Those are document-specific statements, not instructions for your merchandise. That example is a reason to read the linked document rather than treat October 9 as a universal starting date. In your own brief, identify the relevant modification source and its section. Ask the broker which language matters for the product and entry facts supplied. If a document incorporates another annex or publication, list that reference as another reading task. Do not mark the source chain complete because the first document opened. Retain unresolved references until the reviewer has checked them or explained why they do not affect the question. A browser download time, server modification header, or local file creation date belongs in technical provenance. None of those observations supplies the controlling text. Your worksheet should make an attempted substitution visible before someone uses it in purchasing instructions. ## Keep the approved product record attached Use one product reference that the retailer and broker can both recognize. Attach the exact specification version used in the earlier review. Keep materials, function, construction, and other supplied product facts in their original supporting documents. The [USITC FAQ](https://www.usitc.gov/harmonized_tariff_information/frequently_asked_questions) explains why keyword search alone is insufficient for classification. It describes the HTS hierarchy and the role of legal descriptions and notes. A similar product name in a new search cannot replace the reviewed product record. Your comparison scope might contain one approved code or several codes with separate approval records. State that scope before reading differences. Do not quietly add similar catalog products because they share a supplier or merchandising category. If the supplier changes the product specification, create a separate product question. A text comparison against an old approval cannot establish whether that approval still fits the changed goods. Label the relationship unresolved and attach both specification versions. Use the broker's written review as evidence of what was reviewed, without presenting it as a binding government ruling. If the business holds a ruling or another relevant document, preserve its identifier separately. Ask the broker to assess its relationship to the current question. ## Compare defined portions of the schedule Write a comparison statement that identifies both source editions and the inspected fields. “Description differs between saved editions A and B” is narrower and more useful than “tariffs changed.” Include the parent text and references needed to understand the row. The inspected edition JSON files contain fields such as `htsno`, `indent`, `description`, `units`, `general`, `special`, `other`, and `footnotes`. Preserve their original names in the evidence. Explain any friendly worksheet labels separately rather than replacing source terminology without a trace. An empty field should remain visibly empty in the retained source. Do not convert it into zero, “Free,” or “not applicable.” If the meaning is unclear, make that an explicit broker question. Likewise, preserve punctuation and reference text before formatting a readable comparison. Separate a changed description from a changed rate field or note reference. These observations ask different questions. A stable copied rate field cannot establish that the entire source context is unchanged. For the accompanying reading task, use the [HTS notes and footnotes guide](/articles/hts-footnotes-chapter-notes-retailer-tariff-review). State the limits of the comparison beside the result. If you inspected only the description and footnotes, say so. A reviewer should not have to inspect your software or working notes to discover that other sections were outside scope. ## Worked example: a synthetic wording change The following example is entirely synthetic. Product `STORE-A`, approved-code placeholder `BROKER-CODE-A`, and the wording changes do not represent actual merchandise or an actual HTS amendment. No number in the example is a commodity classification. A retailer retains two named official edition files as evidence containers. In the example worksheet, saved snapshot A shows description placeholder “Component type A.” Snapshot B shows “Component type A, revised wording.” The comparison records a description difference and makes no statement about duty. The buyer attaches the same product specification to both observations. The earlier broker review is attached by reference. The buyer also preserves the surrounding heading text, indentation, source reference markers, and linked modification-source list for review. The brief's question reads: “Does this observed wording difference affect your earlier review of product STORE-A? Which controlling text and product facts are needed?” The question invites a review without presupposing the answer. The broker has not yet checked the modification source. The entry date and supporting origin evidence are also missing. The worksheet therefore records “applicability unresolved,” names the missing evidence, and assigns the next reading step. Purchasing receives that status rather than a revised duty instruction. If the broker later concludes that the wording difference does not affect this product, preserve that decision with its scope and date. Do not delete the original observation. A later reader needs to distinguish the observed text difference from the reviewed business conclusion. ## Reject a comparison that lacks the earlier source Consider a second synthetic case. A buyer has last month's copied rate cell and today's downloaded schedule. The earlier row has no edition name, surrounding text, or retained source file. The buyer asks the worksheet to report a rate change. Reject that comparison as incomplete. You can report what the old worksheet contains and what today's source shows. You cannot establish the exact earlier official text from an unattributed copied value. A current download cannot repair that historical gap. Use a status such as “earlier edition unidentified; before-and-after finding unavailable.” Ask the earlier reviewer for the retained file or source reference. If an appropriate archive edition can be identified, record how that identification was established before comparing it. Also reject an automatic effective-date field filled from a file timestamp. Replace the value with “controlling effective-date language not reviewed.” Preserve the timestamp in retrieval evidence, where it answers a different question. The rejected brief still has value as a missing-evidence list. It identifies why the reviewer cannot answer yet and what could resolve the gap. It should never become a reassuring “no change” result because the comparison could not run. ## Close the question without erasing its evidence Give the review an explicit end state. “Awaiting product evidence,” “awaiting source review,” and “broker response recorded” describe different stages. Keep the owner and next required item beside each open question. Avoid a single “done” box that hides whether anyone checked applicability. When the broker requests more information, attach the response to the existing brief. Preserve the original question and record which supplied fact changed. A corrected material description, for example, should remain traceable to the supplier document that supports it. Treat a later product variant as a new scope question. Do not automatically reuse a decision made for the earlier specification. The old brief remains useful because it shows the evidence and reasoning previously reviewed, including the limits the broker stated. Keep business instructions separate from the research observation. If an authorized person issues a purchasing instruction after review, link that instruction to the decision. The source comparison itself should remain a description of inspected text. Finally, set a follow-up only for the unresolved work you can name. A missing annex needs a source-reading task. An unknown product attribute needs a supplier-document task. Distinct next steps make the handoff useful without pretending the comparison resolved the import question. ## Use a worksheet the broker can read without your explanation This is a recommended retailer worksheet, not a USITC form or filing requirement. Keep separate rows for each reviewed product and each observed change. Attach the unchanged source files rather than pasting only a cropped result. | Worksheet field | Evidence or question to retain | | --- | --- | | Product reference | Store SKU and exact specification version | | Prior review | Broker decision reference, date, and reviewed scope | | Earlier edition | Full name, displayed date label, archive URL, download URL | | Later edition | Full name, displayed date label, archive URL, download URL | | Retrieval evidence | Saved filenames, retrieval timestamps, optional file hashes | | Comparison scope | Approved code reference and inspected surrounding sections | | Observed difference | Separate description, rate-field, note, and reference observations | | Modification source | Document identifier, link, relevant section, outstanding annexes | | Effective-date question | Exact source language reference and unresolved applicability | | Missing entry facts | Product, origin, entry, or other evidence requested by the broker | | Review result | Reviewer, decision date, scope, reasons, and open questions | | Business follow-through | Approved instruction reference, or explicit pending status | Before handing it over, test whether another staff member can locate both editions and the changed passage. Ask them to identify the unresolved question. If they cannot, fix the references before expanding the comparison to more products. Retain the broker's response beside the brief, including any request for corrected product facts. The [business memory guide](/articles/business-memory-for-ai-agents-guide) explains how owned records support later work. Here, the reusable record must carry the edition evidence and review limits with the conclusion. Scale With Search can scope the evidence collection, comparison record, and review handoff around your existing product files. Start with one approved product record and two named editions. [Discuss a scoped build](/work) Continue the website review: [AI-native retail and ecommerce: the first functions to build](/articles/ai-native-retail-first-functions); [Brick-and-mortar business: plan the website around visits](/articles/brick-and-mortar-store-website-plan); [CPSC recall matching: compare a product model with your retail SKU](/articles/cpsc-recall-model-match-retail-sku); [CPSC recall dates: keep the announcement, publication update, and store review separate](/articles/cpsc-recall-publication-dates-review-history); [Dealer SEO: make vehicle inventory pages useful](/articles/dealer-seo-inventory-page-checklist); [Google Business Profile products: check the right editor](/articles/google-business-profile-products-or-services); [HTS footnotes and chapter notes: preserve the references in a retailer tariff review](/articles/hts-footnotes-chapter-notes-retailer-tariff-review); [Fix a Merchant Center price mismatch on your store site](/articles/merchant-center-price-mismatch-store-website); [Retail and ecommerce AI rules: data, approvals, and spend](/articles/retail-ai-rules-data-approvals-spend); [Retail gift bundles in Merchant Center: what to submit](/articles/retail-gift-bundles-merchant-center); [Store guest checkout: check Google's requirements](/articles/retail-guest-checkout-google-requirements); [Fix a Merchant Center availability mismatch](/articles/retail-merchant-center-availability-mismatch); [Missing GTIN in Merchant Center: check before you guess](/articles/retail-merchant-center-missing-gtin); [Fix a rejected product image in Merchant Center](/articles/retail-merchant-center-product-image-disapproval); [Fix a Merchant Center shipping cost mismatch](/articles/retail-merchant-center-shipping-cost-mismatch); [Merchant Center website verification and claim problems](/articles/retail-merchant-center-website-verification-claim); [Product variants not grouped in Merchant Center](/articles/retail-product-variants-merchant-center-grouping); [Make store pickup instructions match your Google listing](/articles/retail-store-pickup-website-google-check); [Fix a store return policy that appears wrong on Google](/articles/store-return-policy-wrong-google). [retail stores and ecommerce sellers](/for/retail-and-ecommerce): website and search resources. ## Related: retail stores and ecommerce sellers - [Fix a Merchant Center price mismatch on your store site](/articles/merchant-center-price-mismatch-store-website) - [Retail and ecommerce AI rules: data, approvals, and spend](/articles/retail-ai-rules-data-approvals-spend) - [Retail gift bundles in Merchant Center: what to submit](/articles/retail-gift-bundles-merchant-center) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```