# Client handover — Ecommerce

The client handover with the items a store cannot afford to lose: the catalogue feed and whatever generates it, the product data mapping, creative source files rather than exports, the promotion calendar, and the rules still running against all of them.

Everything else is the general handover, unchanged. One row per item, named exactly, verified from the receiving side, with ownership distinguished from access.

## How to use it

1. Copy this file, or the CSV version if you would rather work in a sheet.
2. List by category first, so a whole class of thing cannot be forgotten.
3. Name items exactly, with identifiers, not by description.
4. Have the receiving side verify each item, and record who and when.
5. Distinguish ownership transferred from access granted.
6. Write the risk if missed on every row, so the list can be prioritised.
7. Keep the notes: the reasons behind decisions are the part that cannot be recovered.

## The columns

**Item** (Text). The specific thing being handed over, named exactly: the feed integration by the app it runs in, a campaign by its name, a shoot by its date. Category names like creative are not items.

**Category** (Text). One of seven: account, asset, data, document, access right, relationship, obligation. A store's handover fails on the last three, because the feed integration, the photographer and the booked promotion never appear on an invoice.

**Where it lives** (Text). The system it is actually in: the store platform's advertising app, the business account, the shared drive, the photographer's own library. A store's configuration is spread across more systems than its account suggests.

**Access before** (Text). Who could reach it before, which in a store is frequently one agency login for the feed and one person for the creative library. Both are the people who will be asked for help in the first month.

**Access after** (Text). Who can reach it afterwards, by name, and at least two current people for the feed and the catalogue connection. Those two break quietly and are the worst things to have behind one person.

**Ownership transferred** (Text). Whether this changed hands, or was merely shared. For a store this matters most on the catalogue connection and the domain verification, both of which disappear when an agency's account is closed.

**Verified by** (Text). Whoever on the incoming side confirmed it, named. For the feed that means watching a refresh succeed rather than looking at a settings screen, because a feed that is connected and stale looks identical to one that works.

**Verified on** (Date (YYYY-MM-DD)). The day it was confirmed. A feed verified a fortnight before a handover may have stopped refreshing since, and in a store nothing announces that except the prices in the ads.

**Risk if missed** (Text). What stops working if this is missed, in one line. For the feed it is that shopping campaigns run on stale prices and availability with no error anywhere, which is the most expensive silent failure available here.

**Outstanding** (Text). What is still to be done and by whom: the custom labels still to be documented, the source files still with the editor, the promotion booked but not yet briefed.

**Evidence** (Text). What shows the transfer happened: a screenshot of the integration settings with its last successful refresh, a delivered export, a confirmation from the photographer about licence terms.

**Status** (Text). Not started, transferred, or verified. For a store, verified on the feed means a refresh was watched to succeed after the transfer, not that a permission screen looked correct.

**Notes** (Text). What the receiving side cannot infer: what each custom label means, why a segment is excluded from shopping, which promotion a strangely named campaign belonged to, the photographer's licence terms.

## The client handover

| Item | Category | Where it lives | Access before | Access after | Ownership transferred | Verified by | Verified on | Risk if missed | Outstanding | Evidence | Status | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|   |   |   |   |   |   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |   |   |   |   |   |

## Before you commit it

- Items are listed by category, so no whole class is forgotten.
- The feed and whatever generates it are both listed, with their refresh schedule.
- Creative source files are handed over, not only exported assets.
- Every row was verified by somebody on the receiving side, with a date.
- Automated rules acting on the catalogue have been listed and transferred or stopped.
- The promotion calendar and any committed bookings are recorded.
- The notes carry the reasons behind decisions, not only the facts.