Seller placement review packet
Use this owner-review packet to collect route screenshots, source labels, seller signoff, source rights, contact routing, fallback paths, rollback decisions, and product-fit boundaries before a seller receives any final placement copy.
Placement review packet guidance only. Packet rows are sample planning records until real seller approval 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.
Owner review packet
The packet keeps screenshots, route checks, signoff, source rights, active inventory, contact ownership, fallback paths, rollback instructions, and product-fit boundaries together before handoff.
Record seller approval, owner reviewer, source owner, and whether the seller approved the exact destination and intended surface.
Seller approval summary, owner reviewer, seller slug, destination URL, intended surface, and approval date.
Hold the packet when approval is missing, verbal-only, stale, or tied to a different URL or placement surface.Open the destination on desktop and mobile and record status, H1, canonical/index state, direct-contact copy, no-overflow review, and no unsupported claims.
Desktop screenshot, mobile screenshot, route status, H1, canonical/index note, and direct-contact/no-guarantee scan.
Hold the placement when the route is broken, noindex unexpectedly, unclear, overflowing, or missing direct-contact marketplace copy.Attach the non-secret source-rights summary for inventory, photos, descriptions, source URLs, seller authority, and active approved status.
Rights status, inventory status, source URL policy, image-rights state, and listing-readiness reference.
Do not hand off a public placement if source, photo, seller authority, price, availability, or contact ownership is unclear.Record who owns buyer contact and where buyers go when inventory is stale, missing, sold, or not specific enough.
Contact owner, fallback path, wanted/saved-search handoff, seller profile path, and buyer confirmation language.
Hold the packet when buyers can reach a dead end or cannot tell that final terms are confirmed directly with the seller.Review the seller website location, widget preview, QR destination, printed link, email signature, or manual-share copy before handoff.
Placement preview, final copy, source label, intended location, rollback instructions, and expected buyer path.
No script installation, seller website edit, outbound message, form submission, analytics activation, call tracking, SMS, CRM delivery, or provider mutation is authorized.Decide whether the need belongs in Parts Masters, Surplix/eAgent, or Shop Command and keep the context source-labeled.
Product fit, workflow label, product-specific boundary, and manual follow-up note.
Do not imply a bundle, live integration, eBay mutation, cart flow, payment handling, freight service, or shared seller-result proof.Name the rollback owner and the condition that will pause, remove, or revise the placement.
Rollback owner, fallback path, stop condition, decision status, and next review date.
Do not hand off a placement unless a named owner can remove or revise it when facts change.Choose ready after owner approval, hold for rights, hold for inventory, hold for contact, block provider change, or revise copy.
Decision status, owner reviewer, decision date, next action, and packet notes.
Only the owner can move a packet from planning to handoff; Codex must not deliver or activate the placement.Packet template
Use these fields for a manual spreadsheet or owner packet. The packet is not CRM delivery, analytics, call tracking, seller notification, public proof, or seller website approval.
| Field | Required | Purpose | Example |
|---|---|---|---|
| Packet ID | Required | Stable internal id for the owner-review packet. | pm-review-001 |
| Seller slug | Required | Seller account or public seller page tied to the review. | parts-masters |
| Seller name | Required | Business name shown to the reviewer. | Parts Masters |
| Owner reviewer | Required | Person responsible for deciding whether the packet can move to handoff. | marketplace owner |
| Destination URL | Required | Reviewed Parts Masters path that a buyer will open. | /sellers/parts-masters/inventory |
| Route status | Required | HTTP and page-readiness result from desktop/mobile review. | 200; h1 present; indexable |
| Desktop screenshot | Required | Local evidence path proving the route rendered at desktop width. | artifacts/browser-qa/wave124/desktop-inventory.png |
| Mobile screenshot | Required | Local evidence path proving the route rendered at mobile width. | artifacts/browser-qa/wave124/mobile-inventory.png |
| Source label | Required | Bounded source value used for safe measurement links. | placement-review-packet |
| Intended surface | Required | Where the reviewed link, snippet, QR code, or copy may be placed later. | seller website inventory page |
| Approval summary | Required | Non-secret summary of seller and owner approval state. | owner_review |
| Rights status | Required | Source/photo/inventory authority state before handoff. | seller_provided |
| Inventory status | Required | Confirms active approved inventory or explains why the packet is held. | active_approved |
| Contact owner | Required | Who receives or owns buyer follow-up after direct contact starts. | parts desk |
| Fallback path | Required | Wanted request, saved search, or seller profile path when inventory is missing. | /wanted |
| Rollback owner | Required | Who removes or revises the placement when facts change. | marketplace owner |
| Decision status | Required | Current owner decision for the review packet. | ready_after_owner_approval |
| Next review date | Optional | Date for checking inventory freshness, routing, links, and rollback needs. | 2026-06-15 |
Route evidence
The owner packet should prove that buyers can inspect inventory, understand seller identity, reach a fallback path, and avoid cart-flow or result guarantees before a placement moves forward.
| Route | Path | Evidence needed | Hold if |
|---|---|---|---|
| hosted_inventory | /sellers/parts-masters/inventory | Desktop/mobile screenshots, 200 status, clear seller identity, inventory cards, direct-contact copy, and wanted fallback. | Inventory is empty, stale, pending, blocked, sold, or lacks approved seller contact routing. |
| seller_profile | /sellers/parts-masters | Seller name, location, contact context, inventory link, direct-contact copy, and public profile readiness. | Seller identity, public contact, or approved business owner is unclear. |
| listing_detail | /listings/[approved-listing-slug] | Listing H1, seller, condition, price type, source-labeled details, contact path, and no fitment/availability guarantee. | Listing source rights, photo rights, price, availability, condition, or seller contact are not approved. |
| wanted_fallback | /wanted | Wanted path, saved-search option, buyer confirmation language, and no guaranteed sourcing claim. | Fallback asks buyers to rely on unavailable inventory or implies guaranteed sourcing. |
| placement_preview | /seller-resources/placement-runbook | Placement surface copy, source label, rollback instructions, and no provider-change authorization. | The preview requires seller website edits, scripts, outreach, analytics, call tracking, SMS, CRM, or provider changes. |
| software_fit_contact | /contact | Manual product-fit context for Surplix/eAgent or Shop Command with product boundaries and no live integration claim. | The handoff implies a bundle, eBay mutation, cart flow, payment handling, freight service, or shared seller-result proof. |
Owner decision states
These statuses keep a useful placement from becoming public before rights, inventory, contact routing, provider boundaries, and copy quality are resolved.
The packet is complete enough for the owner to manually hand off reviewed copy later.
Owner may deliver the reviewed URL or copy outside Codex after seller approval is recorded.
Ready does not mean live, installed, sent, or proven.Source, photo, seller authority, or reuse scope is missing or unclear.
Collect corrected source-rights evidence before any handoff.
Do not rely on copied marketplace content or unclear image permissions.Inventory is not active, approved, useful, fresh, or specific enough for the buyer path.
Refresh listing readiness or route buyers to wanted/saved-search fallback only.
Do not preserve traffic by pointing buyers at stale or unavailable inventory.Buyer contact ownership, branch routing, or seller response owner is unclear.
Confirm the approved business owner for calls, emails, texts, inquiries, and follow-up.
Do not expose private contacts or route buyer details without approval.The placement depends on DNS, Cloudflare, analytics, call tracking, SMS, CRM, storage, or production DB changes.
Create a separate owner-approved provider plan before proceeding.
The review packet cannot authorize provider activation or third-party mutation.The route or placement copy is too broad, unclear, or claim-heavy.
Revise copy to direct-contact, manual quote, no-guarantee language and review again.
Competitor claims, sample packets, and planning records are not Parts Masters proof.Use for owner-reviewed marketplace placements, hosted inventory, seller profiles, listing detail paths, wanted fallback, widgets, and direct seller contact.
Parts Masters does not process cart flows, escrow, payment handling, freight service, title transfer, or guaranteed fitment and availability.Review next stepUse 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 cart flows, or claim seller results.Review next stepUse 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, cart flow, payment handling, freight service, or lead guarantee.Review next stepUse the placement checklist for approval gates, the runbook for log ownership, referral widgets for setup, referral reports for sample reporting, and measurement hooks for source labels before any seller receives placement copy.