xobytes.com

Page

How to Use the Plugin Update Server by XoBytes

If you sell WordPress plugins, you need more than a download button. You need a way to upload releases, protect update files, connect updates to licenses, and let customers receive update notices inside their own WordPress dashboards.

In this guide, you will learn how to use the Plugin Update Server by XoBytes to manage private WordPress plugin updates from your own WooCommerce website.

As a result, you can build a cleaner software business. Instead of emailing ZIP files or asking customers to reinstall plugins manually, you can deliver private updates through WordPress.

What Is Plugin Update Server by XoBytes?

Plugin Update Server by XoBytes is a private update server for WordPress plugin sellers.

It helps you upload plugin release ZIP files, connect those releases to WooCommerce products, inject the XoBytes update client, and send update notifications to customer websites.

In simple terms, it lets your customers update your private plugins from their WordPress dashboard, similar to how they update plugins from WordPress.org.

How to Use the Plugin Update Server Step by Step

Learning how to use the Plugin Update Server is easier when you understand the full flow.

The system works like this:

  1. Create a WooCommerce software product.
  2. Add the product ID under Plugins / Products.
  3. Upload a release ZIP under Releases.
  4. Inject the XoBytes update client and bootstrap files.
  5. Customers install the prepared plugin ZIP.
  6. Customers enter their license key.
  7. Future updates appear inside the customer’s WordPress dashboard.

Because of this, your WooCommerce store becomes part of your private software delivery system.

Step 1: Install Plugin Update Server by XoBytes

First, install the plugin on the WordPress site where you sell your software.

Usually, this will be your WooCommerce store.

Go to:

Plugins > Add New > Upload Plugin

Then upload the Plugin Update Server ZIP file and click Install Now.

After that, click Activate Plugin.

Once active, the plugin will add update server pages inside your WordPress admin area.

Step 2: Activate Your Product License

Next, activate your XoBytes license.

The Plugin Update Server is a licensed product. Therefore, you need an active license before you can use the main update server features.

Go to the plugin license page, paste your license key, and click Activate License.

After activation, confirm that the license status shows as active.

If the license is not active, the product should stay locked. This protects the software from unauthorized use.

Step 3: Create a WooCommerce Product for Your Plugin

Now create the WooCommerce product that customers will buy.

Go to:

Products > Add New

Then add your product name, price, description, image, and download settings.

For example, your product could be called:

My Plugin Pro

After you publish the product, copy the WooCommerce product ID.

You can usually find the product ID in the product edit URL. For example, if the URL includes:

post=123

then the product ID is:

123

Step 4: Add the Plugin Under Plugins / Products

Next, go to:

Plugin Update Server > Plugins / Products

This is where you connect your plugin to the WooCommerce product.

Add the plugin name, plugin slug, main plugin file, and WooCommerce product ID.

For example:

Plugin Name: My Plugin Pro
Plugin Slug: my-plugin-pro
Main Plugin File: my-plugin-pro/my-plugin-pro.php
WooCommerce Product ID: 123

If possible, use the active plugin dropdown to populate the fields automatically.

This helps prevent mistakes because the plugin can detect installed plugins and fill in the plugin name, slug, and main file for you.

Step 5: Upload a New Release ZIP

After the plugin product is mapped, go to:

Plugin Update Server > Releases

Then upload the plugin ZIP file for the release.

Make sure you upload the actual customer plugin ZIP, not the Plugin Update Server ZIP.

For example, if you are releasing My Plugin Pro, upload:

my-plugin-pro-v1.0.1.zip

Do not upload:

plugin-update-server-by-xobytes.zip

The release ZIP should contain the plugin files your customer needs to install or update.

Step 6: Add Release Details

Each release should include the correct version and compatibility details.

Fill out fields such as:

  • Version number
  • Changelog
  • Requires WordPress
  • Tested up to
  • Requires PHP
  • Release status

For example:

Version: 1.0.1
Requires WP: 6.0
Tested up to: 6.8.2
Requires PHP: 7.4

These details can appear in the customer’s plugin update information popup.

Step 7: Use Auto-Inject for the Update Client

The most important part of the setup is the update client.

WordPress needs update-checking code inside the customer’s installed plugin before it can show private update notices.

Plugin Update Server by XoBytes can inject this code for you.

When uploading a release, leave Auto-Inject Update Client turned on.

The system will add these files to the release ZIP:

includes/xobytes-update-client.php
includes/xobytes-update-bootstrap.php

It will also patch the main plugin file with a small bootstrap require block.

As a result, the prepared release ZIP can check your private update server for future updates.

Step 8: Use Release History Actions

The release history table gives you actions for each uploaded release.

For each release, you can:

  • Download the current release ZIP.
  • Inject or repair the update client.
  • Download the update client file.
  • Download the bootstrap file.
  • Delete a release if needed.

This is useful when you want to verify the ZIP, repair a release, or manually inspect the injected files.

If a release was uploaded before the update client was injected, click Inject / Repair. Then download the updated release ZIP again.

Step 9: Make Sure the Prepared ZIP Is Used for Customers

After injection, the customer needs the prepared ZIP.

This matters because a raw plugin ZIP without the update client cannot receive private update notifications.

