Custom-order evidence guide
How to document customer proof approval for custom orders
A useful approval record does more than say “approved.” It connects one Shopify order and line item to the exact proof version, the production specification, the customer's decision, and the file released to production.
For a proof-required order, the goal is simple: another person should be able to answer what was ordered, what changed, which version was approved, and what production used without reconstructing the story from several inboxes and folders.
The seven fields in a useful proof-approval record
1. Shopify order and custom line item
Start with the Shopify order number and identify the exact line item being approved. One order can contain several garments, placements, or personalisations; “order approved” is too broad when only one item or decoration is shown in the proof.
2. Exact proof filename and version
Use a fixed, versioned filename such as 1047-left-chest-v03.pdf. Avoid “latest proof,” “final,” or an attachment with no version. If the proof is replaced, create a new version rather than overwriting the old file.
3. Customer-facing production specification
The approval should make the important production details visible: garment or product, colour, quantity or size breakdown reference, personalisation text, placement, approximate dimensions, thread or colour references, and any limitation the customer needs to understand.
An embroidery-industry proof guide similarly tells customers to check the order number, design dimensions, digitised preview, product, colour, and position before acceptance. It also notes that production follows approval and later amendments may not be possible. See the embroidery proof guidance.
4. One unambiguous decision
Separate these outcomes: approved, changes requested, and not approved. A reply containing new edits is not approval. Record the requested changes, issue a new proof version, and ask for a fresh decision.
5. Approver, channel, date, and time
Keep the customer's name or business role, the email address or account used, the approval channel, and a timestamp with timezone. Preserve the original email, message export, form response, or platform event rather than copying only the words into an internal note.
6. Revision history
Retain each issued version and the decision attached to it. The useful sequence is: proof issued → changes requested → revised proof issued → approved. This prevents a later approval from being accidentally attached to an earlier file.
7. Production-release connection
Approval and production should point to the same version. A short release record can contain the order number, line item, approved proof version, production filename, release date, and staff member who released it. This is the handoff that keeps an approved customer-facing proof connected to the actual file used at the machine.
The practical test
Can a team member compare the approved proof and production file in under one minute without asking who handled the order?
A six-step approval-to-production workflow
- Freeze the ordered specification. Save the product, variant, quantities, personalisation, delivery requirement, and source artwork under the Shopify order number.
- Issue a named proof. Give every proof a unique version and show the production details the customer is expected to check.
- Ask for a structured decision. Invite approval or clearly listed changes; do not treat silence, payment, or an unrelated reply as approval.
- Preserve the original response. Keep the full message or event, including the sender, timestamp, and referenced version.
- Release only the approved version. Record which file went to production and who released it.
- Complete the order story. Connect finished-item photos, packing evidence, tracking, and delivery to the same order record.
Worked example: order #1047
Order captured. Navy polo, left-chest logo, 24 units; source artwork saved under order #1047.
Proof v01 issued. Customer asks for the logo to move 10 mm upward. Status: changes requested.
Proof v02 issued. Filename, placement, dimensions, garment, and colour reference are visible.
v02 approved. Original customer email and timestamp retained; no further changes included in the reply.
Production released. Release sheet points from order #1047 and proof v02 to the production file used.
Five approval records that look useful but are weak
- “Looks good.” The reply is retained, but the exact proof it refers to is unclear.
- “Final.pdf.” Several different files use the same name or overwrite one another.
- A screenshot without context. It omits the sender, full conversation, timestamp, or attachment reference.
- Approval followed by an undocumented change. Production uses a later adjustment that the customer never reapproved.
- An approved proof with no production link. The shop cannot show that production used the approved version.
Where chargeback evidence fits—and where it does not
Proof approval is an operational record first. It can help explain a custom order later, but it does not guarantee a complaint, refund request, or payment dispute will be decided in the merchant's favour.
Shopify says the appropriate evidence depends on the dispute reason and that merchants have a limited submission window. Shopify can populate basic order, billing, fulfilment, and shipping information, while merchants may add relevant evidence. Files must also meet Shopify's format and size rules. Read Shopify's current chargeback guidance and evidence-format requirements.
That is why the useful habit is to connect the records while the order is moving—not to promise that one form will determine an outcome later.
Frequently asked questions
Does a customer need to sign an approval form?
Not always. A retained email, form response, or proofing-platform event can record an explicit decision. What matters operationally is that the approver, exact version, decision, and timestamp remain connected. Your terms and local law determine the legal effect, so obtain appropriate advice for your business.
Is payment the same as proof approval?
No. Payment confirms a transaction, not necessarily the spelling, placement, dimensions, artwork version, or other custom production details.
What if the customer requests a change after approval?
Pause the release where possible, create a new proof version, record the change, and obtain a new approval before production resumes. Do not edit the already-approved file in place.
Should every Shopify order use this workflow?
Use it where the item is produced or personalised to a customer-specific specification and the customer is expected to approve a proof. Standard stocked products usually need a different evidence routine.
Start with your current process
Check whether your approval record connects to production.
The free ten-question score identifies the first gaps. The $49 Starter Kit adds editable approval messages, a version log, production-release sheet, photo routine, and Order Dossier tools.
This guide provides general operational information, not legal advice, compliance certification, or a guarantee of fewer errors, refunds, disputes, chargebacks, or favourable outcomes.