11 parts · 7 checkpoints
Show all 11 parts
- 01Start with the promise on one order
- 02Choose fulfillment for the first batch
- 03Reconcile rates, checkout, and delivery wording
- 04Calculate costs and coverage for the same order
- 05Turn each promise into an operating rule
- 06Repair the promise and handle the exception
- 07Review a delayed order at seven checkpoints
- 08Test the promise against operating failures
- 09Separate tracking practice from your six evidence gates, has a checkpoint
- 10Review in order and keep the handoff
- 11Work it out: which of five orders must break its promise
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.
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.
- Customer promise
- How free shipping, flat rates, zone rates, express fees, and remote-region costs are calculated.
- Evidence to check
- Shipping profile, margin check, and checkout cost screenshots for representative countries.
- Failure signal
- Storefront says free shipping, but remote regions add unexpected checkout cost.
- Customer promise
- When it ships after payment, how long transit takes, whether business days apply, and exceptions.
- Evidence to check
- Supplier/warehouse timing, carrier tracking, page copy, email notices, and support snippets align.
- Failure signal
- Only says global 7-15 days, so support must re-explain handling and transit every time.
- Customer promise
- Who owns DDP, DAP, unpaid duty, import tax, refusal, and destination charges.
- Evidence to check
- Shipping Policy, FAQ, checkout signal, and support language use one logic.
- Failure signal
- Buyer learns about extra fees at customs or delivery, turning into refusal and refund.
- Customer promise
- When tracking is sent, how often it updates, where buyers check, and how the team finds exceptions.
- Evidence to check
- Order confirmation, shipping notice, tracking link, fulfillment status, and exception alert screenshots.
- Failure signal
- Buyers can only email about package status, so support load spikes.
- Customer promise
- How delays, lost parcels, damage, refusal, address errors, and returns are handled.
- Evidence to check
- Responsibility boundary, first-response SLA, escalation threshold, reship/refund/compensation rules.
- Failure signal
- Every exception is improvised, buyers receive inconsistent promises, and chargeback cost rises.
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.
| Layer | Question to answer | How to use the result |
|---|---|---|
| Fulfillment model | Who ships, from where, which SKUs, cash needs, and upgrade trigger | Choose for the first batch you can actually support. |
| Delivery promise | Handling, transit, rates, tracking, and duties | Align product page, policy, checkout, and email. |
| Exception response | Evidence, responsibility, first reply, and refund/reship authority | Give 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.
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.
- When it fits
- Fits a few stable SKUs where more control is needed without overseas warehouse inventory.
- Main risk
- Cross-border transport still involves customs, duties, and a return route to manage.
- Acceptance check
- Handling time, outbound time, carrier, duty logic, and responsible contact are clear.
- When it fits
- Fits validated core SKUs and markets ready for scaling and repeat-purchase experience.
- Main risk
- Higher inventory, cashflow, dead-stock, return, and multi-location complexity.
- Acceptance check
- Sales can absorb stock, and locations, order routing, cut-off time, and return path are clear.
- When it fits
- Fits core SKUs in local warehouse and long-tail SKUs from remote stock.
- Main risk
- Different SKUs have different timing, so storefront and support must be explicit.
- Acceptance check
- Product page, checkout, emails, and support can show different promises by SKU/market.
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.
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.
- When it fits
- Fits early stores with low order volume that need to personally validate packing, labels, tracking, and support flow.
- Day 0 order placed
- Manually confirm payment, address, SKU, packaging material, and whether shipment should be bundled. Evidence: Order detail, address validation, packing checklist, and product photo.
- Day 0-2 pack
- Finish quality check, weigh parcel, print label, take proof photos, and mark fulfillment in Shopify. Evidence: Weight screenshot, parcel photo, label, and Shopify fulfillment record.
- Day 2-4 first scan
- Hand parcel to carrier, confirm first scan, and judge whether shipment notice fires too early or too late. Evidence: Carrier acceptance, tracking first scan, and shipment email timestamp.
- Day 7-15 delivery
- Record actual delivery days, support questions, and damage/address issues, then decide whether self-fulfillment remains viable. Evidence: Delivery tracking, support ticket, damage photo, and review conclusion.
- Classroom promise example
- Storefront can say: orders usually process in 1-2 business days and arrive 7-15 business days after shipment; tracking may update after carrier first scan.
- Support risk
- Manual handling can miss notices, use wrong weight, or skip address checks; volume quickly slows the process.
- When to use it
- Use it when you still need to learn packaging, first-batch SKU behavior, real shipping cost, and support language.
- When it fits
- Fits light-inventory validation, but requires a more conservative promise, stronger supplier evidence, and clearer no-scan explanation.
- Day 0 order placed
- Order syncs to supplier; confirm SKU, color/spec, shipping address, stock, and dispatch time. Evidence: Supplier intake screenshot, stock confirmation, and expected dispatch time.
- Day 1-4 supplier dispatch
- Supplier creates tracking or platform order number; confirm whether the route is trackable. Evidence: Supplier shipment record, tracking number, and route description.
- Day 4-7 first scan or transfer
- Watch for first scan or transfer checkpoint; if no tracking after 72 hours, trigger supplier inquiry. Evidence: Tracking page, supplier reply, and internal exception flag.
- Day 10-20 delivery
- Record actual delivery, delay, duties, damage, and support messages, then decide whether to switch supplier or narrow markets. Evidence: Delivery tracking, customer feedback, exception cost, and supplier review.
- Classroom promise example
- A conservative classroom example is 2-4 business days for handling and 10-20 business days after carrier transfer; tracking updates after transfer checkpoints.
- Support risk
- Supplier instability, tracking gaps, unclear duties, and damage responsibility can turn light inventory into refund and chargeback pressure.
- When to use it
- Consider it for validation. When core SKUs stabilize and delay becomes a main complaint, compare self-fulfillment, domestic stock, and 3PL against actual cost and capacity.
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.
| Check | Why it matters | Evidence to request |
|---|---|---|
| Match zones and costs first | A 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 stable | If 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 rules | Tracking 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 responsibility | Reconcile 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 improvised | A 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.
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.
- What the buyer sees
- The buyer sees one simple rate, such as $6.99. This is good for launch only if most orders stay inside an acceptable cost band.
- Cost that can be missed
- Small lightweight orders may feel expensive, while heavy or remote orders may lose money. One global flat rate pushes cost surprises into support.
- Setup action
- Test three bands by weight, bundle, and primary market: low-cost order, common order, and highest acceptable order.
- Evidence to retain
- Keep product, weight, country, checkout rate, and real carrier quote for each test band.
- What the buyer sees
- Buyers see different rates and timing by country or region. It is more complex than one rate, but closer to real fulfillment cost.
- Cost that can be missed
- Too many zones are hard to maintain. Too few zones hide expensive countries inside cheap regions, causing loss or blocked shipments.
- Setup action
- Start with primary-market groups only: core markets, test markets, and blocked markets. Do not build a complex global matrix on day one.
- Evidence to retain
- Keep shipping zones, open countries, blocked countries, representative checkout screenshots, and review date.
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 order | Common failure |
|---|---|---|
| Markets | Enabled regions, product scope, and currency | An enabled market is mistaken for delivery to every address. |
| Settings > Shipping and delivery > Shipping profiles; after upgrade, Markets > the market’s Shipping options | Products, locations, zones, price/weight conditions, rate name, and checkout total | One item has a rate but the mixed cart has none or costs more. |
| Settings > Locations; Orders > target order > Timeline | Inventory location, routing, warehouse intake, handling, and carrier-transfer times | Routing chooses a location that cannot fulfill. |
| Orders > target order > Fulfillment; carrier tracking page | Each parcel’s status, label, actual transfer, first scan, and notice | A created label or fulfilled status is read as carrier possession. |
| Settings > Policies; order timeline and support inbox | Shipping/Returns, duties, returns, refund/reship authority, first reply, and recheck | Pages, 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.
| Topic | Vague wording | Testable classroom wording |
|---|---|---|
| Handling time | Delivered in 7-15 days. | Orders are processed within 1-3 business days after payment; pre-orders and holidays are explained separately. |
| Transit time | One global 7-15 day range. | US 7-12 business days, UK/EU 8-15 business days, remote regions may take longer. |
| Tracking update | Tracking is provided after shipment. | Tracking updates within 24-72 hours after shipment; it can be blank before carrier scan. |
| Duties responsibility | Duties 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.
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.
- Buyer expectation
- A buyer might place one order while receiving multiple parcels, tracking links, or arrival dates. Make that difference clear first.
- Actual route
- Record the locations able to fulfill each SKU, routing rule, split status, each shipping leg, and whether duplicate packing or exception cost can arise.
- Cost focus
- Do not use one average shipping cost. Record carrier, packing, remote-area, and reship reserves by parcel.
- Scan evidence
- Routing result, inventory by location, split-order status, each tracking link, customer notice, and first scan.
- Exception branch
- When one parcel arrives and another stalls, explain the split and each current status first. Do not misclassify the whole order as lost or automatically refund it.
- Pause boundary
- Until split notices, multiple tracking links, and support explanation work end to end, do not feature cross-location bundles as fast or free shipping.
- Buyer expectation
- Show the buyer separate production or restocking and transit windows so a production wait is not mistaken for a carrier delay.
- Actual route
- Record preorder or custom conditions, change cut-off, production range, when fulfillment begins, when a first scan can exist, and cancellation or return boundaries.
- Cost focus
- Keep production, packing, rush, remake, or post-cancellation recoverable cost separate from carrier cost.
- Scan evidence
- Preorder or custom confirmation, production state, actual dispatch, first scan, order email, and customer-change record.
- Exception branch
- When production is still incomplete, do not call blank tracking a carrier issue. Give a production review time first and handle cancellation or changes through the stated boundary.
- Pause boundary
- When production range, change cut-off, or expected dispatch is not verified, do not place custom or preorder items under a generic fast-shipping promise.
- Buyer expectation
- Before payment, the buyer needs to see the applicable market, delivery range, and actual duty or import-cost presentation, not learn it only after a parcel is held.
- Actual route
- Record origin, destination market, whether product HS and origin details are verified, carrier capability, actual DDP or DAP setup, and remote-area exceptions.
- Cost focus
- Put carrier cost, duty or brokerage reserve, remote surcharge, refusal or return, and possible reship exposure into the same representative order.
- Scan evidence
- Representative-address checkout screenshot, market and rate settings, product records, label capability, first scan, and duty or refusal wording.
- Exception branch
- When duties, customs, or refusal appear, return to the actual checkout, carrier terms, and policy promise. Do not guess responsibility from an old template.
- Pause boundary
- Without representative-address checkout readback, carrier capability, and duty-boundary evidence, pause opening that market or claiming there are no extra fees.
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.
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
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
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.
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."
- Promise field
- Define free-shipping threshold, flat rate, zone rate, express fee, remote surcharge, and blocked regions.
- Buyer question
- Can I know final shipping cost before checkout, and why can it change by address in the same country?
- Cost check
- Test carrier quote, parcel weight, package dimension, subsidy amount, and order margin with representative addresses.
- Exception rule
- Remote areas, PO boxes, islands, military addresses, oversized, and fragile items need separate rules instead of default free shipping.
- Before publishing
- Only make free shipping an ad or homepage claim after core, remote, and heavy-order addresses are tested.
- Key guidance
- Before publishing free shipping, check that margin covers the cost of core and remote addresses.
- Promise field
- Define transit time, business-day language, carrier service, country differences, first scan, and delay explanation.
- Buyer question
- When will I receive it? Does the window start after shipment or after order placement?
- Cost check
- Compare economy, standard, and express routes by cost, on-time rate, tracking quality, and support load.
- Exception rule
- Weather, customs, carrier delay, promo peak, and cross-border transfer need prepared explanations instead of improvised dates.
- Before publishing
- Only publish a specific delivery window when page, checkout, order email, and real first-order tracking match.
- Key guidance
- Separate processing and transit; buyers ask "when it arrives," and the team must explain when the clock starts.
- Promise field
- State when shipment notice sends, when tracking first scans, who checks stalled tracking, and response timing.
- Buyer question
- The order shipped, so why is tracking not updating, and where should I check?
- Cost check
- Check early shipment notices, weak tracking quality, support ticket load, and carrier inquiry cost.
- Exception rule
- No first scan after 72 hours, split parcels, partial shipment, supplier delay, and address issues need fixed replies and escalation thresholds.
- Before publishing
- Only emphasize tracked shipping after notice trigger, tracking link, support template, and internal exception alert work together.
- Key guidance
- Tracking does not end with a number; define first scan, no-update, split parcel, and support escalation rules.
- Promise field
- Define refund, reship, exchange, and return-cost rules for late, damaged, lost, wrong, buyer-remorse, and size-fit cases.
- Buyer question
- If it is late, damaged, missing, or I want to return it, what happens and do I pay postage?
- Cost check
- Calculate reship cost, return label, return warehouse, refund-without-return, chargeback risk, and product margin together.
- Exception rule
- Hygiene items, custom products, final sale, cross-border returns, and high-postage SKUs need separate labels instead of generic free returns.
- Before publishing
- Only claim free returns or easy reship when policy, support template, order notes, and approved cost limit match.
- Key guidance
- Handle returns and reships under applicable rights first, then reconcile policy, responsibility, evidence, cost, and authority.
- Promise field
- Define the order of handling stockout, backorder, split shipment, address error, fraud hold, supplier delay, and cancellation.
- Buyer question
- What do I need to do for this exception, and what happens if I do not reply?
- Cost check
- Prepare refund reserve, replacement SKU, carrier upgrade, manual follow-up, and support first-response SLA.
- Exception rule
- Address validation failure, inventory mismatch, supplier no-ship, and fraud review need pause lines; ads cannot keep pushing the same promise.
- Before publishing
- Only move to launch QA when exception review lead, notification template, refund/reship authority, and review window are defined.
- Key guidance
- Define the exception process in advance: what to check, who owns it, response time, and when to pause the promise.
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.
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.
- Signal
- The same free-shipping threshold works for metro orders, but remote-region orders still show free shipping while real carrier cost is high.
- Tempting shortcut
- Keep one global free-shipping rule and manually cancel or ask buyers for extra postage after orders arrive.
- Repair first
- Split markets into core, test, and blocked groups; add zone rates or block delivery for remote regions.
- First evidence
- Test checkout with 3-5 representative addresses and keep screenshots, the carrier quote, parcel weight, margin, and total price.
- Places to update
- Update shipping zones, rates, free-shipping threshold, shipping policy, and free-shipping claims in ads/product pages.
- What to pause
- Before remote-region cost is tested, do not make “free shipping on everything” the main ad promise.
- Signal
- Buyer receives a shipment notice, but tracking has no scan after 72 hours and support receives “where is my package” messages.
- Tempting shortcut
- Reply “please wait” without checking supplier dispatch, carrier first scan, and notification timing.
- Repair first
- Check fulfillment status, carrier first scan, supplier dispatch time, and shipment-notice trigger before setting the next update time.
- First evidence
- Save order fulfillment status, tracking page, carrier record, shipment email, and supplier dispatch proof.
- Places to update
- Update shipment notice copy, tracking-update timing, internal exception threshold, and first-reply template.
- What to pause
- Until the no-scan cause is clear, do not label the route as a stable tracked or fast-delivery promise.
- Signal
- Hero SKUs ship from a local warehouse in 3-5 days, long-tail SKUs ship remotely in 10-18 days, but product page and checkout show one promise.
- Tempting shortcut
- Keep one clean delivery range for the page and let support explain differences after purchase.
- Repair first
- Split the promise by SKU, location, and market: product pages state handling/transit time and checkout shows the matching delivery method.
- First evidence
- Save SKU, inventory location, order routing, product-page promise, checkout method, and order-email screenshots.
- Places to update
- Update product-page shipping block, Shipping Policy, checkout delivery-method names, order emails, and support routing rules.
- What to pause
- Before hybrid fulfillment display is working, do not place long-tail SKUs into the same fast-shipping product set or ad promise.
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.
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.
- First check
- Check last scan, delivery proof, carrier responsibility, and buyer address.
- Action
- Reship, refund, or file claim based on responsibility boundary before it becomes a chargeback.
- Support wording
- Explain the action and expected completion time in one reply.
- First check
- Collect photos, packaging, order number, outer box, and carrier record.
- Action
- Reship, partially refund, fully refund, or claim based on damage severity.
- Support wording
- Acknowledge the issue and give evidence requirements once, not repeatedly.
- First check
- Separate buyer typo, system sync issue, whether it can be edited before shipment, and intercepted after shipment.
- Action
- Define edit, intercept, reship, return handling, and cost responsibility.
- Support wording
- Tell the buyer which stage can still be changed and which requires return or reship.
- First check
- Check refusal reason, duties, uncollected status, address error, buyer regret, or product issue.
- Action
- Check the reason, applicable consumer rights, disclosed terms, and actual costs before deciding a refund, reshipment, or legally permitted charge. A policy cannot create a right to withhold a refund.
- Support wording
- Explain the verified cause, available remedies, and next update. Check return movement, refusal, and refund responsibility separately.
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.
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.
- Trigger
- Tracking stops at a checkpoint, the carrier confirms an exception, or the internal lost-parcel window is exceeded.
- Cost and responsibility
- Determine the buyer’s remedy first, then record carrier claims, insurance, supplier reship terms, and margin reserves for the authorized owner. Cost review cannot delay a required refund.
- Support boundary
- Give clear options: wait for investigation, reship, refund, or escalation, and record the buyer’s choice.
- Update the public promise
- Add countries, carriers, or SKUs with high loss rates to an exception watchlist; close a market or change the route when needed.
- Trigger
- The customer receives a duties/tax notice, believes it was unclear at checkout, refuses delivery, or asks for a refund.
- Cost and responsibility
- Compare duties language in policy, checkout, product page, and email. Establish any undisclosed charge or conflicting promise before assigning responsibility and remedy cost.
- Support boundary
- Support cannot rewrite policy live. Explain the current promise, available options, and the page fix that follows.
- Update the public promise
- Put duties responsibility near shipping, returns, FAQ, and checkout, not only at the bottom of a policy page.
- Trigger
- Cross-border return cost is near or above gross margin, while the buyer expects free return.
- Cost and responsibility
- Within applicable rights and the buyer’s agreement, compare exchange, partial refund, a local return address, and refund without return. Margin does not decide the buyer’s legal entitlement.
- Support boundary
- Support should follow rules by SKU, country, reason, and amount, not negotiate from scratch every time.
- Update the public promise
- State the applicable situations, postage responsibility, and available options. Labels such as custom, hygiene, or final sale do not by themselves remove mandatory rights.
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.
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.
- What is happening
- Shopify shows fulfillment created and the buyer may have received a shipment notice, but tracking has no first scan.
- First check
- Check 3PL SLA, cut-off time, warehouse intake, label creation time, actual dispatch, and whether the shipment notice went out too early.
- Customer wording
- The parcel is in warehouse processing. Tracking usually updates after the carrier first scan; we will recheck within 24-48 hours.
- Refund and reship decision
- Check actual transfer and whether a remedy is already due. Escalate confirmed loss, inability to dispatch, or a missed internal SLA; an open promise window does not override that evidence.
- Key guidance
- At Day 2, locate the gap between label creation, physical transfer, and the first scan, then explain the progress to the buyer.
- What is happening
- At this checkpoint, the buyer may be worried. Check 3PL transfer proof, a missed carrier scan, supplier delay, and premature notification.
- First check
- Check warehouse dispatch proof, carrier pickup record, split-parcel status, supplier reply, and whether internal exception alert fired.
- Customer wording
- We are checking warehouse and carrier records. The next update is X; if tracking is still blank by Y, we will offer reship/refund options.
- Refund and reship decision
- Set a clear threshold: for example, no first scan after 72 hours or no warehouse transfer proof triggers reship/refund review.
- Key guidance
- At Day 5, give the next update time and the threshold for action.
- What is happening
- Support SLA matters now. SLA simply means how fast the first reply happens, when to recheck, and when to escalate.
- First check
- Check first-response time, order timeline, tracking, 3PL/carrier case, policy-page promise, and whether the internal escalation line is crossed.
- Customer wording
- Here is the current status: the parcel is stuck at X, we have checked with Y, and the next reply time is Z.
- Refund and reship decision
- If still inside the 7-12 day window, escalate inquiry first; if evidence shows no warehouse transfer or loss, reship or refund early.
- Key guidance
- Day 8 explains SLA in plain terms: reply, recheck, and escalation timing.
- What is happening
- Use this checkpoint when the 7-12 business day window, measured from the confirmed start, has reached its end. It does not mean every order is overdue on Day 12 after payment. Open-ended waiting adds refund, dispute, and complaint risk.
- First check
- Check last scan, carrier case, delivery proof, loss likelihood, reship stock, margin, and refund authority.
- Customer wording
- The confirmed delivery window has passed. We will explain the remedies available to you and offer an actionable refund, reshipment, or agreed waiting option. A partial refund applies only where appropriate and agreed.
- Refund and reship decision
- Separate refunds, reshipments, agreed waiting, and carrier claims. A merchant’s claim against a carrier does not replace or delay the buyer’s remedy.
- Key guidance
- Day 12 is the promise boundary and needs clear options.
- What is happening
- The order may be lost, returned, stuck in customs, or address-blocked. The team must decide cost responsibility instead of improvising.
- First check
- Check responsibility source: buyer address, warehouse, carrier, duty refusal, supplier delay, or an overpromised page.
- Customer wording
- We have escalated this order to exception handling. The current option is X; if you choose reship/refund, we will complete it within Y.
- Refund and reship decision
- Resolve the buyer’s case under applicable rights and established responsibility, then have the owner allocate merchant, warehouse, carrier, or supplier costs. Check any extra postage for an address error separately and pursue claims alongside the remedy.
- Key guidance
- Day 15 documents refund/reship boundaries so support does not improvise.
- What is happening
- Resolving one order is not enough. Return to product page, Shipping Policy, order email, support template, 3PL SLA, and ad promise before the next order repeats it.
- First check
- Check route exception rate, SKU exception rate, support tickets, refund/reship cost, and whether to narrow markets or pause fast/free shipping claims.
- Customer wording
- Finish affected-buyer resolution; for future buyers, rewrite the public promise into what the team can actually keep.
- Refund and reship decision
- Write the exception back into the matrix: reship, refund, partial refund, claim, pause selling, or change route.
- Key guidance
- At Day 20, use the resolution to update pages and operating rules before the next batch.
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.
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.
- Trigger
- The free-shipping threshold raises AOV, but remote addresses, heavy items, or low-margin bundles consume profit. The extra basket revenue can hide an unaffordable fulfillment subsidy.
- Check
- Test checkout shipping, carrier quote, package weight, and order margin across metro address, remote address, heavy order, low-margin SKU, and bundle cart.
- Evidence to check
- Representative checkout screenshots, shipping profile, carrier quotes, COGS/margin sheet, and excluded countries or regions.
- Customer wording
- State eligible countries, threshold, product exceptions, and remote-region exceptions before the buyer orders.
- Pause boundary
- Until primary and remote addresses are tested, do not use sitewide free shipping as the hero promise or main ad hook.
- Key guidance
- A free-shipping threshold needs address, weight, and margin proof, not only higher AOV.
- Trigger
- The buyer receives shipment notice, but tracking has no first scan or stalls at transfer, creating repeated "where is my package" tickets.
- Check
- Check whether shipment notice was too early, carrier first-scan rule, supplier or warehouse dispatch proof, split parcels, and internal exception threshold.
- Evidence to check
- Shipment email, tracking page, carrier log, supplier dispatch proof, Shopify fulfillment status, and support tickets.
- Customer wording
- Explain when tracking may update, where it is stuck, the next check time, and options after the threshold.
- Pause boundary
- If a route repeatedly has no first scan, stop labeling it as tracked or fast shipping.
- Key guidance
- A tracking gap needs notice timing, first-scan proof, and support SLA, not just "please wait."
- Trigger
- Late, lost, damaged, wrong, or returned parcels happen, and support improvises refund versus reship each time, losing control of cost and expectation.
- Check
- Classify responsibility: carrier, warehouse/supplier, buyer address, overpromised page copy, or product quality. Then check margin, reship cost, return label, and chargeback risk.
- Evidence to check
- Photos, outer box, delivery proof, carrier case, order notes, policy screenshot, refund/reship authority, and approved cost limit.
- Customer wording
- Give a clear option: wait for investigation, reship, refund, partial refund, or escalation, and state required evidence.
- Pause boundary
- Before refund/reship rules are clear, do not publicly claim easy reship, free returns, or risk-free purchase.
- Key guidance
- Handle refunds and reships under applicable rights and responsibility, then have the authorized owner review evidence and costs.
- Trigger
- As shipping tickets grow, support knows to reassure buyers but not where to check first, when to reply, when to escalate, or who can approve refunds.
- Check
- Turn first-response time, recheck time, escalation condition, review lead, allowed actions, and forbidden promises into a support path.
- Evidence to check
- Support macros, ticket tags, order lookup path, warehouse/carrier contacts, refund authority, and 7-day review sheet.
- Customer wording
- The first reply states known status, next update time, evidence needed from the buyer, and the option after threshold.
- Pause boundary
- Do not scale complex fulfillment markets before the support path has first-response and escalation lines.
- Key guidance
- Support SLA needs first response, recheck, escalation, authority, and forbidden promises, or shipping problems become trust problems.
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
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.
Strict-record status
Hold
Evidence still missing
Six tasks self-recorded
Choose the next action
Self-check not answered
Judgment for the selected answer
Check the worldwide promise
Self-check not answered
Judgment for the selected answer
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
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.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.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.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.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.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.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.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 group | Scope | Use in this lesson |
|---|---|---|
| Shopify order routing documentation | Use 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 documentation | Use 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 documentation | Use 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 documentation | Use 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.
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.
Choose a route for the current gap
- Next job
- Sync fulfillment promise back to policies, product page, checkout, and support snippets.
- Next job
- Continue turning delays, lost parcels, damage, refusal, and returns into a support playbook.
- Next job
- Enter launch QA and test rates, notifications, tracking, policies, and support path with a test order.
- 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
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
| Item | Order | Handling days | Transit days | Peak buffer | Page promise |
|---|---|---|---|---|---|
| A | A | 1 | 3 | 0 | 5 days |
| B | B | 2 | 4 | 0 | 6 days |
| C | C | 1 | 3 | 1 | 5 days |
| D | D | 3 | 4 | 0 | 6 days |
| E | E | 2 | 5 | 1 | 7 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.