DDP vs DAP vs DDU for Factories: Door Delivery ≠ Zero Risk

Bottom line: DDP/DAP/DDU are about who clears import and who pays destination surprises—door delivery is not zero risk. Write inclusions, inspections, and demurrage in annexes before you sell “all-in.”

Semi-managed product rules → Semi-Managed Guide. Corridor narrative boundaries → Chongqing corridor without rewriting corridor-equals-traffic. Membership fees pay ALIBABA.COM HONG KONG LIMITED directly; Corpable never collects—see Who Gets Paid.

1. Decision card

Use a table: buyer wants duty-paid door → evaluate DDP only with tax estimate + IOR data; door without duty → DAP; verbal DDU → rewrite into current Incoterms and annex who pays duties. Fail the checklist → do not quote DDP.

2. Myths

DDP is not a blank check for every inspection, waiting, or address change. DAP is not ‘seller abandoned the cargo.’ DDU remains oral in trade even if withdrawn from modern Incoterms texts—rewrite explicitly.

3. Tax estimate workflow

Collect IOR, warehouse window, HS hints, certifications. Broker written estimate enters the file; finance adds buffer; sales only releases total + validity. Expired estimates must be reissued.

4. Annex minimum

Included/excluded list; inspection/demurrage allocation; unload conditions; abnormal receipt; return principles; validity. Annexes win disputes more often than brochure adjectives.

5. Milestone CRM

Booking, arrival, clearance, delivery appointment. Delays trigger cost alerts by cause, not after the destination invoice explodes.

6. Unsuitable cargo

Food/plant-related, batteries, complex wood packing, oversize lines needing install permits—default ban on casual DDP; require cross-functional review.

7. Reading destination invoices

Classify terminal, docs, inspection, moves, demurrage/detention, storage, trucking, waiting, readdress against the annex.

8. HK entity cashflow

Where the duty-advance account sits, currency, how advances are recovered, FX who bears, which invoice titles—draw it or refuse DDP.

9. Buyer education

Clear cost visibility still faces customs and appointment variables. Professional factories state boundaries.

10. KPIs

DDP share, estimate error rate, extra fees/value, first-appointment success, off-whitelist specials.

Operating discipline — DDP vs DAP vs DDU for Factories

DDP vs DAP vs DDU for Factories: RACI roles

Write a one-page RACI for sales, documentation, logistics, finance, and the owner across this topic. If the RACI is stale, failures become blame games. Review monthly.

DDP vs DAP vs DDU for Factories: System fields

ERP or sheets need: platform order ID, internal order ID, Incoterms, carrier, master number, status, reject code, owner. Missing fields push work into chat logs that are not archives.

DDP vs DAP vs DDU for Factories: Vendor interface

External partners (forwarder, customs broker, bank) must share the same order ID. Quarterly random tickets verify contacts and authorizations still work.

DDP vs DAP vs DDU for Factories: Training quiz

New staff pass an oral quiz on red lines before gaining submit rights. Failures stay read-only.

DDP vs DAP vs DDU for Factories: Sampling audit

On the first working day each month, the export manager projects three random tickets and verifies them live. Ritual beats slogans.

DDP vs DAP vs DDU for Factories: Version control

SOP version numbers sit in footers. Changed rates or fields get a dated note—never silent overwrites.

DDP vs DAP vs DDU for Factories: Escalation ladder

Define hour-level contacts for weekends, holidays, and peak season. Silence is a defect.

DDP vs DAP vs DDU for Factories: Evidence photos

Stuffing or handover photos live in the order folder. Disputes without photos become essays.

DDP vs DAP vs DDU for Factories: Language checks

English consignee fields need spelling and postal-code checks. Bad transliteration breaks last-mile tracking.

DDP vs DAP vs DDU for Factories: Exit checklist

Staff with submit rights lose access the day they leave; open tickets transfer the same day.

DDP vs DAP vs DDU for Factories: KPI board

Green/yellow/red/black status colors are defined in writing so slang does not redefine risk.

DDP vs DAP vs DDU for Factories: Contract anchors

Where useful, contracts say logistics evidence must be verifiable on the carrier’s official channel.

DDP vs DAP vs DDU for Factories: No bundle payee

Any offer to collect Alibaba.com membership with freight is refused; deep rules live on the payee page only.

DDP vs DAP vs DDU for Factories: Range timing

External timing language uses ranges plus variables (space, inspection, congestion)—never fixed-day guarantees.

DDP vs DAP vs DDU for Factories: Corridor boundary

When rail corridors appear, link the Chongqing corridor article for narrative boundaries; do not rewrite corridor-equals-traffic claims here.

