EquaShop turns WordPress into a clean subscription storefront. You define products, billing plans (monthly \/ every 6 months \/ yearly), and rich multilingual marketing content, then sell them through Stripe.<\/p>\n\n
It ships a complete selling engine: a multilingual catalogue admin, a public storefront via shortcodes, a Stripe-powered checkout tunnel (subscriptions and one-off), a self-owned versioned consent referential, and native order management. The product catalogue is always unlimited and the ability to sell is never limited.<\/p>\n\n
equashop<\/code>), driven by the admin's WordPress locale. The admin ships in English (source); a translation template (languages\/equashop.pot<\/code>) is included, and community translations are served through translate.wordpress.org.<\/li>\n- Storefront content & strings<\/strong> \u2014 fully translatable by you in the five shipped languages (English, French, Spanish, German, Portuguese). Strings resolve in three steps: your admin override \u2192 a built-in default for the shipped languages \u2192 fall back to your default shop language.<\/li>\n<\/ul>\n\n
Admin<\/h4>\n\n\n- Products<\/strong> \u2014 multilingual catalogue: non-translatable fields (slug, logo, reference price), billing plans, and per-language label \/ description \/ features \/ benefits.<\/li>\n
- Languages<\/strong> \u2014 configure your shop languages among the five shipped ones and pick exactly one default (fallback).<\/li>\n
- Storefront translations<\/strong> \u2014 override every storefront string per language.<\/li>\n
- Settings<\/strong> \u2014 Stripe keys, cart & storefront behaviour, demo data management.<\/li>\n<\/ul>\n\n
Standalone, with optional companions<\/h4>\n\n
EquaShop requires no other plugin to run \u2014 it works as a generic shop for any vendor. It is part of the EquaSuite range: when the optional EquaFulfil companion plugin is installed, EquaShop delegates order fulfilment to it. It can also, entirely optionally and off by default, display content from the EquaMarket service \u2014 a remote HTTPS service, not an installed plugin (see External services). Neither is required; without them the shop stays fully functional.<\/p>\n\n
Fonts<\/h4>\n\n
The storefront embeds the open-source fonts Plus Jakarta Sans<\/strong> and Inter<\/strong> (SIL Open Font License 1.1), so it never depends on a theme or a CDN.<\/p>\n\nExternal services<\/h3>\n\n
Stripe (payment processing \u2014 required to sell).<\/strong> EquaShop uses Stripe (api.stripe.com<\/code>) for everything money-related. It contacts Stripe:<\/p>\n\n\n- at checkout<\/strong>, to create the Stripe customer and the subscription or one-off payment (sending the buyer's name and e-mail, the cart contents and amount);<\/li>\n
- to read prices<\/strong>, on demand and on a scheduled WP-Cron price sync<\/strong> you configure in Settings \u203a Stripe sync<\/em> (refreshing the cached amounts of your tariffs);<\/li>\n
- during product import<\/strong>, to list your Stripe products and to download each product's image<\/strong> into your Media Library;<\/li>\n
- on the \"Test connection\"<\/strong> button in Settings \u203a Stripe keys<\/em>, to query your Stripe account.<\/li>\n<\/ul>\n\n
Stripe also notifies your site by webhook<\/strong> (Stripe \u2192 your site) to record paid orders and renewals. Stripe Terms: https:\/\/stripe.com\/legal \u2014 Stripe Privacy: https:\/\/stripe.com\/privacy<\/p>\n\nEquaMarket content service \u2014 marketing.equadev.fr (optional, opt-in \u2014 OFF by default).<\/strong> EquaShop can display EquaSuite news and offers as an admin banner and an \u201cEquaSuite\u201d page inside the WordPress admin. This feature is off by default<\/strong> and only makes a request if you explicitly authorise it in Settings \u203a EquaSuite<\/em> \u2014 a technical server-call authorisation, distinct from any marketing consent, revocable at any time. When enabled, and only while viewing an EquaShop admin screen, the plugin requests this content over HTTPS from https:\/\/marketing.equadev.fr<\/code>. It sends the technical values needed to serve the right content: the plugin identifier (equashop<\/code>), the content edition it runs (free<\/code>), and the language of the plugin's admin display. In addition, WordPress's own HTTP user-agent carries your site's URL and WordPress version, and \u2014 as with any request \u2014 your server's IP address is visible to the server it contacts; none of these transport values is used. No personal data is collected for marketing or prospecting when querying the marketing.equadev.fr<\/code> server. The content is display-only (admin-only, never on the storefront). Terms of use for this service are the EquaShop End-User Licence Agreement \u2014 https:\/\/equasuite.equadev.fr\/contrat-de-licence\/ .<\/p>\n\nFor developers<\/h3>\n\n
EquaShop exposes a small, stable set of public extension points so other code can react to its lifecycle and integrate with it. None of them are required to run the shop; each is simply a documented moment (a hook or a method) you may use.<\/p>\n\n
Payment signal<\/h4>\n\n\nequashop_payment_processed<\/code> (action) \u2014 fires once a paid order has been recorded, on both the subscription and the one-off checkout paths. Listeners receive one associative-array payload with a fixed, versioned key shape (the payment hook, contract v4). Use it to react to a completed sale \u2014 fulfilment, CRM, accounting, and so on.<\/li>\n<\/ul>\n\nPHP API fa\u00e7ade<\/h4>\n\n\nEquaShop_Api<\/code> (class) \u2014 a read-mostly, static-method integration surface for in-process consumers; always call it under your own class_exists( 'EquaShop_Api' )<\/code> guard. Catalogue identity: enumerate()<\/code>, get_product()<\/code>, count()<\/code>. Availability verdict: set_availability()<\/code> (a binary in-stock \/ out-of-stock verdict). Order read and sync: get_order()<\/code>, get_orders_by_ids()<\/code>, orders_cursor()<\/code>, orders_delta()<\/code>, set_order_status()<\/code>, update_order_field()<\/code>. Method names and return shapes are kept stable (contract version 3).<\/li>\n<\/ul>\n\nLifecycle & data hooks<\/h4>\n\n\nequashop_after_create_tables<\/code> (action; args: table prefix, charset\/collate) \u2014 fires after the base tables are created or upgraded, on both fresh install and upgrade. A moment to create your own related tables.<\/li>\nequashop_after_seed<\/code> (action) \u2014 fires after the base seed data is written. A moment to seed your own related data.<\/li>\nequashop_before_product_delete<\/code> (action; arg: product id) \u2014 fires just before a product (and its i18n and price rows) is deleted.<\/li>\nequashop_before_price_delete<\/code> (action; args: product id, months) \u2014 fires just before a single tariff row is deleted.<\/li>\nequashop_product_save_columns<\/code> (filter; args: columns map, submitted data) \u2014 filter the column\/value map written when a product is saved. With no listener the map is unchanged.<\/li>\nequashop_product_price_saved<\/code> (action; args: tariff row id, tariff data) \u2014 fires after each tariff row is upserted during a product save.<\/li>\nequashop_demo_installed<\/code> (action; arg: array of product ids) \u2014 fires after the demo products are installed.<\/li>\nequashop_demo_removed<\/code> (action) \u2014 fires after the demo data is removed.<\/li>\nequashop_fulfilment_active<\/code> (filter; default false) \u2014 return true to take over the native Orders screen; used by a fulfilment companion plugin (returns false when none is present).<\/li>\nequashop_checkout_finalize_error<\/code> (action; args: stage, product slug, WP_Error or null) \u2014 fires when a checkout line cannot be finalised (coupon or subscription), for logging or alerting.<\/li>\nequashop_content_slot<\/code> (filter; default free<\/code>) \u2014 the opaque content-set key sent to the EquaMarket content service (see External services); it names which content set the server should return. Return a different key to request another content set.<\/li>\n<\/ul>\n\n\n\nCan I sell already?<\/h3><\/dt>\nYes. On first activation you review and accept the End-User Licence Agreement and the liability limits on a one-time screen (EquaShop's own admin pages wait behind it; your site and storefront are unaffected). Then publish the storefront with the shortcodes, add your Stripe keys in Settings \u203a Stripe keys<\/em>, and buyers can subscribe or buy through the Stripe checkout tunnel; paid orders are recorded and shown in the Orders screen.<\/p><\/dd>\nHow are Stripe keys protected?<\/h3><\/dt>\nThe publishable key is stored as-is (it is public). The secret key and webhook secret are encrypted at rest with a key (EQUASHOP_KEK<\/code>) kept only in wp-config.php<\/code>, never in the database. From Settings \u203a Stripe keys<\/em> you generate this key with one click and the plugin writes it to wp-config.php<\/code> for you (through WordPress's file API); when the file is not writable, the same screen shows the exact line to add by hand. Nothing is written at activation, and until a key is set the admin warns you that the secrets are stored in plain text. On uninstall the line is left in place \u2014 remove it by hand if you wish.<\/p><\/dd>\nDoes uninstalling delete my data?<\/h3><\/dt>\nOnly if you tick \u201cDelete data on uninstall\u201d<\/em> in the settings (OFF by default).<\/p><\/dd>\n\n<\/dl>\n\n\n1.4.0<\/h4>\n\n\n- Maintenance and refinement release \u2014 no change to how your shop sells, and no database change. Internal source clean-up (comments and identifiers) for a tidy submission. On the Withdrawal notice screen, switching the behaviour (blocking waiver \/ display-only notice) now fills each language with the wording that matches the chosen mode, and never overwrites text you have already edited. The encryption key (
EQUASHOP_KEK<\/code>) is generated and written to wp-config.php<\/code> from the Stripe settings screen with one click, through WordPress's file API (WP_Filesystem<\/code>); nothing is written at activation. It never overwrites an existing key, is staged through a private temporary file in the same directory as wp-config.php<\/code> that is always removed, shows the exact line to add by hand when wp-config.php<\/code> is read-only, and never stores the key in the database; the line is left in place on uninstall. The payment hook (v4) keeps its byte-identical contract.<\/li>\n<\/ul>\n\n1.0.4<\/h4>\n\n\n- Maintenance release: internal comment and admin-label tidy-up only \u2014 no change to how your shop works, and no database change. The payment hook (v4) keeps its byte-identical contract.<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Documentation and refinement release \u2014 no change to how your shop sells, and no database change. The in-product help was corrected to match the plugin exactly (out-of-stock behaviour, consents and the delivery-mode field). The payment hook (v4) keeps its byte-identical contract.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Refinement and non-destructive-downgrade release \u2014 no change to how your shop sells. New products now default to the \"Immediate execution\" withdrawal regime, so a product is compliant out of the box (fully editable afterwards). Order management is now driven by a single \"Physical order management\" setting, and its help was rewritten to match. The in-product help was tidied and de-duplicated. No database change; the payment hook (v4) keeps its byte-identical contract.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Security and refinement release \u2014 no change to how your shop works. Values submitted on the product form are sanitised before they are stored. This release also leaves wp-config.php untouched, adding the encryption key by hand from the settings screen (the automatic, writable-only write with a manual fallback is reinstated in 1.4.0). Fixed a broken documentation link in this readme. No database change; the payment hook (v4) keeps its byte-identical contract.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First public WordPress.org release. The complete selling engine: an unlimited multilingual catalogue, storefront shortcodes, and Stripe checkout for both subscriptions and one-time products. A self-owned, versioned consent referential (marketing and transactional texts, each edit archived and transmitted with the order) and a single, editable withdrawal notice (blocking waiver or informational) shown at the cart. Native order management with manual handling statuses. The storefront and the dedicated product page render inside your active theme on both classic and block themes (with an accessibility skip-link on block themes). English is the source language; community translations are served through translate.wordpress.org. Hardened for the directory: consistent input sanitisation and output escaping, and capability + nonce checks on every admin action; fixed a fatal error that could occur when refreshing a product's Stripe prices. No database change; the payment hook (v4) and PHP API fa\u00e7ade keep byte-identical contracts.<\/li>\n<\/ul>","raw_excerpt":"A generic, multilingual Stripe subscription shop for WordPress \u2014 build a catalogue of plans and sell them, with no other plugin required.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/366925","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=366925"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/equadev"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=366925"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=366925"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=366925"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=366925"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=366925"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=366925"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}