Create a merge template and check plan credit limits

Quick answer

Convert a disposable workbook into a merge template, map two synthetic records, preview both, and check current credits before a save-only merge.

Before you start

Zoho Sheet web editor in an English desktop browser; rolling service, official documentation reviewed 20 October 2026. Not desktop-app or mobile instructions. Use an editable practice file containing only synthetic data. Keep the original unchanged and record the file name and storage location so that you reopen the same copy. These are documentation-based instructions and independently checked examples, not a claim of native application testing.

Prepare two records and a disposable template

Create a source worksheet with headers RecordID, Name and Units, containing T01, Blue sample, 12 and T02, Green sample, 8. Use no email addresses or personal data. Make a separate blank workbook for the template with visible labels Record, Description and Units in A1:A3 and empty destination cells B1:B3.

Conversion into a Zoho Sheet Merge Template is documented as irreversible. Do not convert your only copy of a normal workbook. Name the disposable template clearly and preserve the source separately. This exercise saves new spreadsheets only; it does not email attachments or schedule a future run.

Convert and map the fields

1. In the disposable template, choose Tools → Merge Template and review the conversion warning before Proceed.
2. In the merge side pane, choose Click to add source and select Zoho Sheet as the source type. Choose your synthetic source workbook and its intended dataset.
3. Select the three fields, inspect the mapped headers and choose Map Fields. RecordID must not accidentally map to Name.
4. Place RecordID in B1, Name in B2 and Units in B3 using the field list’s drag-and-drop or add control.
5. Use Preview and select each record in turn. T01 must show Blue sample and 12; T02 must show Green sample and 8.

The source-to-field mapping, not the order in which values happen to appear, defines the output. A plausible-looking template with swapped IDs is still incorrect. Keep the visible labels in column A to make that failure easy to notice.

Check the plan before generating files

The workflow article and the dedicated credit add-on article disagree about email credit consumption and some daily limits. Do not use either to promise an email quota. Both describe saving spreadsheets as one credit per record, but the usable balance, organization-wide consumption and daily allowance still need checking in the actual account.

Inspect the current plan and available credits with the organization administrator if necessary. Two selected records should require two save credits under the documented per-record rule. Do not buy credits or change a subscription merely to complete this tutorial. Stop at the verified preview if the account has insufficient allowance or merge access is disabled.

Run one save-only merge

Under Merge Action, choose Save as new spreadsheet(s). Inspect the selected records and the naming/folder choices. Use a private practice folder and names that include the record ID, so the outputs cannot be confused. When ready, run the merge once.

Open View Logs in the merge pane and inspect the result before retrying. A slow response is not proof that nothing was created; repeating the action could generate duplicate files and consume more credits. Check the destination folder and log status first.

Reconcile the outputs

Expect two new spreadsheets, one for T01 and one for T02. Open both and compare all three fields against the source. The units should remain 12 and 8, with a combined control total of 20 across the two outputs. Check that template placeholders have been resolved rather than left as literal field names.

A saved merge result is an output snapshot. If source Units changes later, do not assume the already generated file updates. Preview the new source values before any additional authorized run and use distinguishable output names.

Keep a brief record of source, selected records, destination folder and merge log outcome. Collaborators need access to the connected source to run a merge, and their actions use their own account context. A template edit permission alone does not establish complete source access or available credits.

Related tutorial

Continue with tables and named ranges.

Official sources

Documentation reviewed 20 October 2026.

• Merge template workflow
• Credit add-on and account usage