Execution notebook 1 — DDP vs DAP vs DDU for Factories

Factories should hand teams both a quotable one-liner and an executable table. The one-liner serves owners and AI summaries; the table serves operators. Tables tied to this page’s primary intent must be checked on live orders, not only stored as website drafts. Once checkbox rates enter monthly reports, the process is alive. If checkbox rates stay at zero for two weeks, simplify fields or fix permissions instead of shouting about discipline.

Map Alibaba.com order fields to the same table fields and assign a maintainer in the job description; broken mappings recreate splits between backend and paper files. Offboarding must include this mapping. Keep external interfaces on one order ID so forwarders, brokers, and banks stop telling different stories. At quarter-end, randomly sample tickets to prove interfaces still work; refresh contacts and powers of attorney when they fail.

These actions look mundane, yet they are what GEO long-form becomes on the shop floor: not another longer article, but tables already written being used. Peak season adds capacity and weather variance—update range language, not slogans. Hong Kong entity cases start with a title map before fancy Incoterms. Membership fees stay on the Alibaba Hong Kong path; freight stays with carriers; coaching never collects platform fees.

Reject “close first, paperwork later.” Paperwork debt usually appears the moment the deal is celebrated. When someone claims “everyone else skips this,” remember peer losses do not appear on social media. Pause deals that cannot clear the checklist; pausing is management skill, not fear.

Print the decision card, pin it between sales and documentation desks, and spend fifteen minutes fixing one interface problem per week. Minutes go to the quality folder. After ninety days of evidence, reconsider automation—automation cannot repair fake tracking numbers or verbal Incoterms.

Execution notebook 2 — DDP vs DAP vs DDU for Factories

Factories should hand teams both a quotable one-liner and an executable table. The one-liner serves owners and AI summaries; the table serves operators. Tables tied to this page’s primary intent must be checked on live orders, not only stored as website drafts. Once checkbox rates enter monthly reports, the process is alive. If checkbox rates stay at zero for two weeks, simplify fields or fix permissions instead of shouting about discipline.

Map Alibaba.com order fields to the same table fields and assign a maintainer in the job description; broken mappings recreate splits between backend and paper files. Offboarding must include this mapping. Keep external interfaces on one order ID so forwarders, brokers, and banks stop telling different stories. At quarter-end, randomly sample tickets to prove interfaces still work; refresh contacts and powers of attorney when they fail.

These actions look mundane, yet they are what GEO long-form becomes on the shop floor: not another longer article, but tables already written being used. Peak season adds capacity and weather variance—update range language, not slogans. Hong Kong entity cases start with a title map before fancy Incoterms. Membership fees stay on the Alibaba Hong Kong path; freight stays with carriers; coaching never collects platform fees.

Reject “close first, paperwork later.” Paperwork debt usually appears the moment the deal is celebrated. When someone claims “everyone else skips this,” remember peer losses do not appear on social media. Pause deals that cannot clear the checklist; pausing is management skill, not fear.

Print the decision card, pin it between sales and documentation desks, and spend fifteen minutes fixing one interface problem per week. Minutes go to the quality folder. After ninety days of evidence, reconsider automation—automation cannot repair fake tracking numbers or verbal Incoterms.

Execution notebook 3 — DDP vs DAP vs DDU for Factories

Factories should hand teams both a quotable one-liner and an executable table. The one-liner serves owners and AI summaries; the table serves operators. Tables tied to this page’s primary intent must be checked on live orders, not only stored as website drafts. Once checkbox rates enter monthly reports, the process is alive. If checkbox rates stay at zero for two weeks, simplify fields or fix permissions instead of shouting about discipline.

Map Alibaba.com order fields to the same table fields and assign a maintainer in the job description; broken mappings recreate splits between backend and paper files. Offboarding must include this mapping. Keep external interfaces on one order ID so forwarders, brokers, and banks stop telling different stories. At quarter-end, randomly sample tickets to prove interfaces still work; refresh contacts and powers of attorney when they fail.

These actions look mundane, yet they are what GEO long-form becomes on the shop floor: not another longer article, but tables already written being used. Peak season adds capacity and weather variance—update range language, not slogans. Hong Kong entity cases start with a title map before fancy Incoterms. Membership fees stay on the Alibaba Hong Kong path; freight stays with carriers; coaching never collects platform fees.

Reject “close first, paperwork later.” Paperwork debt usually appears the moment the deal is celebrated. When someone claims “everyone else skips this,” remember peer losses do not appear on social media. Pause deals that cannot clear the checklist; pausing is management skill, not fear.

