Constraints and approval TrustDelivery

Bring constraints into the customer journey

Communicate meaningful limitations early enough to prevent a false expectation, without burying the customer in caveats.

Evidence
Context-dependent. The reasoning is sound and the outcome genuinely depends on your business, your customers and your production. Worth testing rather than adopting wholesale.
Difficulty
Moderate. Difficulty is an initial editorial assessment of how much work an idea usually takes, not a guaranteed estimate for your systems. A change that is small in one storefront can be significant in another because of where the data lives.

The commercial problem

Constraints tend to live at the two extremes: buried in terms nobody reads, or revealed at the end when the customer has already invested effort. Both produce the same outcome, which is a person who feels misled by an accurate website.

Why it matters

The cost of a constraint rises with how late it appears. A minimum order quantity stated on the product page is information. The same quantity stated at checkout is a wasted journey and a lost trust.

Where it applies

  • Minimum order quantities and minimum values
  • Geographic restrictions on delivery or installation
  • Lead times that exceed customer expectation
  • Combinations that are unavailable for technical reasons

Suggested implementation

  1. Rank constraints by how much work a customer does before hitting them. Fix the latest-and-largest first.
  2. State the constraint where the relevant choice is made, not on a separate information page.
  3. Give the reason where there is one. A constraint with a reason is accepted far more readily than a bare rule.
  4. Say what is possible alongside what is not, so the statement is navigational rather than merely restrictive.

Risks and constraints

  • Front-loading every constraint produces a page that reads as a list of refusals and deters qualified customers.
  • Constraints stated as absolute when they are negotiable will lose business the sales team would have taken.
  • Constraint data drifts. Displaying it prominently makes it more damaging when it is out of date.

What to measure

  • How far customers progress before encountering a blocking constraint
  • Abandonment concentrated at the moment a constraint appears
  • Enquiries asking whether a stated limitation is firm, which indicates it is stated too absolutely

How this relates to Specify

A Constraint Record is the structure this idea depends on: what may be offered, under which conditions, and with whose approval.

When an engagement is worth it

Worth an engagement when constraints are enforced inconsistently between the website and the sales team, which usually means they have never been written down in one place.

Related ideas

Start with evidence

Or start with one of your own enquiries

The complimentary Enquiry Audit takes one real customer enquiry and shows what a structured reading of it produces. It runs on this site and costs nothing.