BITE Databases
Create, manage, continuously monitor, and reuse compliance records for imported products, exported items, and third parties.
What Are BITE Databases?
- Centralized systems of record
- Reusable product, item, and entity records
- Continuously updated compliance information
- Documented reviews and audit trails
Why Use Them?
- Reduce duplicate research
- Maintain current classifications and screening results
- Identify changes that require review
- Reuse approved records across BITE workflows
- Support scalable compliance operations
What It Stores
Products, parts, assemblies, and the import-compliance information associated with them.
Import Database Walkthrough
Learn how the BITE Import Database helps organizations centralize product records, maintain import-compliance information, and monitor classifications, tariff exposure, and agency requirements over time.
The Import Database was previously called the Product Database. This walkthrough reflects the same core product-management capabilities now available through the Import Database.
In this demo you'll learn how to:
- Create an Import Database using a flat product list or bill-of-material hierarchy
- Add records manually or through a CSV upload
- Store HTS classifications, country of origin, and product details
- Review tariff exposure and PGA requirements
- Identify priority issues and compliance flags
- Maintain supporting documentation and activity history
- Share approved product information with brokers or connected systems
- Monitor products for regulatory and tariff changes
Typical Workflow
- 1
Create an Import Database
Choose a name and organize products using a flat list or bill-of-material hierarchy.
- 2
Add Product Information
Add products manually or import records using the downloadable CSV template.
- 3
Review Compliance Information
Review HTS classifications, country of origin, tariff exposure, PGA requirements, and compliance scores.
- 4
Investigate Priority Issues
Open flagged products to understand the applicable tariff, agency, or classification concern.
- 5
Store Supporting Documentation
Attach source documents, classification records, comments, and internal review notes.
- 6
Share Approved Product Data
Send approved information to brokers, ERP systems, 3PLs, or supported integrations.
- 7
Keep Records Current
Review notifications and activity logs when tariff or compliance information changes.
Information Maintained
Store HTS classifications, product descriptions, SKUs, country of origin, and related product data.
Maintain duties, trade remedies, and tariff applicability, including Section 301 and Section 232 exposure.
Identify FDA, EPA, CPSC, and other Partner Government Agency requirements associated with products.
Maintain source documents, comments, classification rationale, and a dated activity history.
Continuous Monitoring
Import Database records are regularly screened to keep tariff and compliance information current. When results change, BITE records the update in the activity log and surfaces it through database notifications for review.
Best Practices
- Maintain accurate HTS classifications
- Keep country-of-origin data current
- Use hierarchical structures where appropriate
- Review classifications periodically
Common FAQ
Operational guidance for working with BITE databases.
Which BITE Database should I use?
Use the Import Database for imported-product classifications, tariffs, and agency requirements; the Export Database for export classifications, licensing, and authorization records; and the Entity Database for customers, suppliers, and other third parties.
Can records be uploaded in bulk?
Yes. Databases can be populated through supported CSV uploads, and records may also be added or maintained individually where available.
Can database records be used in other BITE tools and workflows?
Yes. Databases serve as reusable systems of record, allowing saved information and prior reviews to support related BITE tools, analyzers, and workflows.
How do databases stay current?
BITE regularly rescreens applicable records and surfaces changes through review queues, notifications, and activity logs.
Are database changes documented?
Yes. Database records maintain supporting information and activity history to help teams understand what changed, when it changed, and how the record was reviewed.