You ship an order, the platform collects tax, and you assume the money side is settled. Then a customer gets hit with a fee at delivery, and suddenly landed cost vs marketplace tax collection stops sounding like back-office jargon and starts looking like a margin problem with your name on it.
That confusion sticks because both charges seem attached to the same box. They aren’t governed by the same moment, the same rules, or the same party. One charge lives at checkout, the other shows up when goods cross a border, and a platform can cover one while leaving the other fully exposed. If your pricing blurs that line, the bill doesn’t disappear. It just waits for the doorbell.
Charge ownership: Checkout tax vs border duties
An order lands on a Tuesday. You packaged it, priced it, and listed it on a platform that handles checkout. Three days later you get a message from a customer in another state asking why they owe customs fees they weren’t told about at purchase. You pull up the order and realize the confusion runs in both directions: you’re not sure who was supposed to collect the tax, and you have even less clarity on who owes the duty.
Those are two different problems, and conflating them is where indie shop owners tend to get hurt.
For US sales tax, the governing principle is delivery destination: tax is owed in the state where the customer takes possession of the goods, so a sale shipped to Maryland is a Maryland transaction. If you sell through a qualifying marketplace, the platform is legally required to collect and remit that tax on your behalf. In Maryland, Utah, Colorado, and every other state with marketplace facilitator laws, the platform’s payment discharges your obligation as the seller, meaning you don’t double-collect and the customer doesn’t get billed twice. Colorado’s rules make one exception worth keeping in mind: if a marketplace is relieved of liability because it acted on incorrect information you provided, that tax liability, along with penalties and interest, flows back to you. The platform’s coverage is real, but it’s conditional on the accuracy of the data you supply.
Import duty and VAT work on a completely different axis. These are border costs, not checkout costs, and no marketplace facilitator law transfers them. Under UK rules, the marketplace is liable for VAT on overseas goods valued at £135 or less sold into Great Britain. Above that threshold, normal import VAT and customs rules apply, and no platform absorbs those charges automatically. The buyer either discovers them at the door or, if you’ve shipped Delivered Duty Paid, you’ve already absorbed them yourself as part of the landed cost: the full price of moving a product from factory to customer, including transportation, customs duties, regulatory fees, and insurance.
The landed cost vs marketplace tax collection question, then, is really a question about where in the transaction each obligation attaches. Marketplace tax collection is a checkout mechanism. Import duties are a logistics mechanism. They share a customer and a parcel, but they answer to entirely different rules, and treating them as interchangeable is what leaves customers with unexpected bills and sellers holding liability they assumed someone else had covered.
Total cost of ownership: Audit fees hidden in freight
Landed cost is not a single charge. It is a stack of obligations that accumulates across every handoff between factory and doorstep, and the stack is easy to misread because its components are invoiced separately, often by different parties, and don’t always announce themselves as cost items at all.
The basic structure is easy to parse: the product price, freight, customs duties and taxes, and other required charges. DHL’s description of this model positions customs clearance charges not as a separate administrative cost but as part of the freight bucket, which is where audits often go wrong. A shipper who scrutinizes their duty rate but doesn’t decompose what the transport provider is actually billing will miss clearance fees folded into the freight line. That bundling is common, and it means the real landed cost can exceed the one your spreadsheet calculated before the shipment departed.
On the tax side, the structure shifts depending on where goods are going and what they’re worth. In the UK, the £135 threshold determines who holds VAT liability: below it, the marketplace is accountable at point of sale. Above it, import VAT and standard customs valuation rules apply, and the customs value itself must include transport, insurance, loading and handling, and certain surcharges like peak-season and port congestion fees when those are applicable. They are required inputs to the valuation. Discretionary add-ons are what they are excluded from, and skipping them makes your declared value incorrect.
For cross-border sales into the US, the picture is different but carries its own complexity. Every state that imposes a sales tax has now adopted some form of marketplace facilitator law, so platform-collected sales tax is fairly predictable territory. Import duties are not covered by those frameworks. US Customs and Border Protection also assesses user fees on imported goods, and those accumulate alongside standard duties, even when the duty rate itself is low.
The useful exercise is not to memorize rates but to audit your cost model against each layer independently:
- Verify that freight invoices are itemized enough to separate clearance and brokerage from transport charges.
- Confirm which surcharges, seasonal or otherwise, your carrier includes in the customs value.
- Check that regulatory fees specific to your product category are captured before you price.
- Identify whether your declared customs value excludes any delivery-related cost that the destination country’s rules require.
A Nebraska-based customer, for instance, triggers a state sales tax obligation once your platform crosses $100,000 in sales or 200 transactions into the state, and that part is handled. What is not handled by any platform is the duty, the user fee, and whatever your customs broker charged to move the parcel across the border. Those costs belong to the logistics mechanism, and they land wherever your pricing model left them.
Operational control: Domestic tax ends at the border
The two workflows govern entirely different categories of obligation, and treating them as interchangeable is what causes cross-border pricing to break down. Marketplace facilitator remittance is a domestic tax mechanism: the platform collects and transmits sales tax on your behalf once it crosses state-specific thresholds, and that structure is settled law following the Wayfair decision. What it covers stops cleanly at the border. Customs duties, import VAT, and brokerage fees are outside it by design.
Under DAP terms, the buyer absorbs that gap. Goods arrive ready for unloading, and the buyer handles import customs clearance and pays whatever duties and taxes apply at that point. The buyer also arranges unloading. From a seller’s operational standpoint, DAP is administratively simple: your liability ends at delivery to the agreed place. The buyer’s experience is a different matter, because a parcel that arrives with an unexpected customs invoice generates the kind of friction that doesn’t show up in your cart-abandonment rate until it’s already a pattern.
DDP shifts the whole import burden to you. Under DDP terms, you clear the goods for import, pay duties and customs costs, and bear the risk of getting everything to the destination fully cleared. The buyer receives a parcel with no outstanding charges. That cleaner experience has a specific cost attached to it: you become the importer of record, which means compliance responsibility and duty exposure both land on your books before you’ve collected a cent from the customer. For products where duty rates are variable or classification is contested, that’s not a theoretical risk.
The relationship between these two approaches and marketplace facilitator remittance is sequential rather than competitive. When a platform remits sales tax in Illinois or New York, it certifies to you that it has assumed the retailer’s rights and duties for those transactions. That certification covers the domestic tax side. The moment the same shipment crosses an international border, the Incoterm you chose at checkout determines who carries what from there. A DDP commitment made at checkout has to be funded by a landed cost calculation accurate enough to price the duty before the shipment moves, which is precisely the stack the previous cost model was built to capture.
The operational question, then, is whether your current pricing absorbs the DDP commitment reliably or transfers the gap to the buyer through DAP terms that look clean on your end and arrive messy on theirs.
Decision matrix: Where billing uncertainty lives—domestic or cross-border
The decision, stated plainly, is about where uncertainty lives in your operation and whether you can afford to put it there.
On the domestic side, the choice is largely made for you. Following Wayfair, 43 of 45 states with a statewide sales tax enacted remote seller obligations, and 38 of those built marketplace facilitator regimes that transfer the collection and remittance duty to the platform. When you sell through one of those platforms and it crosses the applicable thresholds, it handles the tax and confirms that it has assumed those obligations. Your compliance exposure for that transaction is real but managed: you still need to track whether marketplace-facilitated sales count toward your own economic nexus thresholds, because states differ on that point and the rules evolve. The platform’s remittance doesn’t seal the question entirely; it just moves the active obligation off your checkout.
Cross-border is where the decision actually requires judgment. If your international volume is concentrated in a handful of markets and your product classifications are stable, a DDP commitment backed by a precise landed cost calculation is sustainable. You price the duty in before the shipment moves, the customer takes delivery with nothing outstanding, and delivery-stage billing surprises disappear from that relationship. That calculation is precise enough for your top destinations, though not universally portable: VAT and GST rates shift, de minimis thresholds change, and a landed cost model calibrated for one country can produce margin erosion the moment a new destination enters your mix.
The hybrid position follows from that constraint directly. Marketplace facilitator remittance handles domestic tax collection automatically, which frees your attention. For cross-border shipments where your cost model is solid, DDP delivers the clean experience. For destinations where duty variability is too wide to price confidently, DAP keeps the obligation off your books while making the tradeoff visible to the buyer before checkout, not after delivery.
The channels you choose and the Incoterms you set are pricing decisions as much as they are logistics decisions. A seller who treats them as operational defaults rather than deliberate choices is effectively letting destination-country tax authorities and freight variables set the margin on every international order.
Final thoughts
The bill at the door is usually a pricing decision that was made earlier and hidden inside the wrong system. When checkout tax, duties, brokerage, and delivery terms get treated as one blended problem, your customer experience and your margin are both being set by whichever charge shows up last.
The useful split in landed cost vs marketplace tax collection is operational control. Marketplace rules can remove domestic tax collection from your checkout workload, but they can’t choose who absorbs cross-border uncertainty. That choice sits in your pricing model and your shipping terms. Put that choice in plain view, and the surprise charge becomes a deliberate policy instead of an expensive accident.
