The right tool.
The right setup.

The Botble edition is designed for Botble 7.x with PHP 8.1 or later and Ecommerce active.

An eBay seller account and your own approved eBay developer credentials are required.

Configure the background jobs required by your edition; the Botble package uses a queue worker and Laravel scheduler.

Marketplace charges and any paid advertising are separate from the plugin licence.

The Botble edition requires Botble 7 and PHP 8.1 or later, with Ecommerce active.

An Amazon Professional selling account, approved private developer profile and your own SP-API application are required.

Buyer-address access needs the appropriate Amazon application role.

Configure scheduled background jobs; Amazon selling, fulfilment and advertising charges remain separate.

The Botble edition requires Botble 7 and PHP 8.2 or later, with Ecommerce active.

A Square account and location matching your store's currency are required.

On-site wallets and alternative payment methods depend on Square eligibility; Apple Pay requires domain registration.

Configure background sync. Square processing fees, hardware and any Square Loyalty subscription are separate.

The Botble edition requires Botble CMS 7.0.0 or later with Ecommerce active.

Card and payment-link options need a configured supported provider. Telephone card entry needs provider account approval and a confirmed payment reference. Remote links support actual cash deposits; loyalty and additional card prepayments use normal till splits. Email needs a sending mail service; Square text invoices are completed in Square. Provider fees and hardware are separate.

Printing, cash drawers and scale reads require a configured local bridge and tested device commands. All Loyalty and All Weighted Products are separate plugins.

The Botble edition requires Botble CMS 7.3.0 or later with Ecommerce active.

All POS is required for earning and spending points at the till.

A working task scheduler is needed for expiry, reminders and birthday bonuses; Botble uses the Laravel scheduler.

Direct Square loyalty import is available in the Botble edition and requires a Square token with LOYALTY_READ and CUSTOMERS_READ permissions; All Square is not required.

The Botble edition requires Botble CMS 7.0.0 or later with Ecommerce active.

Physical-scale sales require All POS and a configured compatible local bridge. Hardware is separate.

The Botble edition requires Botble CMS 7.3.0 or later with Ecommerce active.

Printing uses your browser's print dialog and a printer suitable for your chosen sheets.

Custom template editing uses HTML and CSS; ingredient labels need ingredient data in product specifications.

The Botble edition requires Botble CMS 7.3.0 or later.

Use your existing email or messaging tool to send the copied message.

The Botble edition requires Botble CMS 7.3.0 or later.

Works with messages sent through the website's email system; review category settings for your installed plugins.

PHP 8.2 or later and a compatible Botble installation with Ecommerce active.

Your own Etsy shop, approved developer application, authorised permissions and eligible products are required.

Configure the queue worker, scheduled jobs, secure callback URL and any applicable webhook access.

Etsy fees and seller eligibility are separate. Buyer data and dispatch access depend on the permissions Etsy grants to your application.

Botble CMS 7.5.0 or later with Ecommerce active.

Use stock-managed products and consistent SKU or barcode data. Review ambiguous codes and variation mappings.

A barcode reader that enters text can be used; hardware is separate. Product search is also available.

Keep a backup and review count acceptance or restoration before changing live stock. Private invoices use the website’s configured storage.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

Store stock updates apply to stock-managed products and variations received in whole base units at the store location. Other receiving locations are recorded for review.

Optional: supplier email needs All Workflows with your own verified SMTP connection, and accounting bill links need All Profit with a read-only Xero connection.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

Refunds are completed with your existing payment provider and recorded here with a verified reference. Automatic provider refunds are not included.

The customer portal works with signed-in customer accounts. Guest verification codes are written to the shop's private mail log rather than emailed; use signed-in accounts for the customer portal.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

Trade checkout pricing supports ordinary unit products. Bundles, product options, pack modes and basket promotions are not combined with trade prices; unsupported baskets stop for review.

Quotation conversion creates a collection order with pending payment. Invoices, payment collection and tax calculation stay with your store and accounting processes.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

Xero comparison needs your own Xero app, a registered callback address and an organisation you authorise. An administrator must configure and enable the connection for the organisation you authorise.

Accounting writes are disabled. Square payout evidence comes from a reviewed CSV file, not a live Square connection.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

Store stock changes need a reviewed stock-ownership setting for each product and whole base units. Review locations record lots without changing store stock.

Labels are internal PDFs for manual lot entry. GS1 barcodes, scanner hardware and channel listing updates during a recall are not included.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

Provider steps need your own PrintNode account and client, SMTP account or HTTPS service. Server delivery stays off until an administrator configures and enables the connection.

Configure the Laravel scheduler and a dedicated staff worker account for timers, schedules and unattended runs.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

Live publication to provider accounts is switched off by default. Connect your own authorised accounts, review the delivery settings and enable publication when ready.

Facebook Pages, Instagram professional accounts and X each need your own registered app, permissions and account authorisation. Provider API charges and access rules are separate.

Run the publication worker from your server scheduler with a dedicated staff worker account.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

This edition rehearses transfers in an isolated target. It does not write to a live store, take payment for a migration, switch licences or move trading to the new platform.

Native rehearsals need an isolated target database and a profile configured by your administrator. WooCommerce staging targets use the included staging companion plugin.

Passwords, credentials and saved payment details are never transferred; customers and integrations reconnect or reset after a move.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active, plus All Operations Core, which is included in the download and installed first.

Recovery runs in a marked isolated target. Live-site restore, off-site storage and automatic monthly recovery drills are not included.

Needs MySQL or MariaDB with InnoDB tables, a configured protection profile and the Laravel scheduler. A capture is not an atomic database-and-files snapshot; files that change during capture make it fail.

Keep the recovery key and your application key safe and separate. Encrypted documents need the original application key, which is excluded from archives.

The Botble edition requires Botble CMS 7.6.0 or later with Ecommerce active. It was developed against Botble 7.6.12 and Ecommerce 3.11.10.

Configure the Laravel scheduler and a dedicated staff worker account for unattended background work.

Keep Core active while any operations product is installed. Deactivating a product keeps its records and does not reverse stock.