Shop Policies: 4 Mistakes That Create Complaints

A policy fails before anyone reads it if two reasonable people can give it different meanings. The fix is to write each promise against a clock, condition, and check, then test it before material, machine time, or a board is committed.

Mistake 1: Combining processing time and shipping time

Processing time is the time needed to make, inspect, and prepare the work. Shipping time starts after that work is ready and depends on the carrier, service level, destination, and handoff. They are separate promises, yet buyers routinely read them as one number.

The complaint arrives as: “The ten-day estimate has passed, so where is it?” The writer may have meant ten working days in production plus transport. The reader may have understood delivery within ten days. Both interpretations came from the same sentence.

Write the two clocks separately:

• Processing time: counted from the point when the required information, payment, or approval is complete to the point when the work is ready to leave.
• Shipping time: counted from carrier acceptance or dispatch to delivery, subject to the carrier and service selected.
• Approval pauses: time waiting for a proof, missing dimension, colour choice, or answer does not silently disappear inside the estimate.
• Change requests: revisions after approval either restart part of the processing clock or receive a separate estimate.

The check is a timeline test. Read the policy without context and ask, “Could someone calculate the delivery date from this?” If yes, the statement is probably hiding a promise you cannot control. Replace it with two labelled durations and state the event that starts each one.

Do not publish a single “turnaround” number unless it names whether it means processing, dispatch, or delivery. A shorter, less impressive processing time is better than a combined estimate that turns a carrier delay into a production complaint.

Mistake 2: Treating personalised goods like stock goods

A return policy handmade for stock goods often gets copied onto personalised work. That creates a contradiction: the text promises a general return, while the item may have been made to a supplied name, measurement, file, or layout and cannot be put back into ordinary stock.

The landed complaint usually sounds like this: “I changed my mind, so I want a refund.” A different complaint appears if the maker tries to refuse every return: “The item is wrong, damaged, or not as described.” Those are not the same case.

Consumer protection rules on returns vary by jurisdiction and generally treat personalised goods differently from stock goods. A made-to-order or personalised item may fall under an exception to a change-of-mind return right in one jurisdiction, while defective, misdescribed, or improperly supplied work can still carry legal remedies. The policy cannot erase those rights, and a generic “no returns” sentence is not a substitute for checking the rules that apply to the transaction.

Separate the conditions in writing:

• Change of mind: whether a personalised item can be cancelled or returned after work starts.
• Maker error: what happens if the approved spelling, dimensions, file, or specification was not followed.
• Buyer-supplied error: what happens if the supplied text, measurement, file, or approval contained the mistake.
• Defect or damage: what evidence is needed and what remedy is available.
• Stock item: whether an unused, non-personalised item has a different return path.

The check is an approval-record check. Before material is cut or a board is committed, capture the exact text, dimensions, file version, colour or finish selection, and approval date in one place. If the policy refers to “custom items,” but the workflow cannot show what was approved, the policy is missing its proof.

The cheap way is good enough here: a dated approval email or a clearly named PDF can prevent a dispute. A specialised customer portal is an upgrade that fixes a record-keeping problem you may not have. Build the evidence trail before buying software.

Mistake 3: Writing damage handling without a communication window

“Contact us if damaged” sounds helpful but has no operational edge. It does not say how soon to report the problem, what evidence to keep, or whether the item should be used, repaired, or discarded while the claim is being assessed.

Once the complaint lands, the useful evidence may be gone. Packaging has been thrown away, the damage has spread through handling, or the carrier’s reporting period has closed. The maker then has to decide whether the damage happened in production, in transit, or after delivery, with no consistent record.

A workable damage section names the event, the window, and the evidence. The window is a business and legal decision, not a universal number. Check the carrier’s conditions and the consumer rules that apply before choosing it. Then state the same window in plain language, including the time zone or delivery event if those details matter.

Ask for:

• photographs of the outer package before opening, if it is visibly damaged;
• photographs of the inner packaging and the item from several angles;
• the delivery date and any carrier damage notation;
• a short description of whether the item is usable, unsafe, incomplete, or cosmetically marked;
• the packaging to be retained until the review is complete, if the carrier may inspect it.

The check is a dry-run claim. Hand the policy to someone who did not write it and ask them to process a simulated damaged parcel. Can they identify the reporting deadline, the first contact method, the evidence required, and what not to do next? If they have to ask four follow-up questions, the policy is not finished.

Do not promise a replacement before checking the cause and the available remedy. Promise a defined review step instead. That keeps a transport claim, a manufacturing defect, and a misuse case from being treated as one category.

Mistake 4: Promising communication without defining the event

“Questions will be answered promptly” is not a communication standard. Promptly can mean an hour to one reader and a week to another. It also fails to say what happens when a message arrives outside working time, lacks a required file, or concerns an active production decision.

The complaint looks like this: “Nobody told me there was a problem.” The maker may have sent a message to an old address, posted a request in a channel the buyer did not monitor, or waited for a reply without saying that the processing clock was paused. The work then proceeds on an assumption that was never confirmed.

Define communication windows by event, not by mood:

• acknowledgement of a new message;
• request for missing information;
• proof or approval sent for review;
• notice that a deadline is at risk;
• confirmation that a change is accepted or rejected;
• final dispatch or completion notice.

State which messages pause processing and which do not. A question about a minor preference may not stop the work; an unresolved dimension or spelling error should stop it. Do not call an unanswered message an approval. Silence is not a technically safe input.

The check is a state-machine check. List the states as received, waiting for information, in production, waiting for approval, complete, and dispatched. For every transition, identify the message that records it and the condition that permits it. If the same status can mean two different things, rewrite the policy.

This is where a shared order record earns its keep. It can be a spreadsheet with a file name, timestamp, current status, and next action. The expensive system is not automatically safer. A simple record that someone updates at the decision point beats an elaborate system that nobody checks.

A pre-commit policy check for small shops

Run the following before publishing a new policy or accepting work under a revised one:

The order matters. First define what event starts the clock. Then define what evidence proves the required input. Then define what happens if the input is late, wrong, or absent. A policy written in that order mirrors the work instead of pretending every job follows a neat calendar.

Keep a copy of the version that applied when the commitment was made. Changing the wording after a dispute creates a second problem: nobody can tell which promise governed the job. Date each revision, record the effective date, and make the accepted version retrievable.

Frequently asked questions

Should processing time include shipping time?

No. State processing time through completion or dispatch, then state shipping time from carrier acceptance to delivery. If a combined estimate is shown for planning, label it as an estimate and explain which part is outside the maker’s control.

Can personalised goods be excluded from returns?

Sometimes, depending on the jurisdiction and the reason for the return. Personalisation may change the treatment of a change-of-mind return, but it does not automatically remove rights related to defects, incorrect work, or goods that do not match the agreement. Check the rules that apply before writing the exclusion.

What should a damage-report policy require?

Name the reporting window, the contact method, the photographs or other evidence needed, and whether the packaging must be retained. Set the window with the applicable law and carrier conditions, then test it with a simulated claim before publishing it.

The Boss Factory builds custom, made-to-order work in Custom Electronics & Smart Systems, Design & Product Development, and Custom Projects, with /quote as its only path.