[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]  James Kemp [@jamesckemp](/creator/twitter/jamesckemp) on x 4358 followers Created: 2025-07-21 10:20:53 UTC I asked Grok to summarise the responses to this post, and these were the results. What do you think? X. Admin/Dashboard and User Experience Improvements (Most frequent theme, ~10 mentions) - Unify scattered WooCommerce menus (e.g., Products, Payments, Analytics) under a single WooCommerce menu for clarity, especially for new users. - Create a more WooCommerce-focused admin experience, feeling like logging into a “Woo store” rather than a WordPress site with Woo add-ons; include a separate merchant dashboard from wp-admin. - Simplify the home dashboard to reduce overwhelm (e.g., hide or streamline “Things to do next,” Inbox, and Stats for new/experienced users). - Provide a unique product creation UI instead of relying on a modified WordPress post/page editor. - Make editing product variations less “torturous.” X. Performance, Updates, and Stability (~8 mentions) - Reduce update frequency (e.g., to once a year) to minimize testing and crashes. - Introduce a Long-Term Support (LTS) channel for merchants who don’t need frequent new features, avoiding monthly untested updates. - Improve overall speed and allow disabling backward compatibility on new stores for better performance. - Prevent breaking changes in updates (e.g., settings/analytics broken after version 9.9.3 due to marketplace connection). - Separate WooCommerce tables from core WordPress data to handle large order volumes better (noted as resolved in newer versions). X. API, Extensibility, and Integrations (~8 mentions) - Update the API to allow creating/processing orders via third parties, including exposing shipping data (e.g., for real-world scenarios like phone orders or events) and standards for third-party plugins (e.g., couriers, weight-based shipping. - Improve hooks for coupons (currently insufficient and hard to follow). - Enhance API-driven purchase flows for better flexibility. - Add support for custom endpoints and integrations like trustless cross-chain crypto swaps (e.g., pay in any token via protocols like SilentSwap). - Fix shipping rate caching issues that can brick checkouts. X. Blocks, Cart, and Checkout Enhancements (~6 mentions) - Make Cart and Checkout blocks fully backward-compatible and extensible via PHP, without losing Woo’s open extensibility (avoid locking down like Shopify). - Finish “blockification” work and add Interactivity API for near-instant cart-to-checkout transitions. - Improve documentation for blocks (currently poor). X. New Features and Additions (~10 mentions) - Add min/max quantities, custom user roles (e.g., Customer A/B with pricing, show/hide products), and tiered pricing tables. - Include invoicing features. - Global customer profiles with quick checkout across stores. - Multi-currency support in core. - Allow optional blocks in product descriptions with access to patterns. - Improve product image gallery to avoid duplicates when selecting from gallery. - Improve product editor. X. Analytics, Reporting, and Marketplace (~5 mentions) - Enhance built-in analytics/reporting (currently too basic and resource-intensive; users often switch to alternatives like Metorik). - Organize the Woo marketplace by contribution to GMV (Gross Merchandise Value) and use value metrics for extensions; stop Woo competing in its own marketplace. - Prefix dependencies in official extensions (e.g., UPS, USPS) to avoid conflicts. X. Onboarding, Hosting, and Education (~5 mentions) - Revamp initial setup: Allow selecting a business type for auto-configuration. - Relaunch Woo Express with easy sign-up, scalability (e.g., CDN, caching), bundled plugins, and onboarding; create educational videos using blocks for building stores. - Easy activation of WooPlus features via core placeholders, pre-activated in WooExpress. X. Payments and Other (~3 mentions) - Avoid locking down payments (e.g., WooPayments limits access to Stripe’s full APIs, features like delayed charges, fraud tools). - No removals suggested, except one user said “nothing as such.” XXXXX engagements  **Related Topics** [clarity](/topic/clarity) [coins analytics](/topic/coins-analytics) [woocommerce](/topic/woocommerce) [mentions](/topic/mentions) [Post Link](https://x.com/jamesckemp/status/1947240354677248385)
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
James Kemp @jamesckemp on x 4358 followers
Created: 2025-07-21 10:20:53 UTC
I asked Grok to summarise the responses to this post, and these were the results. What do you think?
X. Admin/Dashboard and User Experience Improvements (Most frequent theme, ~10 mentions)
X. Performance, Updates, and Stability (~8 mentions)
X. API, Extensibility, and Integrations (~8 mentions)
X. Blocks, Cart, and Checkout Enhancements (~6 mentions)
X. New Features and Additions (~10 mentions)
X. Analytics, Reporting, and Marketplace (~5 mentions)
X. Onboarding, Hosting, and Education (~5 mentions)
X. Payments and Other (~3 mentions)
XXXXX engagements
Related Topics clarity coins analytics woocommerce mentions
/post/tweet::1947240354677248385