Free Trade Agreement Software

Free trade agreement software determines whether your goods qualify for preferential, often duty-free, treatment under an agreement such as USMCA, gathers the evidence that supports the claim, and tracks the duty you save. It runs the agreement's rules of origin, tariff shift, regional value content, de minimis, against each product's bill of materials, so a good is claimed as originating only when it genuinely meets the criteria. Captain also solicits and manages the supplier certifications a valid claim requires, feeds the preferential rate into the duty calculation, and tracks savings claimed against savings eligible. The result is preferential duty you actually capture, backed by a record you can defend if customs verifies the claim.

Trade compliance software is the broad suite covering export classification, licensing, screening, and controls. Free trade agreement software is a focused tool on the import-duty-savings side: qualifying goods under agreements, managing origin certifications, and capturing preferential duty. In Captain the FTA module sits on the same platform as the broader compliance suite and shares its data, so a good's qualification and its export-control status live on one record. If your need is a complete export-control program, the suite is the answer; if your immediate goal is capturing FTA duty savings correctly and defensibly, this is the module that does it, feeding the duty engine rather than duplicating the compliance suite.

USMCA qualification is not about where a good ships from; it is about whether the good meets the agreement's rules of origin. The software runs those rules against the product's bill of materials: whether non-originating inputs undergo the required tariff shift, whether the good meets a regional value content threshold, whether de minimis allowances apply, and whether accumulation across member countries helps it qualify. A good that passes is claimed as originating with the specific rule it satisfied recorded; one that fails falls back to the standard rate rather than an unsupported claim. Because the criteria are applied against real component data, the qualification reflects how the good is actually made, which is exactly what customs examines in a verification.

Many FTA claims depend on your suppliers certifying the origin of the components they provide, and chasing those certifications by email is where claims quietly fall apart. The platform automates the solicitation: it requests the certificates of origin and blanket certifications your vendors owe, stores them, tracks which are outstanding, and follows up on missing or expiring ones. A claim is then backed by a certification on file rather than an assumption that a supplier's part qualifies. This matters because in a verification, customs asks for the support behind the claim, and a good's originating status often traces back to a supplier's declaration you must be able to produce. Managing that solicitation systematically is what keeps claims supported at scale.

Rules of origin are the criteria an agreement uses to decide whether a good counts as originating in the member territory and therefore qualifies for preferential duty. The common tests are a tariff shift, where non-originating inputs must change tariff classification through processing, and regional value content, where a minimum percentage of the good's value must come from the region, plus de minimis tolerances and accumulation provisions. They matter because shipping from a member country is not enough; a good assembled there from non-qualifying inputs may not originate. Applying the rules correctly is the difference between a valid claim and one that collapses under verification, taking the saved duty plus penalties with it. The software runs the tests so qualification rests on the criteria, not a guess.

The platform tracks the preferential duty actually claimed against what you were eligible to claim, so the gap, the savings you left on the table, is visible rather than invisible. It flags shipments where an eligible good was not claimed, whether because a certification was missing or a claim was simply overlooked, and reports savings by lane and product so you can see where the program is working and where it leaks. This closes the common blind spot where a company assumes it is capturing FTA benefits but never measures claimed against eligible. Making leakage a number on a report, rather than an unexamined assumption, is what turns available savings into captured savings.

Yes. Qualification is only useful if it changes what you pay, so when a good qualifies, its preferential rate feeds directly into the duty engine and lands in the duty calculation and landed cost. A good that does not qualify falls back to the standard most-favored-nation rate, so the duty math always reflects the good's true status rather than an optimistic claim. Because qualification and duty share one data set in Captain, there is no disconnect between what the FTA module claims and what the entry declares. The claim status also rides on the entry record, so if customs asks, the preferential treatment is tied to the qualification and certification that justified it.

When you claim preferential treatment, customs can verify that the good actually qualifies, often by sending a verification request asking for the basis of the claim and the supporting records. If you cannot support it, the duty saved is reclaimed and penalties can follow, so the claim's defensibility is the whole point. The platform builds that defense as goods move: each qualification is linked to the origin rule it met, the bill of materials behind it, and the supplier certification that supports it, and certificates are kept valid and on file. When a verification arrives, you produce a record that was assembled at the time of the claim rather than reconstructed under the response deadline, which is exactly what a verification tests.

Yes. Importers often source across lanes touched by different agreements, each with its own rules of origin and certification requirements. The platform holds the rule sets for USMCA and the other US free trade agreements your trade touches, qualifies each good under the agreements available to it, and where more than one applies, helps identify the best treatment per product. Managing multiple agreements manually is where mistakes creep in, because the origin tests and documentation differ by agreement. Encoding each agreement's rules means a good is qualified under the right criteria for the right agreement, rather than one team's memory of how a single agreement worked being applied everywhere.

Yes. The platform connects to your ERP, product data, bills of materials, and supplier records through API integration, so qualification runs on live component data and certification solicitation reaches your actual vendors. This is what makes FTA management workable at scale: qualification reflects how products are currently built, and certifications are tied to the suppliers and parts they cover rather than a static spreadsheet that drifts out of date. Because qualification lives on the shared platform, the preferential rate feeds the duty engine and the claim rides the entry record automatically, so the saving is captured in the systems that actually price and file, not trapped in a separate FTA tool.

Qualification logic can be live in two to three weeks, but capturing the supplier certifications is usually the longer pole. Setup involves connecting bills of materials and supplier data, configuring the agreement rules for your lanes, and running the catalog through qualification. The certification solicitation then runs as an ongoing campaign, because it depends on suppliers responding, so the program reaches full coverage as certificates come in over the following weeks. We prioritize the highest-duty, highest-volume goods so the largest savings are secured first. As with the rest of the platform, clean bill-of-materials and supplier data speeds qualification, and the main external dependency is how promptly your suppliers return their certifications.