Documentation

Requirements

• PHP 8.1 or newer
• WordPress 6.0 or newer recommended
• WooCommerce for commerce modules
• Elementor for Elementor widgets

Install and license

1. Download the latest ZIP from your Emargy account.
2. Open Plugins → Add New Plugin → Upload Plugin.
3. Install and activate the ZIP.
4. Open StoreKit → License, enter the key, and activate it for the current domain.

Licensed updates are delivered through WordPress using temporary signed package URLs. StoreKit keeps a bounded offline validation window after a successful remote check.

Open StoreKit → Modules and enable only the capabilities used by the project.

Product and catalog

• Product Images
• Product Swatches
• Product Add To Cart
• Art Product Grid
• Variant Product Grid
• Wishlist and Compare

Story and conversion

• Product details, review showcase, related rail, and sticky add-to-cart
• Header Actions for account, search, language, wishlist, and cart
• Designer Message editorial block
• Checkout layout built on native WooCommerce checkout

The Cart Empty State module is reserved for a future opt-in design and is disabled by default.

StoreKit keeps WooCommerce as the source of truth. Custom requests verify a nonce and normalize product, variation, and quantity input before calling WooCommerce APIs.

• Quantities are bounded and server-validated.
• Products must remain purchasable.
• A variation must belong to the submitted variable product.
• Custom cart endpoints are rate-limited.
• Guest wishlist and compare state uses scoped browser tokens rather than trusting arbitrary record IDs.

Always test variable products, stock limits, taxes, shipping, and checkout extensions on a staging copy before launch.

StoreKit loads each module only after its declared dependencies are present. It does not replace WooCommerce product storage, cart sessions, checkout validation, totals, or order creation.

Before launch

1. Regenerate Elementor CSS and data after major template changes.
2. Exclude cart, checkout, and account routes from full-page caching.
3. Test logged-in and guest cart behavior.
4. Test every variation combination and unavailable state.
5. Confirm third-party payment, checkout, wishlist, and multilingual extensions do not render duplicate controls.

A widget is missing

Confirm its module is enabled and that Elementor or WooCommerce is active when required. Then regenerate Elementor files and clear page caches.

Cart or variation actions fail

Check the browser network response, verify that product and variation IDs match, and test with optimization plugins disabled on staging. WooCommerce can reject unavailable, out-of-stock, or non-purchasable items by design.

An update is not offered

Confirm the license is active on the exact domain and use WordPress Check for updates again. Contact [email protected] with the StoreKit version and WooCommerce system report.