Order timeline
Show the order date, product name, fulfillment or delivery status, and any delivery timestamp. Hide private customer details that are not needed for the audit.
Client intake
What to send for the first audit
The $29 launch audit can start from public store context and limited proof screenshots. The goal is to prove the order story without asking for Shopify admin access first.
One product flow
Masked data accepted
24-hour report after payment
Useful screenshots
Delivery or access event
Show a download, key reveal, email delivery, link click, account login, course access, or app delivery event connected to the order flow.
Policy context
Send the current refund terms, digital delivery terms, product page, and checkout consent text if they are visible to the buyer.
Do not send
No passwords or admin sessions
Do not send Shopify passwords, collaborator invites, payment processor admin access, payout access, bank data, or customer card data for the first audit.
No full customer exports
For the launch audit, mask unnecessary personal data. Order IDs, timestamps, product names, delivery events, and policy context are usually enough.
No live dispute submission
The first audit identifies proof gaps and prepares a response structure. It does not submit live disputes or promise processor, bank, issuer, platform, or legal outcomes.
What you get back
Proof readiness score
A simple score for whether the current flow can support a product-not-received or access dispute response.
Missing proof list
The exact missing items: product snapshot, policy context, delivery event, access event, buyer tie, or response structure.
Setup recommendation
A practical next step only if the gap is worth fixing. The $29 audit is credited toward setup for 7 days.
Why this is enough to start
Public flow first
The public product, terms, delivery description, and masked proof usually reveal the biggest gaps.
No trust leap
You do not need to grant admin access just to find out whether the audit is useful.
Fixed decision
After the report, either the flow is acceptable, or there is a clear setup project to quote.
1
Send context
The client sends the store, one product flow, delivery method, policy URL, and any masked proof available.
2
Confirm route
ProofKey confirms the fixed audit scope and the preferred payment route before work starts.
3
Start audit
The 24-hour clock starts after payment is received or a marketplace escrow milestone is funded.
4
Receive report
The client receives a proof readiness score, missing evidence list, dispute response structure, and setup recommendation.
What the report answers
Can this store show what was sold, what the buyer saw, how access was delivered, whether the buyer had relevant terms, and what proof is missing before a dispute response is prepared?