10
open
Turn supplier evidence, BOM data and shipment documents into review-ready Lacey data.
Reconcile species, country of harvest, quantities and supporting evidence. Surface only the missing facts and conflicts that require human review.
Compliance workspace · production view
10
open
3
needs review
4
ready to export
18
completed
Verified supplier evidence memory
12 reusable claims · validity tracked across shipments
Built for U.S. Lacey Act preparation
Every preparation decision stays tied to evidence, review state, and the shipment record that produced it.
Invoice, transport, customs and supplier records resolved together.
Commercial species terms normalized into reviewable botanical data.
Missing facts and conflicts are isolated instead of buried in complete records.
Resolved values remain traceable to documents and evidence provenance.
Material outputs remain reviewable before downstream use.
Generate review-ready LAWGS XML work products after preparation is complete.
Evidence to review-ready data
Keep the source set intact, reconcile regulatory data, resolve exceptions and export only after review.
01
Shipment and supplier evidence
02
Cross-document values
03
Taxonomy and structured fields
04
Exceptions and missing evidence
05
Review-ready declaration package
Supplier evidence
One shipment-level view of the evidence state, with every ready value still tied to its source.
Complete evidence
Ready values stay traceable to source.
Conflicting evidence
Differences are sent to review.
Missing evidence
Gaps are visible before downstream filing work.
Review gaps, not complete records.
One view of what is ready, what needs review and what is still missing.
5 ready · 1 review · 1 missing
Taxonomy and conflicts
Taxonomy resolution
Supplier term
White Oak
Resolved taxonomy
Quercus alba
Evidence source supplier_species.xlsx · row 18
Conflict handling
REVIEW REQUIREDWhen sources disagree, both values remain visible for human review.
Supplier species sheet
Quercus alba
Product specification
Quercus rubra
Security & data handling
The production service preserves organization scoping, PostgreSQL row-level security, least-privilege runtime roles, private evidence storage and encrypted transport.
Organization-owned records remain tenant-scoped with PostgreSQL RLS and FORCE RLS controls.
TLS protects application transport and evidence is kept in private object storage.
Sandbox tenants and uploaded data are scheduled for destruction after four hours unless explicit support-debug consent applies.
Litoral Trace processes customer documents for the requested compliance workflow; the product does not operate a customer-document model-training pipeline.
Preparation output
After human confirmation, Litoral Trace generates a review-ready XML work product and an audit workbook while preserving source context. Export does not itself submit a filing to ACE or LAWGS.
LAWGS XML · review-ready work product
Illustrative output structure
<LaceyDeclaration>
<EntryNumber>2026-18472</EntryNumber>
<BillOfLading>MAEU8471932</BillOfLading>
<PlantMaterial>
<Genus>Quercus</Genus>
<Species>alba</Species>
<CountryOfHarvest>US</CountryOfHarvest>
<Quantity unit="KG">1840</Quantity>
</PlantMaterial>
</LaceyDeclaration>
Professional plan
Start with a production workspace, secure Paddle billing, and a clear monthly operation allowance.
Litoral Trace Professional
USD 149/month
Up to 100 Lacey operations per month.
Evaluate the workflow
Synthetic data. No upload required.