You got the tariff alert. Now you have no idea which of your entries it actually hits.
Send one structured import file and get back a clear review showing which entries deserve attention first, what records are missing, and what should happen next.
Your email app should open now. If nothing happened, use the quick request box below and copy the request into any email to hello@dutysignal.com.
Go to quick request boxThis is the fallback path if clicking the email button does nothing on your device. Fill this out, copy the prepared message, and send it to hello@dutysignal.com from any email service you use.
Request prepared. Copy this message and send it to hello@dutysignal.com.
Small importers do not just need another stream of headlines. They need to know which entries may be affected, where money may be at stake, what support is missing, what deadline matters, and what exact next step to take.
DutySignal is being built around that narrower job: importer action, not vague awareness.
This is the strongest part of the workflow: a triage view that shows what deserves attention now and what to do next.
| Priority | SKU | Change Detected | Deadline | Next Action |
|---|---|---|---|---|
| Critical | SKU-1042 | Possible refund review on recent entries | Apr 22, 2026 | Ask broker to review 3 affected entries |
| High | SKU-2230 | Entry appears reviewable but still missing support | No hard deadline | Pull missing invoice and broker backup |
| Medium | SKU-8811 | Item pressure tied to current landed cost | Review this week | Compare landed cost against current sell price |
Qualified • Exposure: $3,800 • Priority: High
Request the upload template, then send one structured CSV for review. Redaction is acceptable if the row logic stays usable.
The intake is run through the cockpit to surface affected entries, readiness gaps, item pressure, and ranked next actions.
You receive a printable handoff showing what looks actionable now, what still needs documents, and what to send or do next.
Most importers should walk away knowing exactly which entries to hand to their broker first instead of guessing where to start.
Plain-English explanation of the issue or operating signal that may affect recent import entries.
Which entries, SKUs, origin patterns, and related items appear to deserve review first.
Which cases look action-ready now and which still need entry packets, broker backup, invoices, or classification support.
Ranked next actions instead of a flat list of alerts, so a small operator can move in order.
SKU-level pressure snapshot so entry review and margin decisions are not treated as separate worlds.
A printable action pack built for review and follow-through, without pretending the tool is filing software.
If you want to move forward, request the upload template and send one structured CSV for review.
DutySignal is built around structured import-entry data. The preferred intake includes:
entry_id, entry_date, importer_name, supplier_name, country_of_origin, declared_value_usd, duty_paid_usd, freight_cost_usd, sku, product_name, quantity, selling_price_usd
Recommended support columns:
entry_packet_on_hand, broker_backup_on_hand, commercial_invoice_on_hand, classification_support_on_hand, hs_code, marketplace, fba_fee_usd, referral_fee_usd, other_cost_usd
Redaction is acceptable for early review if aliases stay consistent and the row structure remains usable.
No. The current version is a pilot workflow supported by a working MVP demo and manual delivery.
A reviewed action-pack style output showing possible opportunity, readiness status, missing records, priority entries, item pressure, and ranked next actions.
No. For early review, redacted files are acceptable if aliases stay consistent and the structure remains usable.
No. DutySignal is built to help you review what deserves action and what should happen next. It is not customs filing or broker representation.
Because the wedge is clarity and action for small importers. The goal is to solve one hard problem well instead of drifting into a bloated platform.
If you are a U.S. small importer and want to test whether DutySignal fits your workflow, request a pilot review and include a brief summary of your import setup and current pain point.