Ask a customs expert
Questions about customs, classification, or trade compliance
Answers about classifications, sources, tariff updates and everyday tasks. Results support your review; they do not replace your customs decision.
Questions about customs, classification, or trade compliance
Report a bug, suggest an improvement, or provide product feedback
Contact usNeeds details means the attempt has not produced a complete code and more product information may be needed. Needs review can include a supported but conditional code: read the reasoning and the unresolved facts before using it. Needs attention can indicate a failed attempt; an older or imported code still on the product is not proof that the failed run verified it.
Open the product's classification for the selected market, read the explanation and supply the requested facts before retrying. U.S., EU and Canadian results are separate. A date labelled attempted records work on the product, not a successful classification.
Update the affected products through ordinary editing or Export for update and its workbook import. Check that each change describes the actual product; similar products do not necessarily share composition, origin or specifications.
After saving the correct facts, select the affected products and classify the required markets again.
Choose the level when starting classification: six digits identifies the HS subheading; eight digits identifies the national or regional tariff level (CN in the EU); ten digits gives the full code used by this app’s duty and preference workflows. The default is ten. A verified six- or eight-digit result can be complete for the level you requested without being a complete duty assessment. Codes are verified at their actual level, never padded or guessed.
Human verified records an explicit user decision. Review the code, product facts, reasoning and selected market before confirming it. Neither human nor assistant verification establishes every duty, preference or regulatory requirement.
Read the selected market’s explanation and Classification evidence, then use Edit details to correct the product’s composition, use or other facts. Save and reclassify the affected markets. Existing recorded answers remain available in the evidence view; it does not add another confirmation system.
For a correction to the shared product description or Additional item details, use Edit details; shared facts can affect multiple markets. Human-confirmed classifications require explicit unverification before their evidence can change. Answers from an older product revision are shown separately, not silently reused. Older results without structured questions do not gain an invented assessment from their prose.
For Photos, check both the extracted information and the details supplied for the selected market. State a correction explicitly if the image was misunderstood. A photograph cannot establish hidden composition, origin, value or manufacturing processes.
The model assigns an evidence-strength score based on the product facts and supporting tariff and ruling evidence. Complete, consistent details and relevant evidence support greater confidence; missing or conflicting details weaken it. It is not a calibrated probability that a customs authority will agree.
A score of 85% or above can support assistant verification, but the score alone is not enough. Decisive missing facts, assumptions or conflicting product identity keep a conditional result in review. Human verified is separate and requires a person's explicit confirmation.
No. Review filters select saved products; they do not change the score, code or verification status. Select the destination market before reviewing confidence or status, and distinguish a missing score from a score of zero. Read the reasoning rather than relying only on a badge.
The source families used by the tools include the U.S. International Trade Commission's HTSUS and CBP CROSS rulings for the U.S.; European Commission TARIC and published EBTI decisions for the EU; and the CBSA Customs Tariff and published Canadian rulings for Canada. A result uses the evidence actually returned by its tools, not every source in this list.
Tools use stored reference datasets and, for supported lookups, official-source requests or checks. Opening a result does not guarantee a new live request to the issuing authority. Check its source links, release or observation date, entry-date coverage and any stated limitations. A model explanation is not itself an official source.
Compare a ruling's product facts with yours and check the current code separately. Older reasoning may remain useful, but an old code must not automatically be reused. Review source-reported modification or revocation information where available; missing legal-status metadata is not confirmation that the ruling is active.
News and Rulings contain saved workspace matches, not an exhaustive search of all relevant publications. New, Reviewed and Dismissed are feed-workflow labels, not legal-validity decisions. A match is a lead to review, not a conclusion that your product is affected; no match is not clearance.
Context displays source links retained for the conversation. A missing card does not prove that no lookup ran. Check the answer's citations and the selected conversation. If a cited link or expected card is missing, report the conversation, approximate time and affected source through Feedback & Support; administrators can investigate the recorded diagnostics.
Reference updates, calculations and workspace monitoring are separate processes:
In Master Data, select EU and the entry date, set the catalogue filters, then open Check saved EU codes for a date. Check matching EU codes includes all matching pages, up to 5,000 products. Repeated complete codes share one lookup; a short or missing code is identified separately.
Declarable on selected date means the dated source contains that code, not that it is the right classification for the product. A verified no-match is different from Source check unavailable. This action does not replace codes, calculate duty impacts or run continuous monitoring. Stay on the page while it runs, or stop remaining checks; export the results to retain completed and Not checked outcomes.
There is no single refresh interval for all sources. A stored release, a source check during a request and a scheduled workspace-matching job have different timestamps and purposes. Do not infer the source's freshness from the application version, a recent calculation time or the presence of a News or Rulings tab.
Monitoring jobs can be enabled, disabled, delayed or unsuccessful. Administrators can review the available configuration and run history in Jobs & Schedules; configuration alone does not prove a completed run or fresh source ingestion. Ask your administrator or support team to confirm the current process and coverage for the source you need. Some source maintenance requires operator action.
Review the affected product rather than treating a saved amount as a new quote:
Compare the market, entry date, origin, product facts and selected treatment before comparing amounts. A saved snapshot can represent earlier inputs or evidence. Stale is a reason to review or recalculate, not an assessment of zero duty. An unavailable result means the application could not provide that result; it does not establish that the saved calculation or applicable charge is zero.
For a loading or provider error, try the displayed retry action once and report a persistent failure with the workspace, product, market, entry date and approximate time. Changing a product fact does not fix an unresolved source-verification problem. Do not treat a partially completed catalogue run as a fully calculated catalogue.
Use Look up base rate in TLC with an exact code and entry date to retrieve the published general/MFN base-rate reference without inventing an origin. A base rate is not a complete payable tariff stack. Origin, preferences, additional duties, tax treatment and shipment facts are assessed separately.
In Master Data, select EU and show EU tariff stack under Columns. Open a product's tariff details and choose Look up & save MFN base rate, or Refresh saved MFN base rate for an existing reference. It is saved for that code and entry date separately from the full duty result. Changing origin does not remove this origin-independent reference; the full origin-dependent assessment still needs recalculation. A different code or entry date needs its own reference.
Country of origin alone does not establish a preference claim. Select a program only when its qualifying conditions are met; an available program or screened candidate is not a confirmed entitlement.
Free base duty does not resolve additional duties or taxes. Read the missing-information prompts beside the relevant inputs and distinguish them from an unresolved source or backend check. Independently verified base duty can remain visible while the complete total is withheld.
Specific or compound rates can require weight, volume or reporting quantities in addition to customs value. Use the units requested. GST/VAT confirmations and other tax-base inputs are separate from customs-duty requirements. An amount not calculated or not entered is not zero.
Read What this result includes and the coverage details. The subtotal combines customs value, calculated charges and entered costs within the stated scope; it is not a complete assessment of every import liability. Freight, insurance, brokerage and other expenses may need separate entries.
An amount entered only to establish a tax base is not automatically an added expense. Follow the field guidance and record an actual expense only once. Review exclusions and unresolved regulatory requirements separately from the displayed arithmetic.
Use Export for update (this page) or Export for update (all matching), edit the supported fact columns, then choose Update existing products and preview the .xlsx file. The controlled workbook supports up to 5,000 rows and 4 MB. Keep Product ID, Expected updated at and Format unchanged; products are matched by ID, not by SKU.
Blank cells leave saved values unchanged. Use [CLEAR] only to remove an optional value; descriptions cannot be cleared. Classifications and verification are not editable in this workbook. Review the before/after differences and select the ready rows you want to apply. Stale or protected rows must be resolved separately.
Each selected product saves separately. Stop remaining updates waits for the current save; completed saves remain and later rows are not attempted. An unconfirmed save is not retried automatically. Refresh and export current versions before trying remaining changes again. The update does not start classification, screening or duty calculation.
Priority view applies named filters and ordering across the selected market's catalogue, not just the visible page. You can find classifications needing review, missing codes, higher recorded unit values, comparable saved duty rates, or existing risk flags. Check the explanation beside the selected view; changing its defining filters or order makes the selection custom.
Recorded unit value is not annual spend. The duty view uses comparable saved rates for the selected date and excludes conditional, missing and stale rates rather than calling them zero. Risk views show existing supported flags or unavailable screening, not comprehensive EU regulatory clearance or a fresh screening.
No. Saving a product document and activating it as classification evidence are different actions. Follow the confirmation before using selected evidence: reassessment can reset automated classifications across markets to draft, and human-confirmed results require explicit unverification first. Activation does not itself start classification.
Follow the file types and size limits shown by the upload control. Chat attachments belong to that conversation; reading an attachment or saving a chat answer is not the same as applying a classification to a catalogue product.
Select the destination market and review its independent result. Save the selected market to the catalogue when you want to retain it there; Discuss in chat opens that market's conversation context. Check the destination and product before applying any later answer.
Supply distinguishing facts such as materials and percentages, construction, function, dimensions and how the goods are imported. Do not assume a whole catalogue was audited because a photo or attachment was read.
Fast is for focused answers and directly requested lookups or calculations. Research can gather and compare more evidence and take longer. Neither mode guarantees that every authority or product fact has been found. Check the sources and precise uncertainty in the answer, not just whether the run completed.
Background research exposes progress and saves its final answer. You can navigate away and return to the conversation. Steering can correct facts during a run; cancellation stops the run rather than approving a classification.
Specify the saved products and market you want, for example: Show five products from this workspace and their saved EU classifications. Saved values are not a fresh classification unless you request and complete that work separately.
When Use Master Data view is selected, chat receives the selected catalogue market, filters and ordering. Check that summary before asking for a product list; uncheck it to ignore the view. A follow-up can request the next products or another market's saved classifications for the same products.
Only upload information you are authorized to use in this service. Product records, uploaded evidence and saved conversations can remain available in their workspace or conversation; closing a browser tab is not a deletion request. Review workspace membership before adding customer-sensitive information, and avoid unnecessary personal information or credentials.
Questions about retention, deletion, hosting location, model-provider processing or contractual confidentiality should go to your organization's administrator or privacy contact. A product-help statement is not a substitute for the applicable privacy notice or agreement.
Ask an expert prepares a draft for you to review with your question and the available workspace or product link. It does not automatically send the draft or attach conversations, documents or tool results. A link does not grant the recipient workspace access.
Contact us is for product feedback and support. Review the destination and the information you choose to submit. Redact unrelated customer details and never include passwords, API keys, cookies or authorization headers in screenshots or logs.
For the applicable privacy notice and data-handling arrangements, contact your organization's administrator or privacy team.
Use Ask an expert for customs, classification or trade-compliance advice. Use Contact us under Feedback & Support for a bug, an improvement suggestion or product feedback.
For a problem report, include the feature, workspace or product link, selected market and entry date where relevant, the steps taken, expected versus actual behavior, approximate time and a redacted screenshot. If a job failed, include its visible status or reference. Do not repeatedly restart a long-running job without checking its current state.