Shipping-policy vendor lock-in becomes dangerous when the business cannot retrieve its approved policy versions, reproduce checkout promises, export order evidence, or operate delay and refund workflows outside one platform. Check data ownership, version history, configurable rules, exports, integrations, notice records, and a tested migration plan before treating a platform as replaceable.
Identify every policy dependency
Map the policy page, product and cart messages, checkout estimates, order confirmations, carrier services, fulfillment rules, delay notices, cancellation choices, refunds, and support scripts. For each component, record whether the business controls the wording and data or whether the platform generates it from hidden rules. A policy document is portable only if the promises customers actually saw can also be reconstructed.
Ask for exports that retain order time, the shipment representation shown at purchase, destination, item and fulfillment source, promised date or window, actual shipment event, notices, customer responses, cancellation, and refund evidence. A generic order CSV may omit the exact promise or notice history needed to explain an exception.
Treat compliance evidence as essential data
For covered U.S. sellers, the FTC explains that shipment claims need a reasonable basis and that delay, cancellation, consent, and refund duties may apply when an order cannot ship on time. The detailed FTC business guide also explains the value of accurate, current records. The prompt-delivery summary recommends retaining delay-notice content, timing, and customer response. Other laws and platform rules may apply, so this is an operational review rather than legal advice.
A platform is a high lock-in risk if notices can be sent but not exported, customer consent is stored only as an unreadable status, or refund timing cannot be reconstructed. Confirm that evidence remains available for the necessary retention period after cancellation and that the contract explains access, export timing, and deletion.
Check whether rules can move
Inventory zones, methods, rates, free-shipping thresholds, product restrictions, pickup options, processing times, preorder logic, split shipments, duties, and exceptions. Ask whether they can be exported in a documented format or must be rebuilt by hand. Record custom code, marketplace extensions, carrier accounts, labels, and warehouse mappings that belong to the business versus the vendor.
Watch for features that work only with a vendor-owned payment account, carrier account, domain, email identity, or fulfillment contract. A discount may be valuable, but the exit plan should state what changes, which promises must be updated, and how existing orders continue during migration.
Rehearse the exit
Export a representative set of policy versions, rule settings, and synthetic orders. Rebuild the core promises in a neutral test environment and compare product, cart, checkout, confirmation, delay, cancellation, and refund paths. Include an order already in progress so the team proves it can handle obligations created before the cutover.
Score each dependency by customer impact, evidence loss, time to rebuild, contractual restriction, and availability of a tested alternative. The goal is not to avoid platforms. It is to know whether changing one requires a controlled migration or leaves the business unable to support promises already made.
Sources
- Business Guide to the FTC's Mail, Internet, or Telephone Order Merchandise Rule — Federal Trade Commission
- Selling on the Internet: Prompt Delivery Rules — Federal Trade Commission