IOSS Is Not Enough: How Germany and France Are Tightening VAT Enforcement on Low-Value Imports
IOSS Is Not Enough: How Germany and France Are Tightening VAT Enforcement on Low-Value Imports
FBA Prep Germany
We streamline your German Amazon operations by handling FBA prep, managing removal orders, and forwarding shipments to any German Fulfillment Center for FBA and Vendor accounts.
IOSS registration was designed to simplify VAT on low-value imports into the EU. For many non-EU sellers, getting an IOSS number felt like the final compliance step before shipping into Germany or France. It is not. Both countries are now applying closer scrutiny to low-value consignments, cross-referencing the IOSS number on the customs declaration against the marketplace VAT records on file and the declared shipment value. When those three data points do not align, the shipment does not simply pass through. It may be held, re-assessed, or subjected to additional VAT collection at the border. Sellers who have not audited their data flows before goods move are discovering this at the worst possible moment — after inventory is already in transit. This article explains what Germany and France are each enforcing, where the three-point mismatch risk sits, and what to check before your next inbound shipment crosses either border.
Why IOSS Alone No Longer Guarantees Smooth EU Entry
When the EU introduced IOSS in July 2021, the mechanism was straightforward: a seller or marketplace registers for IOSS, collects VAT at the point of sale on consignments valued at or below €150, and declares that IOSS number on each customs entry. Customs authorities in the member state of entry accept the number and release the goods without collecting VAT again at the border.
The problem is not the mechanism itself. The problem is data quality. Customs authorities in Germany and France are increasingly validating IOSS declarations against a wider set of data: the VAT identification number associated with the marketplace account, the declared customs value of the shipment, and the IOSS number itself. All three must be consistent and traceable back to the same transaction. A shipment where the declared value appears understated relative to the sale price, or where the IOSS number belongs to a different marketplace account than the one that processed the sale, creates a mismatch that automated customs systems can flag. Sellers relying on Amazon compliance prep Europe workflows that were set up in 2021 and never revisited may be operating on assumptions that no longer hold in either market.
What Must Be Confirmed Before Goods Move
Before a low-value consignment enters Germany or France, three data points must be consistent across every document in the chain: the customs declaration, the shipping invoice, and the marketplace transaction record.
The IOSS number on the customs entry must match the IOSS registration held by the marketplace or seller that collected VAT at checkout. The declared customs value must reflect the actual transaction price — not a reduced figure applied to lower duty exposure. The marketplace VAT identification number must correspond to the entity whose IOSS number is being used.
For sellers using Amazon's own IOSS number under the deemed supplier model, this means confirming that Amazon's IOSS reference is correctly populated in the carrier's customs data feed, not just printed on a label. Carriers and freight forwarders handling FBA prep in Germany or pre-Amazon storage buffers in France need to transmit this data electronically, not rely on paper documentation alone.
What Breaks When Responsibility Is Unclear
The most common failure point is not fraud — it is ambiguity about who owns each data field. A seller ships from a third-country warehouse. The freight forwarder populates the customs declaration. The carrier transmits the electronic data. The marketplace holds the IOSS number. If no single party has confirmed that all four data sources are aligned before the shipment moves, the mismatch is discovered at the border rather than at the desk.
In Germany, this can result in the shipment being held at the customs office pending clarification, with the importer of record — often the seller or their fiscal representative — required to provide supporting documentation. In France, additional VAT may be assessed directly on the consignment if the IOSS reference cannot be validated against the declared value. Neither outcome is recoverable quickly. Inventory stuck in customs clearance in either market creates stock availability gaps that affect Amazon FC forwarding timelines and seller performance metrics simultaneously.
Germany and France: Two Enforcement Approaches, One Shared Risk
Germany and France are both tightening IOSS validation, but their enforcement emphasis differs in ways that matter operationally.
Germany's customs authority, the Zollverwaltung, has been increasing automated cross-checks on low-value consignments, particularly those entering through major parcel hubs. The focus is on value consistency: whether the declared customs value matches the transaction value that would have generated the VAT collected under IOSS. Sellers who declare a lower customs value than the actual sale price — sometimes done to reduce the appearance of duty exposure on goods above certain thresholds — create a discrepancy that German customs systems are designed to detect. For marketplace sellers routing inventory through FBA prep services in Germany before onward delivery to Amazon fulfilment centres, this means the declared value on the inbound customs entry must match the commercial invoice value without adjustment.
France's customs authority, the DGDDI, has placed additional emphasis on the traceability of the IOSS number itself. French customs cross-references the IOSS number against the EU's central IOSS registry to confirm the number is valid, active, and associated with the correct marketplace or seller entity. A number that has lapsed, been reassigned, or was issued to a different legal entity than the one named on the shipping documentation will fail this check. Sellers using Amazon FC forwarding in France should confirm with their logistics provider that the IOSS reference being transmitted is current and matches the active marketplace registration — not a legacy number from a previous fiscal representative arrangement.
Both countries are also paying closer attention to consignment splitting: the practice of breaking a single order into multiple sub-€150 shipments to remain within the IOSS threshold. Where customs data suggests a pattern of artificial splitting, both Germany and France may treat the consignments as a single transaction for VAT assessment purposes.
Product Data Audit Checklist
- Declared customs value matches the actual transaction price recorded in the marketplace order
- HS code assigned to each product is consistent across the commercial invoice, customs declaration, and marketplace product listing
- Product description on the customs entry is specific enough to support the HS code — not a generic category label
- Country of origin is documented and matches the supplier certificate or production record
- Unit value per SKU is consistent across all shipment documents — no rounding or averaging that creates a discrepancy at line-item level
- Any bundled or multi-unit orders are declared as a single transaction value, not split into individual unit values that misrepresent the total
Shipment Value Audit Checklist
- Total shipment value on the customs declaration equals the sum of all line-item transaction values — no unexplained reductions
- Shipping and insurance costs are included in the customs value calculation where required under the applicable valuation method
- Discounts or promotional prices applied at checkout are documented and traceable — not applied silently to reduce the declared value
- For multi-item orders, each item's value is listed separately on the commercial invoice rather than grouped under a single line
- Currency conversion used for the customs value declaration is consistent with the exchange rate applied at the time of sale
- Any free gifts or promotional items included in the shipment are declared at their fair market value, not zero
IOSS Reference Audit Checklist
- IOSS number on the customs declaration matches the active registration held by the marketplace or seller entity that collected VAT at checkout
- IOSS number has been confirmed as valid and active in the EU IOSS registry — not expired or pending renewal
- The legal entity named on the IOSS registration matches the entity named as the seller or deemed supplier on the shipping documentation
- If using Amazon's IOSS number under the deemed supplier model, confirm the number is being transmitted electronically by the carrier — not only printed on the parcel label
- If a fiscal representative manages the IOSS registration, confirm the representative's details are current and the registration has not been transferred or lapsed
- IOSS number is applied consistently across all parcels in a batch — not missing from a subset of shipments due to a data feed error
Responsibility Owner Checklist
- Identify who populates each customs data field: seller, freight forwarder, carrier, or marketplace — and confirm each party has current instructions
- Confirm the importer of record for Germany-bound shipments is correctly identified and has a valid EORI registration
- Confirm the fiscal representative or customs agent for France-bound shipments has been briefed on current IOSS reference requirements
- Establish a single point of contact who can respond to a customs query within the hold window — typically 24 to 48 hours before reassessment is triggered
- Review carrier data transmission agreements to confirm IOSS and customs value fields are included in the electronic pre-notification sent to German and French customs
- Schedule a quarterly review of IOSS registration status, declared value consistency, and carrier data feed accuracy — not only when a shipment is held
Putting the Three-Point Check Into Your Pre-Shipment Workflow
The practical fix is not a compliance programme. It is a pre-shipment data check that runs before goods leave the origin warehouse — not after they arrive at a German parcel hub or a French customs office.
The check has three steps. First, pull the transaction value from the marketplace order record and confirm it matches the value that will appear on the customs declaration. If your carrier or freight forwarder is populating the customs value from a separate data source — a product master file, a price list, or a carrier integration — confirm those sources are synchronised with the actual sale price. Second, pull the IOSS number that will be transmitted on the customs entry and confirm it matches the active registration for the entity that collected VAT at checkout. If you are selling through Amazon and relying on Amazon's deemed supplier IOSS number, confirm with your carrier that the number is being transmitted in the electronic customs data feed, not only on the physical label. Third, confirm the marketplace VAT identification number associated with your seller account is consistent with the IOSS registration entity. A mismatch here — for example, if your VAT registration was updated after your IOSS number was issued — can cause a validation failure even when the IOSS number itself is correct.
For sellers using Amazon compliance prep Europe workflows that involve a third-party prep centre or forwarding agent before goods reach the Amazon FC, this three-point check should be built into the handoff protocol between the origin shipper and the prep or forwarding partner. The prep centre handling FBA inbound preparation in Germany or France is not responsible for customs data accuracy, but it is often the last point at which a data error can be caught before the shipment enters the customs system.
Germany: Value Consistency
German customs cross-checks the declared customs value against the transaction value implied by the IOSS VAT collected. A declared value that appears lower than the sale price is a primary trigger for additional scrutiny. Confirm your commercial invoice value and customs declaration value match before shipment.
France: IOSS Traceability
French customs validates the IOSS number against the EU central registry and checks the legal entity match. An expired number, a reassigned registration, or a mismatch between the seller entity and the IOSS holder will fail this check. Confirm your IOSS registration is active and correctly attributed before each shipment batch.
Both Markets: Consignment Splitting
Germany and France both monitor for patterns of artificial consignment splitting — breaking orders into multiple sub-€150 parcels to stay within the IOSS threshold. Where a pattern is detected, both authorities may treat the consignments as a single transaction. Review your order fulfilment logic if multi-parcel shipments are common.
What to Decide Before Your Next Inbound Shipment
The enforcement shift in Germany and France does not require a new compliance programme. It requires a data audit. Before your next batch of low-value consignments enters either market, three questions need a confirmed answer: Is the declared customs value consistent with the actual transaction price? Is the IOSS number on the customs entry current, valid, and attributed to the correct legal entity? Is the marketplace VAT identification number consistent with the IOSS registration?
If any of those answers is uncertain, the risk is not theoretical. A held shipment in Germany or an additional VAT assessment in France creates a delay that affects Amazon FC forwarding timelines, inventory availability, and seller account metrics in ways that are difficult to recover from quickly.
Sellers using a third-party prep centre or forwarding partner for FBA inbound preparation in Germany or France should also confirm that their logistics provider understands which data fields they are responsible for transmitting and which fields the seller or marketplace owns. The handoff between the origin shipper, the prep or forwarding partner, and the carrier is where data errors most often enter the chain — and where a pre-shipment check protocol has the most practical impact. Verify your legal and tax obligations with a qualified adviser. For the operational logistics layer — pre-Amazon storage, FBA prep services, and Amazon FC forwarding coordination — that is where FLEX. can support your inbound workflow.
If you are routing inventory into Germany or France and want to confirm your inbound data chain is consistent before the next shipment moves, FLEX. can support the operational layer: pre-Amazon storage, FBA prep services, and Amazon FC forwarding coordination across both markets. Verify your VAT and IOSS obligations separately with a qualified tax adviser. For the logistics and prep execution side, contact FLEX. to discuss your current inbound setup.
