How to Integrate HTS Classification Into Your ERP System

What changed: CorrectedSAPclassification-proposalclaim andremovedunsupportedROIpercentages/paybackperiod. Corrected Section 1592 source summary; removed unsupported implementation ROI percentages and clarified ERP integration scope.

The short answer

HTS classification ERP integration connects an external classification engine to your enterprise resource planning system so that every product record carries a validated, audit-ready HTS code - without manual re-keying between systems. The integration maps product master data fields (description, material, intended use) to classification API requests and writes the resulting 10-digit HTS code, duty rate, and reasoning documentation back to the ERP item record automatically.

Next step:Try the Classification Researcher on one product

In this post
  1. Why can't most ERP systems classify products on their own?
  2. Why ERP Integration Matters for Trade Compliance
  3. What Are the Integration Architecture Patterns?
  4. How Do You Connect Classification to SAP, Oracle, or NetSuite?
  5. How Should You Handle Errors and Fallback Workflows?
  6. Maintaining Audit Trails Across Systems
  7. Implementation Timeline and Batch Migration
  8. Frequently Asked Questions
  9. Start Your ERP Integration
  10. References
  11. Related Articles

Plan HTS classification API integration with ERP systems around input mapping, exception review and the approved value written back to the item master.

Why can't most ERP systems classify products on their own?

ERP systems like SAP, Oracle, and NetSuite store tariff codes as static data fields - they do not apply the General Rules of Interpretation, reference CROSS rulings, or resolve classification ambiguity. Built-in trade compliance modules (SAP GTS, Oracle GTM) provide record-keeping and filing workflows but rely on externally determined classification decisions. The classification logic itself must come from a specialized engine that understands GRI methodology, Section Notes, Chapter Notes, and legal precedent.


TL;DR

Most importers run trade compliance and ERP as disconnected systems, forcing analysts to manually copy HTS codes between classification tools and product master records. This re-keying process introduces transcription errors, breaks audit trails, and consumes 15-25 hours per week for mid-market importers managing 2,000+ SKUs. Integrating HTS classification directly into SAP, Oracle, or NetSuite eliminates this gap, triggering classification automatically when products are created or updated, and writing results back to ERP fields. GingerControl offers two routes: the Classification + Tariff Calculation API (JSON in, a 10-digit HTS code and U.S. duty layers out, 120 items per batch call) for teams that build the integration themselves, and GingerOS, which connects to your ERP per project, read-only, and writes approved codes back with their reasoning.


Why ERP Integration Matters for Trade Compliance

Over 90% of large importers run SAP, Oracle, or NetSuite as their core ERP platform. SAP alone holds roughly 24% of the global ERP market, with Oracle ERP Cloud and NetSuite collectively commanding another 15-20%. These systems hold the product data, purchase orders, and supplier information that drive customs classification decisions.

Yet in most organizations, HTS classification happens outside the ERP entirely. Compliance analysts export product lists to spreadsheets, classify products using standalone tools or manual lookup, and then re-enter the resulting HTS codes back into the ERP's product master. This disconnect creates three systemic problems:

Data re-entry errors. Manual transcription of 10-digit HTS codes is inherently error-prone. A single transposed digit - entering 8471.30.0100 instead of 8471.30.0150 - can change the applicable duty rate by several percentage points. Industry surveys consistently find that manual data entry in trade compliance workflows produces error rates of 2-5%, and at scale, these errors compound into significant duty miscalculations.

Broken audit trails. CBP's reasonable care standard under 19 USC 1484 requires importers to demonstrate how classification decisions were made. When the classification reasoning lives in one system and the HTS code lives in the ERP, there is no connected documentation trail. During a CBP Focused Assessment, auditors will ask to see the decision logic behind each code - and "the compliance analyst looked it up and typed it in" is not a defensible answer.

Stale classifications. Without integration, reclassification depends on someone remembering to re-export, re-classify, and re-import. When the USITC revises HTS codes, when Section 301 or 232 modifications change applicable rates, or when product specifications change upstream, the ERP code drifts out of sync with reality. Integrated systems trigger reclassification automatically when product data changes.

"The ultimate responsibility for classification rests with the importer. Customs expects that the importer will exercise reasonable care in classifying merchandise." - CBP Informed Compliance Publication on Classification

