Skip to content
Ecomwith

Independent Store Shipping and Fulfillment: Rates, Delivery Times, and Tracking

  • Intermediate
  • 1-3 days

update: Added the conditional shipping-options-by-market path and clarified DDP/DAP, shipment versus delivery timing, and exception remedies.

Start with the promise on one order

Shipping settings decide which delivery choices appear at checkout. Fulfillment is the work behind them: who prepares and packs the order, where it leaves from, how it reaches the carrier, and who handles a problem. Check the page promise, actual dispatch, and exception response against the same order before choosing a worldwide rate.

The classroom product is a 20 oz tumbler with standard-lid and straw-lid SKUs. The plan is a US primary market, UK/EU tests, and remote addresses closed initially. Free shipping over USD 49, delivery 7–12 business days after carrier transfer, and full tracking are promises to verify. These are teaching values, not observed performance or evidence of entity, tax, or carrier eligibility.

If you already have a policy-consistency record, bring its delivery or duties statement, first mismatch, and pause action into this review. That record compares wording across pages, email, and support. Here you establish the matching checkout, warehouse/supplier, carrier, and exception evidence; you can start without having completed the earlier lesson. Have product and packed weights, a proposed origin, a carrier or supplier quote, a policy draft, and a support owner ready. You can work with a sanitized paper example before opening a store. Real orders, labels, notices, or refunds require separate operating authority; the local exercises perform none of those actions.

Use these six layers to find the weakest promise. Choose the layer most likely to fail, locate its evidence, and reconcile the remaining layers with the same order.

DDP generally assigns the agreed import charges to the seller; DAP generally leaves them payable by the buyer at destination. Before promising that no extra charge applies, check the destination and actual carrier terms. If they remain unclear, pause that claim and seek relevant carrier or tax/customs advice.

Exercise · pick one

Which promise needs attention?

Customer promise
Which countries/regions are open, which are blocked, and why.
Evidence to check
Shopify shipping zones, deliverable countries, excluded regions, and checkout test screenshots.
Failure signal
Global checkout is open, but some regions cannot ship or cost becomes uncontrolled.

The buyer’s shipping charge and the merchant’s carrier bill are different amounts. A low displayed rate can still lead to an unexpected checkout total or an empty tracking page after payment. Review that customer friction alongside support work and exception costs.

LayerQuestion to answerHow to use the result
Fulfillment modelWho ships, from where, which SKUs, cash needs, and upgrade triggerChoose for the first batch you can actually support.
Delivery promiseHandling, transit, rates, tracking, and dutiesAlign product page, policy, checkout, and email.
Exception responseEvidence, responsibility, first reply, and refund/reship authorityGive support a repeatable escalation and review path.

Choose fulfillment for the first batch

Self-fulfillment puts picking, packing, and carrier transfer with your team. In dropshipping, the supplier ships to the customer. A 3PL is a third-party logistics provider that may store inventory and perform warehouse work. An overseas warehouse describes a location, not a complete returns, support, or duties service. Hybrid fulfillment uses different routes by SKU or market, so the customer promise needs the same distinctions.

Exercise · pick one

Who fulfills the current order?

When it fits
Useful while testing products with limited inventory and unsettled order volume.
Main risk
Timing instability, weaker tracking, and more exception communication.
Acceptance check
Page promise is conservative, and supplier can provide tracking, exception handling, and reship rules.

Compare the work for the actual first batch before planning a scaled operation. The three timelines below separate preparation, transfer, first scan, and arrival. Every date is an illustrative plan to recheck against the service, business calendar, cut-off, holidays, product, and destination.

Exercise · pick one

First-order timeline and promise wording

