Wrong information on my card after proofing it

Approved a proof and received a card with a different middle name than what I had submitted. The proof had shown the correct name. Understanding what happened and how to resolve it took some back-and-forth with the vendor. Here is the full picture.

What the proof should prevent

The proofing process exists specifically to catch this type of error before production. The proof shows a mockup of your card exactly as it will be printed. If the proof is correct and you approve it, the finished card should match the proof. This is the vendor's guarantee, explicit or implied, in the proofing workflow.

What actually happened

According to the vendor, the approved proof was from my correct submission but a production system error applied a different name field from an adjacent order in the same production batch. This is a vendor-side quality control failure — the proof and the production order got decoupled somewhere in their workflow.

Resolving it

I photographed both the incorrect card and my proof screenshot showing the correct name. Sent both to vendor support with the order number. The vendor acknowledged the error and offered a replacement at no charge with priority production. The replacement arrived 10 days later and matched the proof correctly.

What this experience revealed

Even when you do everything right — careful proof review, explicit approval — production errors can still occur. The proof process minimizes these but does not eliminate them entirely. Document your proof by screenshotting the approved proof image before submitting approval. If a card arrives with an error, the proof screenshot is your evidence that the error is on the vendor's side, not yours. Without that documentation, the dispute is harder to resolve quickly.

The broader takeaway is to document the proof approval before the card ships rather than after. Screenshot the proof image, note the date you approved it, and keep that documentation until the card arrives and you have confirmed it is correct. This documentation is what separates a quick vendor correction from a prolonged dispute about who introduced the error.