Digipacket Partner

What it does

Products and prices come from your own reseller account, not from a file: an import creates the WooCommerce categories and products, and a later import refreshes prices without overwriting a page you have customised. When an order is paid, the plugin places it at the provider and writes the outcome — the reference, or the error — onto the WooCommerce order as a note.

• Your catalogue, imported

  Domains, hosting, VPS, Titan and Google Workspace mailboxes and SSL arrive as WooCommerce products with their own categories.

• Domain search on any page

  Shortcodes for a search box, a priced list of every extension, and a trending-extensions banner.

• Plan grids by category

  [digipacket_plans category="Web hosting"] renders a grid, limited or pinned to the exact plans you name.

• Priced the way each thing sells

  Hosting asks for the domain it is for, VPS offers its add-ons as checkboxes, and e-mail multiplies by the number of accounts.

• Re-import without losing your work

  Tick "keep my changes" on a product and imports stop rewriting its name, description and prices. Elementor layouts are never overwritten.

• Paid orders provision themselves

  The domain is registered or the hosting created in your reseller account, and the order carries a note saying which.

What it needs

WordPress

6.0 or newer

PHP

8.2 or newer

PHP extensions

No extension beyond a standard PHP build.

WordPress plugins

WooCommerce

A Digipacket account

A Digipacket reseller account with API access, the site's IP address on the API allowlist, and a funded balance.

Install it

cd /path/to/wordpress/wp-content/plugins \
  && curl -fL -O https://github.com/digipacket-net/digipacket-partner-for-woocommerce/releases/download/v1.1.0/digipacket-partner-for-woocommerce.zip \
  && echo "3681007d0a2bf0911f22f2e7c8f382556a3a18bdcfef3cb3e7ccb0021d70c9dd  digipacket-partner-for-woocommerce.zip" | sha256sum -c - \
  && unzip -q digipacket-partner-for-woocommerce.zip \
  && rm digipacket-partner-for-woocommerce.zip

wp plugin activate digipacket-partner-for-woocommerce --path=/path/to/wordpress

Why the commands look like this

• Why -f is not optional

  Without it, curl writes the server's error page into your file and exits 0. You unzip an HTML document into wp-content/plugins and WordPress shows a broken plugin. With -f, curl writes nothing and exits 22.

• Why the checksum is printed here

  A hash served next to the file only proves the download was not corrupted in transit. This page is a second channel: if the number here and the number on the file agree, both would have had to be changed.

• Why the steps are chained with &&

  A semicolon runs the next command whether or not the last one worked. With &&, a failed download or a failed checksum stops the chain before anything is written into your plugins directory.

Verify the download

# GNU coreutils, on a Linux server
echo "3681007d0a2bf0911f22f2e7c8f382556a3a18bdcfef3cb3e7ccb0021d70c9dd  digipacket-partner-for-woocommerce.zip" | sha256sum -c -

# macOS, and anywhere sha256sum is missing
echo "3681007d0a2bf0911f22f2e7c8f382556a3a18bdcfef3cb3e7ccb0021d70c9dd  digipacket-partner-for-woocommerce.zip" | shasum -a 256 -c

Always the newest release

The pinned URL above is the one to use in documentation and in a change you want to be able to repeat. In a provisioning script you usually want whatever is current, and there is a trap in the obvious way of asking for it.

Ask the API which asset the latest release actually publishes, then download that:

url=$(curl -fsSL https://api.github.com/repos/digipacket-net/digipacket-partner-for-woocommerce/releases/latest \
  | grep -o '"browser_download_url": *"[^"]*\.zip"' \
  | cut -d'"' -f4)

curl -fL -O "$url"

Update it

Removing the folder first is safe: your API credentials, imported products and per-product overrides are stored in the WordPress database, not in the plugin directory.

cd /path/to/wordpress/wp-content/plugins \
  && curl -fL -O https://github.com/digipacket-net/digipacket-partner-for-woocommerce/releases/download/v1.1.0/digipacket-partner-for-woocommerce.zip \
  && echo "3681007d0a2bf0911f22f2e7c8f382556a3a18bdcfef3cb3e7ccb0021d70c9dd  digipacket-partner-for-woocommerce.zip" | sha256sum -c - \
  && rm -rf digipacket-partner-for-woocommerce \
  && unzip -q digipacket-partner-for-woocommerce.zip \
  && rm digipacket-partner-for-woocommerce.zip \
  && wp plugin activate digipacket-partner-for-woocommerce --path=/path/to/wordpress

Remove it

wp plugin deactivate digipacket-partner-for-woocommerce --path=/path/to/wordpress \
  && wp plugin delete digipacket-partner-for-woocommerce --path=/path/to/wordpress

What it does not do

Written down for the same reason as everything else on this page: finding out after you have installed it is worse.

• It is not self-contained. Without a reseller account, an enabled API key and this server's IP address on the allowlist, the connection is refused and nothing imports.
• Every order is debited from your reseller balance. An order placed against an empty balance stays pending until the balance is topped up and the order is provisioned again.
• The plugin's own admin screens and storefront strings are in French today. They are not yet internationalised, so they cannot be translated through translate.wordpress.org.
• WooCommerce is required — the plugin declares it and will not run without it.

If a command fails