When it fits
Fits a validated primary market and core SKU when the store wants a 7-12 business day promise for the US or UK.
Day 0 order placed
With the integration configured, check that the order enters the 3PL queue; verify SKU, inventory location, address, and cut-off time. Evidence: Order-routing screenshot, 3PL dashboard intake status, and inventory deduction record.
Day 0-1 pick and pack
Warehouse picks, packs, creates the label, and writes fulfillment status back to Shopify. Evidence: Pick/pack slip, label, carrier service, and Shopify fulfillment timestamp.
Day 1-2 first scan
Reconcile the first scan with the actual tracking-email trigger, and monitor no-first-scan exceptions after 24 hours. Evidence: Tracking page, order email, and exception-alert threshold.
Day 7-12 delivery
Check delivery, delay, damage, and refusal status, then write first-order result back into the fulfillment matrix. Evidence: Delivery screenshot, support messages, and exception review.
Classroom promise example
Classroom wording: core SKUs usually process within 1 business day, with US delivery 7-12 business days after carrier transfer; remote regions are noted separately.
Support risk
Wrong inventory sync, unclear cut-off time, or delayed 3PL status updates turn fast delivery into support pressure.
When to use it
Use it when core SKU demand is stable, stock turn is acceptable, and return/reship rules are defined.

A move from dropshipping to self-fulfillment or a 3PL may make sense when core SKUs stabilize, speed becomes a main complaint, reship and support costs rise, or the brand serves a clearer market. Include inventory cash, materials, labor, storage, and exit costs. There is no universal order-volume threshold here.

Use these five checks when requesting a 3PL quote and evidence sample. An SLA is the agreed timing for a named action such as intake, handling, response, or escalation. Define the action and clock before relying on the acronym.

CheckWhy it mattersEvidence to request
Match zones and costs firstA 3PL quote is not one average number. Primary markets, remote zones, heavy parcels, and return fees need to match the Shopify rate setup first.Keep the rate card, representative checkout screenshots, remote-zone test order, and margin sheet.
Cut-off and status sync must be stableIf cut-off time, stock deduction, label creation, and Shopify fulfillment sync are unstable, a fast-delivery promise quickly becomes support pressure.Keep the 3PL dashboard, Shopify fulfillment timestamp, label, first-scan time, and exception-alert threshold.
Tracking needs first scan and exception rulesTracking does not end at sending a number. Buyers and support need parcel status, first-scan timing, no-update threshold, and the next review time.Keep shipment notice, tracking page, carrier record, no-first-scan ticket, and first-reply support template.
Explain DDP / DAP cost responsibilityReconcile DDP or DAP responsibility with the actual carrier contract, destination, and checkout setup; also check label support and whether brokerage fees are included.Keep checkout duty notice, Shipping Policy, support script, label service, and refusal-handling rule.
Returns and reships cannot be improvisedA 3PL can ship fast without handling exceptions fast. Damage, refusal, address error, return, and reship rules need a responsibility boundary before launch.Keep return address, reship authorization, claim evidence, support escalation line, and cost ceiling.

Receiving a Shopify order does not establish every SKU, parcel, duties, or return path. Ask the provider to demonstrate status updates and first-scan evidence for the same order number, then reconcile the customer notice.

Reconcile rates, checkout, and delivery wording

Separate core, test, and closed markets before choosing free shipping, a flat rate, or zone rates. Carrier/app-calculated rates depend on the plan, provider, location, and setup. A rate appearing at checkout establishes a quote for those inputs, not a delivered shipment.

Exercise · pick one

Choose a rate model and check its costs

What the buyer sees
The buyer sees “free shipping over $X,” not your real logistics cost. Check the threshold against product margin, packaging, payment fees, and actual shipping cost.
Cost that can be missed
A low threshold can consume small-order margin, while a high one can make the extra spend unattractive. Remote-region free shipping can hide loss.
Setup action
Test 3-5 representative orders in primary markets: AOV, product margin, average parcel weight, average shipping cost, and remote-region ceiling.
Evidence to retain
Keep checkout screenshots, shipping profile, margin sheet, and the note for countries/regions excluded from free shipping.

USD 6.99 flat shipping and free shipping over USD 49 are classroom examples. Test low, common, and high-cost orders. For a threshold, inspect 3–5 representative orders for basket value, margin, weight, average shipping, and remote-area ceiling. Include add-ons, bundles, split locations, and both sides of the threshold so a larger cart does not hide a larger loss.

Shopify is gradually moving shipping to market-based Shipping options. First open Settings > Shipping and delivery. A page showing profiles, zones, and rates identifies the existing system; market-organized options identify the upgraded path managed in Markets. Access remains conditional, so another store’s screen does not establish your store’s system.

