Save changes explicitly
Open Dashboard, choose Selling, find the form under My Forms, and choose Edit form. Choose Save changes in the builder header, or press Ctrl+S on Windows or Cmd+S on Mac.
Editing and Save become available after the form finishes opening. If Builder cannot open, choose Reload Builder. If an older tab still holds work you need, download a backup from that tab before reloading it.
Edits stay in the open page until you save. There is no autosave, browser recovery copy, unfinished server draft, or automatic merge with another tab or device. Closing or reloading without saving loses those edits. Opening the form again reads its saved server state.
A successful Save commits form settings, blocks and layout, products and variants, shipping, Coupons and Sales, and explicitly edited individual stock and alerts together. If validation, access or a concurrent change prevents that Save, none of that submission is committed. Shared stock has its own explicit controls in Inventory. Other named actions, such as connecting an integration or duplicating a form, remain separate commands.
Saved confirms the submitted changes reached the server. If you typed more while Save was running, the submitted changes can be saved while your newer edits remain Unsaved changes. Save again when those newer edits are ready.
Handle an interrupted Save
If the result is unconfirmed, keep the page open and choose Check Save or Retry Save. Checking reads the original result. Retrying sends the same submitted operation, so a completed Save is not applied twice. Returning online, focusing the page or waiting does not submit it automatically.
You can keep editing while confirmation is pending, but another Save waits for the original operation to be resolved. A later error does not prove an earlier request never committed. Closing the page discards its in-memory confirmation details; the request already sent may still finish. Reopen the form to inspect saved server state.
Saved; confirmation details unavailable — Check Save means the server confirmed the commit but the page could not safely load or install its details. Keep the page open and choose Check Save before submitting more work. Retry Save is not offered for a save already confirmed as committed.
Review a conflict
Another tab, collaborator, connected app or explicit server command can change the saved form while you work. If Save reports that the form changed, keep your edits in the open page and review the current saved form before proceeding. EZFormz does not silently merge or overwrite another version. You can download a content backup before deliberately reloading.
An order-driven stock change is preserved when your Save does not edit that stock. If you explicitly replace a count or change its source, a concurrent change can require review and prevent the complete form Save. Relative stock adjustments in Inventory apply to the current matching stock source once.
If Save highlights invalid input, review that area and try again. A custom URL and Form Status remain unsaved until Save succeeds. Share links use the last saved URL. Large forms still have a total payload limit even though there is no fixed block-count cap; a size error leaves your current edits in the page.
Use Undo, backups and saved versions
Undo changes only this page. Editor-wide Undo waits while a submitted Save is unconfirmed; ordinary typing remains available. After confirmation, Undo history starts from the retained current page. Choose Save changes when the result is correct. Undo does not undo a server commit automatically. Large forms keep fewer recent Undo steps to limit memory use.
Settings → Tools → Download Backup downloads the existing content-backup format from the current page. It includes supported content and settings, not every unsaved security, URL, status or integration setting. Store the file securely and copy any other needed settings before leaving. Downloading is an explicit file export; it does not save the form.
To load an older configuration, open Publish → Share Link → Published versions and choose Restore version, or use Settings → Tools → Load backup into editor. Loading prepares changes in the open page. Review the result and choose Save changes to commit it. Abandoning the page without Save leaves the saved form unchanged. See Reuse, back up, and restore forms for the stock and promotion rules.
Historical drafts or browser entries from the earlier workflow are not adopted by the new editor. An old open tab must export any content you need before reloading into the current editor. Saved history remains subject to its existing retention policy.
Find older unsaved copies
Open Settings → Tools → Legacy save exports. On the separate page, choose Find legacy copies. Older browser copies are checked only after you choose Find.
The list can include old server drafts and, for the current form owner, browser copies. Browser entries are unverified copies until you choose Download and the tool checks the selected copy against your current access. Use Show more browser copies for another page; older server drafts have their own paging button. If browser entries change while you browse, choose Find again to refresh the list.
Download one copy at a time. Find, paging and other Download controls are unavailable until the export finishes. If a record is too large, unreadable or no longer accessible, the tool explains the exclusion and leaves it untouched. Not every historical record can be recovered.
Downloads are historical JSON for review, distinct from a content backup. This page has no Restore action and never saves, adopts or resubmits a copy. Export before logout or clearing browser data, which can remove old copies. It cannot recover unsaved work created by the new memory-only editor. For older Inventory entries, form owners can use Legacy stock exports.
Keep sensitive data out of form content
Avoid passwords, API keys, payment credentials, private access links or unnecessary personal data in field defaults, hidden fields, instructions, images, previews and exported backups. Permitted collaborators may see form content. Use the dedicated Security controls for form access; replacement password input is not a recovery mechanism.