Product roadmap
What is live, what is next, and the direction of the platform.
What's built and live, what's in flight, and the CBP-filing gates that still pace production — plus the regulatory timeline behind them.
Built (live)
The platform is live in production and operated by licensed brokers: the workspace at app.commers.ai (invite-only), the public tariff tracker at aduaria.com/knowledge, and these docs at aduaria.com/docs. Classification, extraction, screening, landed-cost simulation, and duty drawback all run on real cleared entries today.
- Modulith architecture — Postgres + per-module schemas, dep-graph validation
- Data layer — HTSUS (26.6K codes + Chapter 99), CBP CROSS rulings (850+), OpenSanctions screening (31K entities), tariff programs
- AI classifier — Claude Sonnet, RAG-grounded, calibrated confidence, citable rationale; grounding on real CBP rulings yields measurably better accuracy with 0% hallucinated codes
- Invoice extraction — PDF/image → structured shipment
- Denied-party screening — 8 lists, fuzzy match, risk bands, auto-routes blocks to hold
- Duty calculator — base + Section 301/232/IEEPA + MPF/HMF, landed cost
- Duty drawback — unused-merchandise + manufacturing-BOM matchers running on the org's real cleared entries; ACE type-47 entry generation built against the CBP CATAIR Drawback/TFTEA v27 specification, with a standing 215-case certification harness (141 pass, 0 failures, 53 known gaps tracked and 11 blocked on CBP-side inputs) — only CBP transmission deferred
- State machine — full entry lifecycle with auto-routing
- Closed feedback loop — broker corrections captured → surfaced on the AI evaluation screen → fed into eval set + few-shot prompts
- Tariff intel alerts — live, auto-refreshing feed (FR alerts daily; HTS/CROSS/screening weekly), filterable
- Ask — the copilot — a broker can run entries, drawback claims, audit cases, tariff proposals and the product catalog from one conversation. Every write is a proposal the broker confirms; nothing is filed to CBP. Conversations persist; each answer cites what it read
- Product catalog — a per-importer passport: HTS, origin, BOM, PGA data, FTA eligibility, CBAM/EUDR scope, and the evidence behind each, with broker verification
- Organisations & access — invite colleagues, four roles actually enforced (deny-by-default on every mutating route), scoped API keys
- Document intelligence — PDF, image and spreadsheet (CSV/XLS/XLSX) → doc-type classification → the right extractor
- Post-entry audit — CF-28 / CF-29 case workspace with a grounded response agent that cites only real authorities and the actual documents on file; queue, owner assignment, chase list, fileable letter
- Eval harness — CROSS-holdout, reproducible
- Workspace — app.commers.ai, invite-only, live on Vercel + Render + Supabase
- Knowledge site — aduaria.com/knowledge public tariff tracker from real Federal Register data, daily auto-rebuild
- Marketing + docs site — aduaria.com + /how-it-works + /docs, live on Vercel
In flight / next candidates
| Track | Effort | Value | Blocker |
|---|---|---|---|
| Screening eval harness | ~0.5 day | Quantify FP/FN at the screening threshold | none |
| Penny-accurate duty coverage | ~0.5-2 days | U.S. Note 20(b) parsing for exact stacked rates | none |
| Screening LLM agent | ~1-2 days | Re-rank fuzzy matches by address/DOB/programs | none |
What still gates direct CBP filing
The product is live and brokers operate it today. The one thing that remains on the roadmap is direct ACE transmission to CBP — until it lands, a licensed broker files each entry. The gates specific to that transmission path:
- ACE CERT filer code (application → cert testing → production filer code)
- Continuous surety bond in place before production filings
- LCB partnership for production filings
None of these block the workspace, the knowledge site, or the AI running on real entries — those are already in production.
Regulatory timeline (the long poles to direct filing)
These are the remaining long poles on the path to direct ACE transmission. Until they clear, a licensed broker files each entry — the AI proposes, the broker approves and signs.
| Action | Lead time | Gate |
|---|---|---|
| ACE CERT filer code | 60-90 days | the path to direct filing |
| LCB partnership | weeks of outreach | required for production filings |
| SOC 2 Type I | 2-3 months | enterprise customers |
| Continuous surety bond ($50K) | 1-2 weeks | production filings |
| Production filer code | after cert testing | LCB + bond + passed cert |
See deployment for the technical pre-launch checklist.
Where we are
- Live today — data + AI + workspace + duty drawback, running on real cleared entries; a licensed broker files each entry
- Next — ACE CERT integration, transmission transport, first test transmissions to CBP
- Then — production filer code: supervised ramp of direct transmission
What would change the priority order
- Courting a customs-expert / LCB partner soon → prioritize the CBP-filing track (ACE CERT) to shorten the path to direct transmission
- Design partner's chapter mix → unlocks where the penny-accurate tariff-coverage work pays off first
Put your own book of entries through Aduaria.