IOSS for POD Sellers: What Changes at Checkout?

What Changes at Checkout Under IOSS

IOSS is the Import One-Stop Shop, a scheme that lets a seller charge EU import VAT at checkout on consignments valued at or below 150 EUR. The buyer pays once, at the point of sale, and the parcel clears customs without a second bill at the door. For a POD seller the practical change is that the IOSS number has to be collected, stored, and transmitted to the carrier with the shipment data.

Without IOSS, the carrier collects VAT from the buyer on delivery and adds a handling charge. That is the moment a custom order turns into a refused parcel. The buyer already paid for the product and now faces an unexpected invoice, and on personalised goods there is no resale path for the returned item.

Why the 150 EUR Line Matters

The threshold applies to the intrinsic value of the goods in the consignment, not to the shipping charge. Above it, normal customs duty and import VAT procedures apply and IOSS does not simplify the declaration. That means a mixed cart can cross the line without the seller noticing, because the threshold applies per consignment once it is packed.

B2B buyers and gift orders interact with this differently. Where the seller cannot verify the buyer's VAT status, the safest operating assumption in many production scenarios is that the consignment is treated as a B2C sale and the IOSS rules apply.

The registration routes are described alongside the wider VAT position in our notes on VAT and IOSS for EU-bound POD orders, which covers where an intermediary can act on the seller's behalf.

What the Seller Has to Collect

Three data fields travel with every IOSS consignment: the IOSS registration number, the VAT rate applied to the order, and the amount of VAT charged. Miss any one and the carrier cannot clear the parcel under the scheme, so the buyer gets billed again and the seller absorbs the complaint.

That means the checkout has to compute VAT by destination country rather than applying one rate to the whole region. Rates differ between member states, and a single blended rate produces an under-collection that only appears when a tax authority reconciles the filings.

The registration itself is not the hard part. Keeping the number attached to the right order through production, packing, and handover to the carrier is where sellers lose it, because the IOSS number has to survive every system boundary in the chain.

Where It Breaks in a POD Workflow

The first failure point is the label. The carrier needs the IOSS number in the electronic data, and a manual packing step can drop it silently. Building the field into the label template removes the human decision.

The second is platform versus own store. A marketplace that collects VAT on your behalf will issue its own IOSS number, and using that number on a direct order creates a mismatch. The distinction between channels is worth settling before the peak season, and the recording requirements in Etsy Star Seller compliance are a useful reminder that platform obligations stack on top of tax ones.

The third is record retention. Transactions under the scheme need to be traceable for the period the tax authority requires, and rebuilding them from a carrier portal after the fact is far harder than exporting them monthly.

Related Obligations That Travel Together

The scheme handles tax, not product compliance. A garment sold into the EU still needs the right labelling and documentation, which is where GPSR compliance for print on demand sellers applies, and packaging obligations follow a parallel track under PPWR 2026 changes that hit POD sellers.

Where the seller also ships to the United Kingdom, the equivalent gateway is different again. The requirements in UKCA and UK compliance for custom apparel work alongside the EU regime rather than replacing it.

Shipping routes and carrier capability sit underneath all of this. Not every carrier accepts IOSS data on every lane, which is why the routing factors in our global POD shipping guide belong in the same planning session.

A Practical Sequence

Decide the registration route, then configure the checkout to compute destination VAT and store the collected amount against the order. Then make the IOSS number a required field in the shipping data and test one parcel per lane before a seasonal launch.

Write the refund and refusal policy at the same time. If a buyer refuses a parcel after paying VAT at checkout, the return path and who absorbs the cost should be documented before it happens, not decided during the first dispute.

Reconcile monthly. Exporting the IOSS transactions and checking the totals against platform payouts catches a misconfigured rate before a filing period closes.

Register, store the IOSS number against every order, and transmit it with the shipping data. That sequence keeps the buyer's single payment intact and keeps refusals rare. If you want a product line that stays comfortably under the 150 EUR threshold, browse our custom product catalogue and price the bundle deliberately.

Related Articles

De Minimis Changes and POD Duties in 2026

What Is Print on Demand? A 2026 Guide for Sellers

Custom Packaging That Survives Shipping