WooCommerce One Page Shopping eCommerce is a WordPress plugin that removes the separate checkout step from a WooCommerce store. When a shopper adds an item to the cart, the cart and checkout fields appear at the bottom of the same page, so the purchase can be completed without a page reload or a redirect. It is built for store owners who believe the standard WooCommerce funnel loses sales at the final step and want a shorter path to payment.
The plugin is sold on CodeCanyon for $20 by the developer optart, and it has accumulated 2,310 sales with a 4.33 out of 5 rating across 40 reviews. Those numbers place it among the more established single-purpose WooCommerce extensions on the marketplace, which matters when judging whether a small plugin will still be maintained.
What the plugin actually changes on a store
The core behaviour is straightforward: checkout is embedded rather than linked. On a product page, selecting the add-to-cart button reveals the cart contents and the full checkout form directly below, without navigating away. The shopper fills in billing and payment details in place and completes the order. For stores selling a small number of items, or items where the decision is already made by the time the product page loads, this removes an entire step from the funnel.
What separates this from a simple “checkout on product page” tweak is the level of control over where the cart and checkout appear. The settings screen sits under WooCommerce in the WordPress admin and is divided into three panels: product settings, shop page settings and category settings. Each panel contains independent toggles for displaying the cart, the checkout, or both. That means a store can show the checkout on individual product pages while leaving the shop archive as a normal browsing grid, or the reverse.
Scope can also be narrowed per item. Individual products have their own One Page Shopping panel inside the product editor, and product categories have equivalent controls for cart and checkout display. A store that only wants one-page checkout on a single flagship product, or on one category of low-consideration goods, can configure exactly that without affecting the rest of the catalogue.
The plugin exposes shortcodes, including an add-to-cart alternative and a product shortcode, so the cart and checkout blocks can be positioned manually rather than only through the automatic placement. There is also a section shortcode for outputting the checkout in a specific location. These are useful when a theme or page builder controls the layout and the automatic injection point is not where the store owner wants the form to sit.
Elementor and Elementor Pro are listed as compatible, which is significant because page-builder templates frequently override WooCommerce’s default hooks. Payment gateway compatibility is claimed for Stripe specifically, and the changelog shows repeated work on gateway and third-party plugin conflicts. Browser support covers Chrome, Firefox, Safari, Edge, Opera and IE11.
Where one-page checkout fits, and where it does not
The strongest fit is a store with a narrow, high-intent catalogue: a single product, a handful of variants, or a small range where most visitors arrive already knowing what they want. Digital goods, event tickets, memberships and simple physical products all suit this pattern, because the shopper does not need to compare options mid-checkout. Stores running paid traffic to individual product landing pages also benefit, since the ad click and the purchase can happen on the same screen.
Freelancers and agencies building client stores on a fixed budget are a natural audience. At $20 with a one-time licence, the plugin is cheaper than commissioning custom checkout templates, and the per-product and per-category overrides mean a single installation can serve a mixed catalogue without forcing one-page checkout on every item.
It is the wrong choice for stores that rely on a long consideration phase. If customers routinely add several products, compare quantities, apply coupons and adjust shipping before paying, collapsing the cart and checkout into one page can make the order summary harder to read and the editing process clumsier. High-volume stores with complex shipping rules, multi-step checkout requirements, or checkout fields added by other extensions should also be cautious, because every additional plugin that hooks into the checkout form is a potential conflict.
Strengths and limitations
Strengths
- Removes the redirect to a separate checkout page, which is the single largest structural change a store can make to shorten the purchase path.
- Granular placement controls at shop, category and individual product level, rather than an all-or-nothing switch.
- Shortcodes allow the cart and checkout to be positioned manually when automatic placement does not suit the theme or page builder.
- Elementor and Elementor Pro compatibility is explicitly declared, which is uncommon for plugins of this size.
- Stripe compatibility is stated, and the changelog shows a history of gateway and third-party plugin fixes.
- Works in a basic mode without configuration, so a store can test the concept before investing time in per-product settings.
- Established sales history and a public changelog stretching back several years.
Limitations
- The last vendor update was September 2021. The declared compatibility ceiling is WordPress 5.8.x and WooCommerce 5.1.x, so stores running current WordPress and WooCommerce releases are outside the tested range. The vendor does not state whether newer versions are supported.
- The vendor explicitly warns that conflicts with other WooCommerce plugins are possible and names the Booked WooCommerce plugin as a reported case. There is no compatibility matrix, so conflicts surface only after installation.
- Gutenberg optimisation is listed as “No”. Block editor support has been patched historically, but the plugin is not positioned as block-native.
- The rating sits at 4.33 from 40 reviews, meaning roughly one in five reviewers found something to criticise. That is a healthy sample but not a flawless record.
- Checkout fields are generated by the plugin, so extensions that add custom fields to the standard WooCommerce checkout may not render correctly in the embedded form.
- Source files are included (JavaScript, CSS and PHP), but there is no indication of developer documentation beyond the settings screen and demo.
How it compares with the wider category of checkout optimisation tools
Alternatives to this plugin fall into three rough groups. The first is full one-page checkout themes and theme add-ons, which bundle the same behaviour into a larger purchase and lock the store into that theme’s markup. The second is checkout field editors and checkout managers, which reorganise the existing checkout page but keep it as a separate step. The third is custom development, where a developer hooks into WooCommerce to render the checkout template on product pages.
Against theme-bundled solutions, this plugin is narrower and cheaper, and it does not dictate the rest of the site’s design. Against checkout field editors, it solves a different problem: those tools improve the checkout page, while this one removes the need to visit it. Against custom development, it is faster and cheaper but less flexible, and it inherits whatever limitations the vendor has built in.
The trade-off is maintenance risk. A bespoke implementation can be updated by the same developer who built it. A $20 plugin depends on the author continuing to release compatibility patches. Buyers weighing this product should treat the 2021 update date as the central question, not the feature list.
Frequently Asked Questions
Does WooCommerce One Page Shopping work with the latest WooCommerce version?
The vendor does not confirm support beyond WooCommerce 5.1.x, which is the highest version listed in the compatibility data. The plugin was last updated in September 2021. Stores running newer WooCommerce releases should test thoroughly on a staging site before deploying, because untested combinations can break the embedded checkout form or the add-to-cart trigger.
Can the cart and checkout be shown on some products but not others?
Yes. Each product has its own One Page Shopping panel in the product editor, and each product category has equivalent display controls. The global settings under WooCommerce define the default behaviour for shop and category pages, while the per-product and per-category settings override that default for specific items. This allows a mixed catalogue to use one-page checkout selectively.
Does it replace the standard WooCommerce checkout page entirely?
No. The standard checkout page remains in place and still functions. The plugin adds an embedded cart and checkout to the pages selected in its settings, so shoppers can complete an order without leaving the product or shop page. Whether the original checkout page is ever reached depends on how the theme links to it and how the store is configured.
Is the plugin compatible with Stripe and other payment gateways?
Stripe compatibility is explicitly stated by the vendor, and the changelog records specific fixes for Stripe and for payment gateways generally. Other gateways are not individually listed. Because the checkout form is generated by the plugin rather than by WooCommerce’s default template, any gateway that injects scripts or fields into that form should be tested before going live.
Verdict
This plugin is worth buying for store owners running a small, focused catalogue who want to test whether removing the checkout redirect improves completion, and for agencies who need a cheap, configurable way to deliver one-page checkout on a client project without custom development. The per-product and per-category overrides make it more flexible than most single-purpose checkout plugins at this price.
It is not the right purchase for stores on current WordPress and WooCommerce releases that need guaranteed compatibility, nor for catalogues with complex multi-item carts, intricate shipping logic, or several extensions already modifying the checkout. The 2021 update date is the deciding factor: buyers who cannot tolerate an unsupported plugin, or who are unwilling to test conflicts on staging first, should look at actively maintained alternatives or budget for custom work instead.