Under profiles, rates from different profiles or location groups can combine, while a flat rate within one location group can be charged once. In the upgraded system, flat and order-amount rates use the highest matching rate within an option; weight-, carrier-, and app-calculated rates can still be calculated per shipment and added. Recheck the actual cart at checkout rather than applying one formula to every split order.

Use US, UK, German, and deliberately blocked remote addresses as four address cases, recording the cart, quantity, currency, and time. Retain the rate name, shipping charge, duties wording, estimated date, final total, and whether a blocked address is actually unavailable. Repeat with both lid SKUs, changed weights, and different inventory locations, explaining each difference. A real test order is a separate authorized operation.

Admin path (English)Evidence for the same orderCommon failure
MarketsEnabled regions, product scope, and currencyAn enabled market is mistaken for delivery to every address.
Settings > Shipping and delivery > Shipping profiles; after upgrade, Markets > the market’s Shipping optionsProducts, locations, zones, price/weight conditions, rate name, and checkout totalOne item has a rate but the mixed cart has none or costs more.
Settings > Locations; Orders > target order > TimelineInventory location, routing, warehouse intake, handling, and carrier-transfer timesRouting chooses a location that cannot fulfill.
Orders > target order > Fulfillment; carrier tracking pageEach parcel’s status, label, actual transfer, first scan, and noticeA created label or fulfilled status is read as carrier possession.
Settings > Policies; order timeline and support inboxShipping/Returns, duties, returns, refund/reship authority, first reply, and recheckPages, emails, and support give conflicting promises.

Give another person the path, inputs, and observed state so they can repeat the check. These are reading paths, not authority to change an admin. Names can vary with the system and permissions.

Handling covers preparation after payment/intake; transit starts after carrier transfer. State business days, cut-off, timezone, preorder, holiday, and SKU exceptions. The examples below show how to make wording testable; their numbers still need your evidence.

TopicVague wordingTestable classroom wording
Handling timeDelivered in 7-15 days.Orders are processed within 1-3 business days after payment; pre-orders and holidays are explained separately.
Transit timeOne global 7-15 day range.US 7-12 business days, UK/EU 8-15 business days, remote regions may take longer.
Tracking updateTracking is provided after shipment.Tracking updates within 24-72 hours after shipment; it can be blank before carrier scan.
Duties responsibilityDuties may apply.State the actual DDP or DAP terms, who is charged, and the responsibility and process after refusal; check applicable rights and the carrier contract first.

Delivery-date features also depend on plan, location, fulfillment history, and configuration. Manual dates need handling time and a rate with transit time; automated dates have eligibility conditions. A displayed date, first scan, and actual arrival require different evidence. Older material used DDU; this lesson checks the current DDP/DAP terms without rewriting a carrier contract.

DDP generally assigns the agreed import charges to the seller; DAP generally leaves import charges payable by the buyer at destination. Collecting an estimate at checkout does not establish label support, clearance, or coverage of every brokerage fee. Reconcile destination, HS classification, origin, carrier terms, and bills. If unresolved, pause any no-extra-charge claim and get the relevant carrier or tax/customs advice.

Calculate costs and coverage for the same order

Choose one order instead of combining the cheapest worldwide rate, fastest route, and average margin. Single-location, split, preorder/custom, and remote cross-border orders need different evidence. Select a route, then record its market, SKU, currency, actual locations, and clock.

Exercise · pick one

Select the representative-order route

Buyer expectation
The buyer sees one product, one address, and one delivery promise. Even a simple route must separate handling, actual dispatch, first scan, and arrival.
Actual route
Record actual origin, inventory state, cut-off, pick and pack, label creation, carrier transfer, and first scan. Label creation is not proof of carrier transfer.
Cost focus
Use one representative order to put product, packing and pick-pack, carrier, and exception reserve into a same-currency record.
Scan evidence
Order timeline, inventory location, pick-pack record, label, carrier first scan, and shipment-notice time.
Exception branch
When a first scan is missing, check warehouse dispatch proof and notification trigger before choosing a recheck time, carrier escalation, or a pause on fast-shipping claims.
Pause boundary
When the label and first scan cannot yet be reconciled for one order, do not promote a faster timeframe in new ads or the homepage.

