Seller placement runbook

Run the first seller placement from approval to rollback.

Use this runbook and placement-log template before any seller receives a hosted inventory URL, seller website link, widget snippet, QR code, printed link, email-signature link, or manual share.

First-placement runbook guidance only. Log rows are sample planning records until real seller usage and lead history exist. This is not public seller pricing, not verified seller results, and not a lead, sales, traffic, backlink, ranking, or SEO guarantee. Parts Masters remains a direct-contact marketplace. Buyers confirm price, condition, fitment, freight, payment, title, and availability directly with sellers.

Runbook control record

Record the placement before a seller receives a link, snippet, QR code, or share copy.

The runbook keeps seller approval, source rights, active inventory, contact routing, fallback paths, source labels, rollback ownership, and review dates together before handoff.

Listing readiness
Runbook steps7manual workflow
Log fields14record template
Rollback triggers4stop rules
Product paths3kept separate

Create the placement-log row

Record seller, placement type, destination URL, source label, intended location, fallback path, contact owner, rollback owner, and review date.

Placement-log row, seller slug, source label, destination URL, intended placement location, and reviewer.

Do not hand off any URL, widget, QR code, or manual-share copy until the row exists.

Verify the destination

Open the hosted inventory, seller profile, listing, wanted fallback, or software-fit contact route on desktop and mobile.

Browser screenshot, route status, no-overflow check, direct-contact copy, and no-checkout/no-guarantee check.

Hold the placement if the page has stale inventory, broken links, unsupported claims, or unclear seller identity.

Preview the placement surface

Review the seller website link location, widget preview, QR destination, printed link copy, email signature, or manual-share wording.

Placement preview, final link copy, source label, expected buyer path, and buyer fallback note.

Do not install scripts, change seller websites, send emails, submit forms, or activate analytics from Codex.

Collect seller and owner signoff

Save seller approval, owner approval, source/photo rights, active inventory check, contact routing approval, and rollback owner.

Approval summary, rights status, active inventory status, contact owner, fallback path, and date.

Hold the placement when approval is missing, verbal-only, stale, or tied to unapproved provider changes.

Hand off the approved placement manually

Provide the reviewed URL or snippet to the seller or owner with the exact source label and rollback instructions.

Manual handoff note, reviewed copy, destination URL, source label, and rollback instructions.

No automated outreach, CRM import, email/SMS delivery, seller notification, or third-party mutation is authorized.

Review early activity without claiming results

Use bounded source context and sample reporting language to decide whether the placement should stay, be revised, or be removed.

Manual review note, source label, placement status, any approved first-party signal, and next review date.

Do not call activity real seller proof, sales proof, traffic proof, lead guarantee, backlink value, or SEO value.

Rollback or refresh when facts change

Remove, pause, or revise the placement when inventory, rights, contact routing, seller approval, buyer fallback, or provider boundaries change.

Rollback trigger, removal owner, updated destination or copy, and final status.

Keep the placement paused until the owner records a corrected approval path.

Placement log template

Fields to record before first seller placement handoff.

Use these fields for a manual spreadsheet or owner review packet. The log is not CRM delivery, analytics, call tracking, seller notification, or public proof.

Measurement hooks
Placement-log fields for owner review before seller handoff
FieldRequiredPurposeExample
Placement IDRequiredStable internal id for the placement record.pm-placement-001
Seller slugRequiredSeller account or public seller page tied to the placement.parts-masters
Placement typeRequiredHosted URL, seller website link, widget, QR/printed link, manual share, or software-fit handoff.hosted_inventory_url
Destination URLRequiredReviewed Parts Masters path that buyers will open./sellers/parts-masters/inventory
Source labelRequiredBounded source value used in safe measurement links.first-seller-placement
Intended locationRequiredWhere the seller or owner plans to place the link or snippet.seller website parts page
Seller approvalRequiredRecords whether the seller approved the exact placement.owner_review
Rights statusRequiredSource/photo/inventory authority state before placement.seller_provided
Inventory statusRequiredConfirms active approved inventory or explains why the placement is held.active_approved
Contact ownerRequiredWho receives or owns buyer follow-up after direct contact starts.parts desk
Fallback pathRequiredWanted request, saved search, or seller profile path when inventory is missing./wanted
Rollback ownerRequiredWho removes or revises the placement when facts change.marketplace owner
Review statusRequiredCurrent state: sample hold, owner review, ready after approval, live, paused, or removed.owner_review
Next review dateOptionalDate for checking inventory freshness, routing, links, and rollback needs.2026-06-15