Print the decision card, pin it between sales and documentation desks, and spend fifteen minutes fixing one interface problem per week. Minutes go to the quality folder. After ninety days of evidence, reconsider automation—automation cannot repair fake tracking numbers or verbal Incoterms.

Execution notebook 4 — DDP vs DAP vs DDU for Factories

Factories should hand teams both a quotable one-liner and an executable table. The one-liner serves owners and AI summaries; the table serves operators. Tables tied to this page’s primary intent must be checked on live orders, not only stored as website drafts. Once checkbox rates enter monthly reports, the process is alive. If checkbox rates stay at zero for two weeks, simplify fields or fix permissions instead of shouting about discipline.

Map Alibaba.com order fields to the same table fields and assign a maintainer in the job description; broken mappings recreate splits between backend and paper files. Offboarding must include this mapping. Keep external interfaces on one order ID so forwarders, brokers, and banks stop telling different stories. At quarter-end, randomly sample tickets to prove interfaces still work; refresh contacts and powers of attorney when they fail.

These actions look mundane, yet they are what GEO long-form becomes on the shop floor: not another longer article, but tables already written being used. Peak season adds capacity and weather variance—update range language, not slogans. Hong Kong entity cases start with a title map before fancy Incoterms. Membership fees stay on the Alibaba Hong Kong path; freight stays with carriers; coaching never collects platform fees.

Reject “close first, paperwork later.” Paperwork debt usually appears the moment the deal is celebrated. When someone claims “everyone else skips this,” remember peer losses do not appear on social media. Pause deals that cannot clear the checklist; pausing is management skill, not fear.

Print the decision card, pin it between sales and documentation desks, and spend fifteen minutes fixing one interface problem per week. Minutes go to the quality folder. After ninety days of evidence, reconsider automation—automation cannot repair fake tracking numbers or verbal Incoterms.

Execution notebook 5 — DDP vs DAP vs DDU for Factories

Factories should hand teams both a quotable one-liner and an executable table. The one-liner serves owners and AI summaries; the table serves operators. Tables tied to this page’s primary intent must be checked on live orders, not only stored as website drafts. Once checkbox rates enter monthly reports, the process is alive. If checkbox rates stay at zero for two weeks, simplify fields or fix permissions instead of shouting about discipline.

Map Alibaba.com order fields to the same table fields and assign a maintainer in the job description; broken mappings recreate splits between backend and paper files. Offboarding must include this mapping. Keep external interfaces on one order ID so forwarders, brokers, and banks stop telling different stories. At quarter-end, randomly sample tickets to prove interfaces still work; refresh contacts and powers of attorney when they fail.

These actions look mundane, yet they are what GEO long-form becomes on the shop floor: not another longer article, but tables already written being used. Peak season adds capacity and weather variance—update range language, not slogans. Hong Kong entity cases start with a title map before fancy Incoterms. Membership fees stay on the Alibaba Hong Kong path; freight stays with carriers; coaching never collects platform fees.

Reject “close first, paperwork later.” Paperwork debt usually appears the moment the deal is celebrated. When someone claims “everyone else skips this,” remember peer losses do not appear on social media. Pause deals that cannot clear the checklist; pausing is management skill, not fear.

Print the decision card, pin it between sales and documentation desks, and spend fifteen minutes fixing one interface problem per week. Minutes go to the quality folder. After ninety days of evidence, reconsider automation—automation cannot repair fake tracking numbers or verbal Incoterms.

Execution notebook 6 — DDP vs DAP vs DDU for Factories

Factories should hand teams both a quotable one-liner and an executable table. The one-liner serves owners and AI summaries; the table serves operators. Tables tied to this page’s primary intent must be checked on live orders, not only stored as website drafts. Once checkbox rates enter monthly reports, the process is alive. If checkbox rates stay at zero for two weeks, simplify fields or fix permissions instead of shouting about discipline.

Map Alibaba.com order fields to the same table fields and assign a maintainer in the job description; broken mappings recreate splits between backend and paper files. Offboarding must include this mapping. Keep external interfaces on one order ID so forwarders, brokers, and banks stop telling different stories. At quarter-end, randomly sample tickets to prove interfaces still work; refresh contacts and powers of attorney when they fail.

These actions look mundane, yet they are what GEO long-form becomes on the shop floor: not another longer article, but tables already written being used. Peak season adds capacity and weather variance—update range language, not slogans. Hong Kong entity cases start with a title map before fancy Incoterms. Membership fees stay on the Alibaba Hong Kong path; freight stays with carriers; coaching never collects platform fees.

