Written by DROPS.ST.
WooCommerce software and WooPayments are different parts of a shop. The ability to use the open-source commerce plugin does not mean the WooPayments service accepts your CBD business, or that every host and extension supports the catalogue. Check the software, hosted services and payment arrangement separately.
DROPS offers another model: a hosted shop with catalogue, BTC/XMR checkout, order records and customer tools together. Compare that complete buying path with the specific WooCommerce setup you could operate, including the services your products actually qualify to use.
Know which decision each provider controls
WooCommerce's highly regulated products guidance distinguishes use of the open-source plugin from direct services offered by Automattic. It also directs CBD merchants to separate CBD guidance. Do not apply a broad regulated-products summary without checking that product-specific page.
The practical separation looks like this:
| Layer | What it does | Question for a CBD merchant |
|---|---|---|
| WooCommerce core software | Provides commerce functionality within WordPress | Can the proposed implementation handle the required shop tasks? |
| Hosting | Runs the website | Does this host support the exact products and selling locations? |
| Payment service | Handles the agreed payment route | Has this business and catalogue been approved? |
| Extensions and connected services | Add functions such as shipping or reporting | Do their own policies and dependencies permit this use? |
A functioning checkout page can exist before the commercial payment arrangement is resolved. Treat that as incomplete setup, not launch readiness.
WooPayments has an explicit CBD restriction
The official WooPayments CBD policy states that CBD and other hemp-derived products cannot be sold using WooPayments because of restrictions imposed by its payment processor. That is a service-specific statement, not a claim that the open-source WooCommerce plugin universally bans CBD shops.
Check this policy directly when evaluating the service. A forum account of a successful store, an old agency article or a payment plugin appearing in an extension list does not override the current provider terms.
These official pages were checked on 10 October 2026. Product rules can change, so confirm the arrangement for the exact business before purchasing implementation work.
Hosting and CBD-specific guidance add another layer
WooCommerce's CBD and hemp-derived product guidance describes conditions for stores hosted on WordPress.com or Pressable, including specified payment providers and geographic scope. It also distinguishes self-hosted use and particular product categories.
Read the full scope rather than treating the named providers as automatic approval. Ask the intended host and payment provider to confirm the exact catalogue and location. There is no need to turn that enquiry into a general debate about whether CBD is accepted everywhere: you need an answer for the setup you plan to buy.
Likewise, a shipping label service being available does not by itself establish that a carrier accepts the shipment. Keep the operational services in the comparison instead of stopping at the software licence.
Compare one realistic shop scenario
Consider an illustrative merchant with 80 product listings, two staff members and regular repeat orders. Their comparison should include moving products, prices and images; showing the right pack information; taking a supported payment; identifying order status; and helping a returning customer find a previous item.
In DROPS, assisted catalogue migration and customer accounts address parts of that workflow. Existing customer and historical order migration need a separately confirmed scope. Do not assume that moving product images also transfers every past record.
Use our WooCommerce alternative guide for the connected-shop comparison, and operating-cost guide to include the work between services.
Explore DROPS with your real catalogue and payment requirements. Compare a complete order from selection through fulfilment, with each provider's role understood and the ongoing workload visible.