We build a system that calculates the preferential origin of your exported products rule by rule, tracks supplier origin declarations at product and validity level, and records HS classification decisions together with their reasoning. The goal is to be able to show the calculation behind an origin claim the moment it is asked for.
In most businesses, origin looks like a paperwork exercise in exporting: the certificate is issued, filed, done. Yet origin is not a document but an outcome; the document is merely the declaration of that outcome. Whether a product acquires preferential origin depends on where its inputs came from, what processing was carried out in production, and what the rule defined for that product in the trade agreement requires. In most factories, the place where that calculation lives is an Excel file or the memory of an experienced employee.
The problem arises less from the calculation not being done than from it not being traceable. An input supplier changes; one batch of the same product is made with domestic inputs and another with imported ones; currency and price movements push the value-added ratio below the threshold. The product looks the same, but the origin outcome has changed. When a post-clearance verification comes, what is expected is not the certificate itself but the calculation it rests on: which input, which origin, which value, which rule. If that chain has not been built, the claim cannot be defended.
The system we build sits this chain on top of the product's bill of materials. Origin and value information is held for every input; supplier origin declarations are recorded per product, with their validity periods; the rule the product is subject to is defined per agreement, and the calculation is done by the machine. The result is not a single yes or no: you can see which limb of the rule was satisfied, which input determined the outcome and how close the product came to the threshold. Products near the threshold are flagged separately, because that is where the real risk sits.
The software described on this page provides decision support; it does not replace your responsibility before the customs authority. As the declarant you are responsible for the accuracy of the declaration, and classification and declaration procedures belong to your customs broker; if you need a binding assurance on a tariff heading, the route is not software but a binding tariff information application to the customs authority. The layer we build keeps these decisions in one place with their reasoning, applies the same decision to recurring products, and lets the full calculation be produced when questions come later.
Manufacturers exporting under a preferential origin claim. Because the duty your buyer pays at customs depends on that claim, a problem surfacing in post-clearance verification directly affects the customer relationship and commercial cost.
Textile, plastics, machinery and food manufacturers that import a significant share of their raw materials or intermediates. Origin acquisition is not automatic in these businesses; as the input mix changes, so does the outcome, and tracking it has to be done product by product.
Businesses working with hundreds of variants. When calculating origin by hand per product becomes practically impossible, most firms generalise from a single example; the risk accumulates precisely in that generalisation.
Firms with a foreign trade officer on staff but with the knowledge held by an individual. Recording decisions together with their reasoning keeps the institutional memory when that person leaves.
Origin is calculated from the origin and value of the inputs in the product tree. Value-added thresholds, change-of-tariff-heading rules and specific processing rules are defined per product; the calculation can be re-run for every batch and every BOM version. The result comes with a reasoning trail showing which rule was satisfied with which data.
Origin declarations from suppliers are recorded at product and period level; which declaration covers which input and which date range is visible. Declarations that expire or fall short in scope trigger early warnings. The collection process can be run end to end, including requests and reminders to suppliers.
Different agreements may demand different rules for the same product. Rules are defined per agreement and the same product is assessed separately for each target market. Where cumulation is used, which countries' inputs are counted is explicit in the calculation.
Candidate tariff headings and comparisons are suggested from product characteristics; the real value is that each decision is archived with its reasoning. When a similar product arrives, the past decision surfaces first, preventing the same product being classified differently at different times. The final classification decision belongs to your customs broker.
Products whose origin qualification comes out close to the threshold are listed separately. Whether currency movements, supplier changes or price rises have pushed them below the threshold is recalculated periodically. The problem thus becomes visible before the export happens, not after.
The basis for the origin claim on a shipment is compiled at a single click: the BOM, input origins, supplier declarations, the rule applied and the steps of the calculation. This file stands as the assembled version of exactly what would otherwise have to be hunted down when answering a verification request.
We map which products go to which markets under which agreements. We discuss on site how the origin claim is currently constructed and who decides. The first surprise in this map is usually the discovery that the basis of the claim is not written down anywhere.
The origin calculation depends on BOM quality. Existing product trees, input costs and supplier records are reviewed and the gaps are flagged. This step usually exposes the difference between the BOM in the ERP and the real BOM on the shop floor — and that finding is valuable in itself.
The rules that apply to your product groups are written into the system and validated together with your foreign trade officer or customs broker. Writing the rules is a matter of legal interpretation; we do not do the interpreting — we take the expert's interpretation and make it repeatable by machine.
The system is run over shipments that already happened, and its results are compared with the decisions taken at the time. Every discrepancy is examined one by one. This both validates the rule set and surfaces points that may have been missed in the past.
The calculation is embedded in the order and shipment flow; the origin result is visible before documents are prepared. Supplier declaration reminders and the threshold-proximity report run on schedule. Handover is done with the team using it; how rules are updated is left in writing.
Your customs broker prepares the declaration and handles the procedure; the production data that origin rests on sits with you. The BOM, input origins, supplier declarations and cost data live inside the factory. This system does not replace your broker — it gives them accurate, reasoned data on time. The most common problem in practice is that the information the broker asks for takes days to compile in the factory.
It does not — and be wary of any software that claims to. The software applies the rule you define to your data and shows the result with its reasoning. Correct interpretation of the rule, correct data entry and the accuracy of the declaration remain your responsibility as the declarant. What we provide is a result that is repeatable and defensible.
No. The system puts candidate headings, comparisons and your past decisions in front of you; the decision is made by your team or your customs broker. If a binding assurance is needed, the route is a binding tariff information application to the customs authority; the software makes preparing that application easier, but does not replace it.
It can, but the gaps flow straight into the result. In the first phase we separate the products whose BOMs are reliable and start the scope there. Completing the missing BOMs is a separate piece of work; in most factories that work creates value independently of the origin project, because cost accounting rests on the same data.
The rule set is held as data, not buried in code; changes can be applied without software development. When a change is made, past calculations are preserved, the new rule applies from its effective date, and which decision was made under which rule version stays on record. Monitoring the legislation is your job or your broker's; the system's job is to make the change operational.
An origin calculation that runs per product; validity tracking for supplier declarations; an HS classification decision archive; a risk list of products near the threshold; a supporting file compiled at a single click for post-clearance verification; and an audit trail across all of it. Everything produced, source code included, is one hundred per cent yours.
In a 30-minute discovery call we listen to what you need and tell you honestly whether custom development or an off-the-shelf product is the better answer.
We build a layer that calculates the embedded emissions of the products you export to the European Union at plant, line and batch level. It combines production, energy and raw material data and produces the result in a form your buyer will accept and a verifier can trace.
Details →We build an infrastructure that collects the data behind sustainability reports at source, stores it with an auditable trail and manages the recurring reporting calendar. We are not the ones who sign the report; we produce what the report rests on.
Details →For manufacturers of machines and devices with embedded software, we build a regime that generates the software bill of materials, keeps the component and licence inventory current, monitors known vulnerabilities and establishes notification and update processes.
Details →We build an infrastructure where product-level material composition, production history, supply chain trail and repair information is collected, versioned and published through a data carrier. The way to be ready when the date is set is to start accumulating the data today.
Details →If your business depends on a program whose developer can no longer be reached, whose source code is incomplete or which has no documentation at all, we take that system over, establish how it works on the basis of evidence, and bring it back to a state where it can live on.
Details →We find the cause of systems that lock up at end-of-day close, month-end reports that never open, and screens that stall when a few users log in at once — by measuring. Not with guesswork, but with query plans and profiling data, measuring before and after with the same rig.
Details →