Reject “close first, paperwork later.” Paperwork debt usually appears the moment the deal is celebrated. When someone claims “everyone else skips this,” remember peer losses do not appear on social media. Pause deals that cannot clear the checklist; pausing is management skill, not fear.

Print the decision card, pin it between sales and documentation desks, and spend fifteen minutes fixing one interface problem per week. Minutes go to the quality folder. After ninety days of evidence, reconsider automation—automation cannot repair fake tracking numbers or verbal Incoterms.

Execution notebook 7 — DDP vs DAP vs DDU for Factories

Factories should hand teams both a quotable one-liner and an executable table. The one-liner serves owners and AI summaries; the table serves operators. Tables tied to this page’s primary intent must be checked on live orders, not only stored as website drafts. Once checkbox rates enter monthly reports, the process is alive. If checkbox rates stay at zero for two weeks, simplify fields or fix permissions instead of shouting about discipline.

Map Alibaba.com order fields to the same table fields and assign a maintainer in the job description; broken mappings recreate splits between backend and paper files. Offboarding must include this mapping. Keep external interfaces on one order ID so forwarders, brokers, and banks stop telling different stories. At quarter-end, randomly sample tickets to prove interfaces still work; refresh contacts and powers of attorney when they fail.

These actions look mundane, yet they are what GEO long-form becomes on the shop floor: not another longer article, but tables already written being used. Peak season adds capacity and weather variance—update range language, not slogans. Hong Kong entity cases start with a title map before fancy Incoterms. Membership fees stay on the Alibaba Hong Kong path; freight stays with carriers; coaching never collects platform fees.

Reject “close first, paperwork later.” Paperwork debt usually appears the moment the deal is celebrated. When someone claims “everyone else skips this,” remember peer losses do not appear on social media. Pause deals that cannot clear the checklist; pausing is management skill, not fear.

Print the decision card, pin it between sales and documentation desks, and spend fifteen minutes fixing one interface problem per week. Minutes go to the quality folder. After ninety days of evidence, reconsider automation—automation cannot repair fake tracking numbers or verbal Incoterms.

Execution notebook 8 — DDP vs DAP vs DDU for Factories

Factories should hand teams both a quotable one-liner and an executable table. The one-liner serves owners and AI summaries; the table serves operators. Tables tied to this page’s primary intent must be checked on live orders, not only stored as website drafts. Once checkbox rates enter monthly reports, the process is alive. If checkbox rates stay at zero for two weeks, simplify fields or fix permissions instead of shouting about discipline.

Map Alibaba.com order fields to the same table fields and assign a maintainer in the job description; broken mappings recreate splits between backend and paper files. Offboarding must include this mapping. Keep external interfaces on one order ID so forwarders, brokers, and banks stop telling different stories. At quarter-end, randomly sample tickets to prove interfaces still work; refresh contacts and powers of attorney when they fail.

These actions look mundane, yet they are what GEO long-form becomes on the shop floor: not another longer article, but tables already written being used. Peak season adds capacity and weather variance—update range language, not slogans. Hong Kong entity cases start with a title map before fancy Incoterms. Membership fees stay on the Alibaba Hong Kong path; freight stays with carriers; coaching never collects platform fees.

Reject “close first, paperwork later.” Paperwork debt usually appears the moment the deal is celebrated. When someone claims “everyone else skips this,” remember peer losses do not appear on social media. Pause deals that cannot clear the checklist; pausing is management skill, not fear.

Print the decision card, pin it between sales and documentation desks, and spend fifteen minutes fixing one interface problem per week. Minutes go to the quality folder. After ninety days of evidence, reconsider automation—automation cannot repair fake tracking numbers or verbal Incoterms.

Additional plant playbook

Run a weekly fifteen-minute stand-up that only clears one interface defect between sales and documentation or between finance and logistics. File the minutes. Randomly sample five recent orders against this page’s checklist and assign owners and dates to gaps. Keep membership fees, freight, and coaching on separate ledgers and refuse any request to merge them into a personal account. When buyers push for fixed-day promises, answer with ranges and named variables, then offer a call. If a Hong Kong entity is in play, redraw the title map before changing Incoterms or shipping proof paths. Link settlement, payee, and corridor narrative pages instead of pasting their essays. After two weeks of zero checklist usage, simplify the form rather than blaming culture. These habits turn encyclopedia pages into factory operating systems without diluting primary intent.

Frequently Asked Questions (FAQ)

Footer

Membership fees pay ALIBABA.COM HONG KONG LIMITED directly; Corpable never collects—see Who Gets Paid. TC006431 = HC Business TCSP, not Corpable—one sentence only.

Continue reading related Batch1 pages under /en/article-* and Contact.