Most DDP problems start before the parcel reaches the border. When a shopper is charged duties at delivery, a shipment is held in customs, or the import bill does not match what was collected at checkout, the cause is almost always a break between product data, classification, the checkout calculation, fulfillment and the customs workflow. Find where the data changed, and you have found the problem.
This guide walks through the six most common DDP failures, how to diagnose each one and how to fix it, followed by a checklist you can run on any failed international order.
Start here: follow the order from checkout to delivery
A healthy DDP shipment follows one connected chain:
Product data → HS classification → landed cost calculation → customer payment → customs documentation → carrier handoff → customs clearance → duty and tax payment → delivery
If information changes, disappears or conflicts anywhere along that chain, the shipment can fail. The most common trouble spots fall into four areas:
- Duties and taxes: the customer is asked to pay at delivery.
- HS classification: the duty looks wrong or customs questions the product.
- Landed cost: the checkout amount differs from the customs assessment.
- Customs workflow: the shipment is held, delayed or needs documents.
1. The customer was charged duties at delivery
The symptom: your shopper paid what looked like a complete international price at checkout, but the carrier or customs is now asking for more duties, taxes or fees before delivery.
How to diagnose it:
- Check the terms of trade attached to the shipment. A checkout can calculate duties while the shipment itself is sent as DDU or another recipient paid arrangement.
- Compare what the customer paid at checkout with what customs or the carrier says is still owed.
- Check whether duties, taxes, shipping, brokerage or other import costs were left out.
- Confirm who was responsible for paying customs charges once the package entered the destination country. DDP decides who pays import charges and when. The importer of record is who is legally responsible for the import. They are related, but not the same.
How to fix it: use one connected DDP workflow that calculates duties and taxes before purchase, collects them from the shopper, passes the DDP designation into fulfillment and transportation, pays duties and taxes during clearance, and stops the carrier from billing the recipient. FlavorCloud calculates international shipping, duties and taxes at checkout and recalculates them when the cart or shipping service changes.
Key rule: collecting money at checkout does not make a shipment DDP. The payment and customs workflow after checkout must be set up as DDP too.
2. Duties look too high, too low or wrong
The symptom: two similar products get very different duty amounts, customs reassesses a shipment, margins disappear on certain international orders, or shoppers question a surprisingly high import charge. Start with the product classification.
How to diagnose it: review the HS code used for the affected SKU, then check the product data behind it:
- What exactly is the product?
- What is it made of?
- What is it used for?
- What is its declared value?
- What is its country of origin?
- Is the same classification applied across every destination?
A generic description such as "shirt," "beauty product" or "accessory" does not give a classification engine or customs enough to work with.
How to fix it: keep a clean product data record for every SKU you sell internationally, with enough detail to support a defensible HS code and customs declaration. Treat classification as part of the order workflow, not a spreadsheet task after the order ships. See Managing Your Customs Description and Product Classification.
Key rule: bad classification usually starts with bad product data.
3. Checkout landed cost does not match the final import cost
The symptom: your site shows the customer one total, but the amount needed to clear the shipment is different. Sometimes the gap is small. Sometimes it erases the profit on the order.
How to diagnose it: rebuild the original checkout and compare it with the shipment record.
| Checkout data | Shipment data |
|---|---|
| SKU and quantity | Final declared value |
| Product value and discount | Product description |
| Destination | Destination |
| Shipping service | Shipping service |
| HS classification | Classification |
| Country of origin | Origin and terms of trade |
If the two records differ, the landed cost calculation and the customs declaration can produce different results. This often happens when the checkout engine and the shipping workflow run separately.
How to fix it: use the same product and order data from checkout through customs, and make sure landed cost recalculates when the cart, quantity, discount, shipping service or destination changes. To check your current numbers, follow How to audit your true landed cost before checkout.
Key rule: the landed cost is only as reliable as the data that reaches customs.
4. The shipment is stuck in customs
The symptom: tracking stops with a message such as clearance delay, additional information required, importer information required, awaiting documentation or customs hold. It looks like a transportation problem, but it usually began before the parcel left the warehouse.
How to diagnose it: check these four things in order.
- Product data: is the description specific, and are classification, origin and value accurate?
- Documentation: are the customs records complete and consistent with the order?
- Importer structure: is there a valid importer of record arrangement for the shipment?
- Product compliance: does the destination require permits, registrations, certifications, testing or labeling? See Restricted and prohibited items.
How to fix it: move customs preparation upstream. Decide who the importer is, how the product is classified, which documents are needed, whether the product is admissible and who pays duties and taxes before the parcel ships. FlavorCloud handles brokerage, clearance, documentation, classification and landed cost in one workflow. Learn more about Automated Customs Clearance.
Key rule: design customs clearance before shipment, not after arrival.
5. DDP works in one country but fails in another
The symptom: your setup runs smoothly in several markets, then a new destination brings delays, wrong taxes, importer problems or regulatory issues.
How to diagnose it: a DDP setup that works in one country does not automatically work everywhere. Country rules can affect customs registration, importer requirements, VAT or GST, seller tax obligations, product admissibility, carrier availability, documentation, permits and certifications. Tax obligations can also exist separately from customs and importer of record responsibilities.
How to fix it: treat each new market as a compliance check. Before you turn on a destination, confirm:
- The product can be imported there.
- DDP is supported for the shipment.
- Who can act as importer of record.
- Which duties and taxes apply.
- Whether you have separate VAT, GST or sales tax obligations as the seller.
- Which product documents are required.
6. Everything works until the order reaches the warehouse
The symptom: checkout is correct, but problems appear after fulfillment starts. A common example is a well calculated DDP order that becomes a customs problem because the warehouse creates its own commercial invoice, edits a description, changes the declared value or ships on a different carrier service.
How to diagnose it: compare the original ecommerce order with the shipment the warehouse or 3PL created. Look for changes to terms of trade, product value, HS code, origin, description, shipping service, recipient details and importer details.
How to fix it: avoid manual re entry. Connect your ecommerce platform, warehouse or 3PL, cross border provider, customs workflow and carriers so the shipment inherits the same data used at checkout.
Key rule: never rebuild the international order from scratch at fulfillment.
The DDP troubleshooting checklist
When an international order fails, investigate in this order:
- Was the shipment actually sent DDP?
- Were duties and taxes calculated and collected at checkout?
- Did the SKU have accurate product data and a correct HS code?
- Did the landed cost inputs match the final shipment declaration?
- Did the same data flow from checkout into fulfillment?
- Were the customs documents complete?
- Was the importer of record structure valid for the destination?
- Were duties and taxes actually paid during clearance?
- Did the product need additional regulatory documents?
- Did a warehouse, 3PL, carrier or customs handoff change the data?
This sequence usually narrows the problem much faster than starting with the carrier tracking page.
FAQs
Why was my customer charged duties on a DDP order?
Usually because the shipment was transmitted as DDU or recipient paid, even though duties were collected at checkout, or because a cost such as brokerage was left out of the checkout total.
What causes most DDP customs holds?
Vague product descriptions, wrong or missing HS codes, incomplete documents, a missing importer of record, or a product that needs a permit or certification in the destination country.
How does FlavorCloud prevent DDP failures?
We connect landed cost at checkout with classification, customs documentation, brokerage, carrier routing and payment of import charges, so the amount your customer pays stays dependable through customs and delivery. Read How is DDP shipping priced? to see how guaranteed DDP works.
