n8n Inventory Management Automation With Google Sheets and Hard Caps

The inventory templates ranking for this keyword all assume you're running Airtable or an ERP. That's fine for a warehouse. It's overkill for an indie seller with forty SKUs in a Google Sheet who just wants to know before something sells out and wants a hard cap on a limited run.

n8n inventory management automation doesn't need a database product to be useful. A Sheet, a Schedule trigger, a threshold check, and an alert cover the job. This guide builds that Sheets-first path, adds the reorder dedupe the bigger templates skip, and includes the hard-cap pattern that limited-run and lifetime-deal sellers actually need.

It also says the quiet part: a scheduled inventory check has a failure mode the tutorials don't mention. More on that below.

What you can automate with a Sheets-first inventory flow

Small-catalog inventory is a handful of jobs that don't justify an ERP:

• Read current stock counts from a Google Sheet on a schedule.
• Flag any SKU below its reorder threshold.
• Send one low-stock alert per item, not one per run.
• Enforce a hard cap on limited runs and lifetime deals.
• Write a reorder note or draft a supplier email.
• Log stock movements for a simple trend view.

None of these need Airtable. They need a Sheet with the right columns and a workflow that respects state between runs.

Why the Airtable-first templates miss indie sellers

The opinion here is straightforward: most inventory automations are built for a scale their users don't have. An indie seller doesn't need ERP forecasting. They need to not get caught selling something they ran out of, and they need alerts that don't cry wolf every fifteen minutes.

The ranking templates also skip reorder dedupe entirely. They check stock, find it low, and alert. Next run, same item, same alert. By the third run you've got an inbox of identical low-stock emails and you've started ignoring all of them. That's the automation failing at the one job it had.

A Sheet with a reorder_flagged column fixes it. Cheaper than Airtable, and it actually solves the noise problem.

The inventory pipeline

Schedule trigger → Read stock Sheet → For each SKU:
   below threshold AND not flagged? → alert + set flag
   above threshold AND flagged?     → clear flag
   units_sold >= hard_cap?          → mark sold out
                                    → log movement

1. Read the stock Sheet

A Schedule trigger fires on your cadence (hourly for fast movers, daily for slow). The Google Sheets node reads the stock tab: SKU, on_hand, reorder_threshold, reorder_flagged, units_sold, hard_cap.

2. Flag low stock with dedupe

For each row, an IF node checks two conditions together: stock is below threshold AND the item isn't already flagged. Only then does it alert. After alerting, write reorder_flagged = true back to the Sheet. This is the dedupe the bigger templates skip.

3. Clear the flag on restock

When on_hand climbs back above the threshold, clear the flag so the next dip alerts again. Without this reset, you alert once and then go permanently quiet, which is the opposite failure.

4. Enforce the hard cap

For limited runs, compare units_sold against hard_cap. At or over the cap, route new orders to a sold-out path instead of fulfilling. This is the pattern lifetime-deal sellers live on, and it's why this build pairs naturally with launch automation.

5. Log the movement

Append each change to a movements tab. That's your trend view without a BI tool: a timestamped row per stock change you can chart later if you want.

Implementation patterns

Pattern: flag-based dedupe. State lives in the Sheet, not in n8n. The reorder_flagged column is the memory between runs. Set on alert, clear on restock. Simple and durable.

IF on_hand < reorder_threshold AND reorder_flagged == false
THEN alert(); set reorder_flagged = true
IF on_hand >= reorder_threshold AND reorder_flagged == true
THEN set reorder_flagged = false

Pattern: hard cap before fulfillment. On the order side, check units_sold >= hard_cap before dispatching. Over the cap routes to sold-out. This keeps a limited run actually limited even under a burst of simultaneous orders.

n8n nodes you'll use most

Getting started

1. Build a stock Sheet with SKU, on_hand, reorder_threshold, reorder_flagged, units_sold, hard_cap.
2. Add a Schedule trigger at a cadence your catalog size can handle in one run.
3. Read the Sheet and loop rows through the IF dedupe logic.
4. Wire the alert send and the flag write-back.
5. Add the restock reset so flags clear when stock recovers.
6. Add the hard-cap check on the order path for limited runs.
7. Test by dropping a SKU below threshold, confirming one alert, then confirming the next run stays quiet.

For limited runs and lifetime deals specifically, the LTD Launch & Fulfillment Automator already wires hard-cap enforcement against a Google Sheets sales log.

Inventory feeds the rest of the store. When stock is low, the order fulfillment automation needs to route around it; when a launch sells out, the abandoned cart recovery sequence shouldn't keep nudging carts for sold-out items. The LTD Launch & Fulfillment Automator ties the cap to the sales log so those decisions stay accurate.