Source-rights evidence index

Know where each source-rights proof belongs.

Use this evidence index before a seller file, export, photo set, source URL, contact route, or software-fit note moves forward. It separates public-safe summaries from secure owner records and blocked material.

Source-rights evidence index guidance only. Seller pricing remains manual quote only. This is not legal approval, not public seller pricing, not actual seller performance, not verified seller results, and not a lead, sale, traffic, backlink, ranking, conversion, revenue, ROI, or SEO guarantee. Parts Masters remains a direct-contact marketplace. Buyers confirm price, condition, fitment, freight, payment, title, and availability directly with sellers.

Evidence classes

Keep source proof useful without turning it into public proof.

Each class separates the public-safe summary from the secure owner record, legal review cue, blocked material, and next internal step before seller inventory can move toward pending-only review.

Listing rules

Seller authority

Seller confirms it owns, controls, brokers with authority, or has permission to market the inventory.

Use a non-sensitive status such as seller authority summary recorded by owner.

Authority evidence does not publish inventory, approve outreach, create seller proof, or guarantee availability.Review intake checklist

Source file or export

Inventory rows come from a seller spreadsheet, dealer/DMS export, owner-authorized eBay export, internal record, or approved feed.

Use a source class, source channel, row count, and owner-reviewed status without private links or tokens.

A source-file record does not import, persist, publish, revise, delete, mark sold, or contact anyone.Record intake packet

Photo and media rights

Photos, videos, image URLs, and media folders are seller-provided, Parts Masters-owned, or permission-confirmed.

Use photo-rights status, media source class, and review state without exposing original private evidence.

Photo readiness does not prove condition, fitment, title, availability, seller response, or final transaction terms.Review readiness

Source URL and marketplace-export permission

Source URLs are preserved when available, and marketplace or eBay export reuse is owner-authorized before review.

Use source URL policy, source channel, and permission-confirmed summary without copying restricted content.

Source URL evidence does not authorize eBay mutation, provider changes, checkout, payment, seller outreach, or public seller claims.Review channel fit

Contact route and update owner

Approved public seller contact route plus owner for price, quantity, sold status, photos, and availability refresh.

Use public business contact route, branch owner, and refresh cadence summary only.

Contact routing does not send messages, guarantee response, activate CRM, enable call tracking, or prove seller performance.Review measurement hooks

Sensitive-data exclusions

Credentials, private records, buyer/customer data, payment records, and unapproved proof are identified before intake starts.

Use a simple excluded-data status such as sensitive material excluded from repo and public pages.

Sensitive-data exclusion is a safety gate, not legal approval, import approval, public activation, or seller-result proof.Review trust policy

Where proof belongs

Public pages should contain summaries, not raw proof.

Do not place secrets, passwords, API keys, buyer lists, customer records, payment data, bank data, private employee contacts, unapproved media, or unredacted permission evidence in repo files or public docs.

Intake packet

Public guidance summary

Seller-resource pages, source-rights index copy, listing rules, and public education.

Non-sensitive status, source class, proof type, review state, allowed next step, and claim boundaries.

Public summaries are guidance only and must not become seller proof or legal approval.

Owner-controlled evidence record

Real seller files, signed approvals, source exports, media folders, field maps, and owner approval notes.

Records the owner is allowed to retain in a secure local folder, business vault, approved CRM, or approved production system after approval.

Owner records remain private and do not authorize publication, outreach, provider changes, or seller-result claims.

Legal review packet

Questions about seller agreements, content license, titled assets, buyer-lead use, source reuse, privacy, and seller reporting.

Counsel questions, redacted examples, policy drafts, source-rights summaries, and route screenshots.

Legal review packet content is not legal advice or approval until counsel-approved language is recorded.

Blocked material

Proof or source material that must be rejected, redacted, quarantined, or held outside the marketplace workflow.

A safe non-sensitive blocked status, reason code, next owner action, and no-action boundary.

Blocked material must not be imported, published, promoted, sent to outreach, or used as seller proof.

Evidence index

Use the index before a file, photo set, or contact route enters review.

The table gives the owner a safe checklist for what may be summarized, what belongs in a secure owner record, what needs legal review, and what should be blocked.