Sample rows

Use sample rows only for planning until seller approval and real history exist.

These rows show how to separate hosted inventory, widget preview, and software-fit handoff records without claiming results or activating provider workflows.

Demand signals
Sample placement-log rows for planning only
Placement IDSellerTypeSource labelStatusBoundary
pm-placement-sample-001sample-trailer-sellerhosted_inventory_urlfirst-seller-placementowner_reviewSample row only. No seller website change or traffic claim is authorized.
pm-placement-sample-002sample-parts-sellerwidget_previewwidget-previewsample_holdSample row only. No script installation, analytics, call tracking, or CRM delivery is authorized.
pm-placement-sample-003sample-shop-operatorsoftware_fit_handoffsoftware-fitready_after_approvalSample row only. Separate product-fit interest does not create a live integration or checkout.

Rollback triggers

Pause the placement when facts, rights, routing, or provider boundaries change.

A useful seller placement is reversible. Every log row needs a named rollback owner before the seller receives the final destination or snippet.

Approval checklist

Inventory becomes stale, empty, pending, blocked, sold, or no longer seller-approved.

Pause or remove the placement until active approved inventory is restored.

Do not keep a placement live to preserve traffic if the buyer path is no longer useful.

Source rights, photo rights, seller authority, or contact routing becomes unclear.

Remove the placement and keep the log row in review until evidence is corrected.

Do not rely on copied marketplace content, unclear image rights, or private contacts.

The placement requires DNS, Cloudflare, analytics, call tracking, SMS, CRM, email-provider, storage, or production DB changes.

Block the placement and create a separate owner-approved provider plan.

This runbook cannot authorize provider activation or third-party mutation.

The seller asks to publish performance, backlink, SEO, lead, sales, revenue, ROI, fitment, or availability claims.

Keep the placement sample/manual until real seller-specific history is approved for public use.

Competitor claims and sample logs are not Parts Masters proof.

Parts Masters

Use for approved public inventory, seller placement logs, hosted inventory pages, widgets, referral reports, wanted fallback, and direct seller contact.

Parts Masters does not process checkout, escrow, payment, freight, title transfer, or guaranteed fitment and availability.Review next step

Surplix / eAgent

Use when a seller needs separate eBay listing research, repricing review, comp evidence, or seller-controlled listing operations.

This does not authorize Parts Masters to mutate live eBay listings, publish inventory, create checkout, or claim seller results.Review next step

Shop Command

Use when the operator needs separate shop operations support for service orders, technician time, parts workflow, customer history, and invoicing readiness.

Shop Command is separate shop software, not Parts Masters seller proof, checkout, payment, freight, or lead guarantee.Review next step

What this runbook does not authorize

  • The placement runbook is not actual seller lead history or verified seller results.
  • The placement log is not public seller pricing, checkout, payment processing, escrow, freight service, title transfer, inspection, automated ad delivery, or provider activation.
  • Seller placement logs do not guarantee leads, sales, traffic, backlinks, SEO value, ranking, revenue, ROI, fitment, price, condition, or availability.
  • No seller outreach, valid form submission, buyer record creation, production import, storage upload, seller website change, CRM delivery, third-party analytics, call tracking, SMS attribution, seller notification, Cloudflare change, DNS change, billing change, or provider mutation is authorized by this resource.
  • Surplix/eAgent and Shop Command remain separate products and are not implied live Parts Masters integrations.

Recommended next step

Use the placement checklist for approval gates, referral widgets for setup, referral reports for sample reporting, the review packet for route screenshots and owner decision status, listing readiness for inventory gates, and measurement hooks for source labels before any seller receives public placement copy.