Vendor Payouts Automation

No. It decides who is due how much, prepares the payment files and keeps the records. You send the money with your bank or PayPal (upload the file or pay by hand) and then mark the batch paid. Direct API payouts (Stripe Connect, PayPal Payouts API, Wise) are planned for a later version.

No. A request is a core withdrawal and leaves the balance the moment it is created. The run creates at most one request per vendor and period, never while a request is waiting, and only one run can work at a time. A paid request cannot be paid or rejected again.

Because part of the balance belongs to orders inside the hold period, or to orders that have not reached the hold-start status yet (for example Processed instead of Complete). The balances page shows the amount on hold and the number of orders.

Open Vendor balances: the last column says why, for example Below the minimum payout, No payout details, A request is waiting for approval or Manual only. A request is still created later in the same period as soon as the conditions are met.

Core accounting deducts the refund from the vendor's balance; the next payout is smaller. If the balance becomes negative, no payout is made until it is positive again. A longer hold period avoids most of these cases.

Yes. Core withdrawal requests appear in the payout queue as Requested by the vendor and go through the same approval, batch and files.

Yes. Approve or decline there and the queue follows (paid or rejected). The add-on's own e-mails are sent only for actions taken in its queue.

The primary currency of the store. Amounts are rounded down to what the currency can pay. SEPA files need EUR as the primary currency.

They are stored encrypted with your store's encryption key, shown masked in lists and in full only on the payout details page and in the files you download. Vendors only see their own details. Changes shortly before a payout are flagged in the queue.

Yes. Those add-ons pay vendors at checkout and record it in accounting, so the vendor balance (and the payout) is only what is left, for example negative commission. The add-on reads the same balance.

No. The add-on works in the admin panel, the vendor panel and cron only.

The add-on's tables (requests, batches, payout details, schedules), settings, privileges, e-mail templates and language variables. The withdrawals it created stay in core accounting, so balances do not change.

No. Vendor balances and payouts exist only in Multi-Vendor. The installation is refused on other editions.

Without a valid license (no key after the 14-day start period, an invalid or revoked key, a domain the license does not cover, or no successful check for 14 days), no new payout requests are created and batch files, statements and the vendor Payouts page are switched off. The queue keeps working, so requests already created can be approved, rejected and marked paid; core balances and withdrawals are not affected. Once the license is valid again, everything is back.

Open Add-ons → Manage add-ons → Vendor Payouts Automation → Settings → License. The status line says what is wrong: no key, a key for another add-on, a revoked license, or a domain that the license does not cover. Fix it and click Check now. See License.

Yes. Subdomains of your licensed domain (for example staging.example.com) and local development hosts (localhost, private IP addresses, .local, .test) are covered by the same license. Turn off Create payout requests automatically on copies, so a copy never creates requests.

Nothing changes for 14 days: the add-on keeps working and retries every hour. Only if no check succeeds for 14 days is it switched off until the next successful check.

No. The check runs in the admin panel or from cron, once a day. The storefront never runs it.