Include the currency in “Market, representative address, and SKU” so all seven inputs and both outputs use that currency. Product revenue and buyer-paid shipping are the inflows. Product, packing/pick-pack, carrier, duty/brokerage reserve, and exception reserve are the five costs. The arithmetic uses one currency without conversion.

Calculator · change the numbers

Five costs and coverage before ads

Try changing these numbers.

Product revenue in this representative order, excluding ads, fixed costs, and other orders.

Enter the shipping amount actually charged at checkout for this buyer; use 0 for free shipping.

Use the currently checkable cost for this SKU. Do not treat a vague average purchase price as an exact fact.

Include known per-order packaging, labor, or 3PL pick-pack cost.

Use a quote or real bill for this address, parcel, or route, not the store’s lowest shipping rate.

Record only when this route might actually leave it with the merchant. This is not a tax or customs conclusion.

Record the per-order reserve for delay, refusal, return, or reship. It is not a guarantee of future cost.

Five-cost total (same currency)

—

Needs a valid Product or production cost, Packing and pick-pack cost, Actual carrier cost, Duty or brokerage reserve, Exception or reship reserve first

Adds product, packing/pick-pack, carrier, duty/brokerage reserve, and exception reserve.

Coverage before ads (can be negative)

—

Needs a valid Item selling price, Buyer-paid shipping, Product or production cost, Packing and pick-pack cost, Actual carrier cost, Duty or brokerage reserve, Exception or reship reserve first

Product revenue + buyer-paid shipping − five-cost total. Ads, payment fees, overhead, and other omitted costs remain; this is not net profit.

Enter 4, 5, 6, 7, 3, 4, 5 in input order. The five costs total 25.00 and coverage is −16.00: revenue and buyer-paid shipping fail to cover even these costs. Change product revenue to 60, leaving the rest unchanged, and coverage becomes 40.00, still before omitted expenses. Keep the negative value in the record rather than flooring it for a margin chart.

Complete each amount before interpreting a result. A blank stays unknown; enter 0 deliberately for a cost that is genuinely absent. The former calculator treated blank or invalid input as zero. This version preserves the missing-evidence state instead of letting an omitted cost improve coverage. Outputs display two decimals, with nonnegative inputs up to 1,000,000,000,000; costs beyond that range need separate calculation. This exercise is not an accounting ledger.

The evidence groups, amounts, later selections, and work-note groups save, restore, and clear separately. Check the group before saving, then refresh to verify it. Each long-text field holds up to 2000 characters; the former fields were unbounded. Keep longer originals separately rather than treating a short successful import as proof for arbitrary lengths.

Turn each promise into an operating rule

The worksheet turns a promotional line into questions the team can answer. Record the promise, buyer question, cost, exceptions, and publishing condition for each layer. For PO boxes, islands, military addresses, oversized/fragile products, backorders, preorders, fraud holds, or supplier failure, state support, review ownership, and notification. A footer exception alone is insufficient operating guidance.

Exercise · pick one

Build the promise one layer at a time

Promise field
State when the order leaves after payment, the cut-off time, weekend/holiday handling, and whether preorder or custom items use a separate clock.
Buyer question
If I order today, when does it actually leave the warehouse?
Cost check
Check manual labor, packaging, 3PL pick-pack fees, and rush processing against margin.
Exception rule
Stockout, preorder, custom, weekend, and holiday orders need separate language instead of one dispatch promise.
Before publishing
Only promise same-day or next-day dispatch when stock, cut-off, warehouse log, and order notice can prove it.
Key guidance
Split processing into payment, cut-off, dispatch, and exceptions instead of saying only "fast shipping."

Reconcile all six layers across product delivery text, Shipping/Returns, FAQ, checkout wording, order email, and support templates. If one surface promises free returns while another assigns cross-border postage to the buyer, resolve both the wording and the operating capacity first.

Repair the promise and handle the exception

First separate a bad promise, a configuration error, and a fulfillment failure. These repair cases cover surprise duties, remote-area losses, tracking gaps, and mixed-SKU conflicts. A core SKU might use a 3–5 day example while a long-tail SKU uses 10–18 days; the homepage cannot safely collapse them into one unverified fast-delivery claim.