Measure integration ROI on your own workflow: record re-keying and review time before and after, include build and maintenance cost, and count correction work. No shared benchmark establishes a typical saving percentage or payback period. A team can evaluate the Researcher in GingerLite before committing to integration.


What Are the Integration Architecture Patterns?

There are four primary approaches to connecting an HTS classification engine to an ERP system. The right choice depends on your ERP platform, IT resources, classification volume, and compliance requirements.

Approach How It Works Pros Cons Best For
Manual export/import Export product list from ERP, classify externally, import codes back via CSV/XLSX No IT development required; works with any ERP No automation; error-prone re-keying; no audit trail link; does not scale Companies classifying < 100 SKUs/year with no IT resources
Middleware / iPaaS Use MuleSoft, Boomi, Workato, or similar to orchestrate API calls between ERP and classification engine Pre-built ERP connectors; visual workflow design; no custom code Adds a third system to maintain; licensing costs; latency from extra hop Mid-market companies with existing iPaaS investments
Direct API integration ERP calls classification API directly via REST endpoints on product create/update events Real-time classification; tight audit trail; no middleware dependency Requires ERP customization; needs developer resources Companies with in-house development teams
Custom connector / plugin Purpose-built ERP extension (SAP RFC/BAPI, Oracle REST adapter, NetSuite SuiteScript) Native ERP user experience; deepest integration; handles ERP-specific field mapping Highest development effort; platform-specific; maintenance burden Enterprise teams with dedicated ERP development resources

GingerControl's REST API fits all four patterns: it is plain JSON over HTTPS with an X-Api-Key header. If you would rather not build and maintain the connector yourself, GingerOS is set up per project instead: read-only on your ERP and PLM, connected in stages, with write-back only where you approve. There are no pre-built connectors and no master data migration.

Integration Architecture Flow

The core data flow for any HTS classification ERP integration follows this pattern:

ERP System                    Classification Engine              ERP System
───────────                   ─────────────────────              ───────────
Product created/updated  ──►  API Request                        
                              {                                  
                                "description": "material, function,
                                  composition ...",
                                "country_of_origin": "CN"
                              }                                  
                                        │                        
                              Classification Logic               
                              (GRI analysis, CROSS rulings,      
                               Section/Chapter Notes)            
                                        │                        
                              API Response                       
                              {                                  
                                "hts_code": "8471.30.0100",     
                                "tariffs": {
                                  "general_rate": "Free", ...
                                }
                              }                          ──►  Update product master:
                                                              - HTS code field
                                                              - Duty rate field
                                                              - Classification date
                                                              - Reasoning (GingerOS)
                                                              - Audit log entry

GingerControl's API returns structured JSON that maps directly to ERP fields: the HTS code and its U.S. duty layers (general and special rates and each Chapter 99 line, including Section 301 and 232), with split-code products returned as components. The API manual documents no reasoning chain or confidence score; in GingerOS, the reasoning, cited CROSS rulings and approval record are stored with each code.


How Do You Connect Classification to SAP, Oracle, or NetSuite?

Each major ERP platform has different extension mechanisms, field structures, and trade compliance modules. Here is platform-specific guidance for the three most common ERP systems among U.S. importers.

ERP Platform Trade Compliance Module Classification Field Location Integration Mechanism Key Considerations
SAP S/4HANA SAP GTS (Global Trade Services) Material master → Foreign Trade tab → Commodity code RFC/BAPI, SAP CPI (Cloud Platform Integration), or IDoc GTS offers classification proposals; an external API connection is an integration project, not a pre-built GingerControl connector
Oracle ERP Cloud Oracle GTM (Global Trade Management) Item master → Trade compliance attributes Oracle Integration Cloud (OIC), REST adapter, or PL/SQL GTM manages compliance workflows; classification API provides the upstream data
NetSuite NetSuite SuiteCommerce / OneWorld Item record → Custom fields (HTS code, duty rate) SuiteScript 2.0, RESTlet, or SuiteTalk (SOAP/REST) No native trade compliance module; requires custom fields and scripts

SAP S/4HANA + SAP GTS

SAP GTS is the most common trade compliance module among large importers. It handles customs declarations, license determination, and compliance screening - but it relies on externally populated commodity codes. The integration point is the material master's Foreign Trade tab, where the commodity code (HTS number) is stored.

