Simple & Elegant Checkout (dfsimplecheckout) — Complete guide
Install, configure and run the one-page checkout: colors, logo, distraction-free mode, Google and Facebook login, Google Places, country-aware address form, AJAX discount code and troubleshooting for PrestaShop 8 and 9.
Overview
DataFirefly Simple Checkout replaces PrestaShop’s native 5-step checkout with a modern one-page flow inspired by Shopify and Stripe checkouts. The module mounts its controller at runtime via the actionDispatcher hook — no override file is written to disk, and any existing third-party overrides on OrderController are cleanly inherited.
Key features: two-column layout with a persistent order summary, Google and Facebook social login, Google Places address autocomplete, country-aware address form, AJAX discount code, five configurable colors, distraction-free mode.



Installation
- In your PrestaShop back-office, go to Modules → Module Manager → Upload a module.
- Select the
dfsimplecheckout-1.3.3.zipfile downloaded from your DataFirefly account. - Click Install, then Configure.
- Clear the PrestaShop cache (Advanced Parameters → Performance → Clear cache).
- Visit your shop’s
/orderpage with a product in the cart: the new checkout displays immediately.
The module supports PrestaShop 8.0 → 9.x. No theme modification is required. Uninstalling automatically restores the native checkout.
What’s new in version 1.3.3 (2026-11-16): new “Customer must confirm the shipping method” setting. When on, the shipping step stays open until the customer confirms their carrier, instead of the preselected carrier being confirmed automatically. It is off by default, so the checkout does not change until you turn it on. Update: install the new zip over 1.3.2, your settings are kept.
What’s new in version 1.3.2 (2026-11-05): Mollie’s integrated card form (Mollie Components) now pays directly in the checkout, without redirecting to Mollie’s payment page; “Save card” and “Use saved card” are passed on. Update: install the new zip over 1.3.1, your settings are kept.
What’s new in version 1.3.1 (2026-10-30): with a pickup-point carrier (Colissimo Pickup Points…), the shipping step stays open and payment locked until a pickup point is chosen; Mollie’s Express checkout block (Apple Pay, Google Pay, PayPal) shows at the top of the payment step; two new colors (checkout background, block background); gift wrapping fee shown next to the checkbox; spacing fixed on custom themes (checkboxes, step titles, pickup-point button). To update: install the new zip over 1.3.0, your settings are kept.
What’s new in version 1.3.0 (2026-10-29): PrestaShop 9.1 compatibility (the checkout no longer loaded), discount codes applied again on PrestaShop 9, State/Province field for the United States, Spain, Italy, Canada…, typed data kept when the country changes, protection against double clicks on “Place order”, payment amount updated after a discount code, clear messages on network loss or expired session, gift wrapping kept, interface translated into 8 languages (FR, EN, ES, DE, IT, PT, PL, NL). Verified on PrestaShop 8.2.1 (Classic theme) and 9.1.5 (Hummingbird theme). To update: install the new zip over the old one, your settings are kept.
General configuration
Colors
Five colors are configurable in the module settings:
- Primary color — buttons, links, active states, selected radios (default
#1a73e8). - Button hover color — hover state of primary buttons like “Continue” and “Place order” (default
#1559b8). - Accent / success color — completed-step indicators, applied-discount pill, the carrier’s “Free” label, success messages (default
#008060). - Checkout background color — page background behind the steps and the summary (default
#fafbfb, very light grey). It covers the full page width, the theme’s own container included. - Block background color — background of the step blocks, the order summary and the header bar (default
#ffffff, white).
All five are injected as CSS variables (--dfsc-primary, --dfsc-primary-hover, --dfsc-success, --dfsc-page-bg, --dfsc-bg) and validated by a strict hexadecimal regex: an invalid value falls back to the default color.
Logo
Provide a custom logo URL for the checkout header; the shop logo is used as a fallback. Rendered size: up to 190×42 px.
Distraction-free mode
The Hide theme header & footer option (enabled by default) removes your theme’s full header (menu, search, cart) and footer on the /order page only. The implementation overrides the Smarty header and footer blocks in our template: on a theme that doesn’t use these standard blocks, the option is simply a no-op — never a blank page.
Shipping method confirmation
By default, the checkout confirms the carrier preselected by PrestaShop automatically: the shipping step shows as done and collapsed, and the customer lands straight on payment. If the choice of carrier matters to your customers (store pickup, express delivery, pickup point…), turn on Customer must confirm the shipping method (version 1.3.3 or later):
- the shipping step stays open with the carriers listed, and the preselected one stays checked;
- the payment step stays locked until the customer clicks “Continue to payment”;
- the choice is then kept for that cart, even if the page is reloaded; a new cart asks again;
- carts with only virtual products have no shipping step and are not affected.
The setting is off by default, on install and on update.
Other options
- Seller note field (on/off)
- Discount code field (on/off)
- Gift wrapping: when the option is enabled in PrestaShop, the fee shows next to the checkbox (tax incl. or excl. as configured) and the “Gift wrapping” line appears in the summary
- Trust badges — free HTML displayed below the summary
- Legal links in the checkout footer (Terms, Privacy, Returns — detected via native CMS roles)

Google social login
Create the credentials
- Go to Google Cloud Console and create (or select) a project.
- In APIs & Services → Credentials, create an OAuth client ID of type Web application.
- In Authorized JavaScript origins, add your shop URL (e.g.
https://www.myshop.com) — no path, https protocol. - Copy the generated Client ID (ends with
.apps.googleusercontent.com).
Configure the module
- In the module settings, enable Google Sign-In and paste the Client ID.
- Save, then clear the cache.
- On
/order, the Google button appears above the “I am a new customer / I already have an account” tabs.
The flow: the customer clicks, selects their Google account, and the module receives a JWT which it validates server-side via the official tokeninfo endpoint (checking audience, issuer, expiry and verified email). If a customer account exists with that email, they are logged in; otherwise an account is created automatically using the Google profile’s first and last name.
Facebook social login
Create the app
- On Meta for Developers, create a Consumer-type app.
- Add the Facebook Login product and declare your domain in the settings.
- Grab the App ID and App Secret from Settings → Basic.
Configure the module
Enable Facebook Login in the settings, paste the App ID and App Secret, save. Server-side validation is two-step: debug_token (verifies the token belongs to your app) followed by profile retrieval signed with appsecret_proof (HMAC-SHA256). The App Secret never leaves your server.
Google Places address autocomplete
- In Google Cloud Console, enable the Places API and Maps JavaScript API.
- Create an API key and restrict it to your domain (recommended).
- In the module, enable Address autocomplete and paste the key.
The form’s “Address” field then offers suggestions while typing. Selecting a suggestion pre-fills street, complement, city, postcode, country and region where applicable. Suggestions are restricted to your shop’s active countries (up to 5 countries — a Google API limit).
The Places API is billed by Google beyond the monthly free quota. For a moderate-volume shop, the free quota is usually sufficient.
Country-aware address form
The address form automatically adapts to the selected country:
- The dropdown’s default country is the one configured in International → Localization of your back-office (not the alphabetically first country).
- The State/Region field only appears for countries that have states (US, Spain, Italy…), and its dropdown lists only the active regions of the selected country.
- The DNI field appears for countries that require it (Spain).
- Postcode validation uses the country’s format.
- On country change, the page reloads with the form restructured for the new country.
Address editing
Each saved address shows a pencil icon. Clicking it opens the inline form pre-filled with all the address values (loaded server-side with an ownership check — a customer can never view another customer’s address). Saving updates the existing address without creating a duplicate.


Discount code
The (optional) discount code field works over AJAX: apply and remove without reloading, with instant summary refresh. The code is checked with exactly the same rules as PrestaShop’s native cart (CartRule::checkValidity): dates, minimum amount, carrier, country or group restrictions, combinations. Native error messages (“This voucher has expired”, “Minimum amount not reached”…) are surfaced as-is.

Carrier compatibility and Colissimo
Carrier extra content (Colissimo pickup-point map, Mondial Relay widget…) is rendered via {$carrier.extraContent} exactly like the native template. The shipping step is only validated once the carrier module accepts it, exactly like the native checkout (actionValidateStepComplete hook).
- No pickup point chosen (Colissimo Pickup Points, Mondial Relay…): the shipping step stays open with the pickup-point button, and the payment step stays locked. The carrier’s message (“Please select a pickup-point or choose another shipping option”) only shows if the customer clicks “Continue to payment” without a point.
- Point chosen: payment opens and stays open after a page reload. For Colissimo, the saved point is read back automatically (id and mobile phone): the customer does not have to pick it again.
- Carrier change: if the customer switches from a regular carrier to a pickup-point carrier, the shipping step reopens until a point is chosen.



Mollie express payment (Apple Pay, Google Pay, PayPal)
Since version 1.3.1 the module renders the native payment-step hooks. Mollie’s Express checkout block (Express Component: Apple Pay, Google Pay, PayPal) therefore appears at the top of the payment step, above the payment methods. Its buttons stay locked until the terms are ticked, then Mollie checks the cart before the payment.
- Enable the block in the Mollie module (Express checkout settings). Mollie only shows it in live mode, and Apple Pay only appears in Safari (iPhone, iPad, Mac) with a domain verified at Mollie.
- Mollie’s Apple Pay Direct buttons on the product and cart pages do not go through the checkout: they work as they are.
Mollie integrated card form
With Mollie’s integrated credit card form option enabled (Mollie Components), the card fields show in the payment step and the card is paid directly from the checkout: when the customer clicks “Place order”, Mollie creates a secure card token and sends it with the order, without redirecting to Mollie’s hosted payment page.
- Mollie one-click payments work too: “Save card” and “Use saved card” are passed on to Mollie.
- Requires version 1.3.2 of the module: before this fix, the customer was sent to Mollie’s payment page and had to enter the card again.
Developer hooks
displayDfsimplecheckoutExpress— slot at the top of the checkout for express payments (Apple Pay, Google Pay, PayPal Express).displayDfsimplecheckoutSidebarTop/displayDfsimplecheckoutSidebarBottom— injection zones in the summary column.actionDfscSocialLogin— fired after a successful social login, withcustomeranddfsc_social_provider(googleorfacebook) parameters. Useful for CRM tagging.- Native checkout hooks, rendered at the same place as in the native templates (1.3.1):
displayPaymentTop(top of the payment step),displayCheckoutBeforeConfirmation(between the terms and “Place order”),displayBeforeCarrieranddisplayAfterCarrier(before and after the carrier list).
Troubleshooting
The Google button doesn’t show
- Check the Client ID is filled in and the option enabled.
- Check the browser console for an “origin not allowed” error — if present, add your shop’s exact URL (with https, no trailing slash) to the Authorized JavaScript origins in Google Cloud Console.
Social login doesn’t persist
Clear the PrestaShop cache and the browser cache. If the issue persists, check that no third-party security module invalidates session cookies after login.
The State field shows the wrong regions
Make sure you run module version 1.3.0 or later, which resolves the form structure server-side for each country.
Payment opens although no pickup point is chosen
Update to version 1.3.1 or later: the shipping step then stays open until the carrier module validates the pickup point.
Mollie card payment redirects to Mollie’s payment page
Update to version 1.3.2 or later: the integrated card form then passes the card to Mollie from the checkout. If the problem persists, clear the PrestaShop cache and check the browser console for a JavaScript error that stops Mollie’s script from loading.
The shipping step completes on its own
This is the default behaviour: the preselected carrier is confirmed automatically. To let the customer choose, update to version 1.3.3 or later and turn on “Customer must confirm the shipping method” in the module settings.
Blank page on /order
Enable PrestaShop debug mode (_PS_MODE_DEV_) to reveal the error, or check var/logs. Verify no other one-page checkout module is active at the same time.
Uninstall
Uninstall the module from the Module Manager. The runtime environment is released immediately and the native 5-step checkout is restored. No residual files, no orphaned data.