A Shopify checkout delivery estimate, in this app, is a message you write. SK Checkout Customizer includes an estimated-delivery messaging block. The catalog does not describe lead-time settings, a processing-day calculator, or a carrier API. The date on the page is the sentence you configured, not a promise looked up from a shipping label that does not exist yet.
That distinction matters because the delivery question is often the last objection. Shoppers want a window before they pay. A sentence you can stand behind belongs in checkout. A live carrier date does not, because this block does not call a carrier. If the block sits on the checkout step, Shopify’s help on checkout configurations documents that app-block placement as Plus.
A message is not a carrier promise
Lead time is how long you take to pack. Transit time is how long the carrier takes after pickup. A real estimate adds both, then pads for the weekend and for the products that ship slower. This catalog does not add those numbers for you. It shows the messaging block. You decide the words, including any date or window you type into them.
Call the line an estimate in the sentence itself. “Estimated delivery” is harder to misunderstand than “Arrives Tuesday,” unless you are ready to refund or replace when Tuesday slips. The block will not update itself when a storm delays a hub. There is no tracking hook in the catalog for this widget.
What you enter
Write the line the way a support agent would say it on the phone. Name the window, name the assumption, and keep the product scope honest. A domestic ground order and an international order should not share one careless sentence if their transit times differ. The catalog does not document a different message per product or per market inside this block. If you need two windows, confirm in the editor whether you can place two messages or whether you must write one careful range. Do not invent a per-SKU calculator.
- Your words: the date or window is copy, not a computed carrier result.
- No lead-time fields: the catalog does not list processing days or cutoff clocks for this block.
- No carrier lookup: the block does not read a rate API or a tracking number.
- Checkout placement: on the checkout step, plan on Plus and confirm the editor.
The app is free. There is no paid tier that adds a carrier connection the catalog omitted. Free means the message block is included. It does not mean a logistics integration is hiding on a higher plan.
Where Plus matters
Checkout UI extensions render this block in a checkout extensibility context. App blocks on the information, shipping, and payment steps are the Plus row in Shopify Help. A non-Plus store should not expect the estimate beside the shipping methods. Thank-you and order-status pages are a later permission, and they are a weaker place for a delivery question the shopper needed before paying. The catalog calls this an estimated-delivery messaging block. It does not say the block is a thank-you feature. Confirm the target in the editor before you promise the line on a given page.
Stores shipping inside the US, the UK, Canada, or the EU should still write the window for the lanes they sell. A single “3 to 5 days” line is only fair if that is true for the address on the test order. Check out with a domestic address and, if you sell across a border, with an address in the other country. Read the message both times. If you cannot vary it, the sentence has to survive both addresses.
A domestic example
Treat this as an illustration. A home-goods shop packs in one business day and sees ground delivery in two to four more days for most domestic addresses. The checkout line might read: “Estimated delivery 3 to 5 business days after we ship. We ship the next business day for orders placed before 1 p.m.” Those numbers are an example. Replace them with your warehouse’s actual pattern. Place a Friday test order and a Monday test order so you see whether the words still make sense when the weekend sits in the middle.
If some products are made to order, do not reuse the stocked-item window. Either keep those products off the same message or write a range wide enough for the slower item. The block will not detect a made-to-order tag for you.
The shipping methods at checkout stay Shopify’s rates. The message does not choose the rate, rename it, or hide it. Those edits belong to the delivery customization function, which is a different block of logic and still needs a test on your plan. Keep the estimate sentence consistent with the rate names beside it. A line that says “express in one day” next to a rate that is ordinary ground will be read as a promise about that rate.
What support should say when the date slips
When a parcel is late, support should repeat the estimate, not a guarantee the block never made. A useful reply names the window you published, checks the tracking the carrier actually created, and offers the remedy in your shipping policy. Do not tell the agent that the app calculated the date from the label. It did not. If the published window was wishful, fix the sentence. Leaving an optimistic line up will produce the same ticket every week.
- Quote the checkout sentence in the macro, and label it an estimate.
- Look up tracking in the carrier or in Shopify, not in this block.
- Change the message when your average ship time changes.
- Do not promise a calendar day you have not tested.
Questions about checkout delivery estimates
Does the block use the carrier API?
No. The catalog describes a message. It does not describe a carrier lookup or a lead-time calculator.
Can the date change by product?
The catalog does not document a per-product lead time on this block. Write a window you can honor for the products that share the message, and test it.
Can a Basic store show the line on the shipping step?
Shopify Help documents checkout-step app blocks as Plus. Confirm the target in your editor before you announce the line.
Write an estimate you can defend, then place it from SK Checkout Customizer on a checkout your plan allows. The app is SK Checkout Customizer.