Exercise · pick one

Choose the closest problem

Signal
A Canada or EU buyer receives an import duty or clearance-fee notice and says checkout and the Shipping Policy were unclear.
Tempting shortcut
Have support explain that international orders may have duties, while leaving page copy, checkout messaging, and fulfillment method unchanged.
Repair first
First decide whether the promise is DDP, DAP, or unpaid duties; if duties are collected, confirm DDP-capable labels and carriers are actually used.
First evidence
Save checkout duties message, Shipping Policy, order label, carrier service, support record, and a test-order screenshot for that market.
Places to update
Update Shipping Policy, FAQ, product-page shipping note, checkout-adjacent message, and support template together.
What to pause
Until duties language is consistent, do not run “no extra fees” or “fast customs” claims for that market.

Determine applicable rights, the actual cause, and the promise already made before allocating refund, reship, refusal, or return costs. Within its scope, the US FTC merchandise-order rule requires a reasonable basis for the promised shipment time. Shipment means physical transfer to the carrier, distinct from arrival. A missed shipping deadline brings requirements for delay consent or cancellation and refund. Internal review dates, policy, and margin cannot replace those duties; confirm the rules applicable to UK, EU, or other destinations separately.

Exercise · pick one

Choose the exception and first action

First check
Check carrier scans, customs, holidays, remote region, and supplier dispatch time.
Action
Give the known status and next check time. Escalate or offer a remedy according to the evidence, promise, and applicable rights; a known loss need not wait for an internal threshold.
Support wording
Do not say wait longer; tell the buyer where it is stuck and when the next update happens.

Reverse logistics is the route back to the merchant, supplier, or return location. Separate refusal, uncollected or undeliverable parcels, address errors, cancellation, defects, and ordinary returns. Establish address changes before dispatch, possible interception afterwards, inspection and remedies after return, and any local return address. Support needs executable rules and an owner instead of a fresh negotiation for each order.

Exercise · pick one

Bring exception costs into the rule

Trigger
The parcel exceeds the promised window, tracking stalls, and the customer asks for an update.
Cost and responsibility
Check whether the promise was too aggressive, carrier responsibility, and whether coupon, reship, or refund is needed. Do not let support invent a new date.
Support boundary
Support can state known status, next update time, and available options, not an unconfirmed carrier ETA.
Update the public promise
If the route repeatedly delays, make product/policy timing more conservative and pause fast-delivery claims in ads.

A voucher, partial refund, or exchange may be an appropriate additional option, but cannot replace a required refund or other mandatory remedy. Carrier claims, insurance, supplier recovery, and the buyer’s resolution are related jobs with different owners. An unsettled internal bill is not a reason for open-ended customer waiting.

Review a delayed order at seven checkpoints

The example remains a 20oz tumbler with a 7–12 business day delivery window. Day labels are exercise checkpoints, not universal legal deadlines. At Day 0, check the order and record payment, handling completion, and actual transfer separately. For “X handling days plus 7–12 business days after transfer,” calculate the deadline from the agreed start. The Day 12 checkpoint addresses a window that has reached its end; it is not automatically the twelfth day after payment.

Exercise · pick one

Choose a review checkpoint

What is happening
A buyer orders a 20oz tumbler and sees a 7-12 business day delivery promise. The order confirmation email should repeat the same handling time, transit window, and tracking note.
First check
Check order value, SKU, shipping address, rate name, preorder status, remote-region status, and whether the order entered the right fulfillment location.
Customer wording
Your order is confirmed. The current promise is X business days for processing and 7-12 business days after shipment; tracking updates after the first carrier scan.
Refund and reship decision
Align the page promise, order email, and actual route while handling any cancellation or refund request already raised. The internal timeline does not suspend applicable rights.
Key guidance
Day 0 confirms where the 7-12 day promise starts.

A 72-hour first-scan gap, a 24–48 hour recheck, and two delayed batches are internal escalation examples. Act promptly on known loss, inability to ship, or an earlier applicable deadline. Each reply should state the known status, party contacted, next update, and actionable options; feed repeated problems back into the promise and cost sheet.

Test the promise against operating failures

