Dealer SOP Creation Guide

Reference this file before writing any Dealer Portal SOP (external client dealers). Read style-conventions.md first. Dealer SOPs are the most detailed and most image-rich documents we produce.

Audience

Client dealers — often non-technical business owners editing their own website. Assume no prior technical knowledge.

Voice

Plain English. Extremely detailed. Calm and confidence-building. One action per step. Explain every term the first time it appears, before asking them to touch it. State plainly what will and will not change so they feel safe. Mirror the tone of our published dealer guide.

Required template

Copy this structure and fill every section. Be generous with steps, callouts, and images.

# <Plain, friendly title, e.g. "Add Your Product Catalog with the Embed (Option D)">

**Audience:** Dealer
**Owner:** <support/account team>
**Last updated:** YYYY-MM-DD
**Related SOPs:** <links>

## What this is
Plain-English explanation of what they are setting up and why, in 2–4 sentences. No jargon.

## What your customers will see
Describe the end result from the customer's point of view. Include a screenshot of the finished result.

> 🛡️ **Don't worry** — State clearly what will NOT change (their website, their email, etc.).

## Before you start
A short, friendly list of what they need (e.g. "your website login", "about 10 minutes"). Define any term they'll encounter.

## What you need to do
1. <One action.> <What they will see.> 
   _(screenshot pending: alt)_
   *Figure 1 — caption.*
   > 📸 **Screenshot needed** — `01-....png` — <exact capture spec>
2. <Next single action.> ...
(Number every step. One action each. Tell them exactly what to click and what appears next. Add an image at essentially every interaction point.)

## Platform-specific tips
If steps differ by website platform (WordPress, Squarespace, Wix, Shopify, custom), give a table or short sub-sections. Omit if not applicable.

## If something doesn't look right
Plain-English troubleshooting for the most likely problems, each with a friendly fix. Use 🤔 callouts.

> 💡 **Tip** — Helpful aside that smooths the process.

## You're done when
> ✅ **You're done when** — Describe the clear success state.

## Completion checklist
- [ ] <plain-English outcome the dealer can confirm>
- [ ] <plain-English outcome>

## Need a hand?
Reassure them help is available and how to reach it (account manager / support email).

Images (critical for dealer SOPs)

An image at essentially every screen the dealer touches: each login, each menu navigation, each field, and the final “it worked” confirmation.
Store in sops/dealer/images/<slug>/, named 01-..., 02-....
For every image not yet captured, add a 📸 Screenshot needed spec directly beneath the reference, describing exactly what to capture and reminding the capturer to crop out real account data.

Quality checklist (run before done)

Reads as plain English a non-technical owner can follow with zero help.
Every term is explained the first time it appears.
One action per numbered step; each step says what they’ll click and see next.
An image (or screenshot spec) exists for essentially every interaction point.
Reassurance is present: what will and won’t change is stated.
Troubleshooting, “You’re done when”, and completion checklist all present.
Metadata block complete and dated.
Added to sops/README.md dealer table.

Admin Sop Creation Guide Style Conventions