Simpro | Work Order Archiver

1Connection

Use your existing Cloudflare Worker as the Simpro API gateway.

Cloudflare Worker proxy URL

How does your Worker route requests?

Choose the format your existing Worker supports. A proxy must forward GET/PATCH, headers and CORS.

Simpro build URL

Company ID

Simpro API access token / API code

Sent only in the Authorization: Bearer header to your selected Worker. Never placed in the URL, browser storage, or export.

Not connected.

2Work order spreadsheet

Upload only the WOs you intend to review. No automatic database-wide selection.

Select CSV or Excel (.xlsx)

Header row required. Supported: WorkOrderID, WO No., ContractorJobID and custom column mapping.

Work order ID column

Parent job ID column (optional)

Only WOs issued before

Preview how many records?

Important: Only a WO with live status Pending, a matching ID and a valid issue date before the cutoff can be considered eligible. This does not verify subcontractor invoices, outstanding costs or completed work.

No spreadsheet loaded.

3Review and test

Preview is read-only. A live archive is never attempted automatically.

0 records

0Imported unique WOs

0Eligible / checked

0Verified archived

0Blocked / errors / uncertain

Work order	Parent job	Contractor	Issue date	Live status	Result	Details
Upload a file to see work orders.

Showing up to 250 records onscreen. Every record is included in exports. For large batches, download the progress CSV regularly — the browser does not save it for you.

I have independently checked that the selected work orders are genuinely resolved, including subcontractor invoices, liabilities and attendance; I am authorised to change them.

Batch mode stays locked until one archive has succeeded and been verified by a second GET.

4Bulk archive

Each WO is checked again immediately before updating; every update is verified afterwards.

Parallel workers

Maximum API requests / second

Type ARCHIVE to enable batch

A stop request prevents new work from starting, but any in-flight PATCH may still finish. Uncertain responses are flagged for manual verification; the app never automatically retries PATCH requests.

Not started

Ready. No changes made.