Measurement hooks
Source-rights evidence classes and safe storage boundaries
EvidencePublic summarySecure owner recordLegal review cueBlocked material
Seller authorityUse a non-sensitive status such as seller authority summary recorded by owner.Signed seller approval, written authorization, seller agreement exhibit, or owner approval note.Ask counsel before using this proof for paid seller onboarding, titled assets, broker authority, or indemnity language.Do not store signed contracts, private IDs, title documents, private emails, or unredacted proof in public repo docs.
Source file or exportUse a source class, source channel, row count, and owner-reviewed status without private links or tokens.Raw files, source export, field map, import validation output, and cleanup notes in the approved owner-controlled folder.Review reuse permission when the source is a third-party platform, supplier feed, dealer website, or marketplace export.Do not store tokenized links, passwords, private customer rows, vendor cost, buyer lists, or private operational exports in repo docs.
Photo and media rightsUse photo-rights status, media source class, and review state without exposing original private evidence.Original photo folder, seller approval, media permission note, image-source map, and redaction notes.Ask counsel before using media beyond listing/search pages, such as widgets, advertising, social previews, or seller reporting.Do not store unapproved marketplace photos, customer paperwork, private documents, license-plate-sensitive images, or unredacted media proof in public docs.
Source URL and marketplace-export permissionUse source URL policy, source channel, and permission-confirmed summary without copying restricted content.Owner export proof, source URL list, approved API/export note, platform-permission record, or seller reuse permission.Review platform terms before production use of marketplace pages, supplier catalogs, scraped pages, API data, or feed reuse.Do not crawl, scrape, or copy third-party marketplace pages for production imports without explicit permission and reuse rights.
Contact route and update ownerUse public business contact route, branch owner, and refresh cadence summary only.Seller-approved lead recipient, branch routing note, update-owner note, stale review cadence, and owner approval.Review consent and privacy language before sharing buyer details, wanted requests, call/SMS attribution, CRM delivery, or seller notifications.Do not store private employee contacts, customer contacts, buyer PII, call recordings, SMS consent data, or CRM credentials in public docs.
Sensitive-data exclusionsUse a simple excluded-data status such as sensitive material excluded from repo and public pages.Only store sensitive evidence in the approved owner-controlled location when the owner and policy allow retention.Ask counsel or the owner before retaining contracts, buyer/customer records, employee contacts, payment records, bank data, or regulated documents.Never store secrets, passwords, API keys, payment data, bank data, private buyer lists, private customer records, or unredacted permission evidence in repo docs.

Separate software fit

Record software evidence without creating a bundle promise.

Source-rights evidence can explain whether the seller problem belongs in Parts Masters, Surplix/eAgent, or Shop Command. It must not imply live integrations or shared results.

Software stack

Parts Masters

The evidence supports direct-contact marketplace listing review, wanted demand, seller reporting readiness, or owner-reviewed placement.

Source-rights status, approved source class, contact route, update owner, pending-only import readiness, and public-safe summary.

Parts Masters does not process checkout, payment, escrow, freight, title transfer, inspection, or guaranteed fitment and availability.Start fit conversation

Surplix/eAgent

The evidence concerns separate eBay listing research, comp review, repricing review, listing cleanup, or seller-controlled eBay workflow support.

Owner-authorized export note, source-labeled listing sample, eBay operation problem, and clear separation from Parts Masters publication.

Surplix/eAgent is separate and does not authorize live eBay mutation, Parts Masters publication, checkout, or shared seller-result proof.Start fit conversation

Shop Command

The evidence shows a repair-shop operations need such as service orders, technician time, parts workflow, customer history, or invoicing readiness.

Shop workflow note, surplus-inventory split, approved business contact route, and no customer-record transfer unless separately approved.

Shop Command is separate shop software, not Parts Masters checkout, seller reporting proof, listing publication, or marketplace integration.Start fit conversation

Claim boundaries

  • No checkout, cart, buy-now, escrow, payment processing, buyer payment, freight booking, title transfer, inspection, buyer protection, or fulfillment is implied.
  • No guaranteed fitment, guaranteed availability, guaranteed lead volume, guaranteed sales, guaranteed traffic, guaranteed backlinks, guaranteed ranking, conversion, revenue, ROI, or seller profit is allowed.
  • No actual seller performance, verified seller results, public seller pricing plan, lead-history proof, legal approval, or competitor-equivalent result is created by this evidence index.
  • No seller outreach, buyer outreach, valid form submission, production import, storage upload, listing publication, CRM delivery, email, SMS, call tracking, analytics activation, Cloudflare change, DNS change, billing change, eBay mutation, or seller website change is authorized.
  • No secrets, passwords, API keys, private buyer lists, private customer records, payment data, bank data, private employee contacts, unapproved media, or unredacted permission evidence should be recorded in repo docs.
  • Surplix/eAgent and Shop Command remain separate products, not bundled Parts Masters checkout, reporting, listing-publication, or integration promises.

Next safe step

Start with the intake checklist when the seller has not prepared evidence. Use the packet template when the owner needs to record a public-safe summary. Use listing readiness after source, media, contact, and update-owner evidence are summarized.

Intake checklistIntake packetListing readinessWeekly evidence packetAsk what proof belongs where