WooCommerce / plugins & extensions
No packaged PsDevs WooCommerce plugin is available today. This page supports software discovery by making the empty inventory explicit, documenting what future owned software must prove and pointing to a bounded custom path without staging a ‘coming soon’ marketplace.
No packaged PsDevs WooCommerce product is implied. The current paths are a new custom plugin or evidence-led knowledge.
Publication controls
01No product inventory today02No speculative categories03Evidence-gated future software04Custom path remains separateDiscovery
Current inventory
There is no product card, purchase action or availability claim because no owned WooCommerce software has passed the publication gate.
Products lists real software onlyOpen route →Future owned software
A future plugin or extension needs a repeated bounded job, supported versions, scenario evidence, known limits and a maintainable lifecycle.
DEFERRED_TO_FUTURE_PRODUCTOpen route →Custom path
A workflow, checkout or order capability, admin tool, regulatory function or bounded integration can be assessed when existing software does not fit.
Assessment first · no product claimOpen route →Regulation-driven software
Selected EU topics may affect catalogue, interface, pricing or withdrawal workflows, but they do not create a PsDevs product by default.
Official source → technical decisionOpen route →Product evidence
Publication requires a named job, version and dependency scope, visible workflow evidence, data behaviour, acceptance scenarios and known limits.
Compatibility is scoped to tested environments. Updates, documentation, support and safe removal need an explicit owner.
Custom boundary
A contracted plugin answers one approved brief. Reuse, productisation and public availability require a separate product decision and evidence gate.
Until then, this page describes a custom capability path, not software that another merchant can purchase.
Decision path
Name the missing ecommerce capability and its users.
Check native behaviour and maintained software before commissioning a build.
Define one bounded outcome, platform surface, data boundary and acceptance model.
Publish only after recurrence, release evidence and maintenance ownership exist.