製造業者・輸出者の皆さまへ

関税がひとりでにP&Lに入り込む前に、関税を見据えて設計しましょう。

分類は港ではなく、部品表から始まります。GingerControlは製品チームとサプライチェーンチームが設計段階で関税エクスポージャーを見られるようにし、エンジニアリングの選択と着地コストの判断が同じ部屋で行われるようにします。

出発点

製品が港に着くころには、重要な判断はすでに下されています。材料の選択、原産国、製品アーキテクチャのすべてが、どのHTSコードに該当しどの税率が適用されるかを決めます。GingerControlは、製造業者がそうした判断を関税データを手にしながら下し、輸出するものを規制対象がないか審査し、完成品として再び出ていくインプットにすでに支払った関税を回収できるよう支援します。

得られるもの

チームの実際の働き方に合わせて設計。

BOMレベルの分類

部品表を投入すれば、各構成部品がどのHTSコードと関税に対応するかが分かります。

設計段階の関税チェック

わずかな仕様変更が、製品を別の分類と別の関税に移すことがあります。エンジニアリングが設計を確定する前に、それを見つけましょう。

拠点をまたいだ原産地計画

複数の国に拠点を持つ製造業者向けに、Parts Libraryは各市場にとってどの原産地が最良の着地コストを生むかを示します。

BOMからHTSへ

分類は港ではなく、上流から始まる。

各構成部品をHTS Classification Researcherに通し、そのHTSコード、税率、適用可能な特別プログラムに対応づけます。別の生地の混紡、留め具、包装が、製品をより有利な項に移すことがあります。Gingerは、貨物が港で再分類された後ではなく、設計段階でそうしたレバーを見つける手助けをします。

輸出側

出荷するものを審査し、支払ったものを回収する。

Export Control Classifierは、CCLの全10カテゴリーに照らして製品をECCN分類し、ECCNまたはEAR99を返して、コンプライアンスチームや法律顧問向けの必須の調査レポートを添えます。ウェブワークフローとして動作し、APIはまだありません。そしてDuty Drawbackは、完成品の輸出として再び国外に出ていく輸入インプットに支払った関税を最大99%回収します。このプロフィールにとっては、多くの場合これが単一で最大の回収です。

FAQ

Frequently asked questions

How do we classify HTS codes across a large BOM?

Feed the bill of materials in and classify each component to its HTS code and duty rate in one pass, rather than researching parts one at a time. For a large BOM the exposure hides in the components, and a single wrong code repeated across a product line compounds fast. GingerControl maps each line to its code, duty, and applicable special programs with the GRI reasoning attached, so engineering and compliance finally share the same numbers. We classify the parts; your broker still files the finished-good entries.

How do we reconcile HTS codes across multiple ERPs?

Reconciling codes across several ERPs is handled as a custom integration our services team builds, not a self-serve import. Manufacturers that grew by acquisition often carry the same part under different codes in different systems, which shows up as duty leakage and audit risk. GingerControl scopes a bespoke engagement to pull those catalogs into one consistent classification against a shared methodology. Because it is custom, it starts with discovery and a fixed, milestone-based scope, not an off-the-shelf connector, and we build it rather than file your entries.

How do we handle the annual USITC HTS update process?

Treat the annual USITC HTS revision as a re-check of your catalog against added, modified, and sunset codes, because a subheading you have used for years can change or disappear. GingerControl classifies against a current 20,000-plus code HTS database and our free Trade Policy Digest flags database add, modify, and sunset notifications as they publish, so you see the changes before they hit a shipment. We surface the impact and reclassify; applying the corrected codes at entry stays with your broker, and we do not connect to ACE.

What is the difference between an HTS code and a Schedule B code?

An HTS code classifies goods you import into the U.S., while a Schedule B code classifies goods you export out of it, and the same product can carry a different number on each side. Both build on the 6-digit international HS heading, then diverge at the U.S. level. For a manufacturer that both imports components and exports finished goods, you manage both. GingerControl supports classification from the bill of materials through export; for the export side it also classifies ECCN controls, though that is a web workflow with no API yet.

Should we build or buy HTS classification for our BOMs?

Buy the reasoning engine and keep your team on the judgment calls, unless you have both trade-law depth and engineers to maintain a rules database against constant tariff change. Building in-house means owning GRI logic, CROSS rulings, and every USITC update yourself, which rarely pays off against BOM-scale volume. GingerControl gives you that engine self-serve or by API, with a custom build available when it must live inside your stack. We are builder-not-broker, so buying the tool does not hand us your entry filing or importer-of-record role.

Can we use tariff engineering on imported components?

Yes, tariff engineering means making a deliberate design or sourcing change, a different material blend, fastener, or origin, that lawfully moves a component into a more favorable HTS code, and it works best decided at design time. Once a shipment is reclassified at the port, the cheaper option is already gone. GingerControl lets you compare variants and their duty outcomes at the BOM stage so engineering and landed cost are decided together. We show the levers and the numbers; the sourcing and design decision stays yours, and we are software, not legal counsel.

With capital-goods imports at record levels in 2026, how much does a design-time BOM or origin decision actually move our landed cost?

On Chapter 84 and 85 equipment it can move 15 to 50 points, because the base MFN rate is near zero and almost the entire duty is the Section 232 full-value metals layer plus Section 301, both riding on the classification and origin the BOM fixes. With capital-goods imports at a record $128.0 billion in May 2026 and Section 232 now assessed on the machine's full customs value, that design-time decision moves more landed cost than it used to. GingerControl lets you compare material, fastener, and origin variants and their duty outcomes at the BOM stage, so engineering and landed cost are decided together. We show the levers and the numbers; the sourcing decision stays yours, and we are software, not legal counsel.

2週間のAssessment

貴社の貿易支出に眠る機会を、数字にする。

2週間のAssessmentでは、貴社の輸入申告、運送費用、発注書をGingerControlの監査レイヤーにかけ、証跡付きで取締役会にそのまま提示できる回収可能額をお返しします。貴社の通関業者は、これまで通り貴社の通関業者のままです。

We use cookies to understand how visitors interact with our site. No personal data is shared with advertisers.