A small shop already using Google Workspace Business Starter can collect barcode scans and staff-entered quantities in Sheets without another AppSheet subscription—if the creator and every user qualify for included Core access. Google’s entitlement rules and mobile-scanning documentation support that option as of November 19, 2026. Keep a workable manual count unless scanning or offline capture justifies maintaining an app; people must still count and approve stock changes.
This is an existing capability, not a new launch. The example below assumes three nontechnical staff, one stockroom, 200 labelled product variants, existing phones and permitted Sheets/Drive access. All three have domain-verified Business Starter accounts. The US$0 additional-software budget excludes existing subscriptions, equipment, connectivity and staff time; the shop size is an illustration, not a product capacity limit.
The goal is a reviewed physical-count record, not a replacement till system or automatic purchasing.
Should you keep Sheets, use Forms or build an AppSheet app?
Decide by the amount of identifier typing, connectivity in the stockroom, account eligibility, access needs and who will maintain the process. All three routes need counting assignments and discrepancy review. An included licence alone is not a reason to build an app.
Option and best fit | Extra software cost | Prerequisites | Main limitation | Ongoing work |
|---|---|---|---|---|
Paper/Sheets: the existing routine remains manageable | US$0 with existing tools assumed here | Agreed item list, units and counting assignments | Manual entry; paper adds a transcription handoff | Check entries and resolve differences |
Forms → Sheets: structured manual entry is enough | US$0 with existing permitted Forms/Sheets access | Configured questions, response Sheet and access | Do not assume offline camera scanning | Maintain fields, permissions and review |
AppSheet → Sheets: scanning or offline entry matters | US$0 only under the included-Core conditions below | Eligible accounts, enabled service, mobile app and online setup | A scan identifies an item; it does not count units | Maintain the app, devices, sync and reconciliation |
For the simpler form route, collect the count session, item identifier, quantity, unit and counter, then store responses in a linked Google Sheet. Google says later permission changes must be made separately on the form and its response Sheet. Treat this as a connected manual-entry workflow, not a substitute for AppSheet’s offline scanning.
Are all three staff accounts covered?
Google currently lists Business Starter as including Core for each domain-verified user. Have the administrator confirm the entitlement for each person and that AppSheet is enabled. The creator also needs approved source access and Google Drive enabled for the domain.
Check the creator’s licence, not just the staff’s accounts. Under Google’s licensing rules, a Core-created app requires Core or User Pass for its users; an Enterprise Plus-created app requires Enterprise Plus or User Pass. A personal account, outside contractor or higher-tier creator can invalidate this example’s budget.
Illustrative licence calculation: 3 eligible users × US$0 extra Core charge = US$0 additional Core subscription charge. This assumes a Core creator, the default scanner and no paid add-ons. It is not a universally free production plan or a quote for buying Workspace.
If those conditions fail, retain the manual workflow while checking current options. Do not buy an upgrade merely to follow this example. Name an app maintainer and a person authorized to approve stock adjustments before setup.
What should one count row represent?
Make a separate count-log Sheet, not an app that overwrites the live stock balance. Each row should mean one person’s observation of a specified product in a specified area during a named stocktake. These are proposed design conventions, not a supplied Google inventory template.
Agree whether staff count a whole product’s stockroom quantity or individual shelves. Define units—single items and cartons are not interchangeable—and map each barcode to the shop’s product identifier, often called a SKU. Keep an expected-item list and a dated stock snapshot for later comparison. Record zero explicitly; a missing row must not silently mean zero.
CountID: a Text column identifying this observation. Make it the key, set
UNIQUEID()as its Initial Value and prevent staff editing it.CountSession: a shared label for this stocktake, kept distinct from earlier sessions.
Barcode: text in both the Sheet and app, preserving leading zeros. Confirm the code’s product and packaging unit before accepting it.
Quantity and Unit: a required whole-unit quantity for this example, including zero but excluding negatives. Use an explicit decimal/unit convention if counting by weight.
Counter: an Email column initialized with
USEREMAIL()under required sign-in. Keep it out of ordinary staff editing.CapturedAt: a DateTime column initialized with
NOW(). It records capture context, not arrival at the server.Area, RecountOf and Note: add these where needed to identify a shelf, link a correction to its original CountID or explain an exception.
A product code cannot be the count-log key: the same product can be counted again. Google requires a stable, unique row key and places generated keys in Initial Value, not the recalculating App Formula. Avoid worksheet row numbers and multi-user sequential numbering. A unique CountID distinguishes records; it cannot tell whether two people counted the same shelf.
USEREMAIL() identifies the signed-in user, not proof of who physically counted. NOW() uses the device’s date and time, so check phone clocks and agree a timezone convention. Neither field makes this a tamper-proof audit system.
How do you create the app and enable scanning?
Use the existing-data creation route: open AppSheet’s My Apps page, choose Create and start with your own data, selecting the count-log Sheet. Inspect the inferred column types and key before inviting staff.
In the count table, confirm the column settings above. Allow new observations but disable ordinary edits and deletions using table update controls. The documented
ADDS_ONLYoption supports this arrangement. Record a correction as a new row referencing the original.In Data, select the count table and enable Scan for Barcode, or open its column settings and enable Scannable. Google’s scanner setup instructions show both controls.
Open the mobile app on the actual phone. Scan the label, confirm the product and unit, physically count the items, enter quantity and save. Send unknown codes for review rather than guessing their identity.
Camera scanning requires Core or Enterprise and does not work in the browser or editor emulator. Use the default scanner: Scandit needs a separate account and licence. Check your labels and phones before relying on scanning; the emulator is not evidence that a phone will read them.
Two Sheets integration limitations matter here: AppSheet-synced edits do not run Sheets onEdit scripts, and ordinary source-sheet filters can interfere with updates. Use filter views instead. Do not assume an existing spreadsheet script will reconcile a count or adjust stock.
Who can see or change the records?
Require Google sign-in and allow only the three named accounts. Choosing Google as the sign-in provider alone does not restrict access to those people. A hidden field or presentation slice is not a security boundary; review the connected data and source permissions separately.
Choose the data-access mode deliberately. In the default creator mode, the app can expose connected Sheet data to invited users without direct Sheet access. In user mode, each person needs the relevant spreadsheet and folder permissions. Neither setting removes the need to configure what the app permits.
Keep customer information outside this count log. Limit direct Sheet editing to people who need it: an adds-only app does not stop a spreadsheet editor changing old rows. Keep reviewer decisions outside the staff capture form, and retain observations and configuration notes through the business’s approved backup process.
Google’s Workspace service terms, sections 11.4 and 11.8, put responsibility for appropriate data-source rights and support of customer-built apps on the customer. Section 1.2 makes AppSheet data-region coverage conditional on Enterprise Plus; do not assume this Core workflow has that coverage.
How do you collect counts without a connection?
Launch the app online on every phone first. AppSheet stores working data on the device, so offline capture is not local-only processing. In Settings → Offline mode, enable offline startup if needed; review sync controls under Settings → Performance. These requirements and settings are documented in Google’s offline and sync guide.
For deliberate manual synchronization, Google documents Delayed sync on with Automatic updates off. Staff must then sync explicitly. Do not use Quick sync with a Sheets source that computes values using formulas. Avoid leaving phones unsynced for days or weeks.
At the end of the count, reconnect and sync every phone, resolve any errors and check that its rows reached the Sheet. Connectivity alone is not delivery confirmation. Keep the session open while any phone has unsent or unexplained records.
When can you change the stock balance?
Only after a reviewer accepts the physical count. Google documents last-writer conflict handling for changes to the same row, including direct spreadsheet edits. Keeping observations separate is therefore a useful design choice: a late phone upload should not become the shop’s authoritative stock balance.
Compare the log with the expected products and assigned areas. Investigate missing items, unknown barcodes and mismatched units.
Resolve repeated observations. Decide which are separate areas, which are recounts and which are accidental duplicate entries.
Compare accepted quantities with the dated stock snapshot on a common cutoff. Account for sales, deliveries and transfers between the snapshot and the physical count.
Record the accepted quantity, the discrepancy decision, the supporting CountIDs and the reviewer. Only the authorized person makes the justified adjustment in the authoritative stock system.
For example, suppose one row reports seven units and a recount reports eight on the same shelf. Fifteen is not the accepted stock quantity: the reviewer must resolve the disagreement. Seven and eight could be added if they describe different, non-overlapping shelves with the same unit. That is illustrative arithmetic, not a test result.
Keep the original observations and decisions. Do not connect an unreviewed scan to automatic purchasing. If the shop already uses Shopify, low-stock emails with Shopify Flow address alerts from recorded inventory, not collecting physical counts. A weekly sales dashboard in Google Sheets answers a separate reporting question. This setup does not integrate with either workflow automatically.
Would Gemini make this easier?
AI is optional. Google says Gemini for App Creation is available with eligible paid licences, including Workspace Core, subject to administrator controls. It can suggest tables, columns, views and actions. Enterprise Plus AI automation is a separate feature that consumes credits; included Core does not supply it.
There is an important storage distinction: Google’s Gemini creation instructions say generated apps use an AppSheet database and contain sample data that may be inaccurate. That route does not automatically connect the count-log Sheet. For this workflow, starting with existing Sheets data keeps the source choice explicit. Review any generated design and remove sample rows; never treat generated quantities as counted stock.
What should a small pilot establish?
Before a live stocktake, run these proposed checks on isolated trial data using the actual phones. They are acceptance checks for the shop to perform, not results from a completed test:
Count a few items with known quantities. Check the exact barcode, quantity and unit in Sheets, including a label with leading zeros.
Try an unknown code, a zero count and a negative quantity. Confirm that each receives the intended handling.
Have two staff record the same item. Check that observations remain separate, then practice resolving a recount rather than summing it.
Capture while disconnected, restart offline if required, then reconnect and sync each phone. Confirm all expected rows arrive.
Check named-user access and direct Sheet rights separately. Confirm an approved unlisted test account cannot open the app.
Reconcile the trial against its expected-item list and known quantities. Keep stock adjustments outside the capture app.
Complete AppSheet’s deployment check before operational use; development access alone does not establish production entitlement. Keep the previous count routine available until the pilot reconciles, access is correct and every device can sync. Recheck licences and permissions when staff or app ownership changes.
Choose AppSheet when it removes enough identifier typing or supports needed disconnected capture to justify that upkeep. If nobody can maintain the app and review its count log, a controlled paper/Sheets count or simple Forms log is the more workable choice.