Integration approach: Use SAP Cloud Platform Integration (CPI) to create an iFlow that triggers when a material master record is created or updated. The iFlow maps SAP material fields (MAKTX description, WRKST material type, MATKL material group) to a GingerControl API request, processes the response, and writes the HTS code back to the material master's STAWN field (commodity code) and updates the GTS compliance document.

Data mapping for SAP:

SAP Field (MAKT/MARA/MARC)      →  GingerControl API Request
─────────────────────              ──────────────────────────
MAKTX (Material description)   →  description
WRKST (Basic material)         →  description (appended)
MATKL (Material group)         →  description (appended)
HERKL (Country of origin)      →  country_of_origin

GingerControl API Response     →  SAP Field (MARC/STAWN)
──────────────────────────         ─────────────────────
hts_code                       →  STAWN (Commodity code)
tariffs.general_rate           →  Custom field / GTS document
tariffs (Chapter 99 lines)     →  Custom field / GTS document
(run date of your iFlow)       →  Classification date field

Oracle ERP Cloud + Oracle GTM

Oracle GTM provides trade compliance workflow management, including denied party screening, export license management, and customs documentation. Like SAP GTS, it consumes classification data but does not generate it.

Integration approach: Use Oracle Integration Cloud (OIC) to build a flow triggered by item master changes. Map Oracle item attributes to the classification API request, and write results back to the item's trade compliance attributes. Oracle's REST adapter makes direct API calls straightforward.

The trade compliance REST API integration guide places synchronous and batch calls in the receiving system's workflow.

NetSuite

NetSuite does not include a native trade compliance module, which makes it both simpler and more flexible for classification integration. Create custom fields on the item record for HTS code, duty rate, and classification date. Then use a SuiteScript 2.0 User Event script to trigger classification on item create/update.

SuiteScript integration pattern:

// SuiteScript 2.0  -  User Event: afterSubmit
// Triggers GingerControl classification when item record is saved

function afterSubmit(context) {
    var item = context.newRecord;
    var description = item.getValue('displayname');
    var material = item.getValue('custitem_material');
    var origin = item.getValue('custitem_country_of_origin');
    
    // Call the GingerControl Classification + Tariff Calculation API
    var response = https.post({
        url: 'https://api.gingercontrol.com/openapi/v1/tariff',
        headers: { 'Content-Type': 'application/json', 'X-Api-Key': apiKey },
        body: JSON.stringify({
            description: description + ', ' + material,
            country_of_origin: origin
        })
    });
    
    var result = JSON.parse(response.body);
    
    // Write classification results back to item record
    record.submitFields({
        type: item.type,
        id: item.id,
        values: {
            'custitem_hts_code': result.hts_code,
            'custitem_duty_rate': result.tariffs ? result.tariffs.general_rate : '',
            'custitem_classification_date': new Date()
        }
    });
}

No ERP yet, or product data spread across spreadsheets? GingerOS runs on your process and the data you have, ERP or not: without an ERP, we set up your data storage and design a data flow for your team, and messy data is cleaned and organized before the AI system is built. It reads emails, PDFs, Excel files, scans and photos, but not video.


How Should You Handle Errors and Fallback Workflows?

Production integrations must account for scenarios where classification cannot be completed automatically. Building robust error handling into your ERP integration prevents silent failures that lead to unclassified shipments or default codes.

Results that need a person. The API returns a code and its duty layers, and its manual documents no confidence score, so decide which items always go to review (new product families, composite goods, high-duty lines) and route those to a compliance review queue: a custom ERP workflow or a notification to the compliance team. GingerOS handles this for you: it records the reasoning for each code and writes back only what a person approves.

Ambiguity requiring clarification. The API classifies from the description it receives, so put material, function and composition into the description from the start. When facts are still missing, GingerOS asks for them before it suggests a code, and the Classification Researcher in the GingerLite app does the same for a single product.

API unavailability. Implement retry logic with exponential backoff. If the classification API is temporarily unavailable, queue the request and process it when connectivity is restored. Never default to a placeholder HTS code - an incorrect code filed with CBP carries penalty risk under 19 USC 1592.

HTS code validation. After receiving a classification result, validate the returned HTS code against the current USITC schedule before writing it to the ERP. GingerControl's responses are based on the current HTS schedule, but validation at the ERP layer provides defense-in-depth against stale data.

