REDDIT 原始帖子
How do you protect yourself from "I never approved that" disputes on custom orders?
Anyone else selling made-to-order or personalized products deal with customers who forget (or claim to forget) what they actually approved before it shipped? I had a mix-up recently where a customer said they never confirmed a detail that was clearly in our…
Anyone else selling made-to-order or personalized products deal with customers who forget (or claim to forget) what they actually approved before it shipped? I had a mix-up recently where a customer said they never confirmed a detail that was clearly in our message thread, and it made me realize I don't have anything like a proper sign-off - just scattered chat logs. How are you handling proof approvals in a way that's actually documented, not just "somewhere in our messages"?
已收录讨论
Moderator Announcement Read More » Friendly Reminder r/smallbusiness is a question and answer subreddit. Ask a question about starting, owning, and growing a small business and the community answers. Posts that violate the rules listed in the sidebar will be removed. Please do not conduct market research on our community. We are not your focus group and asking us about our pain points, needs, what is hardest about X, etc. is not asking about how small business works or for real help with running your small business. These posts are subject to removal and given the community's disgust with the constant spamming of these posts you might just destroy your brand and contaminate your company search results. Seeing this message does not mean your post was automatically removed. If you asked about pain points or are directly or indirectly promoting a product please remove your post. Come back to post an honest question or give a knowledgeable response to someone else's question and leave your company name in your own profile. We can tell if you know what you're doing and the community can reach out if they need to. We welcome honest question posts, especially from newcomers. Thank you for your post. I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
Yeah, that's the exact problem - going back through a thread to figure out if someone "technically" agreed is subjective, and even when it's clear to me it's not always clear to them (or to Etsy support if it escalates). Honestly this thread is pushing me toward just building a simple one-pager for it - customer sees exactly what's being approved (spelling, color, size, whatever matters for that order) and gives a clear yes/revision instead of a scroll-and-interpret mess. Doesn't need to be legal-grade, just needs to kill the "well it's open to interpretation" argument.
Agreed completely - that's basically what pushed me to build one for myself. A message log tells you what was said, but a proper approval sheet tells you what was actually agreed, which is the part that matters when a customer pushes back later.
I am just wondering is it subjective or is it clear. If the comms are subjective conflict arises. But if it is clear, by anyone reading the comms then the person opposing needs to concede. It really cannot be both in my opinion. It is clear to anyone reading, or subjective and open to confusion. Yeah, I hear you. I am reading into this that they ( the buyer ) is maybe opposing an Etsy rule. If that is the case, this issue is more complex. Hmm. I understand where you're coming from and I really do hope there is resolve. I agree, not legal grade, but some kind of other accountability if such a vision exists.
Message logs are good but a written proof approval contract is much much better.
Would a type of docusign situation be useful? Even a simple one-pager prior to shipping? In reviewing their opposing views of the comms, can you see it is subjective, or is it plain-as-day to comprehend they agreed? Just wondering, is it open to doubt they agreed, or clear to many who reads the comms they agreed?
Always have a standard order form with the design specs or project details spelled out, delivery timeline, costs, and signed by the customer. While brevity is important, clarity is as well, as it minimizes a lot of communication challenges. Any deviations, a similar form that says Change Order, listing the project changes, cost changes, and signed by the customer.
Have been in a custom biz for decades. After all the messaging back and forth you need to create a very clear description and proof for them to approve. Then start the job. Our biggest problems were when more than one person from our business was involved. That's where the extra details got lost and where we lost money by having to replace or refund. And sometimes it's impossible to please a customer. On customer insisted on a specific pms color for her project and we had to special order it. After it was done she refused it saying it didn't look like that color and what was I going to do about it. Really, what can I do, we used the exact color you wanted. I don't have anything to fix. It looks like that color to the rest of us. In that case I chose to refund her, throw her items in the trash and we won't do business with her again. With someone like that you can't ever please them and they think so highly of themselves, they will certainly give bad reviews. The best way to avoid issues is don't agree to do anything special. Limit the choices people have. No special requests, nothing additional without an additional fee.
A form or contract still needs someone to remember to save it and dig it up later if there's a dispute. The stronger version is making the approval itself the gate, so production literally can't start until it happens. Customer gets sent the exact mockup, clicks approve on that specific link, and the timestamp gets created the moment they click. Doesn't need to be complicated, even a basic approval link does this. The record exists automatically because approving created it. You're not the one who has to remember to log it.
after a couple of these we put version numbers on the proofs. turned out most of our 'i never approved that' people had approved an earlier version and didnt realize we revised it after. now the approval and the invoice both show the same version number. doesnt stop someone whos actually lying but honestly those were rarer than i thought