You can customize four things in the Shopify checkout: visible blocks at fixed positions, the logic for discounts, shipping and payment methods, the design through colours, fonts and wording, and the pages after the purchase. The structure of the checkout pages is fixed. We own the assignment of every requirement, the build as an app and the sign-off with real order cases.
NICCOS has been a Shopify Plus Partner since April 2022 and is an OpenAI partner. The Shopify Partner Directory lists 19 reviews with a rating of 5.0. With Best Price Indicator (PAngV) we run an app of our own in the Shopify App Store. Our projects are documented in 13 published case studies.
The checkout handles several countries through Shopify Markets. Currency, tax, language and payment methods follow the customer's market. The rules are set per market, and the checkout stays one checkout.
The operator of the official CR7 online stores sold through physical retail and marketplaces and had no shop system of its own. We built mycr7.eu and mycr7.ch on Shopify Plus. Switzerland is outside the EU and needed its own tax and customs logic, separate price lists and a checkout in CHF, while the EU store charges in EUR. The client's proprietary ERP and warehouse system is connected. According to the MYCR7 case study, the stores went live after 6 weeks and revenue was 120% above the level from retail and marketplaces.
Gusti Leder sells in DACH, France, the UK and further European markets with local tax, currency and domain logic. Before launch we ran a full test phase for checkout, payments, the engraving configurator and the ERP processes. The Gusti Leder case study reports a go-live in under 8 weeks and a 45% higher conversion rate. Our page on Shopify internationalization covers the market setup.
You need Shopify Plus for your own blocks on the information, shipping and payment steps. The same applies to the extended branding configuration and to functions that are built as a custom app for your store alone. Without Plus you keep extensions on the thank-you and order status pages and functions that come with an app from the Shopify App Store.
Before a plan change we check which requirements really need the checkout. A delivery note can sit in the cart, a quantity tier on the product page. When a list remains that can only be solved in the checkout, we calculate the change with you. Our page on the Shopify Plus agency covers the plan decision.
Three topics come up in every project for the EU and Switzerland. Tax is calculated per country. Payment methods differ by market, and a payment function decides which ones a customer sees.
Business customers expect invoice payment and a field for their VAT ID. Payment terms and price lists are features of Shopify B2B, and the checkout adds required fields and payment rules.
Germany adds a rule on price reductions. When you advertise a reduced price, you have to show the lowest prior price. This belongs on the product page and cannot be repaired in the checkout. We developed the app Best Price Indicator (PAngV) for it.
Everything the customer has to choose or design belongs before the checkout: delivery date, greeting text, engraving, add-on items. The checkout receives these details and calculates with them. It is not built to hold a configurator.
BlumeIdeal delivers flowers on a chosen date and ran on Shopware 5, which could only map date and gift logic to a limited degree. For the store on Shopify Plus we built a date logic that combines calendar, cut-off times and availability from JTL-Worker Cloud. Weekends and defined public holidays are blocked, and customers only see dates that logistics can meet. The BlumeIdeal case study reports the go-live after 50 days and 29% higher average order value through upsells in the configurator.
Checkout projects fail because of requirements nobody checked against the platform, and because of special cases that only show after launch. Before release we therefore run through several countries, payment methods, discounts, gift cards, sold-out items and express payments, and we sign off each case on its own.
Tracking is the second reason. No freely embedded JavaScript runs in the checkout. Events arrive through the pixel environment and respect the customer's consent. Our page on tracking setups describes the setup.
When customers already leave on the product page or in the cart, Shopify CRO is the better place to start.
Your own blocks at defined positions: delivery notes, gift options, extra fields, upsell blocks, consent statements. They run in a sandboxed environment and get placed through the checkout editor.
Server-side logic for discounts, shipping options, payment methods, cart transforms and validation. They apply where scripts used to run, are versioned and need no runtime in the browser.
Colours, fonts, corner radii and text through branding settings and translations. That is no free layout, but it covers most of what brands actually need.
Your own UI blocks on the information, shipping and payment pages require Shopify Plus. On the thank-you and order status pages, extensions can be used without Plus.
Functions that we develop as a custom app for your store alone require Shopify Plus. They reorder, rename or hide payment methods and shipping options and enforce your own validation.
The deeper visual configuration of the checkout is a Plus topic as well. Without Plus you keep logo, colours and the basic options from the admin.
Apps from the Shopify App Store may bring functions on every plan. They cover tiering, bundles and promotional rules that previously needed discount codes.
The structure of the checkout pages is fixed. Extensions sit at defined positions. Designing a fully custom checkout means planning past the platform.
No freely embedded JavaScript runs in the checkout. Tracking goes through the pixel environment, logic through functions. That is a platform decision about security and stability, not a setting.
The old template file is retired. First the checkout steps went, then the thank-you and order status pages. Existing customisations had to be moved to extensions and functions.
Additional intermediate steps or your own confirmation flow before purchase cannot be inserted. Where that is needed, the logic belongs before the checkout, in the cart or on the product page.
Every requirement gets assigned: UI extension, function, branding, cart, or not possible at all. That sorting decides effort and feasibility.
We record existing checkout customisations, scripts, apps and pixels. Older Plus stores in particular carry leftovers that were never cleaned up after checkout.liquid was retired.
We play through placement in the checkout editor before any code is written. That shows early which positions really exist and how much room they offer.
Extensions and functions get developed as an app, versioned and deployed through the Shopify CLI. Every change is traceable and reversible.
Multiple countries, payment methods, discounts, gift cards, sold-out line items and express payments. The checkout is where edge cases cost money.
We watch completion, drop-off per step and error rates. An extension that slows completion is wrong even when it is functionally correct.
Showing a concrete delivery date or split-shipment notes right where the shipping method is chosen.
Additional validated fields such as VAT ID, cost centre or age confirmation in B2B and regulated cases.
Invoice payment only for approved company accounts, cash on delivery only in certain countries, ordering by margin instead of by chance.
Quantity tiers, bundle pricing and customer group logic as a function instead of a chain of apps and discount codes.
You have Plus and never use it
Extensibility inside the checkout steps is part of your plan but sits idle. That is room to move you already pay for.
Support answers the same question daily
If a detail is missing at purchase, it comes back later as an email or a call. Those queries can be caught at the source.
Orders arrive incomplete
Vague delivery addresses, missing reference numbers or the wrong payment method cost more in rework than any extension does to build.
Old customisations do nothing
Since checkout.liquid was retired, leftovers from scripts and apps sit in the store with no effect. What is still needed has to be reassigned.
You are not on Shopify Plus
Without Plus you can add neither your own blocks nor custom-built functions inside the checkout steps. The plan question comes first.
To Shopify consultingThe drop-off happens earlier
If users leave on the product page or in the cart, an extension in the final step changes nothing about it.
To Shopify CROCompany accounts and price lists are missing
Payment terms, catalog access and order approvals are features of the B2B platform. A checkout extension cannot stand in for them.
To Shopify B2BWith the checkout, the effort is settled before the first line of code, by what the platform allows.
For teams with a list of wishes who need to know, before any concept, which of them their plan can actually support.
Ends with a basis for decision that states what gets built and what is dropped.
For decided projects that will ship as checkout UI extensions and Shopify Functions.
Ends once the extension runs in the live checkout and the edge cases have been played through.
For stores whose checkout logic has to grow with the range, new markets and changing promotions.
Ends not with a release but with a checkout that matches what your business currently needs.
Every figure appears in the case study, where you can verify it.
Groundies, MYCR7 and Gusti Leder are three of thirteen projects we have published with starting point, delivery and result.
We assign each one: extension, function, branding or cart. We tell you before the concept what the platform does not allow.
NICCOS
The page could not be loaded.
Please reload the page. If an update has just gone live, this will load the latest version.
