A Shareable Configuration Summary That Survives an Unavailable Option

A customer builds a product on your website, saves the summary, and sends the link to a partner. Two days later one chosen option can no longer be offered. If the page quietly swaps in something else, the partner sees a configuration nobody actually chose. This article proposes a workflow that keeps the original selection readable and shows any alternative as a clearly separate suggestion. It is an editorial example, not a description of any observed client result.

The artifact: a two part summary

The shareable summary has two blocks.

Original selection: every option exactly as the customer picked it, with the date it was saved.
Current status: one line per option saying Available, Unavailable, or Not checked yet.

A third block, Proposed alternatives, appears only when at least one option is unavailable. It never overwrites the first block.

Inputs you need

Use a hypothetical public sample so the team can test without real customers. Imagine a made up desk lamp with these choices: Finish (Sand, Slate), Shade size (Small, Large), Cable (Cloth, Plain). The sample customer saves Slate, Large, Cloth.

For each option value, decide who owns the availability answer: a product list, a stock sheet, or a person. Write that owner next to the option in your specification. Without an owner, the status line cannot be trusted.

Decision branches

When someone opens the summary link, check each saved option value.

All available: show the summary unchanged with status Available. No alternative block.
One or more unavailable and a suitable alternative exists: keep the original line, mark it Unavailable, and list the alternative under Proposed alternatives with a short reason, such as a different finish with the same shade size.
Unavailable and no alternative: keep the original line, mark it Unavailable, and offer a contact route instead of inventing a substitute.
Availability cannot be checked: show Not checked yet and do not state either way.

Whether to propose alternatives at all is a business choice. Some shops prefer to offer none and only flag the problem. Both are acceptable, as long as the original selection stays visible.

Stop conditions

Stop and show a plain message, without a rebuilt configuration, if the saved summary references an option group that no longer exists, or if the saved date is missing. In those cases display what was saved as text and invite the customer to start again. Do not guess a mapping.

Also stop any automatic ordering from a summary that contains an unavailable option. The customer must actively accept the alternative, which creates a new selection with its own date.

Worked example

The partner opens the sample lamp summary. Original selection: Slate, Large, Cloth, saved on a given date. Status: Finish Unavailable, Shade size Available, Cable Available. Proposed alternatives: Sand finish, described as the other finish offered for the Large shade. Two buttons appear: Choose this alternative and Contact us about Slate.

If the partner chooses the alternative, the new summary shows two dated entries: the original and the accepted change, with the changed option marked. If the partner does nothing, the original remains exactly as saved.

Wording rules

Use the words Selected by you for the original and Suggested for alternatives. Avoid Updated for you, which hides who made the change. Do not remove the unavailable option from the text, because a partner comparing two links needs to see that both started from the same choice.

Acceptance test

Run this small test with the sample lamp and a person who did not build the page.

Save the summary with Slate, Large, Cloth and copy the link.
Mark Slate as unavailable in whatever source you use for the test.
Open the link in a fresh session. Check that the original block still says Slate and that the status says Unavailable.
Check that Sand appears only under Proposed alternatives and that no order or price changed.
Accept the alternative and confirm the new summary shows both entries with dates.
Mark every option unavailable at once and confirm the page shows the original text and a contact route, with no invented substitute.
Remove the saved date from a test link and confirm the stop message appears.

The workflow passes if the tester can say, without help, what was originally chosen, what is unavailable, and what is merely suggested.

Conclusion

A shareable summary is a record of a decision, so treat it that way. Keep the original selection fixed, report availability separately, and present alternatives as suggestions that need an active yes. The result is a link that stays honest when your range changes.