AdFeed Studio The short answer: do not confuse a pre-checkout delivery picker with an external form that replaces checkout. The former can simplify choosing an office, locker or address, then return the buyer to Shopify. The latter moves the most critical part of the sale outside the native flow. For most stores, the sensible choice is either fully native Shopify Checkout or pre-checkout that always finishes in Shopify Checkout.
Start with three different models
Pre-checkout + Shopify Checkout adds a step before checkout. The buyer chooses a carrier and delivery to an address, office or locker. That choice is passed to the cart or order, while payment and final confirmation remain in Shopify.
Native Shopify Checkout displays delivery methods inside the standard checkout. After entering an address, the buyer sees eligible options and prices, then continues to payment in the same flow.
An external, non-native order form accepts the details and creates an order outside standard checkout — often as a “quick order” with cash on delivery (COD). This model carries the largest hidden risks.
An important distinction about Dostavi.bg: the app offers two modes — interactive pre-checkout and delivery methods inside Shopify Checkout — but the buyer completes the order through Shopify in both. Pre-checkout is a richer delivery-selection interface, not a replacement for checkout.
Pros and cons at a glance
| Model | Strengths | Trade-offs and risks | Best suited to |
|---|---|---|---|
| Pre-checkout + Shopify | Map, carrier logos, visible offices and lockers, point-level pricing, structured delivery data | One extra step; the selection must survive back/forward navigation, cart changes and mobile edge cases | Stores offering several carriers and many pickup points |
| Native Shopify Checkout | Short, familiar flow; centralized pricing, discounts, payment, inventory and order data; strong compatibility | Less room for a rich map; some UI customizations depend on plan; delivery choice appears after the address | Stores prioritizing speed and minimum friction |
| External form instead of Shopify | Complete visual freedom; can appear very short; convenient for one simple COD scenario | Fragmented data and events, price/inventory risk, lost payment options, harder recovery, maintenance and compliance | Only a proven business need backed by serious engineering ownership |
When pre-checkout creates real value
For a Bulgarian store, delivery is rarely just “standard” or “express.” Buyers think in specific offices, lockers, opening hours, distance, price and preferred carrier. A pre-checkout map can translate that complexity into two or three clear actions.
- It presents several carriers through one consistent interface instead of conflicting lists.
- It reduces free-text instructions such as “the office next to the supermarket.”
- It can display live pricing based on weight, zone and COD.
- It passes a machine-readable office or locker to Shopify and the shipping label.
The trade-off is that every extra step can reduce conversion if it is slow, unclear or looks like the final order action. The button should state what happens next — “Continue to payment,” for example — not “Place order” if the order has not yet been submitted.
What native Shopify Checkout gives you
Shopify describes Checkout as its secure flow for taking orders and payments. The system checks inventory as the buyer progresses, presents eligible delivery methods and collects payment information. Extensions and Shopify Functions add logic in an upgrade-compatible way that can benefit from platform releases such as one-page checkout.
In practical terms, that gives the merchant one version of the final total, one order, predictable discounts and taxes, payment events in the timeline, accelerated methods where available, web pixels and checkout events, plus native abandoned-checkout recovery for supported channels.
Shopify reports that its Checkout converts 15% better on average than the solutions compared in its study, while Shop Pay can lift conversion by up to 50% versus guest checkout. These results came from research commissioned by Shopify. They are useful directional evidence — not a promise for an individual store or proof that Shop Pay is available in every country and configuration.
The serious problems with finishing outside Shopify
“Fewer fields” does not automatically mean “better checkout.” If a short form hides two systems, asynchronous order creation and incomplete events, it may save the buyer seconds while adding hours of support and avoidable losses after the sale.
1. The displayed total can diverge from the order total
An external form must reproduce shipping, discount, gift-card, tax, currency and Markets logic. A Shopify configuration change can remain unnoticed in the external layer.
2. Inventory and duplicate orders become harder
Shopify checks stock during checkout but holds inventory only after payment information is submitted. An external process must carefully handle the final unit, retries, double-clicks and failed requests.
3. Analytics loses a clean sequence
Events such as checkout started, delivery selection, payment attempt and checkout completed can be missing, duplicated or split across systems. Meta, Google Analytics and Shopify may then show different funnels, weakening decision-making and optimization signals.
4. Abandoned-checkout recovery can break
Shopify creates an abandoned checkout after a buyer supplies contact information but does not complete the process. Shopify notes that automated recovery emails apply to Online Store and Buy Button, not every third-party channel. If the buyer never enters native checkout, the standard recovery object and link might not exist.
5. You lose native payment convenience and trust
Accelerated payment methods, saved addresses and a familiar UI reduce data entry. If an external form collects card data itself, engineering and compliance responsibilities rise sharply. If it accepts only COD, card-data exposure disappears, but the store may encourage its riskiest payment method.
6. Maintenance becomes an ongoing product
Shopify evolves API versions, checkout behavior, Markets and payment rules. A flow outside the platform must continually catch up, monitor failures and define what happens during outages.
Decide with your own data
Do not compare “checkout conversion” alone because pre-checkout moves the start of the funnel. Measure both versions from the same starting point — for example, carts containing at least one available item.
| KPI | Formula | What it reveals |
|---|---|---|
| Cart-to-order rate | Orders ÷ carts | The outcome of the complete flow |
| Delivery-selection completion | Completed selections ÷ started selections | Friction in the map or list |
| Checkout-to-order rate | Orders ÷ checkout starts | Performance of the native final stage |
| Shipping error rate | Orders needing correction ÷ orders | Quality of address, pickup point and price data |
| Mobile completion time | Median cart-to-order duration | Real speed without a few slow sessions distorting the result |
| Recovered checkout revenue | Recovery revenue ÷ total revenue | The value of native recovery |
Illustrative impact: 1,000 checkout starts at 48% conversion and a €45 average order value produce €21,600 in revenue. If a better flow adds only two percentage points, the result becomes 500 orders and €22,500 — a €900 difference from the same traffic. This is arithmetic, not a forecast.
A practical merchant action plan
- Map the real funnel. Record cart, delivery-selection start and finish, checkout start and completed order.
- Identify the source of truth. Final price, currency, shipping, discount and inventory should be resolved by Shopify at submission.
- Test mobile edge cases. Back/forward, refresh, double-click, quantity change, final unit, weak internet and in-app browsers.
- Run an A/B test. Compare native mode and pre-checkout with equivalent traffic, products and timing. Judge orders and profit, not clicks alone.
- Require a safe fallback. If an external layer fails, the buyer should still reach Shopify without losing the cart.
- Measure operational quality. Wrong pickup points, manual corrections and label-processing time also cost money.
Frequently asked questions
Does pre-checkout always reduce conversion?
No. An extra step can create friction, but it can also remove a bigger problem, such as searching through hundreds of pickup points. The reliable answer comes from an A/B test and cart-to-order rate.
Is native Shopify Checkout flexible enough?
For many stores, yes. Shopify Functions can reorder or hide delivery and payment options, while checkout extensions add UI where the merchant plan permits it. Not every UI surface is available on every plan.
When would I choose pre-checkout?
When pickup-point selection is central to the purchase, buyers need a map or a comparison of several carriers, and the selection can be passed reliably into Shopify Checkout.
What should I ask a vendor of an external “quick order” form?
Request a data-flow diagram, price and inventory rules, duplicate prevention, retry and fallback behavior, supported Shopify features, a complete analytics map, data-processing terms and an incident SLA.
Related reading
- Uncollected COD parcels in Bulgaria: the true merchant cost
- Custom product images for Meta Ads: a merchant guide
Sources and methodology
- Baymard Institute — Cart & Checkout Usability Research (70.19% average abandonment; potential improvements are not guarantees).
- Baymard — Checkout complexity and form fields (17% cite complexity as an abandonment reason).
- Shopify Checkout and Shop Pay study summary (Shopify-commissioned research).
- Shopify Help — Shopify Checkout; Recovering abandoned checkouts.
- Shopify Developer — Apps in checkout.
Market figures are attributed. The financial scenario is illustrative arithmetic and should be replaced with store-specific data.