The correct flow is:

Upload release ZIP
Inject update client
Download or use prepared release ZIP
Customer installs prepared ZIP
Future updates show in WordPress

Therefore, always make sure customers receive the injected release ZIP, not the raw ZIP.

Step 10: Customer Installs the Plugin

After purchase, the customer installs your plugin on their own WordPress site.

They go to:

Plugins > Add New > Upload Plugin

Then they upload the prepared plugin ZIP and activate it.

Because the update client was injected, the plugin can now connect to your private update server.

Step 11: Customer Activates Their License

Next, the customer enters their license key.

The injected update client can create a license page inside the customer’s WordPress admin area.

Usually, the license page appears under:

Settings > Plugin Name License

The customer pastes their license key and activates it.

If the license is active, the plugin can receive private updates.

If the license is inactive, expired, revoked, or not allowed for that product, the update server can block the update download.

Step 12: Upload a Future Update

When you are ready to release a new version, update your plugin version number.

For example, if the customer has:

Version: 1.0.0

then your next release should be:

Version: 1.0.1

After that, upload the new ZIP to the Plugin Update Server.

Again, make sure auto-inject is enabled or use the Inject / Repair action after upload.

Step 13: Customer Receives the Update Notification

Once the customer has an active license and your update server has a newer release, WordPress can show the update notice.

The customer may see the update in:

  • Dashboard > Updates
  • Plugins > Installed Plugins
  • The normal WordPress update count bubble

Then the customer can click Update now.

After that, WordPress downloads the private release ZIP from your update server and installs it.

Step 14: Force a Test Update Check

WordPress caches update checks. Therefore, updates may not appear instantly during testing.

To force a check, go to the customer site and open:

Dashboard > Updates

Then click:

Check again

If the license is active and the uploaded release version is newer, the update should appear.

Step 15: Check the Logs

The Plugin Update Server can log update checks and downloads.

Use the logs to see whether customer sites are contacting your server.

Logs can help you confirm:

  • Which site checked for an update.
  • Which plugin slug was checked.
  • Whether the license was active.
  • Whether a download was allowed.
  • Whether an update request failed.

Because of this, logs are helpful when troubleshooting customer support issues.

Recommended Setup With XoBytes License Manager

Plugin Update Server by XoBytes works best with a license system.

For that reason, we recommend pairing it with Xobytes License Manager for WooCommerce.

The License Manager handles license keys, customer activations, and license status. Then Plugin Update Server handles private update delivery.

Together, they create a stronger software-selling system.

Protect Your Plugin Files With Tamper Guard

After you start selling plugins, you may also want to protect your plugin files from unauthorized edits.

For that, you can use Tamper Guard for WordPress plugins.

Tamper Guard helps protect commercial plugin files from being changed after release.

As a result, it can add another layer of protection to your software business.

Protect Your Store With AgentShield

In addition, your software store may attract bots, scrapers, AI crawlers, and automated abuse.

You can protect your WordPress site with AgentShield.

AgentShield helps block suspicious bots, AI agents, scrapers, risky requests, trap visitors, and automated abuse patterns.

Helpful WordPress Developer Resource

If you want to learn more about how WordPress plugins are structured, you can also review the official WordPress Plugin Developer Handbook.

This is helpful because the update server needs to detect the correct main plugin file and plugin header inside your ZIP.

Common Problems and Fixes

The Update Does Not Show

If the update does not show, first check the version number.

The uploaded release version must be higher than the installed version.

Also, make sure the customer license is active. Then go to Dashboard > Updates and click Check again.

The Wrong ZIP Was Uploaded

If you accidentally uploaded the Plugin Update Server ZIP instead of the customer plugin ZIP, delete that release.

Then upload the correct plugin release ZIP.

The update server should be used to manage customer plugin releases, not to upload itself as a release for another product.

The Plugin Slug Does Not Match

If the plugin slug or main plugin file does not match the mapped product, the update check may fail.

Go back to Plugins / Products and confirm the plugin slug, plugin name, main file, and product ID are correct.

The Customer Installed an Old Plugin Without the Update Client

If a customer installed a version before the update client was added, they may need one manual transition update.

Give them the prepared ZIP with the update client injected. After they install that version, future updates can appear automatically.

Best Practices

For the best results, keep your plugin release process simple and consistent.

  • Use clear version numbers.
  • Always upload the correct customer plugin ZIP.
  • Use auto-inject for every release.
  • Keep changelogs clear and useful.
  • Test updates on a staging site before customers receive them.
  • Confirm customer licenses are active before troubleshooting updates.
  • Use release logs to track update checks and downloads.

Final Thoughts

Now you know how to use the Plugin Update Server by XoBytes.

First, create a WooCommerce product. Next, map the product to your plugin. Then upload a release ZIP, inject the update client, and make sure customers receive the prepared ZIP.

After that, future releases can appear inside the customer’s WordPress dashboard as private plugin updates.

If you want to sell WordPress plugins from your own WooCommerce store, Plugin Update Server by XoBytes gives you one of the most important tools you need: private update delivery that you control.

Get the WordPress Plugin Update Server here.

Hey, I’m Xoie. Let me know if you need help.