The Fulfillment Promise Checker is a local judgment exercise linking a failure, its cost, and customer wording. It does not query a warehouse, carrier, or customer order. After choosing a case, fill in the conclusion, the timeline and the notification evidence below, and put the evidence location and owner on the same line.

Exercise · pick one

Choose a promise stress test

Trigger
The 3PL has received the order, but pick-pack or carrier first scan is 24-48 hours behind the promise. Buyers see delay; the team sees warehouse SLA, cut-off time, and status sync not aligned.
Check
Check when the order entered the 3PL, warehouse intake status, cut-off time, label creation, carrier first scan, and Shopify fulfillment sync. Do not start by rewriting support copy.
Evidence to check
3PL SLA, order timeline, warehouse dashboard, label, carrier tracking, and shipment-email timestamp.
Customer wording
Tell the buyer the parcel is in warehouse processing, the next check time, and what happens after the internal threshold: reship, refund, or escalation.
Pause boundary
If two batches exceed the promise window, stop claiming same-day or next-day shipping in ads, product pages, and checkout-adjacent copy.
Key guidance
For 3PL delay, check warehouse SLA, cut-off, and first-scan evidence before deciding whether to pause the fast-shipping promise.

When a 3PL is 24–48 hours behind, reconcile intake, dispatch, physical transfer, and first scan before support supplies another date. Two batches outside the agreed window can trigger a review of fast-delivery claims; a serious evidenced failure can require action immediately. Define first reply, recheck, escalation, and authority in the support SLA instead of “as soon as possible.”

Separate tracking practice from your six evidence gates

Order confirmation, shipment notice, status sync, exception alert, and support access are five different jobs. The 2/5 classroom example below marks confirmation and shipment notice checked, with three rows pending. Toggle rows to see the count change. These sample ticks establish no real-order evidence and do not complete the six strict gates below. Clearing this practice group restores the 2/5 sample; clearing the strict-gate record leaves it empty.

Current tracking-practice count

Note2/5 classroom tracking rows marked checked
This count describes only these five choices. For a real order, retain separate evidence and times and complete the independent gates below.

Your strict record starts empty. Fix one order, then establish routing sources, checkout readback, the scan gap, exception handling, and the promise to pause. Reading a scenario or toggling a sample is not evidence for a tick.

Checklist0 / 6 required
Your six fulfillment-evidence gates
  • The calculator compares visible cost for this one order. Do not blend different markets or currencies into one average.
  • Confirm where the order actually fulfills before discussing timing, cost, or public promises.
  • Keep same-path evidence for product, market, shipping, duty signal, estimated timing, and final total.
  • Do not automatically treat label creation or admin fulfillment status as carrier acceptance.
  • One generic timeframe cannot cover multiple parcels, production waits, remote surcharges, or refusal handling.
  • Narrow to markets, SKUs, and routes with evidence first, then decide whether to expand.

Strict-record status

Hold

Evidence still missing

Return to unticked tasks and record repeatable evidence, an owner, and review time.
Decision · 1 question0/1 answered

Choose the next action

A rate is available, but dispatch, first scan, and exception costs remain unverified. What comes next?

Self-check not answered

Judgment for the selected answer

NoteNo answer yet
Choose an action, then use its feedback in the record.
Decision · 1 question0/1 answered

Check the worldwide promise

You want to write global 7-15 day delivery, but US, EU, and remote regions differ in cost, customs, and tracking. What should happen first?

Self-check not answered

Judgment for the selected answer

NoteNo answer yet
Choose an action, then use its feedback in the record.

Review in order and keep the handoff

Return from the representative order to the admin, carrier, and public pages. These eight steps connect market, fulfillment, checkout, and exception checks; any account actions belong to a separately authorized operator. Remove unnecessary personal data from the evidence pack. Keep only necessary sanitized references and results in your records, leaving out customer names, full addresses, order numbers, payment data, account credentials, full carrier contracts, and restricted-product records.