Fallback workflow summary:

Classification request
        │
        ▼
   API available? ──No──► Queue for retry (exponential backoff)
        │
       Yes
        │
        ▼
   Auto-approve rule met? ──No──► Route to compliance review queue
        │
       Yes
        │
        ▼
   Needs clarification? ──Yes──► Auto-resolve from ERP fields or
        │                         route to analyst workflow
       No
        │
        ▼
   Validate HTS code
        │
        ▼
   Write to ERP product master + audit log

Maintaining Audit Trails Across Systems

The audit trail is the single most important output of an HTS classification ERP integration - more important than the HTS code itself. During a CBP Focused Assessment, auditors will not simply check whether the HTS code is correct. They will evaluate whether the importer exercised reasonable care in arriving at that code.

An integrated system must maintain an unbroken chain of documentation:

  1. Classification trigger: Log what triggered the classification (new product creation, material change, periodic review) with a timestamp
  2. Input data: Store the exact product data sent to the classification API alongside the ERP record
  3. Classification response: Store the full classification response and the reasoning behind it: GRI rules applied, Section/Chapter Notes referenced, and CROSS rulings cited
  4. Decision record: If human review was involved, log the reviewer, review date, and any overrides with justification
  5. ERP field update: Log the HTS code written to the product master, the date, and the classification version

In GingerOS, every code is stored with its reasoning, applicable rules and supporting precedent, and approved results are written back to your ERP with an audit trail. Store these as ERP record attachments or in a linked compliance document table so that the full classification history is accessible from the product master record.

For companies processing 40+ million entry summaries annually through U.S. customs, CBP's risk-based audit approach means that any importer can be selected for a Focused Assessment. The audit trail produced by your ERP integration is your primary defense.


Implementation Timeline and Batch Migration

A realistic implementation timeline depends on your ERP platform, existing IT infrastructure, and classification volume.

Phase Duration Activities
1. Discovery and mapping 1-2 weeks Identify ERP fields, map product data to API request format, define review rules and fallback workflows
2. API integration development 2-4 weeks Build integration logic (middleware flow, direct API call, or custom connector), implement error handling, set up audit logging
3. Batch migration 1-2 weeks Classify existing product catalog using the API's batch endpoint or GingerOS batch classification; review flagged results; write validated codes to ERP
4. Testing and validation 1-2 weeks Test with live product creates/updates; validate against broker-reviewed classifications; stress-test error handling
5. Go-live and monitoring Ongoing Deploy to production; monitor classification accuracy and API performance; periodic reclassification reviews

Batch migration for existing catalogs. Before going live with real-time classification, you need to classify your existing product catalog. The API's batch endpoint takes JSON items, up to 120 per call by default, each with your own item_id, and returns the results in the same order with a summary block:

POST /openapi/v1/tariff/batch
Content-Type: application/json
X-Api-Key: YOUR_API_KEY

{
  "items": [
    { "item_id": "SKU-001", "description": "Cotton knit short sleeve T-shirt", "country_of_origin": "DE" },
    { "item_id": "SKU-002", "description": "Stainless steel hex bolt, M10 x 50mm", "country_of_origin": "TW" }
  ]
}

If your catalog lives in spreadsheets, PDFs and emails rather than a clean ERP export, GingerOS reads them as they are (text and images, not video) and classifies in batches, with the reasoning recorded for each SKU.


Frequently Asked Questions

What ERP systems does GingerControl integrate with?

There are no pre-built connectors. GingerOS connections are set up per client, for the systems you already run: read-only, connected in stages, with write-back only where you approve, and no master data migration. Teams that build their own integration can call the Classification + Tariff Calculation API from any system that makes outbound HTTPS calls.

How long does it take to integrate HTS classification into an ERP?

A typical HTS classification ERP integration takes 4-8 weeks from discovery to go-live, depending on ERP platform complexity and existing IT infrastructure. Middleware-based integrations (MuleSoft, Boomi) are typically faster than custom connector builds. A GingerOS project, where we build and maintain the connection, typically runs 8 to 16 weeks from the first call to go-live and starts with Prototype Week.

Can the integration handle real-time classification on product creation?

Yes. The API takes synchronous REST calls, so an ERP create or update event can call it and write the code back. Composite or unclear products should go to a compliance review queue; in GingerOS, missing facts are asked for before a code is suggested, and only approved codes are written back.

