Alternative Commerce or WooCommerce for a content-led online store
If you are choosing between Alternative Commerce and WooCommerce for a store with reviews, guides and curated selections, start with the relationship between content and products. WooCommerce on WordPress may be enough for a conventional blog with embedded products. When content forms a separate knowledge base with complex relationships, it is worth testing an implementation on Drupal with Alternative Commerce — using your editorial workflow, not a presentation.
Consider a hypothetical situation: an equipment supplier adds recommended models to a pump selection guide, then replaces one of them. Manually changing the price in several articles creates a risk of inconsistencies. You need a system in which the explanation leads to an up-to-date product without creating a second version of the catalog inside the blog.
What we are comparing: the commerce solution and the CMS together
Alternative Commerce is an online store solution built by GL.ua on Drupal, while WooCommerce adds commerce to WordPress. You need to compare the complete implementation: the CMS, commerce components, theme, editor, integrations and support. A platform name alone does not confirm that the required process is already configured.
The core Alternative Commerce module is called Drupal AlternativeCommerce (Basket). The official Basket project page explicitly describes it as an alternative to Drupal Commerce. These are different commerce projects: Drupal Commerce documentation or extensions are not evidence of Basket's capabilities. Likewise, Drupal's ability to link content does not mean that a particular distribution includes a ready-made interface for editorial selections.
Separate core features, additional modules and custom development in the proposal. Without this distinction, you cannot assess the scope of work or support requirements.
When a content catalog really affects the choice
The deciding factor is not the number of articles, but the complexity of relationships and day-to-day changes. If content simply accompanies products, consider WooCommerce without prejudice. If a single reference resource feeds many pages and editors manage different content types, Drupal provides tools for building a structured model.
In Drupal, reference fields can link content and other entities: for example, “guide → equipment series → products.” Selection and display rules need to be designed. Basket works with multiple content types and has its own price field. However, explanatory content and an item for sale do not necessarily need to be combined: they have different lifecycles.
WooCommerce documents product blocks and shortcodes for displaying products. For example, a selection can be based on SKU, category or attribute. This kind of embed is often sufficient for a review featuring recommended items. However, a two-way relationship with a reference resource, a complex approval process or separate permissions for editing it must be assessed as part of the complete solution, rather than promised as automatic features.
A controlled content model and free-form page composition solve different problems. Decide where an editor should select a relationship in a field and where they should place an embed in the text themselves.
Compare practical criteria, not plugin counts
Evaluate each option using the same products and editorial content. The table below sets out verified capabilities and implementation questions, rather than declaring a winner. A feature's availability in an ecosystem does not mean it is compatible with your site.
| Criterion | Alternative Commerce on Drupal | WooCommerce on WordPress | What to check |
|---|---|---|---|
| Product foundation | Basket works with Drupal content types and its own price field. | Simple, grouped and variable products are documented. | How your product model appears on the product page and in the cart. |
| Relationship with an article | Drupal reference fields provide a foundation for structured relationships. | Product blocks and shortcodes let you display products within content. | Who selects the product and how the block changes after the product is updated. |
| Custom reference resource | Content types, fields and views need to be designed. | A complex model needs to be assessed with the required extensions or custom code. | Whether the relationship is maintained without duplicating data. |
| Extending commerce functionality | Basket has a plugin mechanism for extending the module. | The solution includes WooCommerce, the theme and the selected extensions. | The versions, support and owner of each custom component. |
| Updates | The team must agree on checks for Drupal, Basket and all dependencies. | The official documentation recommends a backup and testing updates on a staging copy. | Whether content, the cart and payments work after the entire stack is updated. |
Business needs determine how much weight each criterion carries: editing speed matters for seasonal pages, while control over relationships matters for a technical reference resource. If the model has not yet been defined, first organize your product catalog structure.
How to test the path from a guide to an order
Ask to see a content change and its consequences for the customer, not a finished homepage. The demonstration should cover product selection, a change in product status and a purchase from an editorial page. This will show whether content is connected to the catalog at a system level or merely links to it manually.
The editor changes a selection without duplicating the price
The editor should select a product from the catalog, not copy its price into the text. The name, link and required commerce data in the embed should come from an agreed source. The contractor should show how the block behaves if the product is unavailable or hidden.
In our hypothetical example, change the pump's name, then remove it from sale. Check the article on a mobile screen. Agree on the outcome in advance: hide the item, explain its unavailability or show a specified replacement. An arbitrary alternative product could undermine the recommendation.
The customer gets the exact variant they selected
A link from the content should lead to a clear product page or add the agreed product to the cart. If a model has variants, the reader must be able to select the right one rather than receive an arbitrary configuration. Verify this with an end-to-end test, including the order data.
- Create a guide, a product and a product variant on a test site with the intended set of components.
- Add a recommendation using the editor role and check which fields that role can change.
- Change the product data, clear the cache or wait for it to refresh according to the agreed rule, and check the embed.
- Follow the path from the content to the cart and a test payment; check the SKU, variant and quantity.
- Repeat the workflow after updating the components on a staging copy and record the result.
The outcome of this test is a verified editorial-to-commerce workflow, not a promise that “anything can be added later.” Include it in the technical specification for the online store as an acceptance criterion.
SEO, performance and editor permissions
Neither platform delivers better SEO or speed on the strength of its name alone. Check which pages a specific implementation creates and what it loads when someone views an article. Editorial permissions should allow people to work on explanatory content without granting unnecessary access to commerce functions.
For SEO, distinguish the intents: a guide answers a question, a category helps people choose a product group, and a product page describes an item. Require clear URLs, manageable metadata and rules for duplicates. If a product block creates additional URLs, find out which of them will be indexed.
Test performance on the complete build: with the actual theme, images, analytics and required extensions. Compare reading a guide and opening the cart in the agreed mobile scenario. Find out when the product embed's cache refreshes: an old price in an article and a new one in the cart create a trust problem, even if each page loads quickly on its own.
For security, test actions under different user accounts: an editor does not need access to customer orders just to embed a product. A catalog import must not overwrite an editorial conclusion. Both requirements need to be implemented in the permissions and integration settings.
Who is responsible for compatibility after launch?
Responsibility for the entire store must be defined separately from module support. Fixing one component does not replace testing your particular combination. Agree on who reproduces an error and restores the working workflow.
The official WooCommerce documentation recommends making a backup before an update and testing the changes on staging — a test copy of the site. Checks cover WooCommerce, WordPress, the theme, extensions and payment gateways. A Drupal solution with Basket also needs an agreed process for checking all its components; using a ready-made distribution does not eliminate the need for support.
Define the boundaries of responsibility for compatibility: who monitors updates, tests workflows and resolves conflicts. The integration owner must monitor product mapping and report missing relationships.
What determines the implementation timeline and budget?
The timeline depends on the catalog model, content readiness and the number of custom relationships, not just CMS installation. The budget must cover configuration, development, testing and ongoing maintenance. Comparing the cost of core components without this work does not reveal the cost of a finished store.
The sequence of work is: content structure and data sources → editor and embed prototype → templates → migration and integrations → end-to-end tests. Older articles with manually entered prices require a separate decision: which parts to convert into relationships, edit or retain as historical explanations.
Break out data modeling, design, CMS and commerce configuration, custom modules, migration, testing and editor training in the estimate. Licenses for selected extensions, hosting, backups and support may be separate costs. A free foundation does not mean free implementation, but a paid extension is not necessarily worse than custom code either: compare functionality, updates and the person or team responsible.
Which option belongs on your shortlist?
Keep WooCommerce on the shortlist if WordPress suits the team and product blocks meet its editorial workflow needs. Test Alternative Commerce on Drupal if the main requirement is structured content and controlled relationships with the catalog. The final choice should be validated by the same demonstration task, not a feature list.
- The editor adds a product without manually duplicating its price and SKU.
- A change in product status produces a predictable result across all related content.
- The customer reaches the right variant and completes the order correctly.
- Permissions, caching and imports do not break editorial relationships.
- The cost and the party responsible for testing after updates are defined before commissioning the work.
GL.ua (Glyanets) develops online stores and online catalogs; Alternative Commerce is its Drupal solution. If you are planning a catalog in which guides and curated selections need to work alongside sales, discuss online store development with GL.ua using your own content and products as examples. The next useful step is to agree on a prototype of the relationship between them and the scope of work needed to implement it.
Frequently asked questions
Do you need to migrate an existing blog to WordPress to add a store?
Not necessarily. First check whether WooCommerce meets the required commerce workflow on the existing site and whether its components can be maintained. Consider migration only after identifying specific limitations, together with the work needed on content and URLs.
Can you keep an expert article if a recommended product has been discontinued?
Yes, if the explanation remains useful and its conclusions are still valid. Agree separately on how the product block should behave and on an editorial review of the recommendation. You do not need to delete the entire article simply because the product range has changed.
What should you give a contractor if there is no technical specification yet?
Prepare examples of a standard article, a complex guide and the related products. Add a description of who edits them and what changes when the product range is updated. These are inputs for discussing the model, not a replacement for an agreed technical specification.
Does a product have to be added to the cart directly from an article?
No. Linking to the product page may be better if the customer needs to choose a configuration or read the terms. Agree on this path in the prototype. A quick-purchase button is appropriate only where it does not hide an important choice.
Is it worth tracking clicks from guides to products?
Yes. This helps you assess whether readers use the recommendations. Agree on the click event and analyze subsequent actions in the store separately. A click alone does not prove a sale and is not a promise of increased conversion.
Just one step to your perfect website