From market to a reviewable promise

  1. Lock primary and blocked markets

    Write open countries, blocked countries, and the reason. Do not assume global shipping. Use shipping zones, target addresses, checkout screenshots, and blocked-region notes to prove the market can order, ship, and be explained.
  2. Choose the real fulfillment model

    Run the 3PL, self-fulfillment, or dropshipping first-order timeline. For 3PL, also run the minimum evaluation checklist for zone costs, cut-off, inventory sync, tracking first scan, DDP/DAP duty language, returns, and reships. Choose the model your current order volume, inventory, cashflow, first-scan evidence, returns, and exception handling can actually support.
  3. Test rates, weight, addresses, and margin

    Use 3-5 representative orders to test free shipping, flat rates, zone rates, or real-time rates. Record rate name, country/region, weight, packaging, carrier quote, checkout cost, and margin impact.
  4. Use the Shipping Promise Repair practice to decide what to fix first

    For duties surprise, remote-zone free-shipping loss, no tracking, and hybrid SKU timing conflict, write the wrong move, safer repair, first evidence, update targets, and pause line.
  5. Use the Fulfillment Promise Worksheet to lock the shipping promise

    Define processing time, shipping rate/free-shipping threshold, delivery window, tracking notice, returns/reshipment, and fulfillment exceptions. Each item needs the promise field, buyer question, cost check, exception rule, and acceptance line.
  6. Use the 7-12 day exception timeline to handle delays

    Use Day 0, Day 2, Day 5, Day 8, Day 12, Day 15, and Day 20 to check the order, first scan, tracking, support reply, refund/reship decision, and public-promise correction.
  7. Use the Fulfillment Promise Checker to decide whether the promise can stay public

    Check 3PL delay, free-shipping threshold, tracking gap, DDP/DAP duty dispute, refund/reship boundary, and support SLA. For each scenario, write trigger, first check, evidence, customer line, and pause line.
  8. Leave a reviewable shipping promise record

    Record primary markets, rate name, handling/transit window, DDP/DAP or duties language, tracking first-scan threshold, exception review time, refund/reship boundary, official review date, review lead, and Store Launch Readiness Scanner input.

Use the Day checkpoints with the clock established above and handle delay/refunds under applicable rights. Scanner input in the final step means only its supported URLs, platform/stage, and confirmations. Keep shipping screenshots, order/parcel evidence, duties records, and support threads in a separate manual pack, then reconcile the scan result. The tool cannot confirm physical transfer or determine duties responsibility for you.

Record the date you actually read an official source rather than reusing a date from an older article. These four source groups answer different questions. Assign unresolved carrier, customs/tax, or consumer-rights questions to the appropriate owner.

Source groupScopeUse in this lesson
Shopify order routing documentationUse it to understand how current orders are prioritized across locations, including default rules for minimizing splits, destination market, and closest location.Bring actual routing and possible splits back to the representative order. Do not assume one warehouse or tracking link is the real path for every order.
Shopify shipping profiles documentationUse it to check shipping-profile, zone, and rate setup for particular products and locations.Compare checkout display with real route, SKU, and location. Do not treat one general rate as evidence for every product and location.
Shopify delivery-date documentationUse it to check how fulfillment time affects checkout dates and visible experience. Eligibility, location, plan, and history can change what is shown.Record admin configuration separately from real handling, dispatch, and first-scan evidence. Do not treat an estimated date as proof of fulfillment.
Shopify duties and import taxes documentationUse it to check current platform boundaries for cross-border duties, DDP or DAP, product records, and carrier capability. Each market, product, and carrier arrangement still needs separate verification.Treat duty or brokerage as a reserve and evidence question in the representative order, not as a tax, customs, or charge conclusion.

Routing guidance explains rules and location choice, not actual dispatch. Identify profiles or market options before using rate guidance. Delivery-date guidance explains display conditions; duties guidance helps reconcile estimates, contracts, labels, and destination requirements. Follow the relevant destination’s official sources and professional advice where needed, recording method, applicable facts, unresolved questions, and the next check.

What you finished

No checkpoint finished in this lesson yet. Start with “Go to the exercise”.

Self-check not answered

Choose the next job from the remaining gap

If duties, returns, or exceptions conflict, repair policy first. If support cannot give a consistent answer, complete the post-purchase process. Move to launch QA once the same-order evidence is available. The relevant owner still confirms any operation.

Exercise · pick one

Choose a route for the current gap

