BITE Databases
Create, manage, and screen products and entities using BITE's centralized system-of-record databases.
What Are BITE Databases?
- Persistent compliance records
- Reusable screening workflows
- Centralized product & entity intelligence
- Operational systems of record
- Audit-ready historical records
Why Use Them?
- Reduce duplicate work
- Improve screening quality
- Centralize compliance information
- Reuse classifications & reviews
- Create defensible audit trails
- Support scalable compliance operations
What It Stores
Products, parts, assemblies, and product compliance data.
Step-by-Step in BITE
- 1
Create Product Database
Start a new system-of-record database for products and parts.
- 2
Select Structure Type
Choose how products are organized.
- Flat Structure
- Hierarchy / BOM Structure
- HTS Grouping Structure
- 3
Upload Products
Import product records via CSV or manual entry.
- 4
Classify Products
Assign HTS codes, ECCNs, and origin data.
- 5
Run Screening
Evaluate products against regulatory and customs controls.
- 6
Review Results
Investigate findings and disposition records.
Video Walkthrough
Product Database Walkthrough
See how to create a product database, choose a structure, upload product records, classify products, and run screening from the database.
What Gets Analyzed?
Identify regulatory obligations and compliance exposure.
Identify customs-related issues such as classification errors, documentation gaps, and filing risks.
Identify tariff exposure, penalties, overpayments, and landed-cost impacts.
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.
When should I use a Product Database versus an Entity Database?
Use a Product Database for products, parts, and classification data (HTS, ECCN, origin). Use an Entity Database for organizations and trade parties you screen against denied-party and ownership risk.
Can I screen directly from a database?
Yes. Both databases support running screening directly against their records, so reviews stay tied to your system of record.
Can I upload CSV files?
Yes. Records can be imported in bulk via CSV upload or added manually.
Can I classify products after upload?
Yes. Products can be classified after upload, and classifications are reusable across shipments and reviews.
Do screening results update when records change?
Screening can be re-run when records or watchlists change, keeping dispositions and audit trails current.