STOCK in Zoho Sheet: Syntax and Data Limitations

STOCK requests a field associated with a market symbol. Omitting the second argument requests the price field:

=STOCK("AAPL")
=STOCK("AAPL";"price")

These express the same documented field choice. They do not establish a fixed price or prove that two requests made at different times will return equal values. No market-data query was performed for this guide, and none of its illustrative numbers is a current quote.

=STOCK(symbol; [function])

The second argument is a field selector, despite being named function. The official STOCK reference documents price as the default. It instructs users to prefix non-US symbols with their exchange, for example NSE:RELIANCE.

The article identifies Twelve Data as the provider, says the information may be delayed by up to 60 minutes, and labels its sample prices as 2024 data. None of those statements guarantees a refresh interval or current availability. A historical help-table number must not be presented as today’s market price.

The documented selectors include:

The help uses an unexplained “PS” abbreviation for tradetime. This guide does not expand it into an assumed timezone or certify the result’s date/time representation. Likewise, the word “percentage” does not establish whether a returned change is stored as a fraction or percentage-point number. Verify those representations before formatting or using them in arithmetic.

Enter A2=AAPL and B2=price, then use:

=STOCK(A2;B2)

A corresponding field request for volume is =STOCK("AAPL";"volume"). Both formulas use documented example identifiers, but neither was executed here.

For a hypothetical demonstration, assume that the requested price field supplies 150 units of its quote currency and that a fictional quantity is four shares. Then:

=4*STOCK("AAPL";"price")

would give 600 quote-currency units only under that fictional price assumption. The arithmetic is 4×150, not an observed valuation. Establish the quote currency and relevant time in an actual worksheet before interpreting the monetary total; the symbol alone in this example is not proof of either.

The following assumptions illustrate how distinct fields should be read. They are invented and are not a snapshot of AAPL or any other security.

These assumptions cannot be used to validate service availability. In particular, volume is a share count rather than money, and previous close is not the same event as today’s open. A report should not substitute one field for another just because both are numeric.

Keep the requested symbol, field and returned value in separate columns. Add an explicitly labeled report-preparation timestamp, while remembering that it is not necessarily the market-data timestamp. When comparing values, check that their currencies, field meanings and time contexts match before calculating differences.

For the fictional values above, 152−147 = 5 is a high-low range in quote-currency units. It is not a percentage return. Using an assumed price of 150 and previous close of 148, an independently computed relative change would be (150−148)/148 ≈ 0.0135135, or about 1.35135%. That calculation does not certify the storage format or timing of STOCK’s own change field.

Do not add prices across different currencies as though they share a unit. SUM can add numbers, but it cannot validate the financial meaning of those numbers. This guide teaches field interpretation and arithmetic, not trading decisions.

Zoho documents “Invalid symbol” and “Invalid Function” for an invalid symbol or field selector. Those are documentation descriptions here, not observed error responses. Other failures, missing values, service interruptions and quote coverage have not been tested. An error should not silently become a zero price in a report.

The official rolling page was checked on October 18, 2026. No service-data request, account, authored workbook or calculation-engine execution was used. Conditional examples do not establish live prices, guaranteed refresh, mobile/import behavior or availability. The page does not identify the first introduction version or establish retirement/deprecation history.