Weekly seller evidence packet
Use this packet guide after the pilot KPI tracker to decide what can appear in a seller-private weekly report, what remains owner-only, and what is safe for public education later.
Weekly seller evidence packet guidance only. Packet fields are planning and owner-reviewed reporting templates, not public seller pricing, not actual seller performance, not verified seller results, and not lead, sales, traffic, backlink, ranking, conversion, revenue, ROI, or SEO guarantees. Parts Masters remains a direct-contact marketplace. Buyers confirm price, condition, fitment, freight, payment, title, and availability directly with sellers.
Private reporting shape
The packet turns the pilot KPI tracker into seller-private weekly reporting. Each row keeps source, evidence state, owner action, redaction status, and product fit separate before anything is shared.
Give one seller a clear weekly view of approved inventory status, aggregate buyer activity, and next owner action.
Seller slug, week start, active listing count, aggregate views, aggregate contact clicks, aggregate inquiries, wanted matches, saved-search demand, and follow-up status.
Seller-private summaries are not public case studies, lead guarantees, revenue proof, ROI proof, or public seller pricing.Keep the proof source, redaction status, approval note, and next owner action clear before any number leaves private review.
Evidence artifact path, owner next action, source-rights decision, route screenshots, route labels, command evidence, and redaction status.
Owner-only notes do not authorize outreach, publication, seller website placement, import activation, or provider changes.Explain the reporting process publicly without revealing seller performance, buyer identity, or private operational evidence.
Approved route categories, evidence classes, workflow steps, no-checkout direct-contact framing, and generic reporting examples.
Public-safe education must not claim actual results, verified seller outcomes, guaranteed traffic, guaranteed leads, or guaranteed sales.Name material that must be rejected, redacted, or held outside public repo docs before a seller report moves forward.
A non-sensitive blocked status, reason code, owner action, no-action note, and whether a secure owner-controlled location is required.
Blocked material must not be imported, published, used for outreach, used as public proof, or used to activate seller placement.Packet fields
Do not include buyer names, buyer emails, buyer phone numbers, private seller contacts, credentials, contracts, payment data, raw analytics exports, provider tokens, customer records, or unredacted approval evidence in public pages or repo docs.
| Field | Packet question | Evidence source | Seller-private use | Blocked use |
|---|---|---|---|---|
| Inventory rows received | Did the seller provide a file, export, source URL, or row set for the week? | Seller intake tracker, intake packet, source-rights evidence index, and owner-approved file summary. | Show the seller what was received and what still needs cleanup before pending-only review. | Do not expose raw files, credentials, private contacts, source URLs with secrets, or unapproved media. |
| Pending import rows | Which rows are ready for pending-only review and which rows are blocked? | Import validation output, field-map notes, source-rights status, and owner review packet. | Show aggregate ready/blocked row counts and the next owner action. | Do not import production data, publish listings, upload storage, or treat pending rows as active supply. |
| Public activation count | How many listings were activated publicly after exact owner approval? | Owner approval note, public route, listing status, source/photo rights, and contact-route review. | Show approved public activations for the seller after evidence exists. | Do not claim availability, publish inventory, mark listings live, or imply activation without approval. |
| Active listing count | How much approved public supply is contact-ready at week end? | Public listings, seller profile, sitemap/link checks, listing freshness, and contact-route review. | Show seller-scoped active listing totals and missing readiness gates. | Do not claim stock is available, fitment is guaranteed, or buyer purchase terms are handled by Parts Masters. |
| Listing views | Did approved listings receive aggregate buyer views this week? | Owner-approved analytics, route events, server logs, or redacted evidence artifacts. | Show aggregate views for seller discussion after real evidence exists. | Do not publish raw analytics, visitor identity, traffic guarantees, rankings, conversion proof, revenue, or ROI. |
| Contact clicks | Did buyers open call, text, email, profile, or inquiry paths? | Contact-start events, listing/seller route labels, admin records, and redacted owner evidence. | Show seller-scoped aggregate contact starts after privacy review. | Do not expose buyer names, phone numbers, emails, messages, call recordings, SMS threads, or seller-result proof. |
| Inquiries | Did buyer inquiries exist, and what owner action is next? | Lead records, contact-routing review, notification status, spam state, and owner redaction notes. | Show aggregate inquiry count and follow-up status without buyer PII. | Do not publish buyer details, messages, revenue, closed-won status, lead quality, or public seller-result claims. |
| Wanted matches | Did wanted demand match seller inventory categories, states, or part families? | Wanted-request starts, no-result demand, saved demand, admin match notes, and redacted owner evidence. | Show demand categories that may guide seller supply cleanup. | Do not broadcast buyers to sellers, send seller notifications, share buyer contact details, or guarantee buyer response. |
| Saved-search demand | Are buyers preserving repeat demand for a part, truck, trailer, equipment type, or location? | Saved-search starts, no-result searches, route labels, and owner-approved aggregate reports. | Show aggregate demand direction to help prioritize inventory cleanup. | Do not promise alerts, leads, sales, availability, fitment, or seller response. |
| Referral or widget evidence | Did approved seller links, share pages, widgets, or placement paths generate safe referral context? | Referral report, placement log, route screenshots, seller approval, owner review packet, and measurement labels. | Show approved placement status and aggregate referral context after seller approval. | Do not edit seller websites, install scripts, use Cloudflare, activate analytics, or guarantee SEO, backlinks, traffic, leads, or sales. |
| Surplix/eAgent referral intent | Did the seller need separate eBay listing research, repricing review, comp evidence, or listing operations help? | Software-stack path, source parameters, manual owner note, and approved eBay-operations context. | Show that the need belongs in a separate Surplix/eAgent conversation. | Do not mutate eBay, revise listings, publish inventory, create checkout, or combine product results. |
| Shop Command referral intent | Did a shop or fleet need service orders, technician time, parts workflow, customer history, or invoicing readiness? | Software-stack path, source parameters, manual owner note, and approved shop-operations context. | Show that the need belongs in a separate Shop Command conversation. | Do not transfer customer records, imply marketplace integration, create invoices, or treat shop-operations interest as seller proof. |
Evidence fields
These fields align with the pilot KPI tracker runbook: use zero or blank sample values until real, owner-approved evidence exists, and never treat source parameters as seller results.
Did the seller provide a file, export, source URL, or row set for the week?
Use only an approved aggregate intake status without seller identity or raw file details.
Do not expose raw files, credentials, private contacts, source URLs with secrets, or unapproved media.Which rows are ready for pending-only review and which rows are blocked?
Use row-state categories only after redaction and owner approval.
Do not import production data, publish listings, upload storage, or treat pending rows as active supply.How many listings were activated publicly after exact owner approval?
Use approved public active listing counts only when activation evidence is current.
Do not claim availability, publish inventory, mark listings live, or imply activation without approval.How much approved public supply is contact-ready at week end?
Use public active listing counts after source rights, freshness, and contact routing are reviewed.
Do not claim stock is available, fitment is guaranteed, or buyer purchase terms are handled by Parts Masters.Did approved listings receive aggregate buyer views this week?
Use trend direction only after owner approval and redaction.
Do not publish raw analytics, visitor identity, traffic guarantees, rankings, conversion proof, revenue, or ROI.Did buyers open call, text, email, profile, or inquiry paths?
Use contact path categories only after owner approval.
Do not expose buyer names, phone numbers, emails, messages, call recordings, SMS threads, or seller-result proof.Did buyer inquiries exist, and what owner action is next?
Use non-sensitive aggregate summaries only after owner and seller approval.
Do not publish buyer details, messages, revenue, closed-won status, lead quality, or public seller-result claims.Did wanted demand match seller inventory categories, states, or part families?
Use category/state/part-family summaries without buyer identity.
Do not broadcast buyers to sellers, send seller notifications, share buyer contact details, or guarantee buyer response.Are buyers preserving repeat demand for a part, truck, trailer, equipment type, or location?
Use non-sensitive demand categories after owner review.
Do not promise alerts, leads, sales, availability, fitment, or seller response.Did approved seller links, share pages, widgets, or placement paths generate safe referral context?
Use approved placement labels only, not traffic proof or backlink proof.
Do not edit seller websites, install scripts, use Cloudflare, activate analytics, or guarantee SEO, backlinks, traffic, leads, or sales.Did the seller need separate eBay listing research, repricing review, comp evidence, or listing operations help?
Use product-fit category only after owner approval.
Do not mutate eBay, revise listings, publish inventory, create checkout, or combine product results.Did a shop or fleet need service orders, technician time, parts workflow, customer history, or invoicing readiness?
Use product-fit category only after owner approval.
Do not transfer customer records, imply marketplace integration, create invoices, or treat shop-operations interest as seller proof.Evidence states
A weekly packet becomes useful only when the evidence level is clear. Public pages should explain the workflow, not reveal private performance or raw proof.
Blank or example report shape before a real seller pilot has evidence.
Field names, owner gates, example decisions, and no-action boundaries.
Any real seller number, buyer identity, private contact, raw export, or performance claim.Internal weekly review before any seller receives the packet.
Redacted evidence paths, aggregate metrics, owner action, and blocked reasons.
Secrets, tokens, contracts, payment data, buyer PII, private seller contacts, and unredacted screenshots.Seller-specific weekly review after source, redaction, and contact-routing boundaries are approved.
Seller-scoped aggregates, active listing status, demand categories, and next action.
Other seller data, buyer PII, raw logs, provider exports, and public case-study language.Public education or approved case-study copy after real evidence exists and exact wording is approved.
Approved route categories, generic evidence classes, and reviewed non-sensitive trends.
Unapproved seller names, raw numbers, buyer identity, competitor comparisons as proof, and public pricing.Classify every metric as sample-only, owner-private, seller-private, public-safe, or blocked before it enters the weekly packet.
Owner confirms the evidence state and next action before report preparation.
Classification does not authorize outreach, imports, seller messages, publication, or provider changes.Remove buyer identity, private seller contacts, credentials, contracts, raw analytics, provider data, and unapproved approval evidence.
Owner confirms the redacted evidence artifact and seller-scoped summary.
Redaction review does not approve public case studies, seller website placement, or pricing claims.Keep Parts Masters marketplace evidence, Surplix/eAgent eBay-operations intent, and Shop Command shop-operations intent in separate rows.
Owner decides whether any separate product conversation is worth manual follow-up.
Product-fit notes do not create bundles, integrations, checkout, eBay mutations, CRM writes, or customer-record transfers.If any seller summary becomes external, the owner must approve source, wording, attribution, redaction, and seller permission.
Owner approval is required before any seller receives final packet copy or public wording.
Codex must not send the packet, submit forms, publish reports, contact sellers, or deploy changes.Separate product fit
Parts Masters evidence stays tied to marketplace discovery and direct seller contact. Surplix/eAgent and Shop Command intent remains separate and owner-reviewed.
The weekly evidence relates to marketplace discovery, approved public supply, direct seller contact, wanted demand, saved-search demand, or seller reporting readiness.
Seller-scoped aggregate route, listing, contact, inquiry, wanted, saved-search, and owner-action summaries after redaction.
Parts Masters does not process checkout, payment, escrow, freight, title transfer, or guarantee fitment, availability, leads, sales, traffic, rankings, revenue, or ROI.Review fit pathThe seller needs a separate eBay listing research, repricing review, comp-evidence, or seller-controlled listing-operations conversation.
Product-fit intent, route source, manual owner note, and no-live-mutation status.
Surplix/eAgent is separate and does not authorize live eBay mutation, Parts Masters listing publication, checkout, or shared seller-result proof.Review fit pathA repair shop or fleet needs service orders, technician time, parts workflow, customer history, or invoicing readiness.
Product-fit intent, route source, manual owner note, and no customer-record transfer status.
Shop Command is separate shop software, not Parts Masters checkout, payment, freight, marketplace integration, invoicing automation, or seller proof.Review fit pathStart with the pilot KPI tracker, then prepare the seller-private packet only after source, redaction, owner action, and product-fit boundaries are clear. Use referral reporting only when the evidence starts with an approved seller placement, widget, or manual share.
Review KPI trackerReview referral reportManual demo path