Litoral Trace Document intelligence for import operations
Private Beta · Lacey Act Phase VII

Stop chasing Lacey data across supplier documents.

Upload the invoices, packing lists, supplier spreadsheets and supporting files you already receive. Litoral Trace helps extract declaration inputs, flag missing or conflicting information, and keep the evidence behind every field — before your entry reaches ACE or LAWGS.

No ERP access No production integration Redact sensitive information if needed

Shipment evidence review

Historical shipment · private beta

REVIEW
Commercial InvoicePDF · evidence
Supplier SheetXLSX · product data
Packing ListPDF · shipment data
Shipment reference
Invoice ↔ Packing List
MATCHED
Quantity
Invoice ↔ Supplier Sheet
MATCHED
Species evidence
Supplier Sheet · needs review
REVIEW
Harvest country
No supporting value found
MISSING

Illustrative private-beta workflow. These statuses are preparation/review signals, not a filing result or legal compliance determination.

Before filing

One preparation layer between supplier files and your entry workflow.

The beta is designed around the manual work that happens before a declaration is filed: finding data, comparing sources and proving where each value came from.

Extract

Turn existing supplier files into structured data for review — without forcing another form before upload.

Reconcile

Surface missing or conflicting information across invoices, spreadsheets and supporting documents before somebody has to chase it manually.

Evidence

Keep extracted values tied to their source document so reviewers can see where the information came from.

Workflow

Use the files your team already receives.

The private beta starts with a completed historical shipment. No ERP project, no process migration and no custom integration are required for the test.

01 · UPLOAD

Bring existing files

Invoices, supplier spreadsheets, packing lists and supporting evidence.

02 · EXTRACT

Structure what is present

OCR and document parsing create candidates with source provenance and confidence.

03 · REVIEW

Focus on exceptions

Missing, conflicting or uncertain values are surfaced instead of silently guessed.

04 · PREPARE

Organize before filing

Review the structured data and evidence before the entry is handled in ACE or LAWGS.

Where manual work hides

Does any of this happen in your Lacey workflow?

These are the problems we are testing with U.S. brokers and import teams — not assumptions we want to code around without evidence.

Species or harvest-country information arrives later than the commercial invoice or in a different supplier file.
Your team re-keys line-item data and repeats follow-up with importers or suppliers.
Documents disagree on product, quantity, shipment reference or origin information.
Weeks later, reconstructing the evidence behind a declared value means searching across folders and email.
Private beta scope

Credible preparation software, not a regulatory shortcut.

Capabilities already used by the beta

  • PDF, Excel and CSV intake.
  • OCR for scanned PDFs.
  • Structured extraction with confidence and source provenance.
  • Human review for uncertain or conflicting fields.
  • Evidence Vault, integrity references and cross-document reconciliation.

Claims we deliberately do not make

  • No automated Lacey filing.
  • No live ACE or LAWGS integration in this beta.
  • No legal compliance determination.
  • No guarantee of APHIS or CBP acceptance.
Test the problem, not a sales deck

Test one completed shipment.

We are looking for a small number of U.S. customs brokers and import teams willing to walk through one historical shipment and show us where Lacey data is collected manually today.

15-minute first walkthrough.
Use a completed historical shipment — not a live entry.
Customer names, prices or other sensitive fields may be redacted.
The objective is to measure manual work and data friction before proposing a commercial engagement.

This weekend beta does not store your answers in the application database. After validation, your email client opens a pre-filled message to comercial@litoraltrace.com. Aggregate funnel events contain no email or form answers.

Your request is ready. If your email client did not open automatically, send the pre-filled message here.
FAQ

A deliberately narrow private beta.

Does Litoral Trace file Lacey declarations?

No. This beta focuses on preparing, extracting, reconciling and reviewing information before filing.

Is this legal advice?

No. Litoral Trace is preparation and evidence software. Responsibility for declarations and regulatory decisions remains with the importer and its authorized professionals.

Do you need ERP access?

No. The test starts with a completed historical shipment and the files your team already has.

Can sensitive data be redacted?

Yes. The goal is to understand document workflow and manual work, not to obtain confidential commercial information.