Passer au contenu principal
Version : 1.x

Extensions

WCPOS supports extensions that add new functionality to your point of sale. The extension directory lets you browse available extensions, install them directly from the POS settings, and manage updates.

Pro Feature

Installing and managing extensions requires WCPOS Pro. The free version displays the extension catalog but disables install and activation controls.

Browsing Extensions​

Open the extension directory from POS Settings > Extensions (also labeled Plugins in some versions).

The directory displays a card grid of available extensions. Each card shows:

  • Icon (or a puzzle-piece fallback if the extension doesn't provide one)
  • Name and version
  • Description
  • Category badge
  • Status — active, inactive, update available, or not installed

Use the category pill buttons at the top to filter extensions by category. You can also use the search field to find extensions by name, description, or tags.

Installing an Extension​

  1. Open POS Settings > Extensions.
  2. Find the extension you want and click Install.
  3. The extension is downloaded and installed using the WordPress plugin installer.
  4. Once installed, click Activate to enable it.

Behind the scenes, WCPOS uses WordPress's native Plugin_Upgrader to handle installation, so extensions follow the same process as any WordPress plugin.

Activating and Deactivating​

Each installed extension has Activate and Deactivate buttons on its card.

  • Activate enables the extension so it can run in the POS.
  • Deactivate disables it without uninstalling. The extension files remain on your server and can be reactivated at any time.

Updating Extensions​

When a newer version of an installed extension is available, the card shows an Update Available badge and an Update button.

Auto-Updates​

Extensions installed from the directory have auto-update enabled by default. You can toggle auto-updates on or off per extension from its card in the directory. When auto-update is on, WordPress will apply new versions automatically, just like it does for plugins with auto-update enabled.

Troubleshooting​

"Requires Pro" Message on Buttons​

The install, activate, and update buttons are disabled in the free version of WCPOS. Upgrade to WCPOS Pro to manage extensions.

Extension Fails to Install​

  • Check that your WordPress server has write permissions to the wp-content/plugins directory.
  • Verify that your server can make outbound HTTPS requests (some hosts block external downloads).
  • Look at the error details in WP Admin > POS > Support > Logs.

Extension Not Appearing After Install​

  • Refresh the POS — the extension list is cached for up to 12 hours.
  • Confirm the extension is activated (installed but inactive extensions won't run).

Catalog Not Loading​

The extension catalog is fetched from a remote source and cached locally for 12 hours. If the catalog doesn't load:

  • Check your server's internet connectivity.
  • Try again after the cache expires, or clear your server's transient cache.

For Developers​

Creating a POS Extension​

A WCPOS extension is a standard WordPress plugin that integrates with the POS through WCPOS hooks and APIs. To create one:

  1. Start with a WordPress plugin. Your extension needs a standard plugin header and entry file, just like any WooCommerce or WordPress plugin.
  2. Integrate with WCPOS. Use the hooks and filters provided by WCPOS to add functionality to the POS interface or backend.
  3. Host releases on GitHub. The extension directory uses GitHub Releases to track versions and deliver updates.

Submitting to the Directory​

The extension catalog is maintained in the wcpos/extensions GitHub repository. To list your extension:

  1. Review the catalog format and metadata requirements in the repository's README.
  2. Open a pull request to add your extension's metadata to catalog.json.
  3. Once merged, your extension will appear in the directory for all WCPOS Pro users.

GitHub Release Conventions​

The update lifecycle relies on GitHub Releases:

  • Tag versions using semantic versioning (e.g., v1.0.0, v1.2.3).
  • Attach the plugin zip as a release asset — this is the file that gets downloaded when a user installs or updates.
  • Publish the release (not draft) so the directory can detect it.

When you publish a new release, users with your extension installed will see the update available in their extension directory. If auto-update is enabled, it will be applied automatically.

For full details on the catalog schema and submission process, see the wcpos/extensions repository.