Blog / Shopify & e-commerce /

A practical checklist for a Shopify catalogue handover

A Shopify catalogue handover can arrive as a spreadsheet and a cheerful “good luck”. Then the next team opens it and has no idea which values to trust.

Products, variants, collections, media, search rules and channel settings all depend on each other. A good handover lets the incoming owner understand the catalogue, change it safely and find the open problems without phoning the person who built it.

Begin with the catalogue structure

Describe how products, variants, collections, tags and metafields are organised, and which identifiers match records. Don’t document every field just because it exists. Focus on what editors must maintain and the rules that affect the storefront.

Identify which information is authoritative in Shopify and which is managed elsewhere. If supplier data, inventory or pricing syncs from another system, name the source and owner. A catalogue handover should make the flow visible without copying confidential credentials or contracts.

Record how products become publishable

Explain the steps to create or update a product: required fields, image standards, variant setup, pricing review, inventory status, search preview and publication approval. Note exceptions, such as products with different shipping or return terms, only when those apply. Provide a sample record that demonstrates the structure without exposing private customer or supplier data.

Clarify draft, active, archived and channel-specific states in the store’s actual workflow. A product may be active in Shopify but not available on every sales channel. Tell the next owner how to check publication status and what approval is needed before enabling a new destination.

Explain collection and search logic

Document how automated or manual collections are maintained and which fields or tags drive membership. Include the owner of conditions and how to test changes. A new tag can affect a large group of products if it appears in a rule.

Record search settings, synonyms, filters or merchandising rules that materially affect discovery. Keep the reasoning and evidence for important mappings, not only the configuration. The incoming team should know which rules are intentional and which are unresolved.

Cover media and content conventions

Explain image selection, ordering, alt text expectations, file naming if used, and any content fields that feed templates. Clarify which images apply to which variant. The handover should help prevent a correct product record from displaying an unrelated image or incomplete description.

Flag product claims that need a source or specialist sign-off. A copy checklist doesn’t prove a specification is accurate, so point to the approved source and say who can confirm it.

Transfer access and ownership

Give the right people individual accounts and sensible roles on the store and its connected services. Note who owns the store, domain, payment, feeds, apps and support channels. Never share credentials in the handover; use the platform’s invitation and ownership process.

List installed apps that affect catalogue data, search, imports, feeds or publication. Note their purpose, owner, renewal or support route where appropriate, and known dependencies. Avoid naming every app without explaining why it matters.

Test the handover

When I hand over a client site, I’d rather watch someone do a routine task than ask whether they have questions. “No questions” usually means they haven’t tried yet. Have the incoming owner update a product detail, preview a variant, check its collection and confirm channel availability using only the handover. If a rule is unclear, fix the guide before the outgoing person disappears.

Include a list of open issues, pending approvals, known exceptions and next review dates. Make clear which tasks are complete and which still need an owner. A handover should not imply that unresolved data is verified.

Ask the next editor to make a small change

A handover is much easier to assess when the incoming team demonstrates a normal task. Give them an approved product correction and ask them to locate the record, find its evidence, make the edit, preview the result and identify any connected output that needs review.

Do this while the outgoing owner is available to answer questions. Every pause reveals an assumption the documentation may have missed: a supplier code hidden in a note, an image naming rule or a field that an app rewrites overnight.

I would capture those discoveries in the working instructions immediately. A recording of the session can help, but people still need a short written route to the common tasks. Nobody wants to search a long video for the sentence explaining which column must stay untouched.

Hand over exceptions as carefully as completed records

I don’t trust a catalogue where every record looks finished. There are always products awaiting supplier confirmation, temporary copy and odd variant handling. List them with their owners and next decisions, or a new editor may “tidy” a deliberate workaround.

Explain what the next team can safely change and what needs another person’s decision. That is especially useful where merchandising, purchasing and technical maintenance share responsibility. A handover should make those boundaries easier to navigate.

Include the next maintenance cycle

Show how fresh supplier data arrives, how images are replaced and how withdrawn items are handled. The catalogue has to keep working after the first week, not just look tidy on handover day.

Agree who will receive questions during the transition and when responsibility fully passes across. Leave a route for urgent issues without making the outgoing editor the unofficial help desk forever.

Finish by asking the incoming owner to summarise the catalogue’s main risks in their own words. If they can explain what is authoritative, what is automated and what remains unresolved, the handover has transferred understanding as well as files.

A strong catalogue handover passes on context, responsibility and a safe way to make the next change. Could a new owner fix a product correctly using only what you’re about to hand them?