Orders and Entitlements
An order records the customer, purchaser, balance users, products, and quantities that can be consumed by license issuance. Both locally created orders and orders received from another tenant appear on this page.
๐ Create a tenant orderโ
Open Orders and choose New order. Supply:
- A unique transaction ID.
- The customer company and optional purchaser.
- A tenant-owned product.
- The initial balance users permitted to issue from the order.
- Base quantity, option quantities, currency, and notes.
New local orders start On hold. After saving, edit the order and change its status to Processing before issuing from it. Use the plus and minus controls beside each product option to set its purchased quantity.
Issuing a license consumes the base entitlement and the selected option entitlements in one transaction. If any required balance is exhausted, the operation is rejected without consuming the remaining balances.
๐ฅ Manage balance usersโ
The purchaser may consume the order balance automatically. Tenant administrators can also use the people action on any order to choose additional active users who may consume its balance. Assignment does not allow those users to edit the order, increase its balance, or manage other users. Removing a delegated user takes effect immediately, including for an issuance page that was already open.
Balance users may belong to any company in the tenant. License recipients remain limited to the purchaser or active users in the order's customer company.
๐ WooCommerce synchronizationโ
Use the synchronization button to import orders after the WooCommerce connection is configured. The progress message reports created orders, companies, skipped records, and unmatched product lines.
For near-real-time processing, configure both Order created and Order updated webhooks using the same delivery URL and generated secret shown in Settings ยท WordPress & WooCommerce.
WooCommerce order balances can be used only when the order is Processing. Issuance treats Processing as fulfillment-ready even when a manual payment method has not supplied a payment date. Completed closes the order to further issuance, even if it was set manually while balance remained. All other statuses also block new licenses, additional license options, and expiration extensions, even if an earlier payment date is still recorded. Administrators can still issue directly without an order; that separate path does not require payment.
๐ Change an order's statusโ
Administrators can change Status in the order editor. For a local order the change is saved immediately. For a WooCommerce order, License Center requests the remote change and shows Updating to โฆ until WooCommerce confirms it. This action is separate from saving other order fields.
If confirmation takes more than two minutes, the editor offers Retry status update. Check the connection or reported error before retrying. In standalone desktop mode, polling confirms status changes; manual synchronization imports other changes made in WooCommerce. Forwarded and received orders do not allow status editing from this control.
๐ Track maintenance renewal remindersโ
Administrators can open Edit order > Reminders to review the recipient, products, purchase date, reminder due date, and recorded sent date. The sent date can also be set or cleared manually. Forwarded and received orders remain read-only.
When a reminder is due, use Preview Reminder to inspect the active email template with this order's customer and product details. Use Send Reminder to deliver it through the email server configured in Settings. A successful delivery records today's date on the order and adds the message to sent-email history; a failed delivery leaves the reminder unsent.
Use Reminders on the Orders page to show orders whose reminder was sent, not sent, or should now be sent. An order should be sent a reminder when it has no recorded reminder date and has reached two weeks before its first annual anniversary, including overdue orders. The optional Last 12 months filter limits results by purchase date; combined with should be sent, it shows the two-week pre-anniversary window while excluding older overdue orders.
License Center checks on startup and every 24 hours while running and alerts active tenant administrators when newly due orders are found. Open the bell's Maintenance renewal reminders due notification to see the due-order filter. Each order triggers this alert once; it is not a daily repeated notification. The alert does not send customer email. Save or discard pending order edits before previewing or sending a reminder. Sending requires a recipient, products, and enabled email delivery; recording a sent date manually only updates tracking.
๐จ Forward an order to a tenantโ
In New/Edit order โ License products, set License expiration (optional) on each base product row. Every license issued from that balance, including a license the user issues for themselves, uses that exact date. Options share the license expiration. Leave it blank to let the issuer choose an expiration. Administrators can change or clear the order setting for future licenses; existing licenses retain their dates and expiration locks. After the date passes, that balance cannot issue new licenses. Forwarding shows and copies the saved dates. Received orders remain read-only. To add options from a restricted balance, the existing license must have the matching expiration.
Platform administrators viewing orders in the main tenant can use Forward to tenant. Select an active receiving tenant, one of its existing companies, and an optional purchaser. The original product records and purchase snapshots are retained; there is no product selection or balance-user assignment in this dialog. The receiving tenant can assign balance users afterward.
The preview shows purchased, used, and remaining quantities for each product and option. Partially used orders are supported: an order with 10 purchased and 3 used arrives with 7 remaining. Used before forwarding records aggregate earlier usage without exposing the source tenant's private license or recipient records.
The original order becomes locked against spending, editing, and deletion, and shows Forwarded to the receiving tenant with live balance tracking. Earlier licenses remain with the source tenant. Deleting those licenses, removing options, or revoking with balance restoration credits the receiving tenant exactly once. The tenant can manage its balance users and licenses, but cannot increase purchase quantities.
WooCommerce orders must be Processing, with all purchase lines matched and some remaining balance. The current Forward to tenant control additionally requires a recorded payment date, even though issuance accepts Processing orders without one. If that control is disabled for a manual-payment order, check its payment details and synchronize it again after they are updated in WooCommerce. Their original payment and status rules continue to apply after forwarding. Exhausting the receiving tenant's balance completes the original WooCommerce purchase. A later return does not reopen a Completed purchase. Synchronization continues to update purchase details without changing the forwarded allocation.
Forwarding transfers the whole order to one tenant and cannot be undone or repeated.
๐ก๏ธ Deletion safeguardsโ
An order cannot be deleted when it is forwarded, received from another tenant, or has issued licenses. Bulk deletion is all-or-nothing when any selected record is protected.
Received orders are read-only. Their tenant can assign balance users and issue node-bound licenses, but cannot increase purchased quantities or access the owner signing keys.