Skip to main content

Product Records

Product Records is a workspace for finding reliable product evidence when a merchant needs to answer a serious question:

  • What exactly did we sell?
  • Who bought it, when, and how many times?
  • What did they pay?
  • What stock movement or product changes happened around that time?
  • What report can we export for a dispute, warranty, or internal review?

It is designed for cases where normal catalog screens are not enough. A product page shows the current item. Product Records shows the trail around that item.

When to use it​

Use Product Records when:

  • A customer says they never bought a product.
  • A customer claims the product was different from what they bought.
  • A warranty, repair, or returns case needs the original sale details.
  • A staff member needs to check older product identity, SKU, barcode, price, or stock movement.
  • A manager needs an evidence packet for a payment dispute or internal investigation.

What you can review​

Product Records can show:

  • Product identity: name, SKU, barcode, brand, images, categories, tags, and current status.
  • Purchase trail: orders, quantity bought, amount paid, payment status, and purchase date.
  • Customer summary: who bought the item, how often, total paid, and last purchase date.
  • Inventory movement: stock changes connected to the product.
  • Timeline: product, purchase, inventory, and evidence activity in time order.
  • Evidence readiness: whether the record is ready to rely on and whether exports have been accessed.

Customer contact information is kept limited in the workspace. Treat exported evidence as sensitive business data.

How to use Product Records​

  1. Open Product Records from the workspace area.
  2. Search by product name, SKU, barcode, customer, order, serial, model, or year.
  3. Select the product record.
  4. Review the purchase trail, customer summary, inventory movement, and timeline.
  5. Check evidence readiness before relying on an export.
  6. Export a packet, printable report, or CSV file when you need to share the record.

Export options​

Use exports when you need to prepare a case file.

  • Packet: downloads the main evidence files together.
  • Print: opens a printable report.
  • CSV: exports purchases, customers, or inventory movement for spreadsheet review.
  • Copy actions: copies product identifiers used to match records across systems.

Only share exports with authorized staff, payment providers, legal representatives, or the customer involved in the case.

Keeping records reliable​

For stronger evidence:

  • Keep product records current and avoid deleting historical context.
  • Keep payment, fulfillment, and customer communication records attached to the case file.
  • Use the workspace proof status before exporting.
  • Record a point-in-time proof before sending evidence for a dispute or formal review.
  • Keep access to Product Records limited to staff who need it.

Product Records helps show a consistent business trail, but it does not replace legal advice. Banks, payment providers, courts, and regulators may still require additional documents.

Practical examples​

Customer says they never bought it​

Search the customer's name, order, email, phone, or year. Open the product record and review the purchase trail. Export the evidence packet and include payment and fulfillment proof from the order.

Customer says the item was different​

Open the product record and review the product identity, images, SKU, barcode, and timeline. Export the printable report and attach any delivery, message, or warranty notes.

Warranty claim years later​

Search by customer, product, barcode, serial, model, or year. Review the original purchase and product details before deciding whether the warranty applies.

Limits​

Product Records is not a full legal evidence system by itself. It is strongest when combined with:

  • Payment records.
  • Fulfillment and delivery proof.
  • Customer communication.
  • Staff action logs.
  • Warranty or repair documents.
  • External timestamping or notarization for formal evidence requirements.

Do not use Product Records to collect unnecessary personal data. Keep exports only as long as your business and legal policies require.