Logs and Tools
The Logs and Tools sub-tab sits next to the booking list under Webkul WC Addons → Booking Management System → Bookings. It holds the housekeeping: what your calendar connections have been doing, how to bring bookings over from another extension, and how to keep the tables tidy.
Sync Logs
Every calendar import or export writes a line here.
| Column | Meaning |
|---|---|
| ID | The log entry's reference |
| Provider | Which calendar the entry came from — google, ics, and so on |
| Entity ID | The booking or connection the entry relates to |
| Status | pending, success, failed … |
| Error | The failure message, when there is one |
| Created | When the entry was written |
Provider and Status are free-text filters — type ics or failed and the table narrows as you type. The count beside them tells you how many rows match.
- Refresh Logs reloads the table.
- Export Logs CSV downloads the filtered rows as
wcbrs-sync-logs-<provider>-<status>.csv.
Tips
If a calendar connection seems to be doing nothing, filter this table by its provider. An empty result means the sync has never run; a run of failed rows with an error message tells you why.
The log retention period, verbose logging and failure alerts are set under Global Settings → Products → Calendar Sync Config → Sync Logs. See Calendar Sync.
WooCommerce Bookings migration
If you are moving from the WooCommerce Bookings extension, this tool copies its existing bookings into this plugin.
| Control | What it does |
|---|---|
| Dry Run | Ticked by default. Reads the records and reports what would happen, without writing anything |
| Batch size | How many records to process in one pass, 1–500. Default 100 |
| Run WooCommerce Bookings Migration | Starts the run |
How to migrate safely
- Back up your database first. A migration writes real booking rows.
- Leave Dry Run ticked and click Run WooCommerce Bookings Migration. You get "WooCommerce Bookings dry run complete." and a report of what was found.
- Read the report. Check the counts match roughly what you expect.
- Untick Dry Run and run it again. You get "WooCommerce Bookings migration completed." and the booking list, calendar and sync logs all refresh.
- Repeat with the same batch size until the report shows nothing left to import.
Warning
Run the migration once per batch and check the result before running again. Running the live migration repeatedly on the same records is the fastest way to end up with duplicates.
After migrating, open Managing Bookings and spot-check a handful of records — especially their dates, their customer and their status.
Compatibility and Scale Audit
This card lives at the bottom of Global Settings → Products, and it is the quickest way to answer "will this work on my store?".
It reports, with a status and a plain-language result for each area:
| Group | Checks |
|---|---|
| Marketplace Vendors | Whether a marketplace plugin is present and how bookings interact with it |
| WooCommerce Platform | WooCommerce version and feature declarations, such as HPOS and block checkout |
| Extension Compatibility | Signals from other extensions that touch products, cart or checkout |
| Multilingual | Whether a translation plugin is active |
| Scale | Your current booking count, and whether the store is in comfortable territory |
Refresh Audit re-runs the checks, and the generated timestamp tells you how fresh the report is.
Tips
Run this before a big launch and after installing any new cart, checkout or marketplace extension. It is read-only — it changes nothing.
Archive and purge tools
Old, finished bookings pile up. The tools in the same card let you clear them out safely.
| Field | Default | Meaning |
|---|---|---|
| Older than days | 730 | Only bookings older than this are eligible. Minimum 30 |
| Purge limit | 100 | How many rows to remove in one pass, 1–1000 |
Three buttons, in the order you should use them:
- Preview Eligible Rows — shows the cutoff date, which statuses are eligible, and how many rows match. Nothing is deleted.
- Dry Run Purge — walks the deletion without writing, and reports the same figures.
- Purge Eligible Rows — deletes them. You are asked to confirm: "Permanently purge eligible terminal bookings?"
The result table shows Cutoff, Statuses, Eligible and Purged.
Warning
Purging is permanent — there is no undo inside the plugin. Only bookings in a finished state are eligible, but take a database backup before your first real purge, and start with a small Purge limit.
Note
Purging removes the booking records. It does not touch the WooCommerce orders they came from, so your sales history and your accounts are unaffected.
Next step
- Calendar Sync — set up the connections these logs describe.
- Global Settings — where the audit and purge tools live.