saascode

Customscore

A forwarder-controlled export-manifest workspace that normalizes authorized booking evidence, proposes field and classification candidates, validates them against a versioned U.S. filing profile, and preserves review, submission, acknowledgment, rejection, correction, and readback.

Genesis score7.11/10
Make Customscore real.0/500
500 more votes and Customscore is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
ProposedCurrent U.S. rule status
0Jurisdictions merged into one filing
0Automatic classifications
The case

The supplied research confirms a February 2026 U.S. electronic export manifest proposal, a closed comment period, an existing pilot, and a government filing portal. The final rule is still pending. The original idea incorrectly combines the U.S. filing flow with a separate European advance-cargo regime; Customscore must model them as independent jurisdictions, messages, authorities, and clocks.

Booking files, messages, and documents can populate candidates, but tariff and export-control classifications, party roles, licenses, exemptions, voyage data, deadlines, and filing responsibility require authorized review. A valid schema is not a valid filing, and portal acceptance is not customs clearance or proof of legal compliance.

The first release should produce reviewed drafts and test submissions only for authorized filers. It must preserve source per field, current rule version, validation errors, approver, destination response, amendments, withdrawal, retention, and correction.

Who pays — and why

Small and mid-sized vessel forwarders, non-vessel carriers, and exporters preparing U.S. export-manifest records under an authorized filing role.

What it unlocks
A jurisdiction-specific filing profile with authority, rule version, message schema, filer role, ports or modes, clock, amendment rules, test status, and effective dates
A shipment record preserving source per shipper, consignee, commodity, package, weight, classification candidate, export-control candidate, vessel, voyage, booking, and document
A review case with conflicts, missing fields, confidence, classification basis, license or exemption evidence, owner, approver, deadline, and no inferred truth
A filing lifecycle separating draft, validation, authorization, submission, transport receipt, agency acknowledgment, rejection, amendment, withdrawal, readback, correction, and no clearance certification
How Genesis scored it
7.11across seven criteria
tension 7temporal 8blindspot 6buyer 8leverage 6convergence 5why-not 8
8
Temporal window

A live proposal and pilot create a preparation window rather than a current mandate.

8
Buyer persona

Forwarders and exporters are specific.

5
Convergence

Several logistics and classification neighbors support the direction.

Why it scored well

The filer buyer, verified proposal, live portal, structured message, and evidence workflow are concrete.

What's holding it back

The rule is not final, jurisdictional framing needed correction, classifications are high risk, enterprise incumbents exist, and authorized filing access requires validation.

Signals detected4 sources crossed
Signalprimary-authority URLs carried in Genesis

Signalagency material carried in Genesis

Signalresearch correction carried in Genesis

Signalcompetitive research carried in Genesis

Direction briefcustomscore.md
customscore.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.