What happens when a classification needs a person to review it?

A properly built integration routes those items to a compliance review queue rather than writing uncertain codes to the ERP. The API manual documents no confidence score, so set rules for which items always get review. GingerOS records the reasoning behind each code and writes back only approved codes, and the review outcome is logged as part of the audit trail.

Does the integration maintain reasonable care documentation for CBP audits?

Yes, when the reasoning is stored with the code. GingerOS records the reasoning behind each code, the GRI rules applied, Section/Chapter Notes referenced and CROSS rulings cited, and writes approved results back to your ERP with an audit trail; the API alone returns the code and duty layers. Stored alongside ERP product records, that documentation supports the reasonable care standard under 19 USC 1484.

How do I handle HTS code changes when the tariff schedule is updated?

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, and writes approved results back to your ERP with an audit trail. In the GingerLite app, Compliance Radar checks new U.S. trade notices against your HTS codes, and the free Policy Briefings email you when a U.S. trade rule changes.

What is the ROI of automating HTS classification in an ERP system?

Measure integration ROI on your own workflow: record re-keying and review time before and after, include build and maintenance cost, and count correction work. No shared benchmark establishes a typical saving percentage or payback period. A team can evaluate the Researcher in GingerLite before committing to integration.

Do we need an ERP to automate HTS classification?

No. If you have no ERP, we set up your data storage and design a data flow for your team, then build 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.


Start Your ERP Integration

Manual re-keying of HTS codes between classification tools and ERP systems is a compliance liability that produces errors, breaks audit trails, and wastes analyst time. API-based classification integration eliminates this gap, triggering classification automatically when products change and writing audit-ready results directly to ERP records.

Build it yourself on the Classification + Tariff Calculation API, which starts with a call, or let GingerOS connect to your ERP per project: it runs on your process and the data you have, ERP or not, and starts with Prototype Week, before any quote. Talk to our team


References

  1. 19 USC 1484 - Entry of merchandise, reasonable care standard
    Data cited: Importer's obligation to exercise reasonable care in classification decisions
    Source: 19 USC 1484 - Entry of merchandise
    Published: Codified statute
  2. 19 USC 1592 - Penalties for fraud, gross negligence, and negligence in import transactions
    Data cited: Under 19 U.S.C. 1592(c), negligence is capped at the lesser of domestic value or twice lost duties, taxes and fees; gross negligence uses four times the loss; fraud can reach domestic value. The 20%/40% dutiable-value caps apply when duty assessment was unaffected.
    Source: 19 USC 1592 - Penalties for fraud, gross negligence, and negligence
    Published: Codified statute
  3. U.S. Customs and Border Protection - Trade priority issues, entry summary volumes
    Data cited: Over 40 million entry summaries processed annually
    Source: CBP Trade Priority Issues
  4. CBP Focused Assessment Program - Risk-based audit methodology for importers
    Data cited: CBP's audit program evaluating importer compliance practices including classification
    Source: CBP Focused Assessment
  5. CBP Informed Compliance Publications - Classification guidance and GRI application
    Data cited: "The ultimate responsibility for classification rests with the importer. Customs expects that the importer will exercise reasonable care in classifying merchandise."
    Source: CBP Informed Compliance Publications
  6. USITC Harmonized Tariff Schedule - Official HTS schedule and revision history
    Data cited: 17,000+ tariff lines; periodic revisions affecting stored HTS codes
    Source: USITC HTS Information
  7. SAP Global Trade Services - Trade compliance module documentation
    Data cited: SAP GTS commodity code management, material master Foreign Trade tab
    Source: SAP GTS Documentation
  8. Oracle Global Trade Management - Trade compliance cloud module
    Data cited: Oracle GTM integration patterns, item master trade compliance attributes
    Source: Oracle GTM
Your next step

Classifying SKUs one ruling at a time?

Hand this to GingerOS.

Get your SKU list classified, reasons included Try the Classification Researcher on one product

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
Customs compliance manager with 42 years of experience (ex Subaru of America, Merck, and Motorola).

More in AI & Technology

Our Risk-Free Promise

Full refund.

If you’re not satisfied before MVP acceptance, get a full refund of your deposit.

Click Me!

See if you qualify