I have around 10,000 product SKUs synchronised into our ServiceM8 account from our e-commerce platform. Field staff are drowning in this huge catalogue when trying to build quotes and invoices on site, so I want to force-archive a defined set of items instead of waiting the default 12-month window. Scope • I will supply a CSV that lists every SKU to be archived. • Before anything is touched, I need a full backup of those SKUs—either a structured export from ServiceM8 or a copy of the data pulled via the ServiceM8 API—in case we ever need to restore them. • After safekeeping the backup, every SKU on the list must be programmatically moved to the archived state so they no longer appear in searches or drop-downs for my road technicians. What I’m expecting 1. A lightweight script or repeatable process (Python, PowerShell, or similar) that authenticates with ServiceM8, reads the provided CSV, archives the matching items, and logs the outcome. 2. Delivery of the backup file plus a simple report summarising how many SKUs were successfully archived and any that failed. 3. Clear, step-by-step instructions so my internal team can rerun the process for future batches. You should already be familiar with the ServiceM8 API and its rate limits, OAuth flow, and item endpoint conventions. If you propose an alternative approach—such as leveraging ServiceM8’s import tools—explain how it will meet the same objectives. Timeline is flexible within a week or two, but I’d like to start as soon as we agree on a path.