Customs Duty Management Software

Customs duty management software calculates the duty, taxes, and fees owed on imported goods and rolls them into a full landed cost per line. It reads HS codes and tariff schedules, applies the HTS duty rate for the country of origin, screens shipments against free trade agreements, and keeps the record an auditor or a refund claim needs. Vendors also call it a customs duty management system, a duty management solution, or simply customs duty software: the scope is the same.

No. Customs duty management system, customs duty management systems, and customs duty software describe the same category, and importers use the terms interchangeably in RFPs and vendor shortlists. What varies between vendors is scope, not naming: whether duty calculation stops at the estimate, or continues into free trade agreement screening, exemptions, refund identification, and the audit trail that supports a claim months later. Captain covers the full span, which is why the same platform serves the compliance team that files the entry and the finance team that reconciles the duty spend at quarter end.

The platform calculates duty on each entry line from three inputs: the HTS code, the declared commercial value, and the country of origin. It applies the correct tariff schedule rate, layers on any trade remedy such as Section 301, adds taxes and fees, and rolls the total into a landed cost per unit. Because the math runs on the same commercial data your customs entry uses, finance plans against the number customs will actually charge rather than an estimate. The calculation updates as rates change, so a shipment entering today is priced with today's rate and a shipment that entered last quarter keeps the rate that applied then. That is what keeps landed-cost accuracy high enough to plan margins against.

Every duty calculation starts from the HS code, the internationally standardized classification that determines which tariff line a product falls under. The platform assigns each product an HS code, holds it consistent across shipments, and pulls the matching rate from the current tariff schedule automatically, so your team is not looking up rates by hand or working from a stale copy. Country of origin is captured alongside the code because origin often changes the applicable rate, whether through a trade remedy or a preferential agreement. Keeping HS codes consistent is also a compliance issue, since customs flags products that are classified two different ways, so the software treats classification as one source of truth feeding both duty accuracy and audit defense.

Yes. The platform screens every shipment against the free trade agreements and WTO framework rules that could lower the rate you pay, so preferential treatment you qualify for is claimed rather than missed by default. When a shipment is eligible, the software flags it and prompts for the documentation the agreement requires, such as a certificate of origin, so the claim is supported if customs asks. Missing an agreement you qualify for means overpaying duty on every shipment, which quietly erodes margin. By checking eligibility automatically on each line, the software turns free trade agreements from something a specialist remembers to check into a standing part of every duty calculation.

Yes. The platform flags shipments that are eligible for duty refunds, exemptions, or drawback, the recovery of duties paid on goods later exported or destroyed, and tracks each recovery from filing to approval. It matches import entries to the qualifying exports that support a drawback claim, so the paper trail is built as goods move rather than reconstructed years later. Refund and exemption candidates surface the moment a shipment qualifies, so recovery you are owed does not expire unclaimed. For importers with export volume, drawback and refunds can return a meaningful share of duties paid, and having the software identify eligible movements automatically is the difference between recovering that cash and leaving it behind.

Digital goods sit in a gray area that trips up a lot of importers. Customs duty on software downloaded from the internet and SaaS import duty depend on how the transaction is structured, whether the item is treated as a good or a service, and the rules of the importing country. The platform applies the valuation and treatment rules for intangible goods so these transactions are handled consistently rather than guessed at case by case. Because the treatment of digital and cloud-delivered products keeps shifting, having the software encode current rules means your team is not relying on a memory of how it worked last year. When the treatment is genuinely unsettled, the record shows the basis you used, which is what an auditor wants to see.

Landed cost estimation adds every cost of getting goods to your door on top of the product price: duty, taxes, fees, freight, and any trade remedies, calculated per line and per unit. The platform pulls the commercial value and origin from your ERP, applies the duty and agreement rules, and returns a landed cost before the shipment arrives, so buying and pricing decisions use the real number. Because the estimate runs on the same data the customs entry will use, the gap between estimate and actual is small, which is what makes the figure usable for margin planning. Finance stops reconciling duty after the fact and starts pricing against a landed cost it can trust the day the purchase order is raised.

Yes. The platform tracks the shipments that feed the duty calculation using AIS and GPS data, so the origin, route, and timing behind each landed unit are captured rather than assumed. A CO2 tracking module estimates the emissions tied to each shipment, which matters for companies with sustainability reporting obligations or customers asking for carbon data on the goods they buy. Tying emissions to the same shipment record that drives duty means one system answers both the landed-cost question and the carbon question, instead of running a separate tool for each. For importers, that connection also helps when route or mode choices affect both cost and emissions, since both numbers are visible against the same shipment.

Yes. The platform connects to your ERP and commercial systems through customs API integration, so commercial value, origin, and HS data flow in automatically and landed cost flows back to your system of record. That two-way link is what keeps the duty finance plans against matching the duty customs charges, because both draw from the same source data. Companies that already run a major ERP do not have to replatform; the duty software sits on top and consumes the data they already maintain. The API also lets landed cost feed pricing, procurement, and reporting downstream, so the duty number is not trapped in a customs screen but available wherever the business needs to price against it.

For the recurring, rules-based work, yes: the software calculates duty accurately, screens agreements, and surfaces refunds on every shipment without a person doing it by hand. For structural strategy, the two work together rather than competing. Deciding whether to re-engineer a supply chain, restructure a transaction, or pursue a novel classification position is judgment work, which is where customs duty reduction consulting adds value on top of the software. The advantage of running both from one platform is that the consultant starts from clean, complete data the software already maintains rather than commissioning a separate analysis. Most importers use the software to handle the volume accurately and bring in an advisor for the handful of high-value structural moves.

Yes. The platform runs on ISO and SOC aligned security controls, with multi-factor authentication and role-based permissions so only authorized staff touch the numbers and every action is attributable. On the compliance side, every duty calculation, agreement claim, and refund is timestamped and linked to the value and origin that drove it, and rate changes are versioned by effective date. When customs opens a review or you file a refund claim, the record shows how each number was derived and which rate applied when, so your reasonable care file and your claim support are built as goods move rather than reconstructed under deadline. Accurate duty and a defensible record are the same feature here: one complete, attributable trail.

A straightforward program can be live in two to three weeks: about a week to connect your ERP through the customs API and load your HS library and tariff scope, a few days to configure agreement and remedy rules, and a reconciliation window where calculated landed cost is checked against real entries before go-live. More complex programs with deep SKU counts, many origins, or heavy free trade agreement use take four to six weeks because the rule sets are larger. We sequence it so the calculation is validated against your actual history before finance relies on it. The usual gate is not our setup, it is how clean your item, value, and origin data is when we load it on day one.

The platform scans your import activity for several kinds of recovery: duty drawback on goods later exported or destroyed, preferential rates under free trade agreements that were not claimed at entry, exemptions that apply to certain goods or uses, and overpayments from misapplied rates. When a shipment fits one of these, it is flagged with the basis and the recovery is tracked to approval. Because the scan runs continuously on the same data your entries use, opportunities surface as they arise rather than during an occasional manual review. Many importers find recoverable duty simply because no one had time to check every shipment against every agreement and refund rule, which is exactly the repetitive checking the software is built to do without missing lines.