Automating Customs Classification in SAP, Oracle, and NetSuite
What changed: The classification report is attributed to the Classification Researcher and GingerOS, not an API response.
You automate customs classification inside an ERP by connecting your product master data to a classification engine that applies Harmonized Tariff Schedule logic at the point of item creation or procurement. SAP GTS, Oracle GTM, and NetSuite each offer built-in tariff code management - but none perform GRI-based classification reasoning natively. For classification that follows the General Rules of Interpretation, references CROSS rulings, and asks clarifying questions to resolve ambiguity, you need an API-powered classification layer that augments your ERP rather than replacing it.
In this post
- Why Do ERP Built-In Classification Tools Produce Errors?
- The ERP Classification Problem: Storage vs. Reasoning
- What Does Each ERP Offer Natively for Customs Classification?
- ERP Classification Capabilities Compared
- How Does API-Powered Classification Augment Each ERP?
- When Should You Use Built-In Classification vs. API-Powered Classification?
- Maintaining Compliance Documentation Across ERPs
- Integration Architecture: Key Considerations
- Frequently Asked Questions
- Start Classifying Inside Your ERP
- References
- Related Articles
Why Do ERP Built-In Classification Tools Produce Errors?
ERP built-in classification tools produce errors because they are designed as tariff code storage systems, not classification reasoning engines. SAP GTS maintains tariff number repositories but does not apply GRI logic to determine which heading applies when multiple candidates exist. Oracle GTM provides trade content databases but does not ask follow-up questions when a product description is ambiguous. These systems store and retrieve codes - they do not reason through classification the way a customs broker or a GRI-logic-driven API does.
SAP GTS, Oracle GTM, and NetSuite all manage tariff codes, but none perform GRI-based classification reasoning, reference CROSS rulings, or ask iterative clarifying questions to resolve ambiguity. The result is silent misclassification at scale: tariff codes that look plausible but cannot survive a CBP audit. GingerOS fills this gap by adding the reasoning layer your ERP lacks, connected per project and read-only, working alongside SAP GTS and Oracle GTM rather than replacing them.
The ERP Classification Problem: Storage vs. Reasoning
More than 70% of large U.S. importers run SAP, Oracle, or NetSuite as their primary ERP. These platforms are deeply embedded in procurement, inventory, and financial workflows - and they are where product master data lives. Naturally, compliance teams want classification to happen inside the ERP, close to the data.
The problem is that every major ERP treats customs classification as a data field to be populated, not a reasoning process to be executed. A tariff code in SAP GTS is a stored attribute on a material master record. A classification in Oracle GTM is a lookup against a trade content database. In NetSuite, customs data is managed through partner integrations or custom fields. None of these systems apply the General Rules of Interpretation in sequence, evaluate Section and Chapter Notes against product attributes, or reference CBP's CROSS ruling database to check precedent.
Resolve missing material attributes that block HTS classification before asking a classifier to choose between headings on incomplete facts.
This distinction - between storing a code and reasoning to a code - is where misclassification originates. WCO studies on customs compliance have found that tariff misclassification remains one of the top sources of revenue loss for customs administrations globally, with error rates frequently exceeding 20% in audit samples of manually classified entries. These error rates reflect the limitations of human-only classification at scale - exactly the problem that purpose-built AI classification tools are designed to solve.
"Classification of goods under the HTSUS is governed by the General Rules of Interpretation (GRIs). The GRIs are applied in numerical order." - U.S. Customs and Border Protection, Informed Compliance Publications
No major ERP applies the GRIs in numerical order during classification. They rely on users - or third-party content databases - to have already done that work before the code is entered.
What Does Each ERP Offer Natively for Customs Classification?
Understanding what each platform actually does (and does not do) is essential before evaluating augmentation options. The capabilities differ significantly across SAP, Oracle, and NetSuite.
SAP GTS (Global Trade Services)
SAP GTS is the most mature trade compliance module among the three ERPs. It integrates directly with SAP ECC and S/4HANA, providing tariff number management linked to material master records, a classification workbench for navigating tariff schedules, sanctioned party list screening, preference determination for FTAs, and regulatory content feeds from providers like Descartes and Integration Point.
What SAP GTS does not do: It does not apply GRI logic to evaluate competing headings, ask clarifying questions when multiple tariff codes are plausible, or reference CROSS rulings during classification. The classification workbench assists with navigating the tariff schedule, but the reasoning process - determining why heading 8471 applies instead of 8528 for a device with both computing and display functions - remains entirely manual.
Oracle GTM (Global Trade Management)
Oracle GTM, part of Oracle's supply chain management cloud, provides trade content integration with tariff databases, keyword-based classification lookup against tariff schedule descriptions, trade agreement management, denied party screening, and customs document generation.
What Oracle GTM does not do: The classification lookup is keyword-driven. It does not evaluate GRI 1 through GRI 6 in sequence, does not perform essential character analysis under GRI 3(b), and does not integrate CROSS ruling precedent. For products where the correct code depends on functional use, material composition thresholds, or the relationship between components, keyword lookup surfaces candidates but cannot reason to the correct one.
NetSuite
NetSuite's native trade compliance capabilities are minimal. HTS codes can be stored as custom fields on item records, but there is no native classification workflow. Trade compliance functionality is typically added through SuiteApps or third-party integrations (Avalara, Descartes, or similar). This is both a limitation and an opportunity - NetSuite's open API architecture and SuiteScript extensibility make it straightforward to integrate an API-powered classification service from day one.
ERP Classification Capabilities Compared
| Capability | SAP GTS | Oracle GTM | NetSuite | GingerOS (GingerControl) |
|---|---|---|---|---|
| Tariff code storage | Yes | Yes | Custom fields only | N/A (augments ERP storage) |
| Tariff schedule browser | Yes | Yes | No | N/A |
| Keyword-based code lookup | Yes | Yes | No | Superseded by GRI logic |
| GRI logic application (GRI 1-6) | No | No | No | Yes - applied in sequence |
| Iterative clarifying questions | No | No | No | Yes - divergence-based |
| CROSS ruling integration | No | No | No | Yes - during classification |
| Section/Chapter Note analysis | Manual reference | Manual reference | No | Automated, per classification |
| Essential character analysis (GRI 3b) | No | No | No | Yes |
| Audit-ready reasoning chain | No | No | No | Yes - full documentation |
| Multi-country tariff support | Yes | Yes | Via partners | U.S. duty only; codes for Canada, and the EU in beta, in the Classification Researcher |
| Batch classification | Manual workflow | Manual workflow | No | Yes - parallel processing |
| Regulatory content updates | Via content providers | Via content providers | Via partners | Watches new rules and lists the SKUs each one hits |
The pattern is clear: ERPs manage tariff codes as data, not classification as reasoning. A reasoning layer fills every gap while leaving the ERP to do what it does well: store codes, link them to financial workflows, and generate customs documentation.
How Does API-Powered Classification Augment Each ERP?
The principle is the same across platforms: your ERP triggers a classification request when a new product is created or needs reclassification. GingerOS follows GRI logic, asks for missing product facts before it suggests an HTS code, and records the reasoning, grounded in Section Notes, Chapter Notes, and relevant CROSS rulings, for your approval. It works alongside SAP GTS, Oracle GTM, and NetSuite as an augmentation layer, not a rip-and-replace, and there are no pre-built connectors: each connection is set up for your project.
SAP GTS + API Classification
SAP GTS supports BAPIs and RFC connections that allow external systems to read material master data and write tariff codes back. A material master change event triggers middleware (SAP CPI, MuleSoft, or a custom RFC module) to extract product attributes and send them to GingerOS. GingerOS returns the HTS code with its reasoning, and once a person approves it, GingerOS writes the code back to the ERP material master, in the fields your IT team approves; it does not write into SAP GTS. The result: classification in the GTS workbench becomes a review and approval step against a reasoned code rather than a research step, reducing per-SKU classification time from 20-30 minutes to a few minutes of validation.
Oracle GTM + API Classification
Oracle GTM exposes REST APIs for trade content management. An item creation event in Oracle ERP triggers a classification workflow, and Oracle Integration Cloud (OIC) sends product attributes to GingerOS before the classification is finalized. The approved HTS code is written back to the Oracle ERP item record, never into Oracle GTM itself, and your Oracle team decides how GTM's downstream workflows, duty calculation, document generation, compliance screening, pick up the reasoning-backed code instead of a keyword-lookup result.
NetSuite + API Classification
NetSuite's SuiteScript 2.0 framework provides clean integration. An afterSubmit trigger on the Item record sends the item to GingerOS, which returns the HTS code and its reasoning for approval. The script writes the code to a custom field on the item record and stores audit documentation in a linked custom record type. NetSuite goes from having no classification capability to having GRI-logic-driven classification embedded directly in the item creation workflow.
When Should You Use Built-In Classification vs. API-Powered Classification?
Not every classification scenario requires an API call. The decision framework below helps compliance teams allocate resources effectively.
| Scenario | Built-In ERP Classification | GingerOS (GingerControl) |
|---|---|---|
| Simple, well-known products | Sufficient - store and reuse validated codes | Not needed for validated simple items |
| New product onboarding (100+ SKUs) | Too slow - manual research per item | Batch classification with GRI reasoning |
| Multiple candidate headings | No GRI logic to resolve | Iterative questioning resolves ambiguity |
| Post-schedule-revision reclassification | Manual review required | Rechecks every SKU the change touches, for your approval |
| Section 301/232 tariff products | Can flag programs, cannot reclassify | Classifies and maps to applicable programs |
| Composite/multi-function products (GRI 3) | No essential character analysis | GRI 3(b) essential character reasoning |
| Audit preparation | No reasoning trail generated | Full audit-ready documentation |
| Supplier-provided HTS code validation | Tariff schedule reference only | Validates against GRI logic and CROSS rulings |
The practical pattern for most enterprise importers is hybrid: use ERP-stored codes for simple, stable products, and route complex, new, or high-risk classifications through GingerOS. The ERP keeps the codes; GingerOS provides the reasoning the ERP cannot.
Maintaining Compliance Documentation Across ERPs
Classification is not a one-time event. The Harmonized Tariff Schedule is revised periodically by the USITC, Section 301 and Section 232 tariffs change with trade policy, and CBP issues new CROSS rulings that may affect existing classifications. CBP's reasonable care standard under 19 U.S.C. Section 1484 requires importers to demonstrate ongoing diligence - not just that the initial classification was reasonable, but that the company has a process for keeping classifications current.
ERPs store compliance documentation well, but they do not generate the reasoning artifacts that a reasonable care defense requires. When GingerControl's Classification Researcher or GingerOS classifies a product, the report includes the HTS code with statistical suffix, the applicable GRI rules, relevant Section and Chapter Notes, CROSS rulings that informed the decision, alternative headings considered and rejected, and a timestamped reasoning chain. This documentation can be stored within the ERP (SAP DMS, Oracle Content Management, NetSuite custom records) and linked to the material record - immediately accessible when CBP audits the classification two years later.
GingerOS is the AI trade compliance platform that runs on your process and the data you have, ERP or not. Each ERP connection is set up per client: read-only, staged, no master data migration, and no pre-built connectors. A company with no ERP gets a data storage setup and a data flow designed for its team, and messy product data is cleaned and organized before the AI system is built.
Integration Architecture: Key Considerations
Regardless of the ERP, the data flow follows a consistent pattern: the ERP product master triggers an integration layer, which calls the classification layer (in GingerControl's case, GingerOS). GingerOS performs GRI-logic classification with CROSS ruling integration, asks for missing facts, then returns the HTS code and its reasoning for approval. The integration layer writes the approved code back to the ERP tariff field and stores audit documentation in the compliance document repository.
Key integration considerations:
- Event-driven triggers: Use material/item creation events as classification triggers, not batch jobs. This ensures every new product is classified before it enters the procurement workflow.
- Fallback routing: When the classification layer cannot settle a code without more facts, route it to a compliance analyst queue within the ERP rather than storing a potentially incorrect code.
- Version tracking: Store the classification engine version, tariff schedule version, and classification date alongside the HTS code. This is essential for reclassification triggers when the HTS schedule changes.
Frequently Asked Questions
Can SAP GTS classify products automatically using GRI logic?
SAP GTS provides a classification workbench for navigating tariff schedules and assigning codes to material master records, but it does not apply GRI logic automatically. The reasoning process, determining which heading applies when multiple candidates exist, remains manual. GingerOS fills this gap by performing GRI-based classification and, once a person approves the code, writing it back to your ERP material master (never into SAP GTS itself), so classification in the workbench becomes a review step rather than a research step.
Does Oracle GTM support automated HTS classification?
Oracle GTM offers keyword-based lookup against trade content databases to identify candidate tariff codes, but it does not perform iterative classification or essential character analysis under GRI 3(b). For complex products that trigger multiple candidate headings, Oracle GTM surfaces options but cannot reason to the correct one. GingerOS augments Oracle GTM by providing the GRI-logic reasoning layer that resolves ambiguity between candidate codes, connected per project through Oracle Integration Cloud or standard REST middleware.
How do you add customs classification to NetSuite?
NetSuite has no native customs classification module. Classification is added through SuiteApps, third-party integrations, or custom SuiteScript development. The most effective approach is calling a classification layer from the item record workflow using SuiteScript 2.0 triggers. GingerOS does this per project: it reads the item record read-only, asks for missing facts, and writes the approved code back with its reasoning.
What percentage of classification errors originate from ERP limitations?
Industry audits consistently show that 15-30% of tariff classifications contain errors when performed through manual ERP field entry without structured reasoning support. Errors cluster around composite products, multi-function devices, and items where the correct heading depends on material composition thresholds or functional use criteria. GingerControl's GRI-logic-driven classification applies structured legal reasoning to every classification, the same framework customs brokers follow, automated and applied consistently. Its iterative questioning targets these divergence points, resolving ambiguity before a code is assigned.
Is GingerControl a replacement for SAP GTS or Oracle GTM?
No. GingerControl augments your existing ERP trade compliance module. SAP GTS and Oracle GTM keep compliance screening, preference determination and customs documentation, and GingerOS writes the approved code back only to your ERP, never into them; GingerOS is the system of record for the classification decision and its reasoning. It works alongside your ERP, not instead of it.
How long does it take to connect GingerOS to an ERP?
A GingerOS project typically takes 8 to 16 weeks from the first call to go-live, in five phases, and the first two come before any contract. It starts with Prototype Week: a clickable prototype of your own flow in three days, with zero permissions and zero production data. ERP connections are then set up in stages, read-only, starting with files your ERP already exports.
Do we need an ERP to automate customs classification?
No. If you have no ERP, GingerControl sets up your data storage and designs a data flow for your team, then builds GingerOS on it. If your product data is messy, we clean and organize it first. GingerOS reads emails, PDFs, Excel files, scans and photos, but not video.
Can the same ERP flow handle export controls (ECCN) alongside HTS?
Yes, inside GingerOS: it rechecks export control alongside HTS classification, which is valuable for companies managing dual-use goods, and writes approved results back to the ERP with an audit trail. The Classification + Tariff Calculation API returns HTS codes and U.S. duty layers only; the Export Control Classifier in the GingerLite app works under the EAR and the CCL, not ITAR, and has no API.
How does GingerControl handle tariff schedule changes affecting existing classifications?
GingerOS watches new rules and changes in your ERP, PLM and supplier records, checks every SKU against a new rule and lists the ones it hits. Each affected code is rechecked and, once approved, written back through the same ERP connection with an audit trail. The free Policy Briefings also email you when a U.S. trade rule changes.
Start Classifying Inside Your ERP
Your ERP is the right system of record for tariff codes. It is not the right system for classification reasoning. The gap between storing a code and reasoning to the correct code is where misclassification, penalty exposure, and audit risk originate.
GingerOS adds the GRI-logic reasoning, CROSS ruling integration, and iterative classification that SAP GTS, Oracle GTM, and NetSuite lack, and records the reasoning behind every classification decision. It runs on your process and the data you have, ERP or not, with each connection set up for your project.
For a single product, the Classification Researcher in the GingerLite app gives the code and its reasoning. For a system fitted to your ERP, start with Prototype Week. Talk to our team
References
- CBP Informed Compliance Publications - GRI application guidance
Source: CBP Informed Compliance Publications - 19 USC 1484 - Reasonable care standard for entry of merchandise
Source: 19 USC 1484 - 19 USC 1592 - Penalties for fraud, gross negligence, and negligence
Source: 19 USC 1592 - CBP CROSS Rulings Database - Customs Rulings Online Search System
Source: CROSS Rulings - USITC Harmonized Tariff Schedule - GRI text, Section Notes, Chapter Notes
Source: USITC HTS - SAP GTS Documentation - Classification workbench, tariff number management
Source: SAP GTS - Oracle GTM Documentation - Trade content integration, classification lookup
Source: Oracle GTM - NetSuite SuiteScript Documentation - SuiteScript 2.0 API, RESTlet framework
Source: NetSuite SuiteScript - CBP Focused Assessment Program - Risk-based importer audit methodology
Source: CBP Focused Assessment - World Customs Organization - Classification compliance and revenue impact studies
Source: WCO Nomenclature
Classifying SKUs one ruling at a time?
Hand this to GingerOS.
Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.
Reviewed by Michael Weick, LCB / CCS