Next job
Sync fulfillment promise back to policies, product page, checkout, and support snippets.
  • Review policies — Sync fulfillment promise back to policies, product page, checkout, and support snippets.
  • Build support playbook — Continue turning delays, lost parcels, damage, refusal, and returns into a support playbook.
  • Start launch QA — Enter launch QA and test rates, notifications, tracking, policies, and support path with a test order.

Series start

For step-by-step admin practice

Use the locations and inventory lesson for those admin checks, and shipping and delivery for rates and address tests. This lesson keeps the reasoning, same-order evidence, and pause conditions.

Keep one reviewable current promise with a next check date and owner. Return to the basics directory for other preparation work.

Work it out: which of five orders must break its promise

Five orders with their fulfillment parameters (example data, business days). Rule: actual arrival = handling days + transit days + peak buffer; whenever the actual exceeds the promise, the promise breaks, no matter how fast the carrier is.

Handling, transit and promise for five orders

ItemOrderHandling daysTransit daysPeak bufferPage promise
AA1305 days
BB2406 days
CC1315 days
DD3406 days
EE2517 days

Add them up before you read on. Get the actual arrival for all five, say which must break, and explain why a faster carrier is not the fix.

Answer key: A 4, B 6, C 5, D 7 and E 8 days. Against promises of 5, 6, 5, 6 and 7, B and C land exactly on the promise (6 vs 6, 5 vs 5), D and E each miss by a day and must break, and A actually has a day of slack (4 against 5). A faster carrier only pulls D and E back onto the line: of D's 7 days, 4 are transit and 3 are handling; of E's 8 days, 5 are transit and handling plus the peak buffer take 3. Saving a transit day puts D at 6 and E at 7, but handling has not changed and the next peak breaks the line again. Either quote handling plus transit plus buffer, or get handling back to one day. Landing exactly is not safe either: B and C have no slack, and A's single day will not survive one delay.

Common questions

When can shipping setup enter launch review?
Submit it for owner review when the same order reconciles market, rate, handling/transit, tracking, duties, exceptions, and support. Keep representative-address/test-order inputs, rate name, order or parcel reference, carrier record, and recheck time. A visible rate or six self-reported ticks is not final launch approval.
Should I begin with free, flat, or real-time rates?
Start with representative-order costs in the primary market. Check threshold and margin for free shipping; weight and remote costs for a flat rate; and feature conditions, quote source, and upkeep for zone or live rates. Test core, remote, and heavy orders, including packaging and payment costs omitted from a partial calculation. Separate core, test, and closed markets first.
How should handling and transit be written?
Handling describes preparation and dispatch after payment/intake. Transit describes the period after carrier transfer. State business days, cut-off/timezone, preorder/holiday exceptions, the first-scan check, and excluded markets or SKUs. A bare “7-15 days” leaves both the start and exceptions unclear.
What comes first when tracking is blank or delayed?
Reconcile Shopify fulfillment, warehouse/supplier dispatch, label, actual carrier transfer, first scan, and notice trigger. Give the known status and next update. Act on no transfer, loss, or another trigger for a remedy through refund/reship review; pursue carrier claims separately rather than leaving the buyer waiting indefinitely.
Where should DDP, DAP, or unpaid-duties wording appear?
Align Shipping Policy, Returns, FAQ, product delivery notes, checkout-adjacent wording, and support. DDU in older material is historical terminology; check actual DDP/DAP terms, the carrier contract, and destination requirements. Reconcile checkout estimates with labels, clearance, and brokerage fees, with carrier or customs/tax advice where needed.
How should the Scanner be used with shipping evidence?
Submit the supported store URL, platform/stage, and boolean confirmations. Keep the page URL map in the manual evidence pack, alongside primary/blocked markets, rate name, rate screenshot, handling/transit, scan threshold, duties, exception review, refund/reship authority, source-read date, and owner. Compare the pack with the result manually; the tool has no shipping-proof file or support-thread upload field.

Edition notes

  • Author Ranfeng Wei
  • Published
  • Updated
  • Reviewed
  • Next review

This update: Reorganizes the lesson around a representative order; adds the current shipping-system branch, signed cost coverage and applicable-rights boundaries, and an early DDP/DAP responsibility cue with existing checks and pause advice for unresolved charges.