Make the charge explainable before checkout
A delivery policy should not depend on a seller remembering which amount was quoted in a chat. The current settings expose flat or free delivery, a standard rate and an optional free-shipping threshold. These are operational inputs: calculate the cost before deciding which rule to offer.
Use the same cost boundary throughout
A free-shipping threshold needs enough basket contribution to cover the delivery expense you intend to absorb. It is not automatically profitable because the basket value is larger. Include packing and any applicable collection costs in your decision. The resource calculator can help compare assumptions without changing the live rule.
Separate location eligibility from pricing
The screen supports allowed and blocked pincode lists. Review the saved entries carefully; the input handling filters for six-digit codes. A missing or malformed entry should not silently become a promise to serve a destination. Test an intended address and an excluded one before promoting the delivery offer.
Keep the limits visible
These controls are not evidence of live carrier rate shopping, universal coverage or automatic pickup. A delivery note explains a policy but does not configure it. After an uncertain save, reload the settings before making another change, and compare the storefront quote with the intended rule.
UNDERSTANDING THE WORKFLOW
A delivery fee is a store rule, not a courier quotation
The amount a store charges a customer and the amount a courier charges the merchant are different figures. Confusing them can make an apparently simple delivery setting misleading.
What the settings cover The inspected delivery screen exposes standard pricing, an optional faster tier, a free-shipping threshold and estimated delivery windows. These are merchant configuration controls. Their presence does not establish a negotiated carrier rate, guaranteed transit time or courier coverage for every address.
Choose the customer charge from your actual operating model. If you subsidise delivery, account for that in the order economics rather than assuming the cost disappears.
Check boundaries Inspect a bag below the threshold, at the threshold and above it in an authorised test setup. Check the fast option separately if offered. Verify the customer sees the intended fee and wording.
Keep the promise consistent A checkout note that mentions an old threshold can contradict the configured rule. Update explanatory text when the policy changes, and distinguish an estimate from a delivery commitment.
Use the delivery-rules feature page for available settings and the help guide for editing. This explanation concerns the meaning of the fee, not a recommendation for a specific shipping price.
Pincode rules express where you choose to take orders
A delivery area should describe a promise you can fulfil. A list of accepted pincodes is not evidence that every courier can serve them.
What the form exposes The inspected delivery screen provides serviceable and blocked pincode lists. Its help text describes comma-separated six-digit entries and says that leaving the serviceable list blank allows delivery everywhere. Treat that as a consequential setting, not a harmless empty field.
Before saving, prepare the areas you actually intend to accept. Do not infer precedence between conflicting entries without testing the current runtime. Remove contradictory rules rather than relying on an undocumented assumption.
Verify representative addresses Check one intended serviceable pincode and one excluded pincode in an authorised test flow. If the interface presents an unexpected result, investigate before promoting delivery availability.
Understand the limit A pincode rule is a storefront eligibility rule. It does not guarantee carrier pickup, delivery dates, parcel acceptance or a live carrier quotation. Keep those checks in the fulfilment process.
This article belongs with delivery rules rather than a new broad shipping guide. Its distinctive purpose is explaining the difference between store-defined order eligibility and external courier serviceability.
Checkout notes explain delivery rules; they do not create them
A checkout note is useful for a short explanation the customer needs at that moment. It becomes dangerous when it describes a rule the store has not actually configured.
What the source supports The inspected delivery settings include a note shown on the delivery step. Pricing and pincode controls appear separately. This separation matters: writing “free delivery above a threshold” in a note is not evidence that the threshold rule is active.
Keep the note aligned with the saved settings. Prefer one practical message over a long collection of policies that becomes hard to scan on a phone.
Use a consistency check Choose a representative bag and inspect the displayed charge beside the note. Check whether the text still makes sense when a faster option is selected or the address is outside the intended area.
Keep exceptions explicit If handmade production takes additional time, do not hide that constraint behind a cheerful delivery slogan. Use accurate wording and the appropriate product or policy surface for detail.
This article should support the existing delivery-rules page, not become another generic checkout checklist. Its specific lesson is that explanatory copy and operational configuration must agree.
Bring this checklist to your evaluation
- A costed standard charge
- A deliberate threshold
- Reviewed pincode lists
- Customer-facing quote checked
Check the workflow that matters to your business
Read the relevant setup and troubleshooting guide, then explore getting started with oBizee. Confirm current account availability and terms before committing.