Know what the tariff does to your margin before it lands.
RONA TariffShield takes a new tariff, runs it as a live scenario against your own bill of materials, and tells you what it does to your landed cost, your margin, and your delivery dates, then hands you a re-sourcing and routing plan you can actually act on. Not a spreadsheet you have to trust, a model with the numbers behind it.
Model a tariff scenario See a sample impact report
THE PROBLEM
A duty schedule changes, your sourced parts get more expensive, and if you are like most importers you find out from an invoice after the shipment clears customs, not from a plan. The usual tools do not close that gap. A landed-cost spreadsheet is static the moment you save it (it does not know the schedule is still escalating), and a trade-compliance consultant sells you an opinion, not a model you can re-run when the next rate step hits. The numbers say this is not an edge case, 82% of importers were hit by the 2025-26 tariffs and 47% of them lost 10% or more of revenue at execution, and the schedule keeps stepping up on dated deadlines through 2026. So the question stops being whether you are exposed, and becomes whether you can see the hit and the way around it before it arrives.
HOW IT WORKS
TariffShield does not replace your customs broker and it does not ask you to change how you source. It sits on top of the sourcing you already run. You give it a product and its bill of materials with HS codes, and a tariff scenario (a Section 301 line, a lost de-minimis exemption, a scheduled escalation), and it does two things at once. It runs the geopolitical arm, classifying the trade action, assessing how hard it hits, and forecasting where the schedule is heading, and it models the tariff as a disruption on the same simulation engine AYA already ships (the tariff is just another kind of shock to the supply chain, so it runs through the engine we already built, we did not bolt on a new one). Then it works the mitigation, forecasting demand under the new landed cost, scoring alternative vendors for re-sourcing, pricing the shipping delta, and optimizing the route. Where the inputs genuinely cannot decide a case (a missing HS code, an unpriced lane) it says so and flags it, rather than inventing a number to fill the gap.
WHAT YOU GET
For the scenario you model, one report you can put in front of a CFO: - the quantified impact, landed cost, margin, and delivery timing under the tariff, versus today, - the geopolitical read, how the trade action is classified and where the duty schedule is forecast to head, - the mitigation plan, alternative vendors scored for re-sourcing, the shipping cost and time delta, and an optimized route, - the honest gaps, the fields the model could not decide and what input would close them.
A plan with the numbers attached, not a static sheet that is stale by the time you read it.
WHO IT'S FOR
Supply-chain and procurement leaders at import-dependent manufacturers and consumer-goods brands with real exposure to Section 301 and reciprocal tariffs and shifting duty schedules, first, then the 3PLs and sourcing agencies who advise them and need a defensible impact model to point at. If a duty change can quietly eat your margin between the PO and the invoice, this is for you. If you source entirely domestic and a tariff costs you nothing, it is not.
PRICING (the ladder)
We price the ladder, not a single number, and every number below is a hypothesis we validate with you, not a commitment. - Scenario pilot, a fixed-price paid proof, we model one live tariff scenario against your own bill of materials and hand back the impact and the mitigation plan before you commit to anything. - Portfolio metered, per SKU portfolio monitored, once the pilot proves the model, we re-run the scenarios as the schedule changes. - Platform, license the tariff simulation and mitigation into your own planning stack.
IP is licensed, never assigned. The engine stays ours, the plan is yours. Any step that takes your money is gated and confirmed before it runs, nothing charges silently.
THE PROOF (dogfood)
We run this discipline on ourselves before we sell it. AYA is an import-dependent operation in its own way, it leans on outside providers (an LLM API, cloud, domains), so we model our own provider-cost and supplier-concentration shocks on the exact same simulation engine this product sells, the engine does not care whether the shock is a tariff on your parts or a price jump on our API, it is the same math. And the product's own build left a receipt, the deliverable pattern was scored by our quality gate and all ten of the atoms it composes were verified on disk before this page was written. That is the same kind of evidence trail TariffShield produces for a scenario.
HONEST NOTE
We would rather under-promise. TariffShield has been built and structurally verified, the pattern composes ten real atoms, the references resolve, the simulation engine underneath is the one AYA already runs. What it has NOT done yet is pull live duty rates from a customs feed or run against a real buyer's bill of materials, the duty rates in the model right now are sample data, and pulling live rates needs a connector we have not built yet (that piece is real code, and we will say so rather than imply it is done). The first live scenario is the natural next test once a rate source and a real bill of materials are in hand. Where a sound number exists we give it to you with the math, where the data will not decide we tell you and flag it, we never manufacture a clean answer. That refusal to fake certainty is the whole point.
Model a tariff scenario
*This page is a specification. The capability it describes is not built yet, and nothing here is a claim that it runs today.*