WooCommerce REST API v3
Planned source for approved catalog and store-management records.
- Products & categoriesPlanned
- Attributes & variationsPlanned
- Prices & stockPlanned
- Webhooks & connection healthValidation required
Planned integration
Bring AI-guided shopping to WooCommerce without replacing WordPress, checkout, payments, or merchant control. Join early access to help shape the catalog, variation, cart, and reporting architecture before release.
Current foundation
Shopify-first product
Core assistant, merchant portal, catalog intelligence, and cart experience.
Planned connector
WooCommerce mapping
Products, variations, Store API cart behavior, and secure authentication.
Early access
Compatibility cohorts
Theme, plugin, product-type, and checkout validation with selected merchants.
General availability
Release after validation
No public date until catalog, cart, security, and reporting pass production review.
01 System Blueprint
The planned connector separates authenticated store-management data from customer-facing cart and session behavior. WardrobeIt will use the appropriate WooCommerce interface for each job rather than treating every API flow as interchangeable.
Planned source for approved catalog and store-management records.
Planned customer-facing path for current-session product, cart, and checkout behavior.
Products, cart validation, taxes, shipping, payment, orders, and fulfillment stay in WooCommerce.
Natural-language requests become catalog criteria, explanations, and valid purchase options.
No competitor products, invented variants, unsupported offers, or silent product substitutions.
02 Early-Access Readiness
The intended merchant experience will keep technical checks visible without pretending the connector already exists. Each gate must pass engineering validation before a store can move from interest to connection.
WooCommerce readiness scan
Store profile
yourstore.com
Early-access review
This preview collects technical context only. It does not connect a store, create credentials, test live endpoints, or confirm compatibility.
Identify the WordPress and WooCommerce environment before requesting access.
The final release may use approved REST API credentials, a managed component, or an enterprise implementation.
Store-management permissions stay separate from shopper-session cart security.
Confirm product access, variation structures, pagination, and safe error handling.
Theme, plugin, cart, checkout, security, and reporting dependencies must be documented.
03 Catalog Intelligence
The planned connector will organise approved products, attributes, variations, prices, and stock into merchant-specific profiles. Missing information becomes a readiness issue, not an invitation for the AI to guess.
One parent product can contain many variation combinations that must map correctly before any cart action.
product_type: variable
attributes: color, size
variations: 12 records
price: variation-level
stock: current sync state
images: parent + variation
Product profile
04 Storefront Choreography
The future experience should preserve the shopper’s current WooCommerce session. Product discovery changes nothing until the shopper confirms a real product, valid variation, and quantity.
I need an elegant neutral dress under $200 in Medium.
I’ll search this store’s catalog and check the available product and variation information.
Match reasons and product facts stay grounded in approved WooCommerce data.
View planned resultPlanned WooCommerce experience
Choose a valid size and colour before the product can move to cart.
Size
Colour
No live cart action yet
The selected product and variation are ready for the approved WooCommerce cart flow.
WooCommerce keeps final authority over availability, coupons, taxes, shipping, payment, order creation, and fulfilment.
Store API validation required
05 Merchant Control
WooCommerce support should inherit WardrobeIt’s catalog-only principle and merchant knowledge boundaries, while every platform-specific control remains marked as planned until the connector is released.
Merchant Portal · Governance
Shopper relevance — Commercial priority cannot override product truth.
Products, categories, attributes, and variations.
Facts, sizing, care, policies, and approved answers.
Commercial priority cannot override product truth.
Variation confirmation, quantity, and safe actions.
No invented prices, stock, claims, or exceptions.
Catalog-only preview
Silk Occasion Dress · Ivory · M
Approved WooCommerce record — no substitution
Intended product and category controls will depend on the released WooCommerce connector.
Do not promise bulk category permissions or variation-level control before implementation.
Seasonal, campaign, and selected-product priorities must preserve shopper relevance and valid availability.
No autonomous margin ranking or hidden commercial override.
WardrobeIt can use merchant-approved facts and policies, but WooCommerce-specific ingestion must be validated.
Missing information produces a safe limitation, not an invented answer.
Protected cart actions and any offers must use merchant-approved rules and current-session security.
Margin-aware offers and autonomous promotions remain future capabilities.
06 Pre-Flight Observatory
WooCommerce stores vary across themes, plugins, product types, currencies, caches, security tools and checkout extensions. The launch needs a tested compatibility matrix and transparent analytics definitions.
Compatibility Radar
Measurement Ledger
Each metric needs its own data source, definition and status.
Security principles for the planned connector
Least privilege, secure credentials, merchant-specific data boundaries, protected cart sessions and merchant-safe error handling.
07 Questions Before Early Access
The page is intentionally direct about what exists, what is planned, and what still needs platform-specific validation.
Join WooCommerce Early AccessNo. WardrobeIt is currently Shopify-first. This page explains planned architecture and early-access readiness without claiming a live connector or downloadable WordPress plugin.
The planned integration may use authenticated REST API access for approved store-management data and WooCommerce Store API or supported storefront methods for customer-facing cart actions. The final method has not been released.
Planned scope may include products, categories, tags, attributes, variations, prices, sale prices, stock, images, SKUs, product URLs, descriptions, and connection-dependent order outcomes.
No. WooCommerce will continue to control cart validation, checkout, payment, taxes, shipping, order creation, refunds, and fulfilment.
Variation support is part of the planned scope, but parent products, attributes, variations, prices, availability, and variation IDs must be mapped and validated first.
No universal compatibility promise is possible. WardrobeIt should publish a tested matrix after reviewing themes, product extensions, multilingual tools, currencies, caches, security plugins, and checkout customisations.
WooCommerce-specific order and revenue reporting will be connection-dependent. Assisted or attributed revenue must not be presented as proven incremental revenue.
No release date should be promised until the connector, storefront deployment, catalog mapping, cart actions, security, compatibility testing, and reporting are production-ready.
WooCommerce Early Access
Share your WooCommerce architecture, product types, variation complexity, theme stack, cart requirements, and reporting needs. WardrobeIt will use early-access cohorts to validate the connector before public release.