Drafts

Overview

The current Custom Plan Builder preserves selected plan, groups, limits, discount code, and current step in browser sessionStorage. This is a session-only convenience, not a server-backed Drafts library. The commercial model does have a persisted Draft status, but the public custom-plan submission normally creates that server draft and immediately submits it in one request.

What Is a Draft?

A pre-submission browser draft is the builder state retained for the current browser session, including the base plan, selected limit groups, requested limit/capability values, and discount code. It is not an order, does not enter the platform queue, and does not notify the platform team. Company/contact fields are not included in the persisted session payload and should be checked again before submission.

The company logo is a special case. A browser will not let any page repopulate a file input, so a selected logo is never restored: not by session storage, and not when a failed submission redisplays the form with your other values. If you sign in mid-flow or a submission is rejected, choose the logo again before resubmitting. Your order is still valid without one.

Saving a Draft

While using the current Custom Plan Builder:

1. Configure the plan to your current best estimate.
2. Move through the builder normally; supported selection fields are saved automatically in the browser session.
3. Use Save & Exit only to leave for pricing. The current source does not create a named server draft from that action.
4. Return in the same browser session and review every restored value before continuing.

The current source exposes no account-level Drafts list. A compatible or future deployment may add one, but it must not be assumed from the “Draft” summary badge.

You do not need to be signed in for session storage, but you must sign in to submit. The login/register return path restores supported selections from the same browser session and returns to step 6.

Accessing Your Drafts

If your deployment exposes a compatibility Drafts page, it may list saved entries with:

• Draft name (or auto-generated name if none was given)
• Base plan name
• Date last modified

Editing a Draft

1. In the current implementation, return to the Custom Plan Builder in the same browser session. In a compatibility deployment, open the entry from Drafts.
2. Confirm which settings were restored; current session storage does not preserve company/contact fields.
3. Make your adjustments.
4. Continue through the steps. Named update/copy behavior applies only if your deployment actually exposes the compatibility Drafts feature.

Submitting a Draft

When you are ready to turn a draft into an official plan request:

1. Return to the session-restored builder, or open the entry if a compatibility Drafts page exists.
2. Review the configuration one final time.
3. Click Submit Request.

On the current public builder, the server authoritatively reprices the request, creates a persisted commercial Draft, and immediately attempts the Draft-to-Submitted transition. If either operation fails, the page displays an error and you should review pricing, country/currency availability, limits, discount eligibility, and sign-in state before retrying.

Deleting a Draft

The current website has no server draft delete control. To remove the local session selection, end/clear the browser session according to your browser controls. If a compatibility Drafts page is present, its documented deletion flow is:

1. Go to Drafts.
2. Click the options menu (three dots) next to the draft.
3. Select Delete Draft.
4. Confirm the deletion.

Deleted compatibility drafts and cleared browser-session state may not be recoverable; verify the configuration before removal.

Frequently Asked Questions

Can the platform team see my drafts? The browser-session selection is local to that browser session and is not an order visible to the platform team. Once submitted, the resulting commercial order is visible to authorized platform staff.

Is there a limit on how many drafts I can have? The current source defines no server-backed draft collection and therefore no ten-draft maximum. Browser storage limits are browser-controlled. If a compatibility deployment offers named drafts, follow the limit displayed there rather than assuming ten.

Do drafts expire? The current source defines no 90-day draft expiry or pre-expiry notification. Browser session state can disappear when the session ends or storage is cleared. A persisted commercial Draft follows commercial state rules, not this former browser-draft expiry claim.

What happens to my draft if I submit it? The submitted values create the commercial order and its invoice snapshot. The browser-session selection may remain until the browser session ends, but it is not a reliable account archive and does not track later order changes.