GO
Overall Score
LineTax
1. One-liner
Catches the parcels where your carrier split one €3 customs line into three — and reclaims the difference.
2. Trend signal — why now?
On 1 July 2026 the EU abolished the €150 duty relief and replaced it with a temporary €3 customs duty, adopted under Council Regulation (EU) 2026/382 and implemented by Commission Delegated Regulation (EU) 2026/1022 of 30 June 2026. It runs until 1 July 2028, after which normal tariff rates apply.
The interesting part is not the €3. It is how the €3 is counted. Per the European Commission’s own guidance:
“the EUR 3 customs duty will automatically apply per declaration line irrespective of the quantity (number of the articles) in that declaration line”
And critically, the Commission amended Article 228(1) UCC-IA so that:
“the grouping of items is not allowed where the temporary EUR 3 customs duty applies.”
That means the bill is a pure function of how many declaration lines the filer chose to open — and the number of lines depends on which dataset the carrier files under. The Commission’s own worked example, a €140 consignment of three women’s suits from China under IOSS:
| Dataset | Classification depth | Lines | Duty |
|---|---|---|---|
| H7 (courier, super-reduced) | 6-digit HS 6104 19 | 1 | €3 |
| H6 (postal) | 8-digit CN 6104 19 90 | 1 | €3 |
| H1 (standard) | 10-digit TARIC …90 10 / 90 20 / 90 90 | 3 | €9 |
Same parcel. Same goods. Same buyer. 3× the duty, decided entirely by a filing choice the seller does not make and usually cannot see.
And the industry is drifting toward the expensive option. Avalara, writing after the rule went live: “one emerging trend is the shift from H7 declarations to H1 declarations, which use a more comprehensive customs dataset, as businesses reconsider their supply chain design in response to increased compliance expectations.” Avalara also names the exact failure: “If a business calculates duties assuming H7 grouping but the carrier files the shipment under H1, the business may undercollect from the buyer.”
Who eats it? Not the consumer. Per the reform’s operating model, the €3 “is charged on businesses (the seller, importer, or their representative) not collected from consumers at the door.” Under the UCC declarant cascade the declarant is “in most cases … the IOSS holder, the special arrangements operator, their indirect customs representative.” The seller is on the hook, and finds out weeks later on a carrier invoice.
The recovery route exists and is unusually friendly: UCC Article 117 permits repayment of duty that was not legally due, within three years of notification of the customs debt, and — per EC guidance on repayment and remission — no de-minimis threshold applies. Small claims are legally reclaimable. Nobody is reclaiming them.
Provenance:
- Signal 1 (Demand): EC guidance confirms the €3 applies per declaration line with grouping prohibited, and the same €140 parcel costs €3 under H7 vs €9 under H1 — a 3× swing the seller does not control — https://taxation-customs.ec.europa.eu/document/download/053e5b4e-f0be-4f20-9a23-3e3b659a6676_en — 2026-09-03
- Signal 2 (Feasibility): Avalara documents the industry shift from H7 to H1 filing and names the seller-side undercollection failure mode; Shopify’s own €3 support explicitly stops short of reconciling collected-vs-assessed — https://www.avalara.com/blog/en/europe/2026/07/eu-customs-h1-h6-h7-declarations.html — 2026-09-03
- Signal 3 (Economic): Rule enacted via Council Reg (EU) 2026/382 + Delegated Reg (EU) 2026/1022, live 1 July 2026 to 1 July 2028, covering ~93% of e-commerce imports via IOSS; incumbent reconciliation-grade tooling starts at $1,349/mo (Descartes Sellercloud) — https://trade.ec.europa.eu/access-to-markets/en/news/eu-applies-eu3-customs-duty-item-low-value-e-commerce-consignments — 2026-09-03 Category: Regulatory arbitrage
3. The opportunity
There are two distinct jobs in the €3 world, and the market has only built the first one.
Job 1 — collect the right amount at checkout. Solved, and solved by serious people. Zonos, Avalara Cross-Border, DutyPilot, and Shopify’s own Managed Markets all calculate and display the €3 at checkout. Shopify shipped native support.
Job 2 — verify that what the carrier actually billed you matches what was legally owed. Nobody sells this to a small seller.
Look at what Shopify’s Managed Markets does not do. Its coverage stops at collection: carrier handling fees “remain merchant responsibility,” and on reconciliation the guidance is that merchants should “reconcile duties and VAT collected at checkout against remittance reports” — with no mechanism offered for resolving mismatches. HS-code accuracy and audit defence remain “entirely merchant responsibility.” The advice is literally “Engage customs experts where product classifications are complex.” That is a vendor telling you the gap exists and declining to fill it.
Then look at who Managed Markets is even available to: merchants based in the continental US, plus certain stores in Canada and the UK, on Shopify Payments, at 6.5% of order value plus 2.5% FX. An EU-facing seller in India, Australia, Turkey or Vietnam cannot buy it at any price. An Etsy-only seller cannot buy it. A seller doing €200K/yr into the EU is not paying 6.5% of revenue for duty handling.
The other end of the market is worse. Reconciliation-grade customs systems — Descartes CustomsInfo, Thomson Reuters ONESOURCE, SAP GTS, E2open — are enterprise trade-compliance suites. Descartes’ Sellercloud publicly starts at $1,349/month. These are built for compliance departments running focused-assessment defence, not for a jewellery seller checking whether DHL opened two lines or five on a €60 parcel.
So the structural gap: the party who pays the €3 is not the party who decides how many €3s there are, and there is no cheap tool that checks the arithmetic. Every incumbent is positioned on the pre-transaction side (quote the duty) because that is where the transaction fee lives. The post-transaction side — auditing the carrier’s filing and reclaiming under Art. 117 — has no natural vendor, because the money it recovers is small per parcel and the incumbents’ unit economics won’t chase it.
This is exactly the case AI collapses. Reading a carrier invoice line, inferring the dataset used, re-deriving the correct line count from the product mix, and drafting an Art. 117 repayment application is a 40-minute customs-broker task per disputed shipment. At €3–€12 recovered per parcel, that task is uneconomic for a human and perfectly economic for a model.
4. Target market
Primary customer: The owner-operator of a non-EU e-commerce business shipping 500–15,000 low-value parcels a year into the EU — €150K–€3M revenue, 0–8 staff, no customs broker on retainer. Concretely: Etsy and Shopify sellers in the US, UK, India, Turkey, Australia and China shipping apparel, jewellery, print, hobby goods, parts and accessories. Secondary: the small 3PLs and fulfilment agencies who ship on behalf of 20–200 such merchants and currently absorb these disputes as unbillable support.
Why they buy: The pain is a line item that appeared on their carrier invoice in July 2026 and was bigger than the number their checkout collected. They are not compliance-curious; they are margin-squeezed. On a €35 average-order-value Etsy parcel, an unexpected extra €6 of duty is ~17% of the order. The multi-item baskets that are supposed to be their best orders are the ones that get split into the most lines.
The failure is silent in the way that matters: the seller collected €3 at checkout, the carrier billed €9, and the €6 gap surfaces on a monthly statement with no per-parcel breakdown. There is no error, no rejection, no alert. It just quietly compounds.
Rough TAM reasoning: The €3 duty covers the low-value e-commerce lane where IOSS handles roughly 93% of imports. Etsy alone has millions of active sellers with meaningful EU-facing cross-border volume, and small Shopify stores selling cross-border number in the low millions. I do not need the whole pool — I need the slice shipping enough EU volume that a monthly fee is trivially justified. Call the serviceable set 150K–400K sellers and small 3PLs worldwide. At a €39–€149/mo blended price, the addressable revenue is comfortably north of $100M; I need well under 1% of it.
Why now for them: The regime started 1 July 2026, so the first three carrier invoices have landed. The Art. 117 three-year clock on the earliest of those debts runs to mid-2029 — there is a recoverable backlog sitting in inboxes right now, and it grows every month. Additionally, mandatory Product Identifier (PID) data lands 1 November 2026 (voluntary from 1 July 2026), which is a second forcing event that will push more filers toward richer datasets — and therefore more lines.
5. Product sketch (MVP)
- Invoice ingest. Forward or connect your DHL / UPS / FedEx / national-post billing account. LineTax parses each customs-duty line back to the parcel and the order.
- Line-count re-derivation. For each parcel, reconstruct the correct number of declaration lines from the actual product mix and its Annex-B tariff classification, and infer which dataset (H1 / H6 / H7) the filer used.
- Overcharge flag. A plain verdict per parcel: “billed 4 lines (€12), correct under H7 grouping is 1 line (€3), overcharge €9.” Plus the counterfactual: what this parcel would have cost had it been filed H7.
- Eligibility screen. Distinguishes genuine overcharges from correct-but-expensive filings, and from cases where grouping is legitimately prohibited — so you don’t file claims you’ll lose.
- Art. 117 repayment pack. Auto-drafted repayment application per Member State of clearance, with the parcel evidence, classification reasoning, and the three-year deadline tracked per claim.
- Carrier escalation letter. For cases where the fix is the carrier’s filing behaviour rather than a customs refund — a dated, specific letter naming the shipments and the dataset used.
- Basket-shape advisor. Flags the SKU combinations in your catalogue that are most expensive to ship together under line-splitting, so you can re-bundle before the next order.
- Monthly leak statement. One page: parcels audited, lines overbilled, € recovered, € recoverable, € still exposed.
6. AI angle — what’s load-bearing
Remove the AI and this product does not exist at this price.
The load-bearing task is classification-to-line-count inference, done per parcel, at a cost of cents. To know whether a carrier over-split a parcel, you must classify each item to the depth the dataset demands — 6-digit HS for H7, 8-digit CN for H6, 10-digit TARIC for H1 — from nothing but a product title, a description and a photo. Then you must reason about whether those items legitimately collapse to one line or genuinely occupy several, against Annex B and the Article 228(1) grouping prohibition.
That is a judgement task over messy, unstructured merchant data — not a lookup. Vision-plus-text classification to HS/TARIC is precisely what modern models do cheaply and well, and it is the reason this is a 2026 product and not a 2019 one. A rules engine cannot do it because merchant product data is free-text chaos (“Boho Wool Blend Jacket - Handmade - Gift for Her”); a human cannot do it because the recovery is €6 and a broker’s hour is €90.
The second AI job is drafting the Art. 117 application in the register a national customs authority expects, per Member State, with the classification argument spelled out. That is a document-generation task with a legal register — again squarely in-model.
The reconciliation arithmetic itself is trivial. The AI is doing the two hard parts on either side of it.
7. Localization angle (if any)
Not a country play, but a Member-State play, and that is a real moat. Repayment under Art. 117 is administered by national customs authorities — Article 117 recourse “falls within the remit of the national customs authorities.” So the claim form, the language, the portal and the practical tolerance differ across 27 states. Clearance concentrates in a handful of them (NL, DE, BE, FR, IE), so v1 covers those five and reaches most volume.
The seller side is global-English: the customers are in the US, UK, India, Turkey, Australia and China. The localization burden sits on the filing side, not the customer side — which is convenient, because it means one English product surface over five localized claim engines. Getting NL and BE right first is worth more than breadth.
8. Business model — path to $1M–$5M ARR
- Pricing: Three tiers by parcel volume. €39/mo (up to 500 parcels/mo), €99/mo (up to 3,000), €249/mo (up to 15,000 + multi-entity for 3PLs). Plus an optional 15% success fee on duty actually recovered through filed Art. 117 claims, for sellers who want the recovery service rather than just the audit.
- ACV: ~€1,100 blended subscription, plus €150–€600 of success fees on active recoverers. Call it €1,400 blended.
- Rough math to $1M ARR: ~640 paying customers at €1,400 blended. Very reachable inside the Etsy/Shopify cross-border seller pool.
- Rough math to $5M ARR: ~3,200 customers, which realistically means winning the small-3PL and fulfilment-agency segment, where one account covers 50–200 merchants and lands at the €249 tier plus volume success fees. That is the expansion story, not more solo sellers.
- Expansion path: Volume tiers ratchet naturally with the customer’s growth. Then: (a) add non-EU lanes as other jurisdictions copy the per-line model; (b) sell the basket-shape advisor as a pre-transaction product to the same account; (c) white-label the audit engine to the 3PLs who want it under their own brand. The 2028 sunset of the €3 flat rate is a real horizon — see risk flags — but the invoice-audit muscle transfers directly to normal tariff rates, which are harder to verify, not easier.
Margin is healthy: cost per parcel audited is a fraction of a cent in inference, and classification results cache hard per SKU. A seller with 200 SKUs pays the classification cost once, then every subsequent parcel is a lookup.
9. Go-to-market wedge — first 100 customers
The wedge is that I can prove the overcharge before the customer pays me anything. That is rare, and I should lean on it hard.
- Free “€3 Leak Report.” A seller forwards one carrier invoice PDF. The tool returns a per-parcel table: lines billed, lines legally owed, € overcharged, € recoverable under Art. 117. No signup, no card. The report is the sales pitch, because it names a number the seller did not know existed. Conversion pitch: “this month’s leak was €340; the tool is €99.”
- Etsy and Shopify seller forums, targeted at the invoice moment. The Etsy community thread on the EU fees and the r/EtsySellers / r/shopify / r/ecommerce cohort are already arguing about July’s charges. Do not post a product link. Post the H7-vs-H1 worked example from the EC guidance — the €3 vs €9 table — because it is genuinely surprising and verifiable, and let the leak report be the call to action. This is a content wedge where the regulation itself is the hook.
- Small 3PLs and cross-border fulfilment agencies — direct outreach. There is a countable list of these (a few thousand globally, findable via freight directories, Shopify’s partner ecosystem, and IOSS intermediary registers). Each one is fielding angry merchant emails about duty invoices right now and has no answer. Pitch: audit your whole book once, free; keep 15% of what we recover for your merchants; then license it. 200 outreach emails at a 10% meeting rate and 25% close gets 5 accounts covering hundreds of merchants.
- IOSS intermediaries as a channel. Firms like EAS Project and the VAT-compliance boutiques already hold the IOSS relationship for thousands of non-EU sellers, and their own published guidance admits the collection/remittance mechanics are unresolved. They have the customer and lack the tool. Revenue share, co-branded.
- Comparison-and-verdict SEO on the exact query. “H7 vs H1 €3 duty”, “why is my EU customs invoice higher than checkout”, “reclaim overpaid EU customs duty”. Low volume, near-zero competition, and every searcher is a qualified buyer mid-problem. This is the slow channel; the first three are the fast ones.
The first 100 come from leak reports off forum posts plus 5–10 3PL accounts. I can see them clearly.
10. Build complexity — justification
Medium. Off-the-shelf: the LLM classification (product text/photo → HS/CN/TARIC), PDF/EDI invoice parsing, the web app, Stripe. The genuinely custom work is threefold: (1) a reliable mapping from carrier invoice formats back to individual parcels and orders — every carrier’s billing export differs, and this is the grubby integration work that makes the product real; (2) encoding the Annex-B line-counting logic and the Article 228(1) grouping prohibition correctly enough that claims survive scrutiny; (3) the Art. 117 claim templates for the first five Member States, which needs a customs-broker advisor to get right.
Two people, 14–18 weeks to a v1 covering DHL + UPS + one national post and NL/DE/IE claims. The classification engine is a week; the invoice-to-parcel reconciliation is a month; the claim packs need domain review, not engineering.
11. Gating checklist
| Gate | Pass? | Note |
|---|---|---|
| Legal in target market | ✅ | Auditing your own duty bills and applying for repayment under UCC Art. 117 is an ordinary trader right. No licence needed to prepare a claim; a customs representative is only needed to file as agent, which is a v2 partnership question. |
| Ethical — no harm / dark patterns | ✅ | Recovers money legally not owed. Product explicitly screens out claims that would fail, and refuses to advise artificial grouping — which the regulation prohibits. |
| Market exists (evidence above) | ✅ | Enacted regulation live since 1 July 2026, EC’s own guidance documents the 3× swing, incumbents priced at $1,349/mo or gated to US/CA/UK merchants at 6.5%. |
| 1–5 person team can build this | ✅ | Two people, 14–18 weeks. |
| Launchable with <$50K / ₹40L | ✅ | Inference costs are cents; main spend is a customs-broker advisor for claim templates. Well under $25K to launch. |
12. Feasibility score
| Axis | Weight | Score | Notes |
|---|---|---|---|
| Problem intensity | 20 | 17/20 | Real money, recurring monthly, and invisible until the invoice lands. On low-AOV multi-item parcels the overcharge is a double-digit percentage of order value. Not hair-on-fire (no penalty, no suspension) — it’s a silent leak, which is why it scores 17 and not 19. |
| Demand evidence | 15 | 13/15 | Enacted regulation, EC’s own worked example proving the 3× swing, Avalara documenting the H7→H1 drift and naming the undercollection failure, Shopify explicitly declining to reconcile, incumbents priced out of the segment. Docked 2: I found no large body of verbatim seller complaints specifically about line-splitting yet — the regime is nine weeks old. |
| Build feasibility | 15 | 11/15 | Classification and drafting are off-the-shelf. Carrier-invoice-to-parcel reconciliation across many formats is genuine grind, and claim templates need domain review. 14–18 weeks, not 6. |
| Distribution clarity | 15 | 12/15 | The free leak report is a strong, provable wedge, and the 3PL/IOSS-intermediary channels are named and countable. Docked because seller forums are noisy and the 3PL sales cycle is weeks, not days. |
| Revenue mechanics | 15 | 12/15 | Pricing sits far below the $1,349/mo incumbent floor and far below Managed Markets’ 6.5%. Success fee aligns incentives. Risk: for the smallest sellers the recoverable sum may not clear €39/mo, which compresses the bottom tier. |
| Time to first revenue | 10 | 7/10 | Leak report → paid conversion can happen in the same week post-launch, but the launch itself is 14–18 weeks out, and success-fee revenue trails claim settlement by months. |
| Defensibility | 10 | 5/10 | The classification engine is copyable. The moat that accrues is the per-Member-State claim playbook, the carrier-invoice format library, and cached SKU classifications per customer — real workflow lock-in by month 12, thin at month 3. |
| Total | 100 | 77/100 |
13. Qualitative modifiers
Founder-fit tags
technical-heavy · domain-expertise-required
You need someone who can build the invoice-parsing and classification pipeline, and access to a customs broker or trade-compliance professional to validate the line-counting logic and claim templates. Do not attempt this without the second person — the failure mode is confidently filing claims that get rejected, which kills trust instantly.
Key assumptions to validate (3–5)
- Assumption: A meaningful share of real parcels are being over-split — i.e. carriers are filing H1 (or splitting within H7) where H7 grouping was available. How to test: Collect 30 real post-July carrier invoices from sellers via forums and a small incentive. Re-derive the correct line count for each. If <15% of parcels show an overcharge, the premise is wrong and this becomes a pre-transaction advisory product instead.
- Assumption: National customs authorities will actually process small Art. 117 repayment claims without friction that eats the margin. How to test: File 10 real claims in NL, DE and IE. Measure approval rate and days-to-decision. If claims routinely take >6 months or get rejected on procedural grounds, pivot to carrier-escalation and prevention only, and drop the success-fee model.
- Assumption: Sellers will connect or forward carrier billing data to a new vendor. How to test: Put the free leak report live and measure how many forum-sourced visitors actually forward an invoice. Below ~15% and the wedge is too heavy — fall back to a manual-entry calculator as the top of funnel.
- Assumption: Small 3PLs will buy at the €249 tier rather than build it. How to test: 20 discovery calls. Ask directly what they currently tell merchants who complain about duty invoices.
Risk flags
- Sunset risk (the big one): The €3 flat rate is explicitly temporary and ends 1 July 2028, after which normal tariff rates apply. That is roughly a 22-month window for the core mechanic as written. Mitigation: the invoice-audit and classification muscle transfers to post-2028 ad-valorem duty verification, which is a harder and more valuable problem — but the product must be positioned to survive the transition, not built as a €3-only tool. Anyone building this should assume they are buying a customer base and an engine, not a permanent rule.
- Platform dependency (favourable direction, but real): If Shopify, Etsy, or the major carriers ship native line-level reconciliation and dispute handling, the audit half of this collapses. Shopify has already shipped collection; reconciliation is the obvious next step. Countervailing: Managed Markets’ geographic gating and 6.5% price leave the non-US and cost-sensitive segments unserved regardless.
- Carrier relationship risk: The product’s output is often “your carrier is filing your parcels expensively.” Carriers may resist, and some sellers will be reluctant to antagonise the carrier they depend on. The framing must be recovery-and-prevention, not litigation.
- Regulatory churn: This regime has already moved once (PID enforcement lands 1 Nov 2026) and implementation details across Member States are still settling — EAS Project notes the collection/remittance mechanism is “not yet fully resolved.” Expect the line-counting edge cases to shift under you for at least two more quarters.
- Claim-quality risk: A batch of sloppy repayment claims can sour a national authority on the filer. Quality gating is a product requirement, not a nicety.
14. Structured verdict
Score: 77/100
Verdict: GO
Confidence: Medium
Best-fit builder: Technical founder who can build invoice parsing + LLM classification,
paired with a customs broker / trade-compliance advisor
Time to revenue: 14–18 weeks to v1; first paid conversions within 2 weeks of launch
via the free leak report
Capital to launch: $15–25K (₹13–21L) — mostly advisor time, not infrastructure
Top 3 assumptions to validate first:
1. Over-splitting is common — re-derive line counts on 30 real post-July carrier
invoices; need >15% of parcels showing an overcharge
2. Art. 117 small claims actually clear — file 10 real claims in NL/DE/IE and
measure approval rate and days-to-decision
3. Sellers will forward billing data — ship the free leak report, measure
invoice-submission rate from forum traffic; need >15%
Kill criteria:
- Abandon if <15% of audited parcels show a recoverable overcharge
- Abandon if Art. 117 claims under €50 are routinely rejected or take >6 months
- Abandon if Shopify or the top-3 carriers ship native line-level reconciliation
with dispute handling before v1 launches
- Reassess hard in Q4 2027 against the 1 July 2028 sunset
15. Next step — 1-week validation sprint
- Day 1–2: Get real data. Post the EC’s H7-vs-H1 worked example (€3 vs €9 on the same parcel) to r/EtsySellers, r/shopify and the Etsy community EU-fees thread, and offer a free manual audit to anyone who forwards a post-July carrier invoice. Target 30 invoices. This doubles as the demand test — if nobody cares enough to forward an invoice, that is itself the answer.
- Day 3–4: Audit them by hand. For each parcel, classify the goods, determine the dataset used, re-derive the correct line count, and compute the overcharge. Produce the actual distribution: what % of parcels are overbilled, and by how much per parcel and per month per seller.
- Day 5: Call 10 of the sellers with their number. Ask one question: “Would you pay €99/month to have this run automatically and the claims filed for you?” In parallel, call 3 small 3PLs and ask what they currently tell merchants who complain about duty invoices.
Falsifiable outcome: Go only if ≥15% of audited parcels show a recoverable overcharge AND the median seller’s monthly leak exceeds €150 (i.e. comfortably more than the €99 tier) AND ≥4 of 10 sellers say yes to the price. Miss any of the three and this is at best a free lead-magnet calculator feeding a different product — which, per my own notes on advisory markets giving the diagnostic away, is a much worse business.
Interested in a detailed proposal?
Get a deep-dive with market research, competitive analysis, and implementation roadmap.
Contact usinfo@